-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[Bug] Creating windows node group actually creates linux nodes #7645
Description
I've been trying to create Windows EKS clusters and every time I try it I actually get Linux nodes instead. I tried with this command to add them to an existing cluster: eksctl create nodegroup --cluster=apama-windows --node-ami-family=WindowsServer2022CoreContainer --node-volume-size=200 --instance-selector-vcpus=16 --instance-selector-cpu-architecture x86_64 --spot
We tried creating a complete cluster including nodes with:
---
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
name: apama-windows
region: eu-north-1
managedNodeGroups:
- name: linux-ng
instanceSelector:
vCPUs: 2
minSize: 1
maxSize: 2
spot: true
- name: windows-managed-ng
amiFamily: WindowsServer2022CoreContainer
instanceSelector:
vCPUs: 16
minSize: 1
maxSize: 3
volumeSize: 200
spot: true
It complained that we would need to run eksctl utils install-vpc-controllers --name=apama-windows --region=eu-north-1 --approve, but created linux nodes so it wouldn't matter.
I tried creating linux nodes only, then running that command, then adding windows nodes. That command failed with Error: error installing VPC controller: creating CertificateSigningRequest: constructing REST client mapping for certificates.k8s.io/v1beta1, Kind=CertificateSigningRequest: no matches for kind "CertificateSigningRequest" in versions ["certificates.k8s.io/" "certificates.k8s.io/v1beta1"], but I ensured we had running VPC controllers, then tried to add nodes, then still got linux nodes.
I tried with 2022Core, 2019Core and 2022Full.
What's going on?