k8s-config-connector: Upgrading from v1.12.1 to v1.14.0 makes all GKE cluster and nodepools update fail

Describe the bug All GKE clusters:

message: 'Update call failed: error validating configuration: "ip_allocation_policy":
      conflicts with cluster_ipv4_cidr'
reason: UpdateFailed
status: "False"

All GKE nodepools:

message: 'Update call failed: error fetching live state: error importing resource:
      Import id "<REDACTED_project-id>/us-central1-a//<REDACTED_clustername>" doesn''t match any of the accepted
      formats: [projects/(?P<project>[^/]+)/zones/(?P<location>[^/]+)/clusters/(?P<cluster>[^/]+)/nodePools/(?P<name>[^/]+)
      projects/(?P<project>[^/]+)/locations/(?P<location>[^/]+)/clusters/(?P<cluster>[^/]+)/nodePools/(?P<name>[^/]+)
      (?P<project>[^/]+)/(?P<location>[^/]+)/(?P<cluster>[^/]+)/(?P<name>[^/]+) (?P<location>[^/]+)/(?P<cluster>[^/]+)/(?P<name>[^/]+)]'
reason: UpdateFailed
status: "False"

ConfigConnector Version When going from v1.12.1 to v1.14.0

To Reproduce Follow the manual upgrade instructions for the Workload Identity installation.

YAML snippets: N/A

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 21 (10 by maintainers)

Links to this issue

Config Connector release notes | Config Connector Documentation | Google Cloud

Most upvoted comments

Thanks for the heads-up on 3-weeks schedule, I think that works for us.

The manual install is what we’ve been using for many months now, fairly smoothly. I’ve decided to test the new add-on, which is why I was wondering if it could be upgraded. The last “stable” version that worked for us smoothly was 1.14.0.

dinvlad on Aug 13, 2020

Oh and if you’re ok with it, I’ll be closing the issue now since the original problem has been fixed, but please feel free to reopen if you have any further issues!

jcanseco on Jul 16, 2020

Gotcha, I’m very glad to hear that the issue is not breaking. I’m sorry for the trouble.

The fix will be part of the next release which will come out by the end of the week.

jcanseco on Jul 16, 2020

Though to clarify, the incoming fix will fix the validation issue with ContainerCluster.

The ContainerNodePool error you shared is due to the referenced ContainerCluster failing, so once the ContainerCluster stops failing to update, the ContainerNodePool should also be able to reach an UpToDate state.

That said, the ContainerNodePool should not be outputting that error due to the referenced ContainerCluster failing. This too is a known issue, but a separate one that will be fixed later.

jcanseco on Jul 15, 2020