Skip to content
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

Not valid networking.k8s.io/v1 #297

Closed
kmaounis opened this issue May 12, 2021 · 2 comments
Closed

Not valid networking.k8s.io/v1 #297

kmaounis opened this issue May 12, 2021 · 2 comments

Comments

@kmaounis
Copy link

Hi ,

I migrated my ingresses from

apiVersion: networking.k8s.io/v1beta1
kind: Ingress

to

apiVersion: networking.k8s.io/v1
kind: Ingress

moving my k8s 1.19 and I am getting

stdin: Failed initializing schema https://kubernetesjsonschema.dev/master-standalone/ingress-networking-v1.json: Could not read schema from HTTP, response status is 404 Not Found

using kubeval Version: 0.16.1, If I am not terrible wrong it is a valid yaml
https://kubernetes.io/docs/concepts/services-networking/ingress/
but I do not see it here
https://github.com/instrumenta/kubernetes-json-schema/tree/master/master-standalone

Do I do something wrong?

@yannh
Copy link

yannh commented May 12, 2021

Hi @kmaounis , Kubeval uses https://github.com/instrumenta/kubernetes-json-schema/ to validate schemas, and schemas for 1.19 and up are missing - see instrumenta/kubernetes-json-schema#26

I am maintaining https://github.com/yannh/kubernetes-json-schema to solve the issue - it contains instructions on how to use it with kubeval. Hopefully that solves your problem :)

@kmaounis
Copy link
Author

@yannh , thank you. That was a big help , I missed the part that this repo is not being actively maintained.

kubeval --strict --schema-location https://raw.githubusercontent.com/yannh/kubernetes-json-schema/master/

The above did the trick

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants