Kubernetes CRDs (CustomResourceDefinition) in JSON schema format.
Go to file
Robert Kaussow 281a01db5e
All checks were successful
continuous-integration/drone/push Build is passing
fix generate script
2023-03-08 13:10:34 +01:00
.drone.yml initial commit 2023-03-08 12:54:34 +01:00
.gitignore initial commit 2023-03-08 12:54:34 +01:00
.prettierignore add toolchain configs 2023-03-08 13:06:57 +01:00
generate.sh fix generate script 2023-03-08 13:10:34 +01:00
LICENSE initial commit 2023-03-08 12:54:34 +01:00
Makefile initial commit 2023-03-08 12:54:34 +01:00
README.md add toolchain configs 2023-03-08 13:06:57 +01:00
renovate.json add toolchain configs 2023-03-08 13:06:57 +01:00

crds-catalog

Build Status License: MIT

This repository to aggregatepopular Kubernetes CRDs (CustomResourceDefinition) in JSON schema format. These schemas can be used by various tools such as Datree, Kubeconform and Kubeval to perform validation on custom (and native) Kuberentes resources. Running Kubernetes schema validation checks helps apply the "shift-left approach" on machines without giving them access to your cluster (e.g. locally or on CI).

The project is inspired by Datree's CRDs-catalog and was created to manage CRDs required for my own Kubernetes deployments.

Usage

Schemes are generated by the CI and automatically pushed to the catalog branch.

Kubeconform

kubeconform -schema-location default -schema-location 'https://gitea.rknet.org/infra/crds-catalog/raw/branch/catalog/{{.Group}}/{{.ResourceKind}}_{{.ResourceAPIVersion}}.json' [MANIFEST]

License

This project is licensed under the MIT License - see the LICENSE file for details.