mayadata-io / mayadata-io/d-operators
feat: proposal to implement a declarative kubernetes controller
Open
@AmitKumarDas is already working on this.
Since Jul 10, 2020.
chef
jsonnet
recipe
uber loop
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
ProblemStatement: As a K8s engineer
- I want to watch a resource & update its status
- I want to watch more than one resources & update their status
- I want to watch multiple resources & update their labels
- I want to watch multiple resources & update their annotations
- I want to watch a resource & create one or more Kubernetes resources as the watch's desired state
- I want to watch a resource & update one or more Kubernetes resources as the watch's desired state
- I want to watch a resource & delete one or more Kubernetes resources when the watch gets deleted
- I want to invoke a series of HTTP APIs via
kind: HTTPcustom resource. Each of these APIs will need data from previous API call(s). - Solve requirements like this
- I want specific controller pods to handle resources from specific namespaces. For example: controller pod running in team-a should handle resources from namespaces x, y, & z only
--include-namespaces, default=all--exclude-namespaces, default=none
- I want to associate specific worker goroutine count to specific controller
- I want to enable & disable reconciliation of my custom resource based on some annotation
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.
Assessment
This issue has not been assessed yet.