Container Cluster not ready when trying to create a new nodepool #5529
Description
Describe your question
When attempting to create a ContainerNodePool resource via Config Connector (KCC), the reconciliation fails with the following message:
reference ContainerCluster gcp-gke/apps-dct is not ready
reason: DependencyNotReady
At the same time, the associated GKE cluster shows:
STATUS: RECONCILING
gcloud container operations describe operation-1761675306166 --region=us-central1
operationType: UPDATE_CLUSTER
status: RUNNING
targetLink: https://container.googleapis.com/v1/projects/.../clusters/apps-dct
we are doing this through argocd sync
NOTES:
when we are doing normally we will sync the new nodepool and it will be provisioned automatically
but with this error the container clusters is in outofsync state
and the nodepool says dependency not ready
ISSUE2:
we see a drift between the live manifest and desired manifest in the container cluster and nodepools sometimes and we have to make the change in Container cluster code in order to sync with live manifest
we also don't why this drift happens what should I do for this .It happens after creating a new nodepools the labels will say expected this value got this value but we wont even touched that label
please shoot your questions need some help with config connector (GKE) willing to learn share some documents if possible the official troubleshooting doesn't cover the fix