DEV-955 operator v1.4.1 docs (#923)

Co-authored-by: Stephen Tung <[email protected]>

Author: rb-kurrent

docs/.vuepress/public/_redirects

@@ -270,6 +270,10 @@
 /server/v5/server/*         /server/v5/introduction.html    301
 /server/v5/streams/*        /server/v5/introduction.html    301
 
+# k8 Operator
+/server/kubernetes-operator/v1.3.0/*                             /server/kubernetes-operator/v1.3.1/:splat                     301
+/server/kubernetes-operator/v1.4.0/*                             /server/kubernetes-operator/v1.4.1/:splat                     301
+
 # ######################
 # Other
 # ######################

docs/server/kubernetes-operator/v1.4.0/README.md renamed to docs/server/kubernetes-operator/v1.4.1/README.md

@@ -1,5 +1,5 @@
 ---
 # title is for breadcrumb and sidebar nav
-title: Kubernetes Operator v1.4.0
+title: Kubernetes Operator v1.4.1
 order: 1
 ---

docs/server/kubernetes-operator/v1.4.0/getting-started/README.md renamed to docs/server/kubernetes-operator/v1.4.1/getting-started/README.md

@@ -46,6 +46,16 @@ Kubernetes is the modern enterprise standard for deploying containerized applica
 [ror]: ../operations/database-deployment.md#deploying-standalone-read-only-replicas
 [em]: resource-types.md#kurrentdbextrametadataspec
 
+### New in 1.4.1
+
+* Fix rolling restarts to be quorum-aware for extra data safety.
+* Add quorum-aware full restarts for changes that must be applied to all nodes at once, like adding
+  TLS.
+* Fix the `internodeTrafficStrategy: SplitDNS` setting to run correctly on more container runtimes.
+* Fix a hang caused adding to pod labels in `extraMetadata` after a KurrentDB was deployed.
+* Correctly enforce the immutability of the `sourceBackup` setting to prevent confusing behavior.
+* Fix the helm chart to prevent allowing two operator instances to briefly conflict during upgrades.
+
 ## Supported KurrentDB Versions
 
 The Operator supports running the following major versions of KurrentDB:

docs/server/kubernetes-operator/v1.4.0/getting-started/images/install/deployments-list.png renamed to docs/server/kubernetes-operator/v1.4.1/getting-started/images/install/deployments-list.png

@@ -53,7 +53,7 @@ If you prefer to install CRDs yourself:
 
 ```bash
 # Download the kurrentdb-operator Helm chart
-helm pull kurrent-latest/kurrentdb-operator --version 1.4.0 --untar
+helm pull kurrent-latest/kurrentdb-operator --version 1.4.1 --untar
 # Install the CRDs
 kubectl apply -f kurrentdb-operator/templates/crds
 ```
@@ -87,7 +87,7 @@ To deploy the Operator in this mode, run:
 
 ```bash
 helm install kurrentdb-operator kurrent-latest/kurrentdb-operator \
-  --version 1.4.0 \
+  --version 1.4.1 \
   --namespace kurrent \
   --create-namespace \
   --set crds.enabled=true \
@@ -122,7 +122,7 @@ To deploy the Operator in this mode, the following command can be used:
 
 ```bash
 helm install kurrentdb-operator kurrent-latest/kurrentdb-operator \
-  --version 1.4.0 \
+  --version 1.4.1 \
   --namespace kurrent \
   --create-namespace \
   --set crds.enabled=true \
@@ -161,7 +161,7 @@ The Operator deployment can be updated to adjust which namespaces are watched. F
 
 ```bash
 helm upgrade kurrentdb-operator kurrent-latest/kurrentdb-operator \
-  --version 1.4.0 \
+  --version 1.4.1 \
   --namespace kurrent \
   --reuse-values \
   --set operator.namespaces='{kurrent,foo,bar}'
@@ -205,5 +205,5 @@ helm upgrade kurrentdb-operator kurrentdb-operator-repo/kurrentdb-operator \
 Here's what these commands do:
 - Refresh the local Helm repository index
 - Locate an existing operator installation in namespace `kurrent`
-- Select the target upgrade version `{version}` e.g. `1.4.0`
+- Select the target upgrade version `{version}` e.g. `1.4.1`
 - Perform the upgrade, preserving values that were set during installation