kapitan-reference
kapitan-reference copied to clipboard
kapicorp
Reference structure for Kapitan - alpha version
https://github.com/kapicorp/kapitan-reference/blob/master/.kapitan#L1 Existing `.kapitan` requires version `0.31.0rc0` As kapitan version 0.31.0 is already released, it seems reasonable to update this requirement to 0.31.0
If you do this with a versioned secret: ```parameters: components: echo-server: env: KAPITAN_SECRET: secretKeyRef: key: 'kapitan_secret' ``` You would expect the name found to include the version, but its taking...
In my current usecase I want to add a service of type `NodePort`. Currently this is possible but without the ability to specify the `nodePort` itself. So if I create...
**Describe the feature** A configmap can take a data or binaryData field. Kapitan only allows the data field. **Expected behavior** When defining an "config_maps" dict, I would love to see...
Possbiel sources: As already mentioned here: [Slack#Kapitan](https://kubernetes.slack.com/archives/C981W2HD3/p1610949488017900?thread_ts=1610949204.017300&cid=C981W2HD3) It might be possible to use this: https://github.com/bitnami-labs/kube-libsonnet which already includes several more ingress things **Types of Ingress** [k8s-docs for Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) - Ingress...
https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/ Allow usage of: ```yaml apiVersion: apps/v1 kind: Deployment/Statefulset metadata: name: "my-release-harbor-portal" labels: heritage: Helm release: my-release chart: harbor app: "harbor" component: portal spec: template: spec: [...] automountServiceAccountToken: false [...]...
# Usecase For a Deployment + Job + CronJob resource it's sometimes required to have one or more additional PV/PVC's. Therfore I need the generators to be able to generate...
Document the manifest generator structure. The idea is to use a json-schema to doc tool to keep the json schema self documenting