Set MACAddressPolicy=none for AWS VPC CNI on AL2023#17933
Set MACAddressPolicy=none for AWS VPC CNI on AL2023#17933k8s-ci-robot merged 1 commit intokubernetes:masterfrom
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@rifelpet: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/retest |
This configuration has been failing cluster validation:
https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/e2e-kops-grid-amazonvpc-al2023-k35/2019554270835118080
non-hostnetwork pods are losing their ability to reach the k8s api service ip:
https://storage.googleapis.com/kubernetes-ci-logs/logs/e2e-kops-grid-amazonvpc-al2023-k35/2019554270835118080/artifacts/cluster-info/kube-system/ebs-csi-node-k4d9w/ebs-plugin.previous.log
after they initially succeed. This is because systemd-networkd is overwriting the VPC CNI's routes. More context here. We originally had this file set for AL2023 but I removed it in #17867 thinking it wasn't needed. After some local testing I confirmed that both are needed.