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

Add support for existing K8s secret for database credentials #106

Open
lbanita opened this issue Jul 4, 2024 · 0 comments · May be fixed by #112
Open

Add support for existing K8s secret for database credentials #106

lbanita opened this issue Jul 4, 2024 · 0 comments · May be fixed by #112
Assignees
Labels
enhancement New feature or request triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@lbanita
Copy link

lbanita commented Jul 4, 2024

Briefly describe the feature

  • Reference an existing for Kubernetes secret to read the credentials for the database, instead of providing them inline in the valus file.

What problem does this feature solve? Please link any relevant documentation or Issues

  • It allows deployment of Paralus Helm Chart via GitOps (e.g. ArgoCD), by securing the secrets in an external source and retrieving them via External Secrets Operator or other similar mechanism

(optional) What is your current workaround?

  • N/A
@lbanita lbanita added enhancement New feature or request new Needs triage labels Jul 4, 2024
@akshay196 akshay196 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed new Needs triage labels Jul 9, 2024
@SorsOps SorsOps linked a pull request Feb 13, 2025 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants