https://pulumi.com logo
Powered by
c

calm-quill-21760

07/27/2021, 6:20 PM
Hi all! I’m building an EKS cluster and wanted to confirm whether this expected behavior. Basically, when I supply the minimum config, the EKS cluster builds and the nodes show up. When I specify the AMI, the nodes get built but they do not get attached to the cluster.
Copy code
cluster = eks.Cluster(
    cluster_name,
    name=cluster_name,
# Omitting the node_ami_id succeeds. Adding it in causes nodes to build but not be attached.
    node_ami_id="ami-092263943bcda23f5",
    node_root_volume_size=50,
    desired_capacity=2,
    min_size=1,
    max_size=2,
    encrypt_root_block_device=True,
    vpc_id=myVpc.id,
    cluster_security_group=my_security_group,
    endpoint_public_access=True,
    endpoint_private_access=True,
    public_subnet_ids=public_subnet_ids,
    create_oidc_provider=True,
)
This is version 3.8.0, BTW and the AMI is AWS’ Windows for EKS image.
b

billowy-army-68599

07/27/2021, 6:48 PM
does your AMI have any user data to make it join the cluster correctly?
c

calm-quill-21760

07/27/2021, 6:52 PM
Yes, it has user data. I assume it’s coming from the CFT that Pulumi uses/invokes. It shows the cluster name in the user data.
Now that I’m looking at it, though, it’s a bash script. This is a Windows AMI. I don’t see that working.
b

billowy-army-68599

07/27/2021, 6:55 PM
yeah, you'll need to specify your own user data I suspect
c

calm-quill-21760

07/27/2021, 6:56 PM
From where is this user script originating, I wonder? Is this something that needs to be fixed in Pulumi? Or is this coming from AWS?
Powered by