New to Kubepack? Please start here.

Scenario-1

This docs trying to explain the behavior of Pack

This section explain test-1.

If you look into this test’s dependency-list.yaml file.

$ cat dependency-list.yaml

items:
- package: github.com/kubepack/kube-a
  branch: test-1

See image below, which describe whole dependency.

Explanation of image:

1. This test directly depends on branch test-1 of kube-a repository.

2. kube-a’s depends on branch test-1 of kube-b. See this dependency-list.yaml file here

3. kube-b’s depends on branch test-1 of kube-c. See this dependency-list.yaml file here

4. kube-c has no dependency. See this dependency-list.yaml file here

Now, $ pack dep -f . command will get all the dependencies and place it under manifests/vendor folder.

$ pack up -f . will generate final version with annotated with git-commit-hash.

Next Steps

• Want to publish apps using Kubepack? Please visit here.
• Want to consume apps published using Kubepack? Please visit here.
• To learn about dependency-list.yaml file, please visit here.
• Learn more about pack cli from here.