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 }}
Repository navigation
Container Cluster stuck in non-ready state because channel update rejected #194
Describe the bug
A clear and concise description of what the bug is.
ConfigConnector Version
Run the following command to get the current ConfigConnector version
kubectl get ns cnrm-system -o jsonpath='{.metadata.annotations.cnrm\.cloud\.google\.com/version}'
cnrm.cloud.google.com/version: 1.9.1
To Reproduce Steps to reproduce the behavior:
Create a ContainerCluster CNRM resource setting the release channel for the cluster to get
the status
Apply the resource to create the cluster
Reapply the resource
Container cluster reports
- lastTransitionTime: "2020-05-29T00:15:38Z"
message: 'Update call failed: the desired mutation for the following field(s)
is invalid: [releaseChannel.0.Channel]'
reason: UpdateFailed
status: "False"
type: Ready
Curiously, the underlying API accepts the lowercase form as well, but further GET requests return the uppercase form, which we currently don't suppress a diff for. If you create your cluster with channel: STABLE instead, you should see this issue go away.
Activity
kibbles-n-bytes commentedon Jun 3, 2020
Hey @jlewi , the underlying API's canonical form for the release channel is all uppercase: https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1beta1/projects.locations.clusters#channel
Curiously, the underlying API accepts the lowercase form as well, but further GET requests return the uppercase form, which we currently don't suppress a diff for. If you create your cluster with
channel: STABLEinstead, you should see this issue go away.jlewi commentedon Jun 3, 2020
Thanks that's super helpful I will fix that on our end.
Feel free to close this issue unless you want to leave open to continue to track handling the diff more gracefully.
Fix a bunch issues with GCP blueprints for private gke. (#1230)