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
The k8 deployment example at path examples/kubernetes/op-connect-deployment.yaml, has chmod -f -R 600 /home/opuser/.op/config as part of the command in the initContainer, but this path is not mounted, hence it does not have any effect on subsequent containers:
The k8 deployment example at path
examples/kubernetes/op-connect-deployment.yaml
, haschmod -f -R 600 /home/opuser/.op/config
as part of the command in the initContainer, but this path is not mounted, hence it does not have any effect on subsequent containers:Only
/home/opuser/.op/data
is mounted,chmod -f -R 600 /home/opuser/.op/config
will ONLY affect the init container.Did you mean
chmod -f -R 600 /home/opuser/.config
?But then you had to mount the
credentials
volume as well at path/home/opuser/.config
...If not, can you clarify what the intention was behind
chmod -f -R 600 /home/opuser/.op/config
?The text was updated successfully, but these errors were encountered: