-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Labels
bugSomething isn't workingSomething isn't workingneeds-epic-linkNeeds a link to an epicNeeds a link to an epicneeds-points-labelNeeds a story point labelNeeds a story point labelneeds-projectNeeds a projectNeeds a project
Description
What happened?
Encountered via higher level upbound/platform-ref-gcp#91 platform ref testing
I was debugging the issue with clean deletion and noticed that NUM_NODES of provisioned GKE is not matching the spec
$ gcloud container clusters list --region=us-west2 --project=official-provider-testing
NAME LOCATION MASTER_VERSION MASTER_IP MACHINE_TYPE NODE_VERSION NUM_NODES STATUS
platform-ref-gcp-bngsf-6wqpt us-west2 1.29.1-gke.1589018 34.94.11.113 e2-medium 1.29.1-gke.1589018 3 PROVISIONING
$ gcloud container clusters list --region=us-west2 --project=official-provider-testing
NAME LOCATION MASTER_VERSION MASTER_IP MACHINE_TYPE NODE_VERSION NUM_NODES STATUS
platform-ref-gcp-bngsf-6wqpt us-west2 1.29.1-gke.1589018 34.94.11.113 e2-medium 1.29.1-gke.1589018 6 RUNNING
In addition, it also dynamically growing, apparently by some condition on the cloud provider side.
MACHINE_TYPE is also something to double check
How can we reproduce it?
Provision this configuration or platform-ref-gcp, run gcloud commands above
What environment did it happen in?
UXP 1.15.1-up.1
xpkg.upbound.io/crossplane-contrib/function-patch-and-transform:v0.4.0
xpkg.upbound.io/upbound/provider-gcp-container:v1.0.1
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingneeds-epic-linkNeeds a link to an epicNeeds a link to an epicneeds-points-labelNeeds a story point labelNeeds a story point labelneeds-projectNeeds a projectNeeds a project