Kpt [UPDATED] beta
Rendering with kpt
kpt allows Kubernetes
developers to customize raw, template-free YAML files for multiple purposes.
Skaffold can work with kpt by calling its command-line interface.
Configuration
To use kpt with Skaffold, add deploy type kpt to the deploy
section of skaffold.yaml.
The kpt type offers the following options:
| Option | Description | Default |
|---|---|---|
dir |
equivalent to the dir in kpt live apply <dir>. If not provided, skaffold deploys from the default hydrated path <WORKDIR>/.kpt-pipeline. |
|
applyFlags |
additional flags passed to kpt live apply. |
[] |
flags |
kpt global flags. | [] |
name |
alpha inventory object name. | |
inventoryID |
alpha inventory ID which annotates the resources being lively applied by kpt. | |
namespace |
alpha sets the inventory namespace. | |
force |
used in kpt live init, which forces the inventory values to be updated, even if they are already set. |
false |
defaultNamespace |
default namespace passed to kpt on deployment if no other override is given. | |
Each entry in paths should point to a folder with a kustomization file.
flags section offers the following options:
| Option | Description | Default |
|---|---|---|
global |
additional flags passed on every command. | [] |
apply |
additional flags passed on creations (kubectl apply). |
[] |
delete |
additional flags passed on deletions (kubectl delete). |
[] |
disableValidation |
passes the --validate=false flag to supported kubectl commands when enabled. |
false |
Example
The following deploy section instructs Skaffold to deploy
artifacts using kpt:
deploy:
kpt: {}
Note
kpt CLI must be installed on your machine. Skaffold will not install it.
Last modified October 27, 2025: chore: bump actions/upload-artifact from 4 to 5 in the github-actions group (#9897) (246c69f0)