I’m using Google Cloud Kubernetes Config Connector (KCC) to manage SQL instances (create/update/delete), and I’m currently working on upgrading existing SQL instances from the Enterprise edition to the Enterprise Plus edition.
While this upgrade is straightforward using the Google Cloud Console, I encounter an error when attempting it through KCC:
Edition Upgrade is accompanied with changes in fields that are not allowed to change with Edition., invalid
I understand that certain fields cannot be modified during the edition upgrade, but the documentation on this is unclear, and I’m not sure which fields specifically are causing the issue.
Update call failed: error applying desired state: summary: Error, failed to update instance settings for : googleapi: Error 400: Invalid request: Edition Upgrade is accompanied with changes in fields that are not allowed to change with Edition., invalid
Has anyone faced this problem or know what fields need to be handled differently during the edition upgrade with KCC?
There is no clear documentation in google to get those information.
Please let me know if you need more information.
Thanks.
Seems like there is an issue with KCC not being able to upgrade the SQL instances from Enterprise edition to Enterprise plus edition.
It might be because KCC is not able to update the YAML configuration to the Enterprise plus edition state. You can try changing the values of the Edition field to ENTERPRISE_PLUS in your case and apply the YAML configurations manually as a workaround.
In order to export the YAML configuration of the SQL instance you can use the tutorial document to set up the config-connector export tool.
After installation use this command $ gcloud sql instances describe [instance_name] | grep "selfLink" and copy the URI from the output of the command to export. After that, retry the edition field change modification to ENTERPRISE_PLUS and apply the YAML configurations.
Refer to this Github link for more information
Note: It is just a workaround that is not reliable and not sure if it works, so make sure your configurations are correct before applying the YAML changes.
Otherwise you can raise a GCP issue. If you have paid support try create an issue or You can create a new public Issue Tracker thread describing your issue.
1