From bed00595e41b506c5128bc4add62096ec24ce9a6 Mon Sep 17 00:00:00 2001 From: Catalin Stratulat Date: Wed, 6 Nov 2024 11:52:14 +0000 Subject: [PATCH] added clarification of secret duplication to porch-fn-system namespace --- .../porch/using-porch/using-authenticated-private-registries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/porch/using-porch/using-authenticated-private-registries.md b/content/en/docs/porch/using-porch/using-authenticated-private-registries.md index 432062ee..946e9e9e 100644 --- a/content/en/docs/porch/using-porch/using-authenticated-private-registries.md +++ b/content/en/docs/porch/using-porch/using-authenticated-private-registries.md @@ -88,4 +88,4 @@ command: ``` All of the `--enable-private-registry`, `--registry-auth-secret-path` and `--registry-auth-secret-name` arguments have default values of *false*, */var/tmp/auth-secret/.dockerconfigjson* and *auth-secret* respectively but should be overridden to enable the functionality and match user specifications. -With this last step, if your Porch package uses a custom kpt function image stored in an authenticated private registry (for example `- image: ghcr.io/private-registry/set-namespace:customv2`), the function runner will now use the secret info as an `imagePullSecret` for the function pods as documented [here](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). +With this last step, if your Porch package uses a custom kpt function image stored in an authenticated private registry (for example `- image: ghcr.io/private-registry/set-namespace:customv2`), the function runner will now use the secret info to replicate your secret on the `porch-fn-system` namespace and attach it as an `imagePullSecret` for the function pods as documented [here](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/).