From 387d6959e0761124becb35f71728809313783bef Mon Sep 17 00:00:00 2001 From: Catalin Stratulat Date: Mon, 18 Nov 2024 15:46:48 +0000 Subject: [PATCH] removed typo --- .../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 14bacfd1..e331eca4 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 @@ -106,7 +106,7 @@ You may specify your desired paths for each `mountPath:` so long as the function The chosen `mountPath:` should use its own, dedicated sub-directory, so that it does not overwrite access permissions of the existing directory. For example, if you wish to mount on `/var/tmp` you should use `mountPath: /var/tmp/` etc. {{% /alert %}} -TThe *--enable-private-registry-tls* and *--tls-secret-path* variables are only required if a private registry has TLS enabled. They indicate to the function runner that it should attempt authentication to the registry using TLS, and should use the TLS certificate information found on the path provided in *--tls-secret-path*. +The *--enable-private-registry-tls* and *--tls-secret-path* variables are only required if a private registry has TLS enabled. They indicate to the function runner that it should attempt authentication to the registry using TLS, and should use the TLS certificate information found on the path provided in *--tls-secret-path*. Lastly you must enable private registry functionality along with providing the path and name of the secret. Add the `--enable-private-registry`, `--registry-auth-secret-path` and `--registry-auth-secret-name` arguments to the function-runner Deployment object in the *2-function-runner.yaml* file: