kubernetes / kubernetes/kubectl
Kubectl validate should validate non-schema assumptions about resources
Open
@seans3 is already working on this.
Since Nov 9, 2022.
kind/feature
lifecycle/rotten
needs-triage
priority/backlog
- Dominant language
- Go
- Stars
- 3.3k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Description
What would you like to be added:
There are certain resource types such as deployment that make assumptions about how their fields interact with each other. For example deployment expects that matchLabels matches the labels in the pod template.
Why is this needed:
Currently the only way to validate even inbuilt kubernetes resources is to dry-run them against a server. It would be nice to be able to validate such invalid manifests before having to run them against an actual kubernetes server.
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.