You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned during the discussion on #285, it is now possible to change the Monitoring Service for a Container Cluster without recreating it. This means the monitoring_service field on google_container_cluster resources should no longer be ForceNew: true, but should instead have a section in the update function, which either uses projects.zones.clusters.monitoring or projects.zones.clusters.update with desiredMonitoringService field to change the value.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Mar 30, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
Affected Resource(s)
Please list the resources as a list, for example:
As mentioned during the discussion on #285, it is now possible to change the Monitoring Service for a Container Cluster without recreating it. This means the monitoring_service field on google_container_cluster resources should no longer be ForceNew: true, but should instead have a section in the update function, which either uses projects.zones.clusters.monitoring or projects.zones.clusters.update with desiredMonitoringService field to change the value.
The text was updated successfully, but these errors were encountered: