Deployed f38bccd3e to main with MkDocs 1.6.1 and mike 1.2.0.dev0

main/api/components/index.html

@@ -3953,7 +3953,7 @@
 
 <h1 id="components">Components</h1>
 <h2 id="overview">Overview</h2>
-<p>Exernal Secrets comes with three components: <code>Core Controller</code>, <code>Webhook</code> and <code>Cert Controller</code>.</p>
+<p>External Secrets comes with three components: <code>Core Controller</code>, <code>Webhook</code> and <code>Cert Controller</code>.</p>
 <p>This is due to the need to implement conversion webhooks in order to convert custom resources between api versions and
 to provide a ValidatingWebhook for the <code>ExternalSecret</code> and <code>SecretStore</code> resources.</p>
 <p>These features are optional but highly recommended. You can disable them with helm chart values <code>certController.create=false</code>, <code>webhook.create=false</code> and <code>crds.conversion.enabled=false</code>.</p>

main/api/controller-options/index.html

@@ -4106,7 +4106,7 @@
 <th>Name</th>
 <th>Type</th>
 <th>Default</th>
-<th>Descripton</th>
+<th>Description</th>
 </tr>
 </thead>
 <tbody>

main/api/generator/mfa/index.html

@@ -4030,7 +4030,7 @@ timeLeft: 25
 <p class="admonition-title">Usage of the token might fail on first try if it JUST expired</p>
 </div>
 <p>It is possible that from requesting the token to actually using it, the token might be already out of date if timeLeft was
-very low to begin with. Therefor, the code that uses this token should allow for retries with new tokens.</p>
+very low to begin with. Therefore, the code that uses this token should allow for retries with new tokens.</p>
 
 
 

main/api/metrics/index.html

@@ -4143,7 +4143,7 @@ This failure may cascade down to the controller or any other user of <code>kube-
 )
 </code></pre></div></p>
 <h4 id="controller-reconcile-error">Controller Reconcile Error</h4>
-<p>The controller should be able to reconcile resources without errors. When errors occurr secret delivery may be impacted which could cascade down to the secret consuming applications.</p>
+<p>The controller should be able to reconcile resources without errors. When errors occur secret delivery may be impacted which could cascade down to the secret consuming applications.</p>
 <div class="highlight"><pre><span></span><code>sum(increase(
   controller_runtime_reconcile_total{service=~&quot;external-secrets.*&quot;,controller=~&quot;$controller&quot;,result=&quot;error&quot;}[1m])
 ) by (result)

main/contributing/release/index.html

@@ -3951,7 +3951,7 @@ Otherwise the <code>latest</code> documentation will point to the older version.
 <li>Update <code>version</code> and/or <code>appVersion</code> in <code>Chart.yaml</code> and run <code>make helm.docs helm.update.appversion helm.test.update helm.test</code></li>
 <li>push to branch and open pr</li>
 <li>run <code>/ok-to-test-managed</code> commands for all cloud providers</li>
-<li>merge PR if everyhing is green</li>
+<li>merge PR if everything is green</li>
 <li>CI picks up the new chart version and creates a new GitHub Release for it</li>
 <li>create/merge into release branch<ol>
 <li>on a <code>minor</code> release: create a new branch <code>release-x.y</code></li>

main/eso-blogs/index.html

@@ -4273,7 +4273,7 @@ set up a local environment with Docker Desktop and how to deploy ESO and Conjur
 <h2 id="comparing-external-secrets-operator-with-secret-storage-csi-as-kubernetes-external-secrets-is-deprecated"><a href="https://mixi-developers.mixi.co.jp/compare-eso-with-secret-csi-402bf37f20bc">Comparing External Secrets Operator with Secret Storage CSI as Kubernetes External Secrets is Deprecated</a></h2>
 <p>@riddle writes about choosing ESO when comparing with Secret Store CSI Driver in their specific use case. They show us the relevant differences between the projects when looking at their scenario and requirements while integrating with ArgoCD. <a href="https://mixi-developers.mixi.co.jp/compare-eso-with-secret-csi-402bf37f20bc">Comparing External Secrets Operator with Secret Storage CSI as Kubernetes External Secrets is Deprecated</a></p>
 <h2 id="tutorial-getting-started-with-external-secrets-operator-on-kubernetes-using-aws-secrets-manager"><a href="https://ptuladhar3.medium.com/getting-started-with-external-secrets-operator-on-kubernetes-using-aws-secrets-manager-6dc403d9630c">Tutorial: Getting Started with External Secrets Operator on Kubernetes using AWS Secrets Manager</a></h2>
-<p>Puru writes about getting started using ESO with AWS Secrets Manager. He uses illustrations to explain ESO to new users and get's you to quickly start using ESO, as article is easy to follow along. <a href="https://ptuladhar3.medium.com/getting-started-with-external-secrets-operator-on-kubernetes-using-aws-secrets-manager-6dc403d9630c">Getting Started with External Secrets Operator on Kubernetes using AWS Secrets Manager</a></p>
+<p>Puru writes about getting started using ESO with AWS Secrets Manager. He uses illustrations to explain ESO to new users and gets you to quickly start using ESO, as article is easy to follow along. <a href="https://ptuladhar3.medium.com/getting-started-with-external-secrets-operator-on-kubernetes-using-aws-secrets-manager-6dc403d9630c">Getting Started with External Secrets Operator on Kubernetes using AWS Secrets Manager</a></p>
 <h2 id="tutorial-how-to-set-external-secrets-with-azure-keyvault"><a href="https://blog.container-solutions.com/tutorial-external-secrets-with-azure-keyvault">Tutorial: How to Set External-Secrets with Azure KeyVault</a></h2>
 <p>Gustavo writes about how to setup ESO with Azure Key Vault and adds an guide on how to make it a bit more secure with OPA (Open Policy Agent). <a href="https://blog.container-solutions.com/tutorial-external-secrets-with-azure-keyvault">How to Set External-Secrets with Azure KeyVault</a></p>
 <h2 id="tutorial-how-to-set-external-secrets-with-gcp-secret-manager"><a href="https://blog.container-solutions.com/tutorial-how-to-set-external-secrets-with-gcp-secret-manager">Tutorial: How to Set External-Secrets with GCP Secret Manager</a></h2>
@@ -4297,7 +4297,7 @@ set up a local environment with Docker Desktop and how to deploy ESO and Conjur
 <h2 id="reversing-the-workflow-with-external-secrets-operators-push-secret-feature"><a href="https://medium.com/@eminalemdar/reversing-the-workflow-with-external-secrets-operators-push-secret-feature-f2a64f3db748">Reversing the Workflow with External Secrets Operator’s Push Secret Feature</a></h2>
 <p>Emin writes about the Push Secret feature of ESO and how this new feature reverse the workflow of ESO by pushing Kubernetes secrets to external secret management providers.</p>
 <h2 id="gcp-secret-manager-with-self-hosted-kubernetes"><a href="https://medium.com/@jjlakis/gcp-secret-manager-with-self-hosted-kubernetes-db35d01d65f0">GCP Secret Manager with self-hosted Kubernetes</a></h2>
-<p>Jacek writes about bringing GCP secrets to on-premises cluster through External Secrets Operator intergration with workload identity.</p>
+<p>Jacek writes about bringing GCP secrets to on-premises cluster through External Secrets Operator integration with workload identity.</p>
 <h2 id="injecting-aws-secrets-in-a-kubernetes-cluster-with-external-secrets-operator"><a href="https://blog.devops.dev/injecting-external-secrets-in-a-kubernetes-cluster-1e9bbe0f0d5b">Injecting AWS Secrets in a Kubernetes Cluster with External Secrets Operator</a></h2>
 <p>Ali writes about integrating AWS Secrets Manager and Parameter Store secrets within an EKS Cluster using ESO. He shows a quick setup of the operator, and how to fetch secrets in a repeatable fashion. The guide is bundled with cool illustrations and code snippets that describe the ESO architecture and injection process</p>
 <h2 id="encoding-decoding-kubernetes-secrets-eso-advanced-templating"><a href="https://blog.devops.dev/encoding-decoding-kubernetes-secrets-externalsecrets-operator-826b9680df63">Encoding &amp; Decoding Kubernetes Secrets — ESO Advanced Templating</a></h2>

main/guides/all-keys-one-secret/index.html

@@ -3939,16 +3939,16 @@
 <span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">extract</span><span class="p">:</span>
 <span class="w">      </span><span class="nt">key</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">all-keys-example-secret</span><span class="w">  </span><span class="c1"># name of the GCPSM secret</span>
 </code></pre></div>
-Here, "example" is the name of the external secret that will be created in our cluster.  <br />
-Whereas, "secret-to-be-created" is the name of Kubernetes secrets that will be created.  <br />
-Note: Since these secrets are namespace-based resources, you can also explicitly specify the "namespace" under the "metadata" block of the above external secret file.  <br />
-when we use, </p>
+Here, "example" is the name of the external secret that will be created in our cluster.
+Whereas, "secret-to-be-created" is the name of Kubernetes secrets that will be created.
+Note: Since these secrets are namespace-based resources, you can also explicitly specify the "namespace" under the "metadata" block of the above external secret file.
+when we use,</p>
 <p><div class="highlight"><pre><span></span><code>  dataFrom:
   - extract:
       key: all-keys-example-secret
 </code></pre></div>
-We get all the key-value pairs present over the remote secret store (GCP or AWS or Azure) and can pass either all or a few key-values as environment variables.  <br />
-Please note that, "all-keys-example-secret" is the name of your secret present on GCP/AWS secrets manager/Azure    </p>
+We get all the key-value pairs present over the remote secret store (GCP or AWS or Azure) and can pass either all or a few key-values as environment variables.
+Please note that, "all-keys-example-secret" is the name of your secret present on GCP/AWS secrets manager/Azure</p>
 <p>We can pass a few secrets as env variables as below:
 <div class="highlight"><pre><span></span><code>        env:
           - name: key1
@@ -3963,15 +3963,15 @@ Please note that, "all-keys-example-secret" is the name of your secret present o
                 name: secret-to-be-created
                 key: surname
 </code></pre></div></p>
-<p>Here,  <br />
-\&lt;key1&gt; and \<key2> are the names of keys that will be created and passed as env variables.  <br />
-\&lt;secret-to-be-created&gt;: is the name of your Kubernetes secret created by you.  <br />
-\&lt;username&gt; and \<surname>: is the particular key in the secrets manager whose value you want to pass.  <br />
+<p>Here,
+\&lt;key1&gt; and \<key2> are the names of keys that will be created and passed as env variables.
+\&lt;secret-to-be-created&gt;: is the name of your Kubernetes secret created by you.
+\&lt;username&gt; and \<surname>: is the particular key in the secrets manager whose value you want to pass.
 To check both values we can run:
 <div class="highlight"><pre><span></span><code>kubectl get secret secret-to-be-created -n &lt;namespace&gt; -o jsonpath=&#39;{.data.username}&#39; | base64 -d
 kubectl get secret secret-to-be-created -n &lt;namespace&gt; -o jsonpath=&#39;{.data.surname}&#39; | base64 -d
 </code></pre></div></p>
-<p>Also, if you have a large number of secrets and you want to pass all of them as enviromnent variables, then either you can replicate the above steps in your deployment file for all the keys or you can use the envFrom block as below:    </p>
+<p>Also, if you have a large number of secrets and you want to pass all of them as environment variables, then either you can replicate the above steps in your deployment file for all the keys or you can use the envFrom block as below:</p>
 <div class="highlight"><pre><span></span><code>    spec:
       containers:
       - command:

main/guides/generator/index.html

@@ -3933,7 +3933,7 @@
 <p>If the External Secret should be refreshed via <code>spec.refreshInterval</code> the generator produces a map of values with the <code>generator.spec</code> as input. The generator does not keep track of the produced values. Every invocation produces a new set of values.</p>
 <p>These values can be used with the other features like <code>rewrite</code> or <code>template</code>. I.e. you can modify, encode, decode, pack the values as needed.</p>
 <h2 id="reference-custom-resource">Reference Custom Resource</h2>
-<p>Generators can be defined as a custom resource and re-used across different ExternalSecrets. <strong>Every invocation creates a new set of values</strong>. I.e. you can not share the same value produced by a generator across different <code>ExternalSecrets</code> or <code>spec.dataFrom[]</code> entries.</p>
+<p>Generators can be defined as a custom resource and reused across different ExternalSecrets. <strong>Every invocation creates a new set of values</strong>. I.e. you can not share the same value produced by a generator across different <code>ExternalSecrets</code> or <code>spec.dataFrom[]</code> entries.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">external-secrets.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">ExternalSecret</span>
 <span class="nt">metadata</span><span class="p">:</span>

main/guides/getallsecrets/index.html

@@ -4023,7 +4023,7 @@ This will match any secrets containing all of the metadata labels in the <code>t
 <h3 id="avoiding-name-conflicts">Avoiding name conflicts</h3>
 <p>By default, kubernetes Secrets accepts only a given range of characters. <code>Find</code> operations will automatically replace any not allowed character with a <code>_</code>. So if we have a given secret <code>a_c</code> and <code>a/c</code> would lead to a naming conflict.</p>
 <p>If you happen to have a case where a conflict is happening, you can use the <code>rewrite</code> block to apply a regexp on one of the find operations (for more information please refer to <a href="../datafrom-rewrite/">Rewriting Keys from DataFrom</a>).</p>
-<p>You can also set  <code>dataFrom.find.conversionStrategy: Unicode</code> to reduce the collistion probability. When using <code>Unicode</code>, any invalid character will be replaced by its unicode, in the form of <code>_UXXXX_</code>. In this case, the available kubernetes keys would be <code>a_c</code> and <code>a_U2215_c</code>, hence avoiding most of possible conflicts.</p>
+<p>You can also set  <code>dataFrom.find.conversionStrategy: Unicode</code> to reduce the collision probability. When using <code>Unicode</code>, any invalid character will be replaced by its unicode, in the form of <code>_UXXXX_</code>. In this case, the available kubernetes keys would be <code>a_c</code> and <code>a_U2215_c</code>, hence avoiding most of possible conflicts.</p>
 <div class="admonition note">
 <p class="admonition-title">PRs welcome</p>
 <p>Some providers might not have the implementation needed for fetching multiple secrets. If that's your case, please feel free to contribute!</p>

main/guides/templating/index.html

@@ -4435,7 +4435,7 @@ NtFUGA95RGN9s+pl6XY0YARPHf5O76ErC1OZtDTR5RdyQfcM+94gYZsexsXl0aQO
 <span class="w">        </span><span class="nt">tls.crt</span><span class="p">:</span><span class="w"> </span><span class="s">&quot;{{</span><span class="nv"> </span><span class="s">.mysecret</span><span class="nv"> </span><span class="s">|</span><span class="nv"> </span><span class="s">filterPEM</span><span class="nv"> </span><span class="s">&quot;</span><span class="l l-Scalar l-Scalar-Plain">CERTIFICATE&quot; }}&quot;</span>
 <span class="w">        </span><span class="nt">tls.key</span><span class="p">:</span><span class="w"> </span><span class="s">&quot;{{</span><span class="nv"> </span><span class="s">.mysecret</span><span class="nv"> </span><span class="s">|</span><span class="nv"> </span><span class="s">filterPEM</span><span class="nv"> </span><span class="s">&quot;</span><span class="l l-Scalar l-Scalar-Plain">PRIVATE KEY&quot; }}&quot;</span>
 </code></pre></div>
-<p>In case you have a secret that contains a (partial) certificate chain you can extract the <code>leaf</code>, <code>intermediate</code> or <code>root</code> certificate(s) using the <code>filterCertChain</code> function. See the following example on how to use the <code>filterPEM</code> and <code>filterCertChain</code> functions together to split the certificate chain into a <code>tls.crt</code> part only containting the leaf certificate and a <code>ca.crt</code> part with all the intermediate certificates.</p>
+<p>In case you have a secret that contains a (partial) certificate chain you can extract the <code>leaf</code>, <code>intermediate</code> or <code>root</code> certificate(s) using the <code>filterCertChain</code> function. See the following example on how to use the <code>filterPEM</code> and <code>filterCertChain</code> functions together to split the certificate chain into a <code>tls.crt</code> part only containing the leaf certificate and a <code>ca.crt</code> part with all the intermediate certificates.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">external-secrets.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">ExternalSecret</span>
 <span class="nt">metadata</span><span class="p">:</span>

main/guides/using-esoctl-tool/index.html

@@ -3898,7 +3898,7 @@ template-test/
 <p>And secret data is:</p>
 <div class="highlight"><pre><span></span><code><span class="nt">token</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">dG9rZW4=</span>
 </code></pre></div>
-<p>Therefor if there is a PushSecret or an ExternalSecret object that the user would like to test the template for,
+<p>Therefore if there is a PushSecret or an ExternalSecret object that the user would like to test the template for,
 simply put it into a file along with the data it's using, and run this command.</p>
 <p>The output will be something like this:</p>
 <div class="highlight"><pre><span></span><code>bin/esoctl template --source-templated-object template-test/push-secret.yaml --source-secret-data-file template-test/secret.yaml

main/provider/1password-automation/index.html

@@ -4319,7 +4319,7 @@ by 1Password. It's feature complete and has parity with this provider's capabili
 <li>Ordered vaults<ul>
 <li>Specify an ordered list of vaults in a SecretStore and the value will be sourced from the first vault with a matching Item.</li>
 <li>If no matching Item is found, an error is returned.</li>
-<li>This supports having a default or shared set of values that can also be overriden for specific environments.</li>
+<li>This supports having a default or shared set of values that can also be overridden for specific environments.</li>
 </ul>
 </li>
 <li><code>dataFrom</code>:<ul>

main/provider/hashicorp-vault/index.html

@@ -4673,7 +4673,7 @@ trade-offs. Depending on the authentication method you need to adapt your enviro
 <strong>NOTE:</strong> In case of a <code>ClusterSecretStore</code>, Be sure to provide <code>namespace</code> in <code>tokenSecretRef</code> with the namespace where the secret resides.</p>
 <h4 id="approle-authentication-example">AppRole authentication example</h4>
 <p><a href="https://www.vaultproject.io/docs/auth/approle">AppRole authentication</a> reads the secret id from a
-<code>Kind=Secret</code> and uses the specified <code>roleId</code> to aquire a temporary token to fetch secrets.</p>
+<code>Kind=Secret</code> and uses the specified <code>roleId</code> to acquire a temporary token to fetch secrets.</p>
 <p><div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">external-secrets.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">SecretStore</span>
 <span class="nt">metadata</span><span class="p">:</span>

main/provider/openbao/index.html

@@ -3914,7 +3914,7 @@
 <h2 id="openbao">OpenBao</h2>
 <p>External Secrets Operator integrates with <a href="https://openbao.org">OpenBao</a> for secret management by using the <a href="../hashicorp-vault/">HashiCorp Vault Provider</a>.</p>
 <p>The integration was tested with <a href="https://github.com/external-secrets/external-secrets/releases/tag/v0.16.1">External Secrets Operator v0.16.1</a> and <a href="https://github.com/openbao/openbao/releases/tag/v2.2.0">OpenBao v2.2.0</a></p>
-<p>Please refer to the <a href="../hashicorp-vault/">HashiCorp Vault Provider</a> documentation for further informations.</p>
+<p>Please refer to the <a href="../hashicorp-vault/">HashiCorp Vault Provider</a> documentation for further information.</p>
 
 
 

main/provider/oracle-vault/index.html

@@ -4125,7 +4125,7 @@ The private key and fingerprint must be supplied in a Kubernetes secret, while t
 <img alt="tenancyOCID-details" src="../../pictures/screenshot_tenancy_OCID.png" /></p>
 <p>Select your user in the top right to see your user OCID as shown below.
 <img alt="region-details" src="../../pictures/screenshot_user_OCID.png" /></p>
-<p>Your fingerprint will be attatched to your API key, once it has been generated. Private keys can be created or uploaded on the same page as the your user OCID.
+<p>Your fingerprint will be attached to your API key, once it has been generated. Private keys can be created or uploaded on the same page as the your user OCID.
 <img alt="fingerprint-details" src="../../pictures/screenshot_fingerprint.png" /></p>
 <p>Once you click "Add API Key" you will be shown the following, where you can download the key in the necessary PEM format for API requests. Creating a private key will automatically generate a fingerprint.
 <img alt="API-key-details" src="../../pictures/screenshot_API_key.png" /></p>
@@ -4237,7 +4237,7 @@ The private key and fingerprint must be supplied in a Kubernetes secret, while t
 </code></pre></div></p>
 <h2 id="pushsecrets-and-retrieving-multiple-secrets">PushSecrets and retrieving multiple secrets.</h2>
 <p>When using <a href="https://external-secrets.io/latest/guides/pushsecrets/">PushSecrets</a>, the compartment OCID and encryption key OCID must be specified in the
-Oracle SecretStore. You can find your compartment and encrpytion key OCIDs in the OCI console.</p>
+Oracle SecretStore. You can find your compartment and encryption key OCIDs in the OCI console.</p>
 <p>If <a href="https://external-secrets.io/latest/guides/getallsecrets/">retrieving multiple secrets</a> by tag or regex, only the compartment OCID must be specified.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">external-secrets.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">SecretStore</span>