oracle / oracle/oracle-database-operator
Watch Names space is not support for OKE Database operator add-on, patched operator is reset when compute is restarted
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 192
- Forks
- 69
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 1
Description
It is recommended to update the WATCH_NAMESPACE in the Operator settings for custom namespaces.
Patching the Operator is only supported via cli with patch + YAML.
When the Database Operator is deployed on Oracle Kubernetes Engine (OKE) and managed as an Add-On, restarts of the operator result in the default add-on configuration being loaded, losing the patch that was applied.
Enhancement request to add the WATCH_NAMESPACE into the configuration list of the add-on.
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
Start by tracing how the OKE Database Operator add-on loads its configuration and where WATCH_NAMESPACE is defined or patched. Confirm the expected add-on configuration format, then verify that a configured WATCH_NAMESPACE survives an operator restart or compute restart without being replaced by the default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100