FYI - <https://github.com/pulumi/eks/issues/18> I...
# general
e
FYI - https://github.com/pulumi/eks/issues/18 I've only started seeing this recently. Wasn't a problem last week, AFAIK. I can share the entire contents of the system logs if needed
m
Thanks! I can't repro this myself with a stock cluster--I'll try digging in to see if I can figure out what's happening here.
e
Can you try using the code I put in the issue including the userdata and create a cluster? I have not been able to successfully create a cluster using that code. I'm starting to suspect it's the implementation of how the userdata is added. It looks like the userdata input is maybe not added correctly in the launch config
Here's the userdata in my current launch config when I run the code I pasted in the issue:
Copy code
#!/bin/bash

/etc/eks/bootstrap.sh --apiserver-endpoint "<https://087AD5872217F6B7067C3537D15225C2.yl4.us-west-2.eks.amazonaws.com>" --b64-cluster-ca "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUN5RENDQWJDZ0F3SUJBZ0lCQURBTkJna3Foa2lHOXcwQkFRc0ZBREFWTVJNd0VRWURWUVFERXdwcmRXSmwKY201bGRHVnpNQjRYRFRFNE1URXdOekU1TVRneU9Gb1hEVEk0TVRFd05ERTVNVGd5T0Zvd0ZURVRNQkVHQTFVRQpBeE1LYTNWaVpYSnVaWFJsY3pDQ0FTSXdEUVlKS29aSWh2Y05BUUVCQlFBRGdnRVBBRENDQVFvQ2dnRUJBTWZWCnNVUDNCaER2SlBqZE1ESXZUQU52d2Zxc0dOeWZnV2NRZTBqMDR1TEJzYlhZa0xnWG1jbDgzaDM0OUZuVlJVMzcKVDdLWjZSU1A0S29jYzRaaklZbVkwbU9aZHlDUWR6czg1L1Z4UmdncDVpd3JoYWJiSHRpV3p6dTB6OXhKQlpvdwp1RTViVkQvLzhtMDhvSlNFQWxFSDNQSHNJSnhrTzI4S0RTUi8wc0NyZHdMTmZ1ckVhRHpBeHduQjJPZklCejNWClhBWXlFc2pheEhtaUt3RUhaSUVXQjlwcUtQY05wT1pCMFRhZXlON1Z4TEVJaFRtb3ZrWHlxM2dSdVdaZjRWUEoKY3ZaMS92L3ZZTG1qcmRLZkU3dHArM2E0OE41K0NDNyt1ZUx2NDUraDJpMlpDMlFQK0s4VGF1M0R5V1FUcmljbQpxLzArRkVMTENxUDlTcXd1c2s4Q0F3RUFBYU1qTUNFd0RnWURWUjBQQVFIL0JBUURBZ0trTUE4R0ExVWRFd0VCCi93UUZNQU1CQWY4d0RRWUpLb1pJaHZjTkFRRUxCUUFEZ2dFQkFDYzJwaDMwc0ZBVmZwS1BaUkYrZFNhYmEwNEgKQnhiWTZVRENNc3JzUzZBQkJqS21LcmE5NmFRUjJ0THlmWTZUeVJWU2pjczExRk9DNkNheDVaVFphQXVqWTZKNwpSL2puWGo3TTg3eFp5cWdxT09XQUQ3eFR5cVpiUEpaak1GeUVVUnhUbko1Vkg3bFpKOVByTTVrcXdwYS9HNnQ1CkJXU3I3d2swT216cE1WY1Qvb1p3QXlSMmFubzhoNy90cnYyN2FTZTlvR214azBxQ3UzQzhnRkZDa05CZDZBZ2kKdkhlajdpMUplY1BPVEdWMThmSlpzME1wcit3b1h1NlRBeXAzbGwwMXAyMnhLejBtVWw5cHZKQXhBQ2doa1FqdgplVU4zSzlFNnNYaHZFcWFTbEh5MUZoUkZzTGJKWDV4ejNYMWswVjA2blNWSXpOZ01RYnkyWFdmRStqaz0KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=" "online-vnext-10az-eks-cluster-eksCluster-1d9f5fd"
cat >/opt/user-data <<online-vnext-10az-eks-cluster-5cdd4608-user-data
set -o xtrace
echo "Starting UserData for the EKS worker nodes"
yum install -y   jq   cifs-utils   nfs-utils   nfs4-acl-tools   portmap   screen   vim   bind-utils   coreutils   util-linux
VOLUME_PLUGIN_DIR="/usr/libexec/kubernetes/kubelet-plugins/volume/exec"
mkdir -p "$VOLUME_PLUGIN_DIR/fstab~cifs"
cd "$VOLUME_PLUGIN_DIR/fstab~cifs"
curl -L -O <https://raw.githubusercontent.com/fstab/cifs/master/cifs>
chmod 755 cifs
online-vnext-10az-eks-cluster-5cdd4608-user-data
chmod +x /opt/user-data
/opt/user-data

/opt/aws/bin/cfn-signal --exit-code $? --stack online-vnext-10az-eks-cluster-5cdd4608 --resource NodeGroup --region us-west-2
@microscopic-florist-22719 I just tried a stock cluster with 5 worker nodes. EC2 shows the instances are all InServer, but they fail to join the EKS cluster: Here's the system log from one of the instances
weird... slack isn't letting me create snippets...
m
I'm not sure if snippets work in a thread 😕
Can you try adding a bash interpreter directive to your userdata?
i.e.
#!/bin/bash