AWS EKS External vault issuer with kubernetes auth

Hello everyone,

Currently I am kinda stuck with this problem.

Here is a quick introduction.

I have 1 AWS EKS where vault is stored, everything works fine, I have the UI exposed HTTPS, API works, all cool.

Now I need to connect another external AWS EKS cluster to be able to get access to the secrets from the vault from which I would like to use via the CSI Secrets store.

Here comes the part where I got stuck.

I made a service account same as described in the tutorials.

Multiple clusters will need to access the vault cluster.

EDITED

UPDATE:

I was able to setup the kubernetes auth with the vault cluster, with a service account, which including the AWS EKS cluster issue.

Currently trying to add another kubernetes auth with another path, but I get “permission denied” error.

UPDATE:

Everything is working now.

@asonnleitner
What Steps do I need to follow to get this working?

I need to connect a Cluster that is running Vault with other EKS Clusters. (The same thing that you struggled with)

Kubernetes Auth is done for all the other EKS Clusters? Like enable kubernetes and enable Auth for each of the Kubernetes Host?

Add it in a different Kube Auth Path, each one from the “other” EKS Clusters?

What do I do?