oracle / oracle/oracle-database-operator
InvalidParameter exception for namespace configuration in the OKE Operator managed add-on
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 192
- Forks
- 69
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 1
Description
The Oracle Kubernetes Engine Operator managed add-on throws an exception when attempting the add the namespace configuration.
In an attempt to update the WATCH_NAMESPACE, I only saw the namespace option available and attempted to use this but this does appear to be the actual namespace of the Operator.
When saving the option an exception is thrown, this option should be removed / replaced witht eh watch names as per the enhancement request in issue #191
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 reviewing issue #191 and reproducing the exception when saving the namespace option in the OKE Operator managed add-on configuration. Trace how WATCH_NAMESPACE is exposed and validated; done means saving the intended watch-names configuration without an InvalidParameter exception and without presenting the incorrect namespace option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100