oracle / oracle/oracle-database-operator
Read Only root file system deployment with oraoperator
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 192
- Forks
- 69
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 1
Description
We have a requirement to meet security compliance to deploy oraoeprator with readonlyRootfilesystem.
Current Oracle image doesn't support readonly deployment and there are many path where it doing writing.
So, this required adaptation in Oracle delivery!
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
No files, tests, or entry points are named. Start by tracing the OraOperator deployment and the Oracle image paths that write during startup, then verify that the deployment succeeds with a read-only root filesystem and that all required writes use supported writable locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100