GCP-428: set HighlyAvailable controllerAvailabilityPolicy for GKE Autopilot#56
Merged
jimdaga merged 1 commit intoapahim:mainfrom Mar 12, 2026
Merged
GCP-428: set HighlyAvailable controllerAvailabilityPolicy for GKE Autopilot#56jimdaga merged 1 commit intoapahim:mainfrom
jimdaga merged 1 commit intoapahim:mainfrom
Conversation
…ilot Switch controllerAvailabilityPolicy to HighlyAvailable and set CPO image to quay.io/cveiga/hypershift:latest for dev testing. CPU request enforcement for GKE Autopilot minimum (500m) is handled by MutatingAdmissionPolicy on the management cluster, so no resourceRequestOverrides are needed. Signed-off-by: Jim DAgostino <jdagosti@redhat.com> Commit-Message-Assisted-by: Claude (via Claude Code)
Collaborator
Author
|
Supporting change that fixes HA mode on GKE AutoPilot: #56 Confirmed to be working: |
jimdaga
changed the title
patjlm
approved these changes
Mar 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
controllerAvailabilityPolicydefault fromSingleReplicatoHighlyAvailableContext
GKE Autopilot requires
HighlyAvailabletopology for proper pod scheduling. The previousSingleReplicadefault caused issues with pod placement on Autopilot clusters.CPU request enforcement (minimum 500m for pods with anti-affinity) is handled separately by a
MutatingAdmissionPolicyon the management cluster (gcp-hcp-infra#376), soresourceRequestOverridesannotations are no longer needed.Changes
deployments/helm-cls-hypershift-client/values.yaml—controllerAvailabilityPolicy: "HighlyAvailable"Test plan