New to Kubepack? Please start here.

Scenario-3

This docs trying to explain the behavior of Pack

This section explain test-3.

If you look into this test’s manifest.yaml file.

$ cat manifest.yaml

package: github.com/kubepack/pack/docs/_testdata/test-3
owners:
- name: Appscode
  email: [email protected]
dependencies:
- package: github.com/kubepack/kube-a
  branch: test-3

See image below, which describe whole dependency.

Explanation of image:

1. This test directly depends on branch test-3 of kube-a repository.
2. kube-a depends on branch test-3 of kube-b repository. See this manifest.yaml file here.
3. kube-b depends on branch test-3 of kube-c repository. See this manifest.yaml file here.
4. kube-c’s has no dependency. See this manifest.yaml file here.

Here, both kube-a and kube-b has patch of repository kube-c’s nginx-deployment.yaml file. You can find these patches here:

• kube-a
• kube-b

Now, run $ kubectl plugin pack dep command. This will vendor branch test-3 of all the dependencies kube-a, kube-b and kube-c. As, kube-a and kube-b both contain patch of kube-c’s nginx-deployment.yaml file. This file is the combination of both patch and original file.

Next Steps

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