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
Vault operator does not allow to specify securityContext for the vaultConfigurer pod container, it only allows to specify the podSecurityContext for the whole pod
This is not sufficient in all cases. For example, we deploy in a managed rancher kubernetes cluster with strict security policies. All containers are forced to have the following security profile or they won't be scheduled:
Some but not all of them can be set by using the pods security context on a pod level, however, e.g., allowPrivilegeEscalation and capabilities can only be set on a container level
This missing feature prevents us from using bank-vaults operator, because it is impossible for us to deploy the vaultConfigurer pod
Proposed Solution
Add a vaultConfigurerContainerSpec that allows to configure/extend container spec for vaultConfigurer - similar to the already existing vaultContainerSpec - to the VaultSpec API
Alternatives Considered
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Preflight Checklist
Problem Description
Vault operator does not allow to specify securityContext for the vaultConfigurer pod container, it only allows to specify the podSecurityContext for the whole pod
This is not sufficient in all cases. For example, we deploy in a managed rancher kubernetes cluster with strict security policies. All containers are forced to have the following security profile or they won't be scheduled:
Some but not all of them can be set by using the pods security context on a pod level, however, e.g., allowPrivilegeEscalation and capabilities can only be set on a container level
This missing feature prevents us from using bank-vaults operator, because it is impossible for us to deploy the vaultConfigurer pod
Proposed Solution
Add a
vaultConfigurerContainerSpec
that allows to configure/extend container spec for vaultConfigurer - similar to the already existingvaultContainerSpec
- to theVaultSpec
APIAlternatives Considered
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: