Release Coherence Operator snapshot docs 3.4.1

docs/snapshot/main/config.js

@@ -1,9 +1,9 @@
 function createConfig() {
     return {
         home: "docs/about/01_overview",
-        release: "3.4.0",
+        release: "3.4.1",
         releases: [
-            "3.4.0"
+            "3.4.1"
         ],
         pathColors: {
             "*": "blue-grey"

docs/snapshot/pages/docs/about/03_quickstart.js

@@ -32,7 +32,7 @@ to install a simple Coherence cluster.</p>
 <markup
 lang="bash"
 
->kubectl apply -f https://github.com/oracle/coherence-operator/releases/download/v3.4.0/coherence-operator.yaml</markup>
+>kubectl apply -f https://github.com/oracle/coherence-operator/releases/download/v3.4.1/coherence-operator.yaml</markup>
 
 <p>This will create a namespace called <code>coherence</code> and install the Operator into it along with all the required <code>ClusterRole</code> and <code>RoleBinding</code> resources. The <code>coherence</code> namespace can be changed by downloading and editing the yaml file.</p>
 

docs/snapshot/pages/docs/installation/01_installation.js

@@ -8,7 +8,7 @@
 <v-card-text>
 <dl>
 <dt slot=title>Coherence Operator Installation</dt>
-<dd slot="desc"><p>The Coherence Operator is available as an image from the GitHub container registry <code>ghcr.io/oracle/coherence-operator:3.4.0</code> that can
+<dd slot="desc"><p>The Coherence Operator is available as an image from the GitHub container registry <code>ghcr.io/oracle/coherence-operator:3.4.1</code> that can
 easily be installed into a Kubernetes cluster.</p>
 </dd>
 </dl>
@@ -192,15 +192,15 @@ for more details if you have well-known-address issues when Pods attempt to form
 
 <ul class="ulist">
 <li>
-<p><code>ghcr.io/oracle/coherence-operator:3.4.0</code> - The Operator image.</p>
+<p><code>ghcr.io/oracle/coherence-operator:3.4.1</code> - The Operator image.</p>
 
 </li>
 </ul>
 <p>If no image is specified in the <code>Coherence</code> yaml, then the default Coherence image will also be used,</p>
 
 <ul class="ulist">
 <li>
-<p><code>ghcr.io/oracle/coherence-ce:22.06.8</code> - The default Coherence image.</p>
+<p><code>ghcr.io/oracle/coherence-ce:22.06.9</code> - The default Coherence image.</p>
 
 </li>
 </ul>
@@ -259,7 +259,7 @@ Operators trying to remove finalizers and delete a Coherence cluster.</p>
 <markup
 lang="bash"
 
->kubectl apply -f https://github.com/oracle/coherence-operator/releases/download/v3.4.0/coherence-operator.yaml</markup>
+>kubectl apply -f https://github.com/oracle/coherence-operator/releases/download/v3.4.1/coherence-operator.yaml</markup>
 
 <p>This will create a namespace called <code>coherence</code> and install the Operator into it along with all the required <code>ClusterRole</code> and <code>RoleBinding</code> resources. The <code>coherence</code> namespace can be changed by downloading and editing the yaml file.</p>
 
@@ -349,15 +349,15 @@ lang="bash"
 
 <h3 id="helm-operator-image">Set the Operator Image</h3>
 <div class="section">
-<p>The Helm chart uses a default Operator image from <code>ghcr.io/oracle/coherence-operator:3.4.0</code>.
+<p>The Helm chart uses a default Operator image from <code>ghcr.io/oracle/coherence-operator:3.4.1</code>.
 If the image needs to be pulled from a different location (for example an internal registry) then there are two ways to override the default.
 Either set the individual <code>image.registry</code>, <code>image.name</code> and <code>image.tag</code> values, or set the whole image name by setting the <code>image</code> value.</p>
 
 <p>For example, if the Operator image has been deployed into a private registry named <code>foo.com</code> but
-with the same image name <code>coherence-operator</code> and tag <code>3.4.0</code> as the default image,
+with the same image name <code>coherence-operator</code> and tag <code>3.4.1</code> as the default image,
 then just the <code>image.registry</code> needs to be specified.</p>
 
-<p>In the example below, the image used to run the Operator will be <code>foo.com/coherence-operator:3.4.0</code>.</p>
+<p>In the example below, the image used to run the Operator will be <code>foo.com/coherence-operator:3.4.1</code>.</p>
 
 <markup
 lang="bash"
@@ -965,11 +965,11 @@ using a standalone Carvel <a id="" title="" target="_blank" href="https://carvel
 
 <ul class="ulist">
 <li>
-<p><code>ghcr.io/oracle/coherence-operator-package:3.4.0</code> - the Coherence Operator package</p>
+<p><code>ghcr.io/oracle/coherence-operator-package:3.4.1</code> - the Coherence Operator package</p>
 
 </li>
 <li>
-<p><code>ghcr.io/oracle/coherence-operator-repo:3.4.0</code> - the Coherence Operator repository</p>
+<p><code>ghcr.io/oracle/coherence-operator-repo:3.4.1</code> - the Coherence Operator repository</p>
 
 </li>
 </ul>

docs/snapshot/pages/docs/installation/07_webhooks.js

@@ -64,7 +64,7 @@ re-start until the <code>Secret</code> has been created.</p>
 <markup
 lang="bash"
 
->curl -L https://github.com/oracle/coherence-operator/releases/download/v3.4.0/coherence-operator.yaml \
+>curl -L https://github.com/oracle/coherence-operator/releases/download/v3.4.1/coherence-operator.yaml \
     -o coherence-operator.yaml
 sed -i s/self-signed/cert-manager/g coherence-operator.yaml
 kubectl apply -f coherence-operator.yaml</markup>

docs/snapshot/pages/docs/installation/09_RBAC.js

@@ -46,7 +46,7 @@
 <p ><p>Before installing the Operator, with either method described below, the CRDs MUST be manually installed from the Operator manifest files.</p>
 
 <p>The manifest files are published with the GitHub release at this link:
-<a id="" title="" target="_blank" href="https://github.com/oracle/coherence-operator/releases/download/v3.4.0/coherence-operator-manifests.tar.gz">3.3.5 Manifests</a></p>
+<a id="" title="" target="_blank" href="https://github.com/oracle/coherence-operator/releases/download/v3.4.1/coherence-operator-manifests.tar.gz">3.3.5 Manifests</a></p>
 
 <p>You MUST ensure that the CRD manifests match the version of the Operator being installed.</p>
 

docs/snapshot/pages/docs/metrics/020_metrics.js

@@ -24,7 +24,7 @@ documentation for full details on the available metrics.</p>
 
 <h3 id="_important_note_regarding_prometheus_metrics_prefix">Important Note Regarding Prometheus Metrics Prefix</h3>
 <div class="section">
-<p>From version 3.4.0 of the Coherence Operator, the packaged Grafana dashboards no longer use the <strong>vendor:</strong> prefix for querying Prometheus metrics.
+<p>From version 3.4.1 of the Coherence Operator, the packaged Grafana dashboards no longer use the <strong>vendor:</strong> prefix for querying Prometheus metrics.
 This prefix was deprecated a number of releases ago and the default, of legacy metrics, in Coherence and will be removed in the most recent
 Coherence releases after this Operator release.</p>
 

docs/snapshot/pages/docs/other/041_global_labels.js

@@ -155,7 +155,7 @@ one global annotation <code>foo=bar</code>.</p>
 by manually editing the yaml file before installing.</p>
 
 <p>Download the yaml manifest file from the GitHub repo
-<a id="" title="" target="_blank" href="https://github.com/oracle/coherence-operator/releases/download/v3.4.0/coherence-operator.yaml">https://github.com/oracle/coherence-operator/releases/download/v3.4.0/coherence-operator.yaml</a></p>
+<a id="" title="" target="_blank" href="https://github.com/oracle/coherence-operator/releases/download/v3.4.1/coherence-operator.yaml">https://github.com/oracle/coherence-operator/releases/download/v3.4.1/coherence-operator.yaml</a></p>
 
 <p>Find the section of the yaml file the defines the Operator container args, the default looks like this</p>
 

docs/snapshot/pages/examples/015_simple_image/README.js

@@ -94,7 +94,7 @@ title="pom.xml"
             <plugin>
                 <groupId>com.google.cloud.tools</groupId>
                 <artifactId>jib-maven-plugin</artifactId>
-                <version>3.4.0</version>
+                <version>3.4.1</version>
             </plugin>
         </plugins>
     &lt;/build&gt;</markup>

docs/snapshot/pages/examples/095_network_policies/README.js

@@ -1223,7 +1223,7 @@ spec:
     spec:
       containers:
       - name: net-test
-        image: ghcr.io/oracle/coherence-operator:3.4.0
+        image: ghcr.io/oracle/coherence-operator:3.4.1
         env:
           - name: HOST
             value: net-test-coherence-server.coh-test.svc

docs/snapshot/pages/examples/300_helm/README.js

@@ -186,8 +186,8 @@ spec:
 <markup
 lang="bash"
 
->docker pull ghcr.io/oracle/coherence-operator:3.4.0
-docker run -it --rm ghcr.io/oracle/coherence-operator:3.4.0 status -h</markup>
+>docker pull ghcr.io/oracle/coherence-operator:3.4.1
+docker run -it --rm ghcr.io/oracle/coherence-operator:3.4.1 status -h</markup>
 
 <p>By creating a K8s Job that runs the status command we can query the Operator for the status of the Coherence resource we installed from the Helm chart. Of course, we could have written something similar that used kubectl in the Job or similar to query k8s for the state of the Coherence resource, but this becomes more complex in RBAC enabled cluster. Querying the simple REST endpoint of the Coherence Operator does not require RBAC rules for the Job to execute.</p>
 
@@ -241,7 +241,7 @@ operator:
   namespace: coherence
   service: coherence-operator-rest
   port: 8000
-  image: ghcr.io/oracle/coherence-operator-utils:3.4.0
+  image: ghcr.io/oracle/coherence-operator-utils:3.4.1
   condition: Ready
   timeout: 5m
   interval: 10s</markup>

docs/snapshot/pages/examples/400_Istio/README.js

@@ -3,7 +3,7 @@
 <h2 id="_using_coherence_with_istio">Using Coherence with Istio</h2>
 <div class="section">
 <p>You can run the Coherence cluster and manage them using the Coherence Operator alongside <a id="" title="" target="_blank" href="https://istio.io">Istio</a>.
-Coherence clusters managed with the Coherence Operator 3.4.0 and later work with Istio 1.9.1 and later out of the box.
+Coherence clusters managed with the Coherence Operator 3.4.1 and later work with Istio 1.9.1 and later out of the box.
 Coherence caches can be accessed from outside the Coherence cluster via Coherence*Extend, REST, and other supported
 Coherence clients.
 Using Coherence clusters with Istio does not require the Coherence Operator to also be using Istio (and vice-versa) .

docs/snapshot/pages/examples/no-operator/04_istio/README.js

@@ -502,7 +502,7 @@ Various utilities are copied from the Operator image into the base.</p>
 <markup
 
 title="Dockerfile"
->FROM ghcr.io/oracle/coherence-operator:3.4.0 AS Builder
+>FROM ghcr.io/oracle/coherence-operator:3.4.1 AS Builder
 
 FROM ghcr.io/oracle/coherence-ce:22.06.7
 COPY --from=Builder /files /files