Manifests Config (Kubernetes)
manifests: - path: targets:
The path to a manifest(s) that you want to deploy. You have the following options for specifying the path:
Path to a directory
The path is relative to the deployment config file. When you specify a directory, CD-as-a-Service reads all the YAML files in the directory and deploys the manifests to the target you specified in
manifests: - path: deployments/manifests/configmaps
Path to a specific local file
The path is relative to the deployment config file. If your directory is at root and your manifests are in a “manifests” folder, your config is:
manifests: - path: manifests/sample-app.yml - path: manifests/sample-app-namespace-prod.yml
URL to a specific file
In this example, you store your manifests in GitHub.
- Org: “my-company”
- Repo: “my-app”
- Manifests location: “manifests” directory
manifests: - path: https://raw.githubusercontent.com/my-company/my-app/main/manifests/potato-facts-v1.yaml - path: https://raw.githubusercontent.com/my-company/my-app/main/manifests/potato-facts-service.yaml
manifests: - path: /path/to/manifest targets: ["<targetName1>", "<targetName2>"]
A comma-separated list of deployment targets that you want to deploy the manifests to. If you omit this option, CD-as-a-Service deploys the manifests to all targets listed in the deployment file. Make sure to enclose each target in quotes. Use the name you defined in
targets.<targetName> to refer to a deployment target.
manifests: - path: manifests/potato-facts.yaml - path: manifests/potato-facts-service.yaml - path: manifests/dev-namespace.yaml targets: ["dev"] - path: manifests/staging-namespace.yaml targets: ["staging"] - path: manifests/infosec-namespace.yaml targets: ["infosec"] - path: manifests/prod-namespace.yaml targets: ["prod"]
Was this page helpful?
Thank you for letting us know!
Sorry to hear that. Please tell us how we can improve.
Last modified November 27, 2023: (803ecce)