You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating an IPv6 enabled cluster with EKS AutoMode results in incorrect validation errors for missing core addons. With EKS Auto Mode, core addons are not mandatory. We should relax this validation when EKS Auto Mode is enabled.
What happened?
Error: the default core addons must be defined for IPv6; missing addon(s): vpc-cni, coredns, kube-proxy
How to reproduce it?
➜ ~ eksctl create cluster -f eksctl.yaml
Error: the default core addons must be defined for IPv6; missing addon(s): vpc-cni, coredns, kube-proxy
➜ ~
➜ ~ cat eksctl.yaml
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
name: eks-auto-ipv6
region: us-west-2
kubernetesNetworkConfig:
ipFamily: IPv6
autoModeConfig:
enabled: true
Logs
Anything else we need to know?
N/A
Versions
$ eksctl info
eksctl version: 0.197.0-dev+e96028b65.2024-12-03T11:01:49Z
kubectl version: v1.31.1
OS: darwin
The text was updated successfully, but these errors were encountered:
Hello saurav-agarwalla 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website
saurav-agarwalla
changed the title
[Bug] IPv6 with AutoMode incorrect returns error when core addons are not specified
[Bug] IPv6 with AutoMode incorrectly returns error when core addons are not specified
Dec 6, 2024
What were you trying to accomplish?
Creating an IPv6 enabled cluster with EKS AutoMode results in incorrect validation errors for missing core addons. With EKS Auto Mode, core addons are not mandatory. We should relax this validation when EKS Auto Mode is enabled.
What happened?
Error: the default core addons must be defined for IPv6; missing addon(s): vpc-cni, coredns, kube-proxy
How to reproduce it?
Logs
Anything else we need to know?
N/A
Versions
The text was updated successfully, but these errors were encountered: