This example shows you how to specify Kubernetes resources in a component’s manifests
list. These files can either be local or remote and under the hood Zarf will wrap them in an auto-generated helm chart to manage their install, rollback, and uninstall logic.
To learn more about how manifests
work in Zarf, see the Kubernetes Manifests section of the package components documentation.
- name : simple-httpd-deployment
# local manifests are specified relative to the `zarf.yaml` that uses them:
# image discovery is supported in all manifests and charts using:
# zarf prepare find-images
- name : simple-nginx-deployment
# remote manifests are specified with a URL and you can verify integrity of a manifest
# by adding a sha256sum to the end of the URL, separated by an @:
- https://k8s.io/examples/application/deployment.yaml@c57f73449b26eae02ca2a549c388807d49ef6d3f2dc040a9bbb1290128d97157
# this sha256 can be discovered using:
# zarf prepare sha256sum https://k8s.io/examples/application/deployment.yaml
# image discovery is supported in all manifests and charts using:
# zarf prepare find-images
- name : podinfo-kustomize
- name : simple-podinfo-deployment
# kustomizations can be specified relative to the `zarf.yaml` or as remoteBuild resources with the
# following syntax: https://github.com/kubernetes-sigs/kustomize/blob/master/examples/remoteBuild.md:
- github.com/stefanprodan/podinfo//kustomize?ref=6.4.0
# while ?ref= is not a requirement, it is recommended to use a specific commit hash / git tag to
# ensure that the kustomization is not changed in a way that breaks your deployment.
# image discovery is supported in all manifests and charts using:
# zarf prepare find-images
- ghcr.io/stefanprodan/podinfo:6.4.0