Smaine Kahlouch

I'll have a look if I can contribute for the TLS support

I got exactly the same issue, any updates please?

Hi @shellwhale , thank you for your answer but I managed to do what I want with openssl [here](https://github.com/Smana/demo-cloud-native-ref/tree/main/terraform/vault#%F0%9F%94%91-public-key-infrastructure-pki-requirements)

Yes thank you @sayboras . I'm working on figure out how AL2023 isn't working properly too. But indeed, this is not related and I'll open an issue if necessary.

Hi @caleb-devops , thanks for the tip but when I put this configuration prior to cilium install the coredns addon doesn't start. (Obviously because no CNI are found).

Thx @caleb-devops , Actually I already have a [toleration](https://github.com/Smana/demo-cloud-native-ref/blob/main/terraform/eks/main.tf#L15). However the cilium install only starts after the EKS module deployment is finished (**including** CoreDNS which is an EKS addon).

Are there any update on this issue? We currently need to specify a constraint for using nvme instance types. And prepare the RAID0 array. ```yaml - key: karpenter.k8s.aws/instance-local-nvme operator: Gt...

I got the same behavior, my repository is [here](https://github.com/Smana/demo-cloud-native-ref/tree/main/terraform/eks). I'm gonna roll back this [PR](https://github.com/Smana/demo-cloud-native-ref/pull/151) because cilium isn't starting with the error ```console failed to start: daemon creation failed: error...

I don't know what I'm missing but it isn't working on my side:   Any help is welcome :)

@mikestef9 could you please tell us where we can track this issue (eks pod identity) please? thanks