smalltown/aws-irsa-example

Hi there 👋

• 👯 I’m looking to collaborate on SRE
• 🌱 I’m currently learning Python
• 🙎‍ I'm Taipei HashiCorp User Group Organizer
• 🙎‍ I'm AWS User Group Taiwan Staff
• 💬 Ask me about SRE/DevOps

aws-irsa-example's Issues

admissionregistration.k8s.io/v1beta1 deprecated + removed

kubernetes/kubernetes#82021

This breaks https://github.com/smalltown/aws-irsa-example/blob/master/pod-identity-webhook/mutatingwebhook.yaml

TLS handshake error

HI,

I am installing IRSA setup on my own self hosted k8s, so I checked your scripts for installation.
What I found is that you are also, like myself using self-signed cert for webook, and I see that you commented out

#kubectl certificate approve $(kubectl get csr --namespace=kube-system -o jsonpath='{.items[?(@.spec.username=="system:serviceaccount:default:pod-identity-webhook")].metadata.name}')

Setup seems fine, and it's working but I keep getting those errors in 'pod-identity-webhook' logs
2020/11/25 13:02:32 http: TLS handshake error from 10.221.136.81:32950: remote error: tls: bad certificate
2020/11/25 13:03:32 http: TLS handshake error from 10.221.136.81:40560: remote error: tls: bad certificate
2020/11/25 13:04:32 http: TLS handshake error from 10.221.136.81:41268: remote error: tls: bad certificate
2020/11/25 13:05:32 http: TLS handshake error from 10.221.136.81:41984: remote error: tls: bad certificate
2020/11/25 13:06:32 http: TLS handshake error from 10.221.136.81:42704: remote error: tls: bad certificate

It's strange as setup is working as expected, so I was wondering if you catch this also ?

Thank you,

Certificates and OIDC provider already installed

Hi,
following your tutorial, I noticed that my non-EKS Kubernetes cluster already has certificates and an OIDC-provider.
How do I need to adapt the procedure to use IRSA on this cluster?

Thanks