Hi @joshua-burns - so far no luck on my end, I’m unable to get it into a failed state, here I’m using the following yaml file for helm :
$ cat x.yaml
And I’m not seeing any issues with startup or related to the tls-init issue you mentioned.
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
kyle-consul-connect-injector-webhook-deployment-6886d5898dm6hl9 1/1 Running 0 2m37s
kyle-consul-mesh-gateway-94f997ff9-jzlnj 2/2 Running 0 2m37s
kyle-consul-mkpjz 1/1 Running 0 2m37s
kyle-consul-server-0 1/1 Running 0 2m37s
This was a fresh EKS cluster that I provisioned just now using the example from EKS’s docs.
eksctl create cluster \
--name kyle-eks-test \
--version 1.16 \
--region us-east-2 \
--nodegroup-name linux-nodes \
--node-type t3.medium \
--nodes 1 \
--nodes-min 1 \
--nodes-max 3 \
The only thing I see is a brief crash from mesh-gateway as it starts up, but this clears once the consul-server is online a second or two later and everything comes online cleanly.
EDIT: I should say that I cleaned it up using the commands I provided earlier and reinstalled and that also worked.