You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using vault_kubernetes_secret_backend with empty kubernetes_ca_cert = null and disable_local_ca_jwt = true the service account jwt should be populated, but is not.
Hello @mikkel3000, I am sorry you are having trouble here.
I believe this is expected behavior. The service_account_jwt is not returned in the READ request from the kubernetes backend's /config endpoint so the UI will have no way of displaying it.
$ vault write -f kubernetes/config kubernetes_host=foo service_account_jwt="header.payload.signature"
Success! Data written to: kubernetes/config
$ vault read kubernetes/config
Key Value
--- -----
disable_local_ca_jwt false
kubernetes_ca_cert n/a
kubernetes_host foo
Terraform Core Version
1.9.2
Terraform Vault Provider Version
4.4.0
Vault Server Version
1.17.3
Affected Resource(s)
vault_kubernetes_secret_backend
Expected Behavior
When using
vault_kubernetes_secret_backend
with emptykubernetes_ca_cert = null
anddisable_local_ca_jwt = true
the service account jwt should be populated, but is not.Setting kubernetes secret backend with:
Expects to see.
Actual Behavior
Service Account JWT is empty.
I did not use "EXAMPLEJWT" when applying it, i used an actual service account jwt.
Gives following in vault ui:
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Try to apply the terraform resource and observe the missing JWT.
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: