zalando / zalando/postgres-operator
sharememory disable is not working
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hi Team,
It seems disabling shared memory in the postgres is not handled on the operator code.
We are trying to run Kata container with postgres and kata container is not running with shared memory,
When we disable the shared memory through CRD, we have noticed that it is getting enabled by default.
When we understand the code we found that mountShmVolumeNeeded is returning always true for ebaling the shm memory. It seems opConfig.ShmVolume is always returning true.
Is that any reason we are always returning true from opConfig.ShmVolume?
Thanks,
Kannan V
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
Trace mountShmVolumeNeeded and opConfig.ShmVolume from the operator code to the CRD configuration handling. Verify why disabling shared memory is overridden, then confirm that a cluster with shared memory disabled no longer receives the shared-memory mount while the default behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100