Skip to content

Commit e007613

Browse files
committed
fix: AWS CCM after upstream v1.29 change with temporary addresses
1 parent f52e646 commit e007613

File tree

6 files changed

+17
-0
lines changed

6 files changed

+17
-0
lines changed

charts/cluster-api-runtime-extensions-nutanix/templates/ccm/aws/manifests/aws-ccm-v1.27.1-configmap.yaml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -167,6 +167,7 @@ data:
167167
cpu: 200m
168168
securityContext: {}
169169
dnsPolicy: Default
170+
hostNetwork: true
170171
nodeSelector:
171172
node-role.kubernetes.io/control-plane: ""
172173
priorityClassName: system-node-critical

charts/cluster-api-runtime-extensions-nutanix/templates/ccm/aws/manifests/aws-ccm-v1.28.1-configmap.yaml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -167,6 +167,7 @@ data:
167167
cpu: 200m
168168
securityContext: {}
169169
dnsPolicy: Default
170+
hostNetwork: true
170171
nodeSelector:
171172
node-role.kubernetes.io/control-plane: ""
172173
priorityClassName: system-node-critical

charts/cluster-api-runtime-extensions-nutanix/templates/ccm/aws/manifests/aws-ccm-v1.29.2-configmap.yaml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -167,6 +167,7 @@ data:
167167
cpu: 200m
168168
securityContext: {}
169169
dnsPolicy: Default
170+
hostNetwork: true
170171
nodeSelector:
171172
node-role.kubernetes.io/control-plane: ""
172173
priorityClassName: system-node-critical
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# Copyright 2024 D2iQ, Inc. All rights reserved.
2+
# SPDX-License-Identifier: Apache-2.0
3+
4+
---
5+
# Starting in Kubernetes v1.29 the Kubelet no longer adds temporary addresses to the Node.
6+
# See https://github.com/kubernetes/kubernetes/pull/121028
7+
# This causes a deadlock with the AWS CCM and some CNI providers including Calico.
8+
# The Calico Pods won't start until some addresses are assigned,
9+
# but the AWS CCM that adds the addresses can't start until the Calico Pods are running.
10+
# Using hostNetworking allows the AWS CCM to start before the Calico Pods.
11+
# The upstream CAPA templates are also already using hostNetworking for the CCM Pods.
12+
hostNetworking: true

hack/addons/kustomize/aws-ccm/kustomization.yaml.tmpl

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ helmCharts:
1212
repo: https://kubernetes.github.io/cloud-provider-aws
1313
releaseName: aws-cloud-controller-manager
1414
version: ${AWS_CCM_CHART_VERSION}
15+
valuesFile: helm-values.yaml
1516
includeCRDs: true
1617
skipTests: true
1718

hack/addons/update-aws-ccm.sh

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@ trap_add "rm -rf ${ASSETS_DIR}" EXIT
2424

2525
readonly KUSTOMIZE_BASE_DIR="${SCRIPT_DIR}/kustomize/aws-ccm/"
2626
envsubst -no-unset <"${KUSTOMIZE_BASE_DIR}/kustomization.yaml.tmpl" >"${ASSETS_DIR}/kustomization.yaml"
27+
cp "${KUSTOMIZE_BASE_DIR}"/*.yaml "${ASSETS_DIR}"
2728

2829
readonly FILE_NAME="aws-ccm-${AWS_CCM_VERSION}.yaml"
2930
kustomize build --enable-helm "${ASSETS_DIR}" >"${ASSETS_DIR}/${FILE_NAME}"

0 commit comments

Comments
 (0)