zalando / zalando/postgres-operator
ConfigMap-based configuration deprecation timeline
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,
I noticed in the documentation that the ConfigMap-based configuration is planned to be deprecated and eventually removed in future releases.
Is there a specific timeline for when this deprecation and removal will occur? We are currently utilizing the ConfigMap-based configuration and would like to understand the timeframe for these changes to assist with our planning and transition.
Thank you!
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 with docs/reference/operator_parameters.md, especially the ConfigMap-based configuration section linked in the issue. Determine whether the project documents a deprecation or removal date, then update the documentation if an authoritative timeline is available; done means the timeframe is clearly stated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100