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
I am guessing this project isn't the right place to host kustomize.config.k8s.io resource definitions, since they're builtin, and not custom. However, they're also not hosted on the project we typically use that has the main schemas (see context in yannh/kubernetes-json-schema#13).
Is it reasonable to assume that since they're not "custom", they shouldn't be added here?
The text was updated successfully, but these errors were encountered:
The main reason why NOT to host the schema in this project (or yannh/kubernetes-json-schema) is that it will just not work 😅
Kubconform relies on the kind property to match the manifest with the right schema.
Kustomize manifests can be valid also without this property, they are "just" yaml files...
Thanks! Yes, I tried using the schema above earlier, and it seemed to work (I believe ours do have the kind property defined), but it wasn’t clear which version(s) it referred to.
I am guessing this project isn't the right place to host
kustomize.config.k8s.io
resource definitions, since they're builtin, and not custom. However, they're also not hosted on the project we typically use that has the main schemas (see context in yannh/kubernetes-json-schema#13).Is it reasonable to assume that since they're not "custom", they shouldn't be added here?
The text was updated successfully, but these errors were encountered: