Closed vkaylee closed 1 year ago
There isn't anything related to self-managed nodegroups that would restrict IPv6 usage - however, you do need to specify the correct bootstrap arguments for IPv6 https://github.com/awslabs/amazon-eks-ami/blob/e99201099a3c4752af465c03bd5dedda0a729ca8/files/bootstrap.sh#L33C14-L33C20
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Description
Hello guys, I have found the issue with features:
IPv6
andself_managed_node_groups
After provisioning the ipv6 cluster with a self-managed node group, the taint appearednode.cloudprovider.kubernetes.io/uninitialized=true:NoSchedule
with node status:Ready
Everything has been checked, it has some differences:
--// Content-Type: text/x-shellscript; charset="us-ascii"
!/bin/bash
set -ex B64_CLUSTER_CA=
API_SERVER_URL=https://.gr7.ap-southeast-1.eks.amazonaws.com
K8S_CLUSTER_DNS_IP=fd33:75f9:08f7::a
/etc/eks/bootstrap.sh eks-nA5EE1ws --kubelet-extra-args '--node-labels=eks.amazonaws.com/sourceLaunchTemplateVersion=1,eks.amazonaws.com/nodegroup-image=ami-0ef7bbe64818b655d,eks.amazonaws.com/capacityType=SPOT,eks.amazonaws.com/nodegroup=eks--green-...,eks.amazonaws.com/sourceLaunchTemplateId=lt- --max-pods=98' --b64-cluster-ca $B64_CLUSTER_CA --apiserver-endpoint $API_SERVER_URL --dns-cluster-ip $K8S_CLUSTER_DNS_IP --ip-family ipv6 --service-ipv6-cidr fd33:75f9:08f7::/108 --use-max-pods false
--//--
Steps to reproduce the behavior:
kubectl describe node <node name>
Expected behavior
Self-managed node group has:
Taints: <none>
Actual behavior
Self-managed node group has:
Taints: node.cloudprovider.kubernetes.io/uninitialized=true:NoSchedule
Terminal Output Screenshot(s)
Additional context