v1.3.0 docs content (#911)

Author: rb-kurrent

docs/server/kubernetes-operator/v1.3.0/README.md

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

docs/server/kubernetes-operator/v1.3.0/getting-started/README.md

@@ -25,9 +25,23 @@ Kubernetes is the modern enterprise standard for deploying containerized applica
 * Back up and restore clusters
 * Perform rolling upgrades and update configurations
 
-### New in 1.2.0
-
-* Configure the advertised FQDN with a template. See the [docs](resource-types.md#kurrentdbnetwork).
+### New in 1.3.0
+
+* Fixed/improved support for resizing KurrentDB clusters, including explicitly handling data safety,
+  minimizing downtime, and allowing the user to cancel a resize operation that is not progressing.
+  See [Updating Replica Count](../operations/modify-deployments.md#updating-replica-count) for details.
+* Support for custom labels and annotations on all child resources (StatefulSets, Pods,
+  LoadBalancers, etc).
+* Allow users to use public certificate authorities like LetsEcrypt without having to manually pass
+  the publicly trusted cert in a secret.
+* Allow manual overrides to the generated ConfigMap that is passed to KurrentDB.  Previously, if a
+  user manually altered the ConfigMap it would get immediately overwritten, where as now it will
+  "stick" until the next time the KurrentDB resources is updated.
+* Fix a bug affecting the KurrentDBBackup behavior when cluster's fqdnTemplate met certain criteria.
+* Fixed and clarified the `credentialsSecretName` behavior in the helm chart.  It is not normally
+  required at all, but in previous versions, it was generating warning events in the default
+  configuration.
+* Updated helm chart to support the normal `--skip-crds` mechanism.
 
 ## Supported KurrentDB Versions
 

docs/server/kubernetes-operator/v1.3.0/getting-started/installation.md

@@ -15,12 +15,12 @@ The Operator is an Enterprise only feature, please [contact us](https://www.kurr
 To get the best out of this guide, a basic understanding of [Kubernetes concepts](https://kubernetes.io/docs/concepts/) is essential.
 :::
 
-* A Kubernetes cluster running `v1.23.1` or later.
+* A Kubernetes cluster running any [non-EOL version of kubernetes](https://kubernetes.io/releases/).
 * Permission to create resources, deploy the Operator and install CRDs in the target cluster.
 * The following CLI tools installed, on your shell’s `$PATH`, with `$KUBECONFIG` pointing to your cluster:
-  * kubectl [install guide](https://kubernetes.io/docs/tasks/tools/install-kubectl)
-  * k9s [install guide](https://k9scli.io/topics/install/)
-  * Helm 3 CLI [install guide](https://helm.sh/docs/intro/install/)
+  * [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl)
+  * [k9s](https://k9scli.io/topics/install/)
+  * [Helm 3 CLI](https://helm.sh/docs/intro/install/)
   * A valid Operator license. Please [contact us](https://www.kurrent.io/contact) for more information.
 
 ## Configure Helm Repository
@@ -52,16 +52,19 @@ If you prefer to install CRDs yourself:
 
 ```bash
 # Download the kurrentdb-operator Helm chart
-helm pull kurrent-latest/kurrentdb-operator --version 1.2.0 --untar
+helm pull kurrent-latest/kurrentdb-operator --version 1.3.0 --untar
 # Install the CRDs
-kubectl apply -f kurrentdb-operator/templates/crds
+kubectl apply -f kurrentdb-operator/crds
 ```
 *Expected Output*:
 ```
 customresourcedefinition.apiextensions.k8s.io/kurrentdbbackups.kubernetes.kurrent.io created
 customresourcedefinition.apiextensions.k8s.io/kurrentdbs.kubernetes.kurrent.io created
 ```
 
+After installing CRDs manually, you should include the `--skip-crds` flag for the `helm install` and
+`helm upgrade` commands.
+
 ## Deployment Modes
 
 The Operator can be scoped to track Kurrent resources across **all** or **specific** namespaces.
@@ -74,18 +77,17 @@ To deploy the Operator in this mode, run:
 
 ```bash
 helm install kurrentdb-operator kurrent-latest/kurrentdb-operator \
-  --version 1.2.0 \
+  --version 1.3.0 \
   --namespace kurrent \
   --create-namespace \
-  --set crds.enabled=true \
   --set-file operator.license.key=/path/to/license.key \
   --set-file operator.license.file=/path/to/license.lic
 ```
 
 This command:
 - Deploys the Operator into the `kurrent` namespace (use `--create-namespace` to create it). Feel free to modify this namespace.
 - Creates the namespace (if it already exists, leave out the `--create-namespace` flag)
-- Deploys CRDs (this can be skipped by removing `--set crds.enabled=true`)
+- Deploys CRDs (this can be skipped by removing `--skip-crds`)
 - Applys the Operator license
 - Deploys a new Helm release called `kurrentdb-operator` in the `kurrent` namespace.
 
@@ -109,10 +111,9 @@ To deploy the Operator in this mode, the following command can be used:
 
 ```bash
 helm install kurrentdb-operator kurrent-latest/kurrentdb-operator \
-  --version 1.2.0 \
+  --version 1.3.0 \
   --namespace kurrent \
   --create-namespace \
-  --set crds.enabled=true \
   --set-file operator.license.key=/path/to/license.key \
   --set-file operator.license.file=/path/to/license.lic \
   --set operator.namespaces='{kurrent, foo}'
@@ -121,7 +122,7 @@ helm install kurrentdb-operator kurrent-latest/kurrentdb-operator \
 Here's what the command does:
 - Sets the namespace of where the Operator will be deployed i.e. `kurrent` (feel free to change this)
 - Creates the namespace (if it already exists, leave out the `--create-namespace` flag)
-- Deploys CRDs (this can be skipped by removing `--set crds.enabled=true`)
+- Deploys CRDs (this can be skipped by setting `--skip-crds`)
 - Configures the Operator license
 - Sets the underlying Operator configuration to target the namespaces: `kurrent` and `foo`
 - Deploys a new Helm release called `kurrentdb-operator` in the `kurrent` namespace
@@ -148,7 +149,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.2.0 \
+  --version 1.3.0 \
   --namespace kurrent \
   --reuse-values \
   --set operator.namespaces='{kurrent,foo,bar}'
@@ -175,3 +176,21 @@ Pods may also be viewed using the `:pods` command, for example:
 Pressing the `Return` key on the selected Operator pod will allow you to drill through the container hosted in the pod, and then finally to the logs:
 
 ![Operator Logs](images/install/logs.png)
+
+
+## Upgrading an Installation
+
+The Operator can be upgraded using the following `helm` commands:
+
+```bash
+helm repo update
+helm upgrade kurrentdb-operator kurrentdb-operator-repo/kurrentdb-operator \
+  --namespace kurrent \
+  --version {version}
+```
+
+Here's what these commands do:
+- Refresh the local Helm repository index
+- Locates an existing operator installation in namespace `kurrent`
+- Selects the target upgrade version `{version}` e.g. `1.3.0`
+- Performs the upgrade, preserving values that were set during installation