From dfdef5480d19e4b3e5f7e56656230b72e76ba88d Mon Sep 17 00:00:00 2001 From: Michael Nelson Date: Thu, 3 Mar 2022 06:26:24 +1100 Subject: [PATCH] Carvel docs to specify namespace for repository. (#4368) Signed-off-by: Michael Nelson --- docs/user/managing-carvel-packages.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user/managing-carvel-packages.md b/docs/user/managing-carvel-packages.md index 849f14f8393..954a44e67c5 100644 --- a/docs/user/managing-carvel-packages.md +++ b/docs/user/managing-carvel-packages.md @@ -139,10 +139,10 @@ EOF Then, you need to apply the `PackageRepository` CR to your cluster using `kubectl` (or, alternatively, the `kapp` CLI), by running the following command: ```bash -kubectl apply -f repo.yaml +kubectl apply --namespace kapp-controller-packaging-global -f repo.yaml ``` -Under the hood, kapp-controller will create `Package` and `PackageMetadata` CRs for each of the packages in the repository. +Under the hood, kapp-controller will create `Package` and `PackageMetadata` CRs for each of the packages in the repository in the global packaging namespace for kapp-controller, enabling those packages to be installed via Kubeapps in any namespace. Note you can instead install the repository in a different namespace if the packages should only be available for install via Kubeapps in a particular namespace. > **TIP**: Run `kubectl get packagerepository`, `kubectl get packages` and `kubectl get packagemetadatas` to get the created CRs.