-
Notifications
You must be signed in to change notification settings - Fork 959
Open
Description
Our Prow build clusters don't support IPv6, and IPv6 has been GA in Kubernetes for several years:
The GKE cluster running the prow control plane has IPv6 enabled already.
Clusters in scope:
k8s-infra-prow-build
k8s-infra-prow-build-trusted
eks-prow-build-cluster
k8s-infra-aks-admin (This cluster never worked)
Runbook:
- Fix all the following outstanding issues:
- Provision new Infrastructure
- New dual-stack VPCs for gke prow build clusters
- Modify the existing AWS VPC to support IPv6
- Deploy new GKE clusters like this: https://github.com/kubernetes/k8s.io/blob/main/infra/gcp/terraform/k8s-infra-prow/gke.tf
- Delete the old clusters
- Deploy the new clusters
- Post cluster provisioning
- Update the endpoints of the clusters in ArgoCD, https://github.com/kubernetes/k8s.io/blob/main/kubernetes/gke-utility/argocd/clusters.yaml
- Update the endpoints of the clusters in Prow by modifying the kubeconfig secrets in GCP Secret Manager
We expect this operation to take 3 hours and ideally be executed on the weekend before the start of v1.36 release cycle.
Metadata
Metadata
Assignees
Labels
No labels