K8SPS-568 Release notes 1.0.0

_resourcepdf/overrides/main.html

@@ -5,9 +5,7 @@
 {# Import the theme's layout. #}
 {% extends "base.html" %}
 
-{% block announce %}
-  Version 0.12.0 of the <a href="https://github.com/percona/percona-server-mysql-operator">Percona Operator for MySQL</a> is <strong>a tech preview release</strong> and it is <strong>not recommended for production environments</strong>. <strong>As of today, we recommend using</strong> <a href="https://www.percona.com/doc/kubernetes-operator-for-pxc/index.html">Percona Operator for MySQL based on Percona XtraDB Cluster</a>, which is production-ready and contains everything you need to quickly and consistently deploy and scale MySQL clusters in a Kubernetes-based environment, on-premises or in the cloud.
-{% endblock %}
+
 
 {% block extrahead %}
                {{ super() }}

docs/ReleaseNotes/Kubernetes-Operator-for-PS-RN0.10.0.md

@@ -107,7 +107,7 @@ Other options may also work but have not been tested.
 
 ## Supported platforms
 
-Percona Operators are designed for compatibility with all [CNCF-certified :octicons-link-external-16:](https://www.cncf.io/training/certification/software-conformance/) Kubernetes distributions. Our release process includes targeted testing and validation on major cloud provider platforms and OpenShift, as detailed below for Operator version 0.9.0:
+Percona Operators are designed for compatibility with all [CNCF-certified :octicons-link-external-16:](https://www.cncf.io/training/certification/software-conformance/) Kubernetes distributions. Our release process includes targeted testing and validation on major cloud provider platforms and OpenShift, as detailed below for Operator version 0.10.0:
 
 --8<-- [start:platforms]
 

docs/ReleaseNotes/Kubernetes-Operator-for-PS-RN0.11.0.md

@@ -131,7 +131,7 @@ Other options may also work but have not been tested.
 
 ## Supported platforms
 
-Percona Operators are designed for compatibility with all [CNCF-certified :octicons-link-external-16:](https://www.cncf.io/training/certification/software-conformance/) Kubernetes distributions. Our release process includes targeted testing and validation on major cloud provider platforms and OpenShift, as detailed below for Operator version 0.9.0:
+Percona Operators are designed for compatibility with all [CNCF-certified :octicons-link-external-16:](https://www.cncf.io/training/certification/software-conformance/) Kubernetes distributions. Our release process includes targeted testing and validation on major cloud provider platforms and OpenShift, as detailed below for Operator version 0.11.0:
 
 --8<-- [start:platforms]
 

docs/ReleaseNotes/Kubernetes-Operator-for-PS-RN0.12.0.md

@@ -156,7 +156,7 @@ Other options may also work but have not been tested.
 
 ## Supported platforms
 
-Percona Operators are designed for compatibility with all [CNCF-certified :octicons-link-external-16:](https://www.cncf.io/training/certification/software-conformance/) Kubernetes distributions. Our release process includes targeted testing and validation on major cloud provider platforms and OpenShift, as detailed below for Operator version 0.9.0:
+Percona Operators are designed for compatibility with all [CNCF-certified :octicons-link-external-16:](https://www.cncf.io/training/certification/software-conformance/) Kubernetes distributions. Our release process includes targeted testing and validation on major cloud provider platforms and OpenShift, as detailed below for Operator version 0.12.0:
 
 --8<-- [start:platforms]
 

docs/ReleaseNotes/Kubernetes-Operator-for-PS-RN0.3.0.md

@@ -16,7 +16,7 @@
 
 * You can now use the [HAProxy load balancer](../expose.md#use-haproxy) in front of the cluster configured for the asynchronous replication. The feature is turned on by default, allowing HAProxy to route traffic and monitor the health of the nodes
 
-* Starting from this release, the Operator [automatically generates](../TLS.md#install-and-use-the-cert-manager) TLS certificates and turns on transport encryption by default at cluster creation time. This includes both external certificates which allow users to connect to a cluster via the encrypted channel, and internal ones used for communication between MySQL nodes
+* Starting from this release, the Operator [automatically generates](../tls-cert-manager.md) TLS certificates and turns on transport encryption by default at cluster creation time. This includes both external certificates which allow users to connect to a cluster via the encrypted channel, and internal ones used for communication between MySQL nodes
 
 ## New Features
 
@@ -26,12 +26,12 @@
 
 ## Improvements
 
-* {{ k8spsjira(23) }} Add [cert-manager support](../TLS.md#install-and-use-the-cert-manager) to generate and update TLS certificates automatically
+* {{ k8spsjira(23) }} Add [cert-manager support](../tls-cert-manager.md) to generate and update TLS certificates automatically
 * {{ k8spsjira(31) }} Show `ready` state in the custom resource output produced by the `kubectl get ps` command only after all LoadBalancers are ready
 * {{ k8spsjira(59) }} Add `mysql.primaryServiceType` Custom Resource option to configure the primary exposure type in one place instead of exposing all Pods with specific Service type
 * {{ k8spsjira(88) }} Allow configuring `prefix` field for backup storages via the [backup.s3.prefix](../operator.md#backupstoragesstorage-names3prefix) Custom Resource option
 * {{ k8spsjira(93) }} Avoid running multiple backups on the same Pod by either scheduling new backup to another Node or blocking it until the running one finishes
-* {{ k8spsjira(97) }} [S3 backup finalizer](../backups-ondemand.md#finalizers) now triggers the actual deletion of backup files from the S3 bucket when there is a manual or scheduled removal of the corresponding backup object
+* {{ k8spsjira(97) }} [S3 backup finalizer](../backups-ondemand.md) now triggers the actual deletion of backup files from the S3 bucket when there is a manual or scheduled removal of the corresponding backup object
 * {{ k8spsjira(103) }} Show MySQL Router and Orchestrator statuses in the Custom Resource through the `kubectl` command
 * {{ k8spsjira(104) }} Avoid using the root user in backup containers to run XtraBackup with the lowest possible privileges for higher security and isolation of the cluster components
 * {{ k8spsjira(115) }} Make it possible [to use API Key](../monitoring.md#install-pmm-client) to authorize within Percona Monitoring and Management Server as a more convenient and modern alternative password-based authentication

docs/ReleaseNotes/Kubernetes-Operator-for-PS-RN0.8.0.md

@@ -33,7 +33,7 @@ unsafeFlags:
 
 ## New features
 
-* {{ k8spsjira(149) }}: Custom Resource options now include [customizable health checks and timeouts](../operator.md#proxyhaproxyreadinessprobestimeoutseconds) for HAProxy
+* {{ k8spsjira(149) }}: Custom Resource options now include [customizable health checks and timeouts](../operator.md#proxyhaproxylivenessprobetimeoutseconds) for HAProxy
 * {{ k8spsjira(186) }} and {{ k8spsjira(370) }}: Removing `allowUnsafeConfigurations` Custom Resource option in favor of fine-grained safety control in the `unsafeFlags` subsection
 * {{ k8spsjira(241) }}: Support for the [cluster-wide Operator mode](../cluster-wide.md) allowing one Operator to watch for Percona Server for MySQL Custom Resources in several namespaces
 

docs/ReleaseNotes/Kubernetes-Operator-for-PS-RN0.9.0.md

@@ -58,8 +58,6 @@ See more detailed instructions on configuring scheduled backups in [our document
 
 * Both upgrade to the Operator version 0.9.0 and the appropriate database cluster upgrade can not be done in a usual way due to a number of internal changes, and require additional manual operations.
 
-    * Upgrading the Operator can be done with [this workaround](../update-to-0.9.0.md)
-    * Upgrading the database cluster can be done by [deleting and recreating it](../delete.md#delete-the-database-cluster)
 
 ## Supported Platforms