We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently the backube/volsync mover pods accepts one securityContext per volume.
If a volume contain files with multiple UID/GID owners it may not be possible to restore it back to the same state with current volsync architecture.
Suggested workaround:
openshift-adp
oc annotate --overwrite namespace/openshift-adp volsync.backube/privileged-movers='true'
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently the backube/volsync mover pods accepts one securityContext per volume.
If a volume contain files with multiple UID/GID owners it may not be possible to restore it back to the same state with current volsync architecture.
Suggested workaround:
openshift-adp
namespace might work.https://volsync.readthedocs.io/en/latest/usage/permissionmodel.html#controlling-mover-permissions
The text was updated successfully, but these errors were encountered: