From a03a001197ee79a7472dbce4a8cca293131f71a4 Mon Sep 17 00:00:00 2001 From: Meori Oransky Date: Sun, 12 Nov 2023 19:06:02 +0200 Subject: [PATCH] Update README.md typo fix --- charts/cbcontainers-agent/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/charts/cbcontainers-agent/README.md b/charts/cbcontainers-agent/README.md index 301b09d7..8b313bcc 100644 --- a/charts/cbcontainers-agent/README.md +++ b/charts/cbcontainers-agent/README.md @@ -44,7 +44,7 @@ To customize that namespace, see [operator-chart](../cbcontainers-operator). The actual namespace where helm tracks the release (see [--namespace flag](https://helm.sh/docs/helm/helm_install/)) is not important to the agent chart, but the recommended approach is to also use the same namespace as the operator chart. -The `agentNamespace` value is only required if the agent chart is responsible for deploying the agent's secret as well. See [secret detection](#secret-creation) for details. +The `agentNamespace` value is only required if the agent chart is responsible for deploying the agent's secret as well. See [secret creation](#secret-creation) for details. If the secret is pre-created before deploying the agent, then `agentNamespace` has no effect. ### Secret creation @@ -83,4 +83,4 @@ Inject this value as part of your pipeline in a secure way! This means storing the secret as plain text in your `values.yaml` file. -If you prefer to create the `Secret` yourself in an alternative and more secure way, don't set the `companyCode` value and the chart will not create the `Secret` objects. \ No newline at end of file +If you prefer to create the `Secret` yourself in an alternative and more secure way, don't set the `companyCode` value and the chart will not create the `Secret` objects.