You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 25, 2020. It is now read-only.
Creating the an AzureSample and WordpressInstance results in the following error:
status:
conditions:
- lastTransitionTime: '2020-05-07T20:32:42Z'
reason: Resource is being created
status: 'False'
type: Ready
- lastTransitionTime: '2020-05-07T20:32:54Z'
message: >-
create failed: cannot create AKSCluster:
containerservice.ManagedClustersClient#CreateOrUpdate: Failure sending
request: StatusCode=400 -- Original Error: Code="InvalidParameter"
Message="The length of the node resource group name is too long. The
maximum length is 80 and the length of the value provided is 85. Please
see https://aka.ms/aks-naming-rules for more details." Target="name"
reason: Encountered an error during resource reconciliation
status: 'False'
type: Synced
I think we're going to land on a solution for all in crossplane-contrib/provider-gcp#222 . However, note that this is different than crossplane-contrib/provider-gcp#222 . We can't set the max length to be compatible with just AKSCluster; if Azure allows ResourceGroup to be created with a longer name than AKSCluster accepts, then we allow it, too. So, we'll decrease the likelihood and probably make our name generator more robust but the validation we'll aim will be the ResourceGroup's name validation, not AKSCluster's resource group name field validation.
If we can't decide on something, then it could make sense to go with the approach that we took in app-wordpress for the release. Though I don't think we'll have to.
Problem
Creating the an AzureSample and WordpressInstance results in the following error:
Using:
WordpressInstance CR
AzureSample CR
AKSCluster
ResourceGroup
Related
The text was updated successfully, but these errors were encountered: