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?
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?
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 https://github.com/fabric8io/kubernetes-model/issues/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?