2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
- Check the following link to verify the Windows AMI version compatible with EKS Cluster https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-windows-ami.html
- Double-check the aws-auth ConfigMap in your EKS cluster to ensure that it includes the correct roles for your Windows nodes. You can use the kubectl get configmap aws-auth -n kube-system -o yaml command to inspect the ConfigMap.
- Review the Amazon VPC CNI ConfigMap to ensure that it has the correct "enable-windows-ipam" setting. You can use the kubectl get configmap aws-node -n kube-system -o yaml command to inspect the ConfigMap
0
Please see the documentation provided here https://docs.aws.amazon.com/eks/latest/userguide/launch-windows-workers.html for launching self-managed Windows nodegroups. Note - you will need some Linux based nodes for core addons such as CoreDNS which are required for the cluster
beantwortet vor einem Jahr
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 7 Monaten- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
thanks for the advice, I checked the AMI is as expected and verified the two config maps, everything is in place yet the nodes don't join the cluster. I verified security group and rules and restarted the instances, nothing helps.