Config connector does not allow to add taint on containerNodepool

[nnbu]

Checklist

• I did not find a related open issue.
• I did not find a solution in the troubleshooting guide: (https://cloud.google.com/config-connector/docs/troubleshooting)
• If this issue is time-sensitive, I have submitted a corresponding issue with GCP support.

Bug Description

Steps

1. create containerNodepool on gke cluster. Allow config-connector to create the nodepool in gcp
2. Add a taint to containerNodepool CR on GKE

This fails with error similar to

 message: 'Update call failed: cannot make changes to immutable field(s): [Field
      Name: nodeConfig.0.Taint.1.Effect, Got: NO_SCHEDULE, Wanted:  Field Name: nodeConfig.0.Taint.1.Value,
      Got: false, Wanted:  Field Name: nodeConfig.0.Taint.#, Got: 2, Wanted: 1 Field
      Name: nodeConfig.0.Taint.1.Key, Got: schedulepods1, Wanted: ]; please refer
      to our troubleshooting doc: https://cloud.google.com/config-connector/docs/troubleshooting'

Adding a taint to nodepool using gcloud command is allowed. So, this is not immutable field from gcp's pov. It looks to be the bug in config-connector.

Additional Diagnostic Information

While searching, I saw this comment. That suggests this to be a known limitation. But the comment is very old. I am not sure if there is a plan to address the issue about adding a taint to containerNodepool.

Kubernetes Cluster Version

1.30

Config Connector Version

1.121.0

Config Connector Mode

namespaced mode (default)

Log Output

No response

Steps to reproduce the issue

Mentioend above

YAML snippets

[nnbu]

oh well.. this seems to have been fixed recently in 1.125
#2485