Kpm Manfiests

01_manifest.yaml

# Manifest 'hand-written' by the user

# metadata: ~equivalent to Chart.yaml
package: 
  name: foo/bar
  version: 0.0.1
# List resources to deploy
resources:
 # can be a template
   # jinja2 
 - template: deployment.yaml.j2
   expander: jinja2

   # jsonnet
 - template: svc.jsonnet
   expander: jsonnet 

 # can be a file-path to import
 - file: ingress.yaml

 # can be an inlined resource
 - value: {apiVersion: 'v1', kind: 'ServiceAccount',
            metadata: {name: 'app-sa'}}
  
  # Could be a globing / recursive walk (No-implemented)
 - file: resources/**/*.yaml
   recursive: true

02_output-manifest.yaml

# Manifest generated to be consumed by the CLI / API
# Difference: resources are expanded and all included
package: 
  name: foo/bar
  version: 0.0.1
# List resources to deploy
resources:
 # the jinja2 resource 
 - {"kind": "Deployment",
        "spec": {
          "template": {
            "spec": {
                 .... 
 # the jsonnet resource
 - {"kind": "Service",
        "spec": {
          "type": "ClusterIP",
          "ports": [
            {
              "targetPort": 80,
              "protocol": "TCP",
              "port": 80
            }
          ],}

 # inlined resource
 - {apiVersion: 'v1', kind: 'ServiceAccount',
            metadata: {name: 'app-sa'}}
 - ... 

03_manifest.jsonnet

# Same than manifest.yaml, but using jsonnet
package: {
  name: "foo/bar",
  version: "0.0.1"},
resources: [
 # can be a template
   # jinja2 
 import("deployment.jsonnet"),
 import("svc.jsonnet"),
 import("...")
  ]