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.

Sign up for GitHub

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

Jump to bottom

Use secrets instead of PVCs for key database #43

Open
sarroutbi opened this issue Oct 8, 2024 · 2 comments
Open

Use secrets instead of PVCs for key database #43

sarroutbi opened this issue Oct 8, 2024 · 2 comments
Labels
priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@sarroutbi
Copy link
Member

Use secrets instead of PVCs for key database. This way, access to the keys will be accessible to the different replicas, without having to care that PVCs is multi-attachable.
More information here: Create a POD that has access to the secret data through a volume

Original issue:
latchset#66
@sarroutbi sarroutbi added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Oct 8, 2024
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 7, 2025
@sarroutbi
Copy link
Member Author

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sarroutbi @openshift-bot