New to Kubepack? Please start here.

Using Kubepack CLI

How to Get Dependencies

$ pack dep -f .

command will get dependencies defined under items field in dependency-list.yaml file. You can get specific version, branch or revision. See tutorial of dependency-list.yaml. All the dependencies will appear in manifests/vendor folder. You can get verbose output with --v=10 or -v 10 flag.

Edit File from manifests/vendor Folder

$ pack edit -p <filepath>

command edit file, exists in manifests/vendor folder and generate patch in manifests/patch folder. This patch file-path will be same as manifests/vendor folder.

Note: filepath: is relative file path.

Combine manifests/vendor and manifests/patch files

$ pack up -f .

command combine files from manifests/patch and manifests/vendor folder. This combination of manifests/patch and manifests/vendor files appear in manifests/output folder. Read more

Validate manifests/output folder

$ pack validate -f .

This command will validate the manifests/output folder yaml files using openapi-spec. If some file is not a valid yaml then throws errors. --kube-version flag is used specify kubernetes version, which you want to validate against.

Next Steps

  • Want to consume apps published using Kubepack? Please visit here.
  • To learn about dependency-list.yaml file, please visit here.
  • Learn more about Pack jsonnet-support here.
  • Learn more about Pack validation here.

Subscribe to our free technical newsletter!

Join thousands of subscribers and stay up-to-date on AppsCode.