Skip to content
New issue

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

The ability to backup policies to AWS S3 buckets instead of local FS / mounted volumes in k8s #521

Open
kostiapl opened this issue Dec 6, 2023 · 1 comment

Comments

@kostiapl
Copy link

kostiapl commented Dec 6, 2023

Is your feature request related to a problem? Please describe.
We'd like to leverage OPAL client capabilities (STORE_BACKUP_PATH, OFFLINE_MODE_ENABLED, STORE_BACKUP_INTERVAL) when backing up policies to S3 buckets, rather than using mounted volumes in the K8s cluster. This is necessary due to the limitations of our platform, which does not support the ReadWriteMany access mode for volumes, especially when dealing with multiple pods equipped with the OPAL client.

Describe the solution you'd like
The ability to back up policies to S3 buckets instead of mounted volumes.

Describe alternatives you've considered
CSI for S3 https://github.com/ctrox/csi-s3

Additional context
Currently, we use custom written k8s admission controller and mutation web hooks that inject sidecar containers (the pair of OPAL client and OPA server) for implementation of distributed authorization. We would like to use backing up policy functionality of OPAL client that would allow us to avoid services downtime in cases when git server with the policies is not available for some reason.

@roekatz
Copy link
Contributor

roekatz commented Apr 30, 2024

Hi @kostiapl, sorry for the late respond.
Have you had the chance to try using csi-s3?
I'm not sure adding support for backup stores for offline mode (other than filesystem) is really something we want to focus on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants