Support CRD lookup without a dependency on a running cluster
Closed this issue · 7 comments
What would you like to be added?
Allow CRDs to be looked from some centrally managed CRD store. I am not sure if that exists, but if it doesn't I believe it would be very valuable to support a more seamless user experience.
Why is this needed?
I find linting fits best in use-cases where linting of manifests is done before applying manifest files to a cluster. This means that CRDs are not guaranteed to exist on the cluster, and thus pointing kubectl-validate towards a cluster isn't feasible.
Storing CRDs or OpenAPI schemas locally is also not a favorable option in this case, as that would require maintaining the CRDs separately, which Is somewhat cumbersome.
Maybe datreeio's CRD collection can be used? https://github.com/datreeio/CRDs-catalog
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle rotten - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Reopen this issue with
/reopen - Mark this issue as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou can:
- Reopen this issue with
/reopen- Mark this issue as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
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-sigs/prow repository.
/reopen
I found this line in the code:
https://github.com/kubernetes-sigs/kubectl-validate/blob/main/pkg/cmd/validate.go#L195-L196
Could this feature be as simple as adding a condition to this line?
@baer95: You can't reopen an issue/PR unless you authored it or you are a collaborator.
In response to this:
/reopen
I found this line in the code:
https://github.com/kubernetes-sigs/kubectl-validate/blob/main/pkg/cmd/validate.go#L195-L196Could this feature be as simple as adding a condition to this line?
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-sigs/prow repository.