You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 6, 2018. It is now read-only.
I think we should just bite the bullet and go with non-empty. I don't see how we can use the latest schema models on older kubernetes/openshift installations without it?
The text was updated successfully, but these errors were encountered:
Well that sounds like a bad validation in kubernetes to me... APIs should be backwards compatible shouldn't they, well unless marked as new major version?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
error validating "https://repo1.maven.org/maven2/io/fabric8/apps/console-kubernetes/2.2.178/console-kubernetes-2.2.178-kubernetes.json": error validating data: found invalid field InitContainers for v1.PodSpec;
seems to be related to this issue #154
I think we should just bite the bullet and go with non-empty. I don't see how we can use the latest schema models on older kubernetes/openshift installations without it?
The text was updated successfully, but these errors were encountered: