Deployed 71ce80fef to main with MkDocs 1.6.1 and mike 1.2.0.dev0

main/contributing/release/index.html

@@ -3542,15 +3542,6 @@
     </span>
   </a>
   
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#release-olm-bundle" class="md-nav__link">
-    <span class="md-ellipsis">
-      Release OLM Bundle
-    </span>
-  </a>
-  
 </li>
       
     </ul>
@@ -3839,15 +3830,6 @@
     </span>
   </a>
   
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#release-olm-bundle" class="md-nav__link">
-    <span class="md-ellipsis">
-      Release OLM Bundle
-    </span>
-  </a>
-  
 </li>
       
     </ul>
@@ -3885,7 +3867,6 @@ Otherwise the <code>latest</code> documentation will point to the older version.
 </li>
 <li>GitHub Release, Changelog will be created by the <code>release.yml</code> workflow which also promotes the container image.</li>
 <li>update Helm Chart, see below</li>
-<li>update OLM bundle, see <a href="https://github.com/external-secrets/external-secrets-helm-operator/blob/main/docs/release.md#operatorhubio">helm-operator docs</a></li>
 </ol>
 <h2 id="release-helm-chart">Release Helm Chart</h2>
 <ol>
@@ -3900,31 +3881,6 @@ Otherwise the <code>latest</code> documentation will point to the older version.
 </ol>
 </li>
 </ol>
-<h2 id="release-olm-bundle">Release OLM Bundle</h2>
-<p>In order to make the latest release available to <a href="https://operatorhub.io/">OperatorHub.io</a> we need to create a bundle and open a PR in the <a href="https://github.com/k8s-operatorhub/community-operators/">community-operators</a> repository.</p>
-<p>To create a bundle first increment the <code>VERSION</code> in the Makefile as described above. Then run the following commands in the root of the repository:</p>
-<div class="highlight"><pre><span></span><code><span class="c1"># clone repo</span>
-git<span class="w"> </span>clone<span class="w"> </span>https://github.com/external-secrets/external-secrets-helm-operator
-<span class="nb">cd</span><span class="w"> </span>external-secrets-helm-operator
-
-<span class="c1"># bump version</span>
-<span class="nb">export</span><span class="w"> </span><span class="nv">VERSION</span><span class="o">=</span>x.y.z
-sed<span class="w"> </span>-i<span class="w"> </span><span class="s2">&quot;s/^VERSION ?= .*/VERSION ?= </span><span class="si">${</span><span class="nv">VERSION</span><span class="si">}</span><span class="s2">/&quot;</span><span class="w"> </span>Makefile
-
-<span class="c1"># prep release</span>
-make<span class="w"> </span>prepare-stable-release<span class="w"> </span><span class="nv">ATTACH_IMAGE_DIGESTS</span><span class="o">=</span><span class="m">0</span>
-</code></pre></div>
-<p>Check the generated files in the <code>bundle/</code> directory. If they look good add &amp; commit them, open a PR against this repository. You can always use the <a href="https://operatorhub.io/preview">OperatorHub.io/preview</a> page to preview the generated CSV.</p>
-<div class="highlight"><pre><span></span><code>git<span class="w"> </span>status
-git<span class="w"> </span>add<span class="w"> </span>.
-git<span class="w"> </span>commit<span class="w"> </span>-s<span class="w"> </span>-m<span class="w"> </span><span class="s2">&quot;chore: bump version xyz&quot;</span>
-git<span class="w"> </span>push
-</code></pre></div>
-<p>Once the PR is merged and the image build job on <code>main</code> has completed, we need create a pull request against both community-operators repositories. There's a make target that does the heavy lifting for you:
-<div class="highlight"><pre><span></span><code>make<span class="w"> </span>attach-image-digests
-make<span class="w"> </span>bundle-operatorhub
-</code></pre></div></p>
-<p>This command will add/commit/push and open pull requests in the respective repositories.</p>
 
 
 

main/introduction/getting-started/index.html

@@ -679,15 +679,6 @@
       </ul>
     </nav>
   
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#installing-with-olm" class="md-nav__link">
-    <span class="md-ellipsis">
-      Installing with OLM
-    </span>
-  </a>
-  
 </li>
       
         <li class="md-nav__item">
@@ -3951,15 +3942,6 @@
       </ul>
     </nav>
   
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#installing-with-olm" class="md-nav__link">
-    <span class="md-ellipsis">
-      Installing with OLM
-    </span>
-  </a>
-  
 </li>
       
         <li class="md-nav__item">
@@ -4111,8 +4093,6 @@ Events:<span class="w">                    </span>&lt;none&gt;
 </code></pre></div>
 <p>For more advanced examples, please read the other
 <a href="../../guides/introduction/">guides</a>.</p>
-<h2 id="installing-with-olm">Installing with OLM</h2>
-<p>External-secrets can be managed by <a href="https://olm.operatorframework.io/">Operator Lifecycle Manager</a> (OLM) via an installer operator. It is made available through <a href="https://operatorhub.io/">OperatorHub.io</a>, this installation method is suited best for OpenShift. See installation instructions on the <a href="https://operatorhub.io/operator/external-secrets-operator">external-secrets-operator</a> package.</p>
 <h2 id="uninstalling">Uninstalling</h2>
 <p>Before continuing, ensure that all external-secret resources that have been created by users have been deleted.
 You can check for any existing resources with the following command:</p>