planetscale / planetscale/vitess-operator
[Feature] Allow setting pod sysctls
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 102
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 15
Description
Description
Allow setting sysctls on pods created by the operator, using the mechanism Kubernetes exposes (pod security context) for doing so.
Use case
Organizations using Vitess may have a database team that operates Vitess on top of Kubernetes clusters managed by an infrastructure team. The infrastructure team may set sysctl defaults which are recommended for the general case, but not ideal for Vitess.
The infra team may be unwilling to change the global defaults, but be willing to let the database team override namespace-scoped sysctls in Vitess-managed pods. In that case, the database team will need some way to set namespace-scoped sysctls.
Thanks
Thanks to @bluecrabs007 for bringing this up w/ me.
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 the Kubernetes pod security context and sysctl documentation linked in the issue, then trace where the operator constructs Vitess-managed pods. Done means namespace-scoped sysctls can be configured for those pods through the operator without changing cluster-wide defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100