-
Notifications
You must be signed in to change notification settings - Fork 693
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REQUEST: Create kubernetes-sigs/kubectl-validate #4159
Comments
I believe a SIG CLI lead client-side validation tool is worthy of a new repository. /lgtm |
Given that this is approved by SIG CLI leads for a while, who should I contact to create this repo? /cc @nikhita |
/sig architecture |
/assign |
Repo create: https://github.com/kubernetes-sigs/kubectl-validate Once all are merged I'll add the teams and this should be good to close 👍 |
teams are added to the repo, you should be good to go! /close |
@mrbobbytables: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
New repo, staging repo, or migrate existing
new repository
Is it a staging repo?
no
Requested name for new repository
kubectl-validate
Which Organization should it reside
kubernetes-sigs
Who should have admin access?
alexzielenski, apelisse
Who should have write access?
alexzielenski, apelisse
Who should be listed as approvers in OWNERS?
alexzielenski, apelisse, richabanker
Who should be listed in SECURITY_CONTACTS?
alexzielenski, apelisse, richabanker
What should the repo description be?
CLI Tool for validating Kubernetes resources from their OpenAPIV3 schemas on client-side aiming for best parity with errors returned by server. Supports core resources, CRDs, CEL validations, and more!
What SIG and subproject does this fall under?
this is a new subproject for sig-cli for kube-validate
Please provide references to appropriate approval for this new repo
Additional context for request
No response
The text was updated successfully, but these errors were encountered: