OpenAPI: Validation schemas

[manusa]

Description

Part of #6130

The legacy model generation approach using Go had as its main outcome the kube-schema.json and validation-schema.json files.

The purpose of the kube-schema.json file was to serve as the base spec for the jsonschema2pojo process to generate the resulting Java types.

Both files were added to the respective kubernetes-model-xxx artifact and made available downstream.

We don't have any record of a project taking advantage of the kube-schema.json artifact being consumed downstream (some parsers won't even load it). Is there anyone using this?

We do have notion of Eclipse JKube consuming the validation-schena.json file. This was originally implemented ad-hoc for this project (fabric8io/kubernetes-model#229, fabric8io/fabric8-maven-plugin#1029, fabric8io/fabric8-maven-plugin#66).

However, this file is not standard and uses some nasty workarounds for the validations. It also uses the Kubernetes object Kind as the identifier for the validation schema which is an issue if two resources share the same kind but belong to different groups (apiVersion).

As part of the new Model Generation approach, we need to replace this functionality in both projects.

Tasks

• Output a validation JSON schema (or alternative) that can be consumed by any project (if possible)
• Replace the ResourceValidator logic in Eclipse JKube to take advantage of the new schema or methodology

Original issues

• [schema] change in JSON schema structure for validation purpose kubernetes-model#229
• Feat/66 resource validation fabric8-maven-plugin#1029
• validate generated resources fabric8-maven-plugin#66

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!