Issue Encountered with Vault Kubernetes Authentication Configuration

[kitokid1313]

Issue Summary:
I am facing an issue related to HashiCorp Vault's Kubernetes authentication configuration. While attempting to set up Kubernetes authentication for Vault, I encountered an error that prevents successful authentication and login. The error message indicates a problem with creating a Vault client using Kubernetes authentication.

I used this example to deploy the vault https://github.com/bank-vaults/vault-operator/blob/main/deploy/examples/cr-aws.yaml and I'm using s3 as a backend

Error Message:

{"level":"error","ts":1692802852.8984349,"msg":"could not create vault client","error":"unable to log in with Kubernetes auth: unable to log in to auth method: unable to log in with Kubernetes auth: Error making API request.\n\nURL: PUT http://vault.vault.svc.cluster.local:8200/v1/auth/kubernetes/login\nCode: 500. Errors:\n\n* could not load backend configuration"}

Logs and Timestamp:

vault 2023-08-23T15:43:41.208Z [TRACE] auth.kubernetes.auth_kubernetes_40614b77: Skipping TLSConfig update, no configuration set
vault 2023-08-23T15:43:56.030Z [INFO]  core: mount tuning of options: path=cnaas/ options=map[version:2]
vault 2023-08-23T15:43:56.109Z [INFO]  core: mount tuning of options: path=internal/ options=map[version:2]

Additional Information:

• HashiCorp Vault Version: 1.13.3
• Kubernetes Version: 1.26

[csatib02]

Hey @kitokid1313,
You might need to tweak the basic settings according to your use-case, before deploying cr-aws.

Other things you should check:

• Within the operator pod logs you should see the applied config automatically applying k8s auth backend.
• Ensure that all settings inside the CR is correct.