ovh / ovh/public-cloud-databases-operator
Improvements
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 9
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 5
Description
Hello,
For helm chart, I would suggest improvements:
- please do not specify namespace in the templates, as the helm chart will be deployed in a dedicated namespace
- it would be nice to be able to specify an existing secret for ovhCredentials (case of external secret management for instance, like vault)
- in default values file, it would be nice to set the tag of the current release, not "latest", so that an upgrade is done in case of new release
For operator:
- in case of public database, it would be nice to have a way to say: use public ips and not private ones
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the Helm chart templates and default values file, then inspect the operator's handling of public databases and ovhCredentials. Break the request into namespace handling, existing-secret support, release image tags, and public-IP selection. Done means each requested option is configurable and the chart or operator behavior reflects it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- cloud, databases, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100