Document using CCM and multi-zone clusters

[salasberryfin]

/kind documentation

Description

The default configuration when installing GCP Cloud Provider is not compatible with multi-zone clusters, unless failureDomains are explicitly set. This can cause intermittent errors depending on where nodes are deployed.

This can be configured via cloud.config by passing the required flags, whether it is multi-zone, regional, etc. Let's document this in the book so users are aware of this when provisioning self-managed clusters, as Kubernetes >=v1.32 requires using CCM.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[salasberryfin]

/remove-lifecycle-stale