https://github.com/bitnami/kube-libsonnet
Bitnami's jsonnet library for building Kubernetes manifests
https://github.com/bitnami/kube-libsonnet
jsonnet ksonnet kubecfg kubernetes
Last synced: about 1 year ago
JSON representation
Bitnami's jsonnet library for building Kubernetes manifests
- Host: GitHub
- URL: https://github.com/bitnami/kube-libsonnet
- Owner: bitnami
- License: apache-2.0
- Archived: true
- Created: 2018-03-21T23:50:22.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2023-06-20T13:16:45.000Z (about 3 years ago)
- Last Synced: 2025-03-29T01:01:59.778Z (about 1 year ago)
- Topics: jsonnet, ksonnet, kubecfg, kubernetes
- Language: Jsonnet
- Homepage: https://bitnami.com
- Size: 150 KB
- Stars: 171
- Watchers: 11
- Forks: 49
- Open Issues: 15
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Codeowners: CODEOWNERS
- Security: SECURITY.md
Awesome Lists containing this project
README
## WARNING: This repository is no longer actively maintained by Bitnami/VMware.
We have made the difficult decision to stop driving this project and therefore we will no longer actively respond to issues or pull requests.
There is a new initiative to continue maintaining this project outside of Bitnami/VMware at https://github.com/kube-libsonnet/kube-libsonnet
[](https://travis-ci.org/bitnami-labs/kube-libsonnet)
# kube-libsonnet
This repo has been originally populated by the `lib/` folder contents
from `https://github.com/bitnami-labs/kube-manifests` as of Mar/2018,
aiming to provide a library of `jsonnet` manifests for common
Kubernetes objects (such as `Deployment`, `Service`, `Ingress`, etc).
Accordingly, above `kube-manifests` has been changed to use this repo as
a git submodule, i.e.:
$ git submodule add https://github.com/bitnami-labs/kube-libsonnet
$ cat .gitmodules
[submodule "lib"]
path = lib
url = https://github.com/bitnami-labs/kube-libsonnet
## Testing
Unit and e2e-ish testing at tests/, needs usable `docker-compose`
setup at node, will run a `k3s` "dummy" container to serve Kube API,
"enough" to run `kubecfg validate` against it:
make tests
If you don't want that full kube-api stack (will then use your "local"
kubernetes configured environment), you can run:
make -C tests local-tests kube-validate