infra
/
crds-catalog
1
0
Fork 0
Code Issues 1 Pull Requests Releases Activity
Kubernetes CRDs (CustomResourceDefinition) in JSON schema format.
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
28 Commits
2 Branches
0 Tags
420 KiB
Shell 74.2%
Makefile 25.8%
 
 
main
catalog
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'main'
${ noResults }
Go to file
Renovator Bot e26cc31d5b
continuous-integration/drone/pr Build is passing Details
continuous-integration/drone/push Build is passing Details
chore(deps): update dependency minio/operator to v5.0.5 		5 days ago
.drone.yml ci: add publish step 3 months ago
.gitignore initial commit 3 months ago
.prettierignore add toolchain configs 3 months ago
LICENSE initial commit 3 months ago
Makefile chore(deps): update dependency minio/operator to v5.0.5 5 days ago
README.md add toolchain configs 3 months ago
generate.sh feat: add k8up crds 1 month ago
renovate.json chore: enable renovate automerge for k8up 1 month ago

README.md

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.