kubernetes/kops

[al2023][amazon-vpc-cni] Additional configuration required

dims opened this issue · 1 comments

dims commented

/kind feature

We have 2 CI jobs that are failing:

I don't believe, we currently do what is being done in the amazon EKS AMI currently in kops based installation, namely:
https://github.com/awslabs/amazon-eks-ami/blob/976fe67e4c359737be71d892a8f55015cc1475f5/scripts/install-worker.sh#L86-L105

Items:

  • install additional package iptables-nft
  • create an empty /etc/udev/rules.d/99-vpc-policy-routes.rules
  • disable ManageForeignRoutes and ManageForeignRoutingPolicyRules (with a new config file under /usr/lib/systemd/networkd.conf.d)
  • set MACAddressPolicy=none in /usr/lib/systemd/network/99-default.link

Note the last one had a fix for ubuntu ONLY in https://github.com/kubernetes/kops/pull/16313/files so we would have to add al2023 in addition.

k8s-triage-robot commented

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