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
Running the init container copy_vault_env always together with the pod
Actual Behavior
I recently got a k8s cluster at my disposal, it has vault v1.6.2 installed, as well as vault-operator and vault-secrets-webhook v1.19.0 from banzaicloud.
The support team began to notice that sometimes pods and jobs start without copy-vault-env init container. Because of this, they do not have access to the vault secrets, and use only the paths in their configuration (secrets are mapped from the config map to ENV, if this is important). The only solution to the problem is deleting the pod and creating it again (with the same configuration and annotations). At the same time, I don’t find any errors in the vault-operator and vault-secrets-webhook logs, the logs are in debug mode.
Please tell me what can be done in this situation, are there any options for analyzing this problem?
Steps To Reproduce
No response
Logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Preflight Checklist
Version
1.6.2
Expected Behavior
Running the init container copy_vault_env always together with the pod
Actual Behavior
I recently got a k8s cluster at my disposal, it has vault v1.6.2 installed, as well as vault-operator and vault-secrets-webhook v1.19.0 from banzaicloud.
The support team began to notice that sometimes pods and jobs start without copy-vault-env init container. Because of this, they do not have access to the vault secrets, and use only the paths in their configuration (secrets are mapped from the config map to ENV, if this is important). The only solution to the problem is deleting the pod and creating it again (with the same configuration and annotations). At the same time, I don’t find any errors in the vault-operator and vault-secrets-webhook logs, the logs are in debug mode.
Please tell me what can be done in this situation, are there any options for analyzing this problem?
Steps To Reproduce
No response
Logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: