mayadata-io / mayadata-io/d-operators
proposal: PodConfig as a custom resource
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
ProblemStatement: As a DevOps engineer, I want a k8s controller that accepts values from various sources and provides a final set of merged values that can in turn be used to arrive at a desired state of a Pod.
For example:
- PodConfig
Aprovides taints & tolerations for Pod - PodConfig
Bprovides resource limits (memory & cpu) for Pod - PodConfig
Cprovides environment variables for containers of the Pod - PodConfigResult
Fshould merge all the above & present a final state that is a 3 way merge of all the above based on priority.
Now there can be custom controllers that make use of resource F to build the desired Pod state & subsequently apply this Pod state against the kubernetes cluster.
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 reviewing the repository's existing Kubernetes controller and metacontroller patterns, then compare them with the proposed PodConfig and PodConfigResult resources. Before implementation, define the resource schemas, priority and three-way merge semantics, and the observable completion criteria for a controller consuming the merged result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100