Skip to content
This repository has been archived by the owner on Nov 6, 2018. It is now read-only.

cannot use new schema on older kubernetes #160

Open
jstrachan opened this issue Sep 27, 2016 · 1 comment
Open

cannot use new schema on older kubernetes #160

jstrachan opened this issue Sep 27, 2016 · 1 comment

Comments

@jstrachan
Copy link
Contributor

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?

@jimmidyson
Copy link
Contributor

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants