Request: option to disable etcd password authentication (RBAC)
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 5.7k
- Forks
- 384
- Avg merge
- 2h 36m
- Merged PRs (30d)
- 2
Description
Given that the default password is only used as a fool-proofing mechanism (#708), and that Patroni cannot reload etcd password without restarting, it's nice to have an option to disable etcd password authentication in pigsty.yml. The benefits are:
- Improve backward compatibility with shared etcd clusters set up by Pigsty v3.7.
- In some environments where weak passwords are forbidden or passwords need to be rotated periodically (e.g. for compliance reasons), this reduces maintenance churn.
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 reading pigsty.yml and tracing the existing etcd password-authentication configuration into Patroni. Check how configuration changes are applied when Patroni cannot reload the etcd password without restarting. Done means an explicit option can disable etcd password authentication while preserving the stated backward-compatibility and password-rotation use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- authentication, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100