DEV-866 operator v1.4 docs (#922)

Author: rb-kurrent

docs/server/kubernetes-operator/v1.0.0/operations/database-deployment.md

@@ -380,11 +380,7 @@ kubectl apply -f cluster.yaml
 ## Three Node Secure Cluster (using LetsEncrypt)
 
 Using LetsEncrypt, or any publicly trusted certificate, in an operator-managed KurrentDB cluster
-is not supported.
-
-The recommended workaround is to combine [self-signed certificates within the cluster](
-#three-node-secure-cluster-using-self-signed-certificates) with an Ingress that does TLS
-termination using the LetsEncrypt certificate.
+is not supported in v1.0.0; please upgrade to v1.4.0.
 
 ## Viewing Deployments
 

docs/server/kubernetes-operator/v1.1.0/operations/database-deployment.md

@@ -445,11 +445,7 @@ kubectl apply -f cluster.yaml
 ## Three Node Secure Cluster (using LetsEncrypt)
 
 Using LetsEncrypt, or any publicly trusted certificate, in an operator-managed KurrentDB cluster
-is not supported.
-
-The recommended workaround is to combine [self-signed certificates within the cluster](
-#three-node-secure-cluster-using-self-signed-certificates) with an Ingress that does TLS
-termination using the LetsEncrypt certificate.
+is not supported in v1.0.0; please upgrade to v1.4.0.
 
 ## Deploying With Scheduling Constraints
 

docs/server/kubernetes-operator/v1.2.0/operations/database-deployment.md

@@ -445,11 +445,7 @@ kubectl apply -f cluster.yaml
 ## Three Node Secure Cluster (using LetsEncrypt)
 
 Using LetsEncrypt, or any publicly trusted certificate, in an operator-managed KurrentDB cluster
-is not supported.
-
-The recommended workaround is to combine [self-signed certificates within the cluster](
-#three-node-secure-cluster-using-self-signed-certificates) with an Ingress that does TLS
-termination using the LetsEncrypt certificate.
+is not supported in v1.0.0; please upgrade to v1.4.0.
 
 ## Deploying With Scheduling Constraints
 

docs/server/kubernetes-operator/v1.3.1/operations/database-deployment.md

@@ -441,11 +441,7 @@ kubectl apply -f cluster.yaml
 ## Three Node Secure Cluster (using LetsEncrypt)
 
 Using LetsEncrypt, or any publicly trusted certificate, in an operator-managed KurrentDB cluster
-is not supported.
-
-The recommended workaround is to combine [self-signed certificates within the cluster](
-#three-node-secure-cluster-using-self-signed-certificates) with an Ingress that does TLS
-termination using the LetsEncrypt certificate.
+is not supported in v1.0.0; please upgrade to v1.4.0.
 
 ## Deploying With Scheduling Constraints
 

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

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

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

@@ -0,0 +1,68 @@
+---
+order: 1
+dir:
+  text: "Getting started"
+  link: true
+  order: 1
+---
+
+<CloudBanner />
+
+---
+Welcome to the **KurrentDB Kubernetes Operator** guide. In this guide, we’ll refer to the KurrentDB Kubernetes Operator simply as “the Operator.” Use the Operator to simplify backup, scaling, and upgrades of KurrentDB clusters on Kubernetes.
+
+:::important
+The Operator is an Enterprise-only feature, please [contact us](https://www.kurrent.io/contact) for more information.
+:::
+
+## Why run KurrentDB on Kubernetes?
+
+Kubernetes is the modern enterprise standard for deploying containerized applications at scale. The Operator streamlines deployment and management of KurrentDB clusters.
+
+## Features
+
+* Deploy single-node or multi-node clusters
+* Back up and restore clusters
+* Automate backups with a schedule and retention policies
+* Perform rolling upgrades and update configurations
+
+### New in 1.4.0
+
+* Support configurable traffic strategies for each of server-server and client-server traffic.  This
+  enables the use of LetsEncrypt certificates without creating Ingresses, for example.  See
+  [Traffic Strategies][ts] for details.
+* Support backup scheduling and retention policies.  There is a new [KurrentDBBackupSchedule][bs]
+  CRD with a CronJob-like syntax.  There are also two mechanisms for configuring retention policies:
+  a `.keep` count on `KurrentDBBackupSchedule`, and a new `.ttl` on `KurrentDBBackup`.
+* Support standalone read-only replicas pointed at a remote cluster.  This enables advanced
+  topologies like a having your quorum nodes in one region and a read-only replica in a distant
+  region.  See [Deploying Standalone Read-Only Replicas][ror] for an example.
+* Support template strings in some extra metadata for child resources of the `KurrentDB` object.
+  This allows, for example, to annotate each of the automatically created LoadBalancers with unique
+  external-dns annotations.  See [KurrentDBExtraMetadataSpec][em] for details.
+
+[ts]: ../operations/advanced-networking.md#traffic-strategy-options
+[bs]: resource-types.md#kurrentdbbackupschedulespec
+[ror]: ../operations/database-deployment.md#deploying-standalone-read-only-replicas
+[em]: resource-types.md#kurrentdbextrametadataspec
+
+## Supported KurrentDB Versions
+
+The Operator supports running the following major versions of KurrentDB:
+- v25.x
+- v24.x
+- v23.10+
+
+## Supported Hardware Architectures
+
+The Operator is packaged for the following hardware architectures:
+- x86\_64
+- arm64
+
+## Technical Support
+
+For support questions, please [contact us](https://www.kurrent.io/contact).
+
+## First Steps
+
+Ready to install? Head over to the [installation](installation.md) section.