Question: can the pkg/validation/ module be used to validate Manifests against the Kubernetes Swagger file? about kube-openapi HOT 6 CLOSED

pkg/validation is a go-swagger fork stripped down to implement exactly the semantics of our CRD validation API. go-swagger introduced unexpected changes in the past "to be a better swagger implementation", but it changed our API in unexpected and "forbidden" ways.

Technically you could validate manifests. But don't expect any compatibility of these packages in the future. They change in ways we need them in k/k, without taking care of the ecosystem (this is true for the whole repository, it is basically internal to k/k).

from kube-openapi.

@sttts I'm a bit confused 🤔 I want to validate Kubernetes manifests and Kubernetes CRDs - I would love to stay as close as possible to k/k's validation as possible (ideally if it breaks in Kubernetes, it should break in kubeval/kubeconform). Is the logic to validate CRDs different than the logic to validate other Resources such as Services & Deployments?

We (Kubeval/Kubeconform) have problems with having to maintain JSON Schemas (see instrumenta/kubernetes-json-schema#26 ) so being able to validate OpenAPI directly using K/K's swagger file, without having to convert first, would be a nice time-saver.

Are there benefits to converting to JSON Schemas first? Is there tooling I could use to validate against K8S swagger file directly? Doesnt for example kubectl uses this package for validation? Apologies again if this issue is more a support request than a question 😢

from kube-openapi.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

from kube-openapi.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

from kube-openapi.

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

from kube-openapi.

@fejta-bot: Closing this issue.

from kube-openapi.