New to Kubepack? Please start here.

Scenario-2

This docs trying to explain the behavior of Pack

This section explain test-2.

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

$ cat manifest.yaml

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

You’ll see it depends on branch test-2 of repository kube-a.

You can see the whole dependencies in below image.

Explanation

1. test-2 directly depends on branch test-2 of kube-a.

2. kube-a depends on branch test-2 of kube-b repository. kube-a contains the patch of kube-b’s nginx-deployment.yaml file.

3. kube-b depends on branch test-2 of kube-c repository. kube-b contains the patch of kube-c’s nginx-deployment.yaml file.

When run $ kubectl plugin pack dep in test-2, following things happen.

1. Get all the dependencies, reading manifest.yaml file.
2. kube-b’s nginx-deployment.yaml file is combination of patch (exists in kube-a repository) and original file (exists in kube-b repository).
3. kube-c’s nginx-deployment.yaml file is combination of patch (exists in kube-b repository) and original file (exists in kube-c repository).

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.