Merge pull request #1496 from EnterpriseDB/content/josh/cnp-1.5.1-update

CNP 1.5.1 update

Former-commit-id: 6f51463

Author: josh-heyer

advocacy_docs/kubernetes/cloud_native_postgresql/api_reference.mdx

@@ -503,13 +503,13 @@ SecretsResourceVersion is the resource versions of the secrets managed by the op
 
 Name                     | Description                                                          | Type  
 ------------------------ | -------------------------------------------------------------------- | ------
-`superuserSecretVersion  ` | The resource version of the "postgres" user secret                   - *mandatory*  | string
-`replicationSecretVersion` | The resource version of the "streaming_replication" user secret      - *mandatory*  | string
-`applicationSecretVersion` | The resource version of the "app" user secret                        - *mandatory*  | string
+`superuserSecretVersion  ` | The resource version of the "postgres" user secret                   | string
+`replicationSecretVersion` | The resource version of the "streaming_replication" user secret      | string
+`applicationSecretVersion` | The resource version of the "app" user secret                        | string
 `caSecretVersion         ` | Unused. Retained for compatibility with old versions.                | string
-`clientCaSecretVersion   ` | The resource version of the PostgreSQL client-side CA secret version - *mandatory*  | string
-`serverCaSecretVersion   ` | The resource version of the PostgreSQL server-side CA secret version - *mandatory*  | string
-`serverSecretVersion     ` | The resource version of the PostgreSQL server-side secret version    - *mandatory*  | string
+`clientCaSecretVersion   ` | The resource version of the PostgreSQL client-side CA secret version | string
+`serverCaSecretVersion   ` | The resource version of the PostgreSQL server-side CA secret version | string
+`serverSecretVersion     ` | The resource version of the PostgreSQL server-side secret version    | string
 
 <a id='StorageConfiguration'></a>
 

advocacy_docs/kubernetes/cloud_native_postgresql/installation_upgrade.mdx

@@ -11,12 +11,12 @@ product: 'Cloud Native Operator'
 The operator can be installed like any other resource in Kubernetes,
 through a YAML manifest applied via `kubectl`.
 
-You can install the [latest operator manifest](https://get.enterprisedb.io/cnp/postgresql-operator-1.5.0.yaml)
+You can install the [latest operator manifest](https://get.enterprisedb.io/cnp/postgresql-operator-1.5.1.yaml)
 as follows:
 
 ```sh
 kubectl apply -f \
-  https://get.enterprisedb.io/cnp/postgresql-operator-1.5.0.yaml
+  https://get.enterprisedb.io/cnp/postgresql-operator-1.5.1.yaml
 ```
 
 Once you have run the `kubectl` command, Cloud Native PostgreSQL will be installed in your Kubernetes cluster.

advocacy_docs/kubernetes/cloud_native_postgresql/interactive_demo.mdx

@@ -65,7 +65,7 @@ You will see one node called `minikube`. If the status isn't yet "Ready", wait f
 Now that the Minikube cluster is running, you can proceed with Cloud Native PostgreSQL installation as described in the ["Installation"](installation_upgrade.md) section:
 
 ```shell
-kubectl apply -f https://get.enterprisedb.io/cnp/postgresql-operator-1.5.0.yaml
+kubectl apply -f https://get.enterprisedb.io/cnp/postgresql-operator-1.5.1.yaml
 __OUTPUT__
 namespace/postgresql-operator-system created
 customresourcedefinition.apiextensions.k8s.io/backups.postgresql.k8s.enterprisedb.io created
@@ -245,7 +245,7 @@ curl -sSfL \
   sudo sh -s -- -b /usr/local/bin
 __OUTPUT__
 EnterpriseDB/kubectl-cnp info checking GitHub for latest tag
-EnterpriseDB/kubectl-cnp info found version: 1.5.0 for v1.5.0/linux/x86_64
+EnterpriseDB/kubectl-cnp info found version: 1.5.1 for v1.5.1/linux/x86_64
 EnterpriseDB/kubectl-cnp info installed /usr/local/bin/kubectl-cnp
 ```
 

advocacy_docs/kubernetes/cloud_native_postgresql/operator_capability_levels.mdx

@@ -90,6 +90,9 @@ workload requirements, based on what the underlying Kubernetes environment
 can offer. This implies choosing a particular storage class in
 a public cloud environment or fine-tuning the generated PVC through a
 PVC template in the CR's `storage` parameter.
+The [`cnp-bench`](https://github.com/EnterpriseDB/cnp-bench) open source
+project can be used to benchmark both the storage and the database prior to
+production.
 
 ### Replica configuration
 
@@ -173,17 +176,16 @@ Kubernetes API Server and the operator itself.
 ### Cluster's certification authority
 
 The operator automatically creates a certification authority for every PostgreSQL
-cluster, which is used to issue and renew TLS certificates for the authentication
-of streaming replication standby servers and applications (instead of passwords).
-The operator will use the Certification Authority to sign every cluster
-certification authority. Certificates can be issued with the `cnp` plugin
-for `kubectl`.
+cluster, which is used to issue and renew TLS certificates for clients' authentication,
+including streaming replication standby servers (instead of passwords).
+Certificates can be issued with the `cnp` plugin for `kubectl`.
 
 ### TLS connections
 
 The operator transparently and natively supports TLS/SSL connections
 to encrypt client/server communications for increased security using the
 cluster's certification authority.
+Support for custom server certificates is available through secrets.
 
 ### Certificate authentication for streaming replication
 

advocacy_docs/kubernetes/cloud_native_postgresql/operator_conf.mdx

@@ -21,15 +21,19 @@ namespace as a Kubernetes `Deployment` called `postgresql-operator-controller-ma
 !!! Note
     In the examples below we assume the default name and namespace for the operator deployment.
 
-The behavior of the operator can be customized through a `ConfigMap` that
+The behavior of the operator can be customized through a `ConfigMap`/`Secret` that
 is located in the same namespace of the operator deployment and with
 `postgresql-operator-controller-manager-config` as the name.
 
 !!! Important
-    Any change to the config map will not be automatically detected by the operator,
+    Any change to the config's `ConfigMap`/`Secret` will not be automatically detected by the operator,
     - and as such, it needs to be reloaded (see below). Moreover, changes only
     apply to the resources created after the configuration is reloaded.
 
+!!! Important
+    The operator first processes the ConfigMap values and then the Secret’s, in this order.
+    As a result, if a parameter is defined in both places, the one in the Secret will be used.
+
 ## Available options
 
 The operator looks for the following environment variables to be defined in the config map:
@@ -65,6 +69,24 @@ data:
   EDB_LICENSE_KEY: <YOUR_EDB_LICENSE_KEY_HERE>
 ```
 
+## Defining an operator secret
+
+The example below customizes the behavior of the operator, by defining a
+default license key.
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+  name: postgresql-operator-controller-manager-config
+  namespace: postgresql-operator-system
+type: Opaque
+data:
+  EDB_LICENSE_KEY: <YOUR_BASE64_ENCODED_EDB_LICENSE_KEY_HERE>
+```
+
+## Restarting the operator to reload configs
+
 For the change to be effective, you need to recreate the operator pods to
 reload the config map. If you have installed the operator on Kubernetes
 using the manifest you can do that by issuing:

advocacy_docs/kubernetes/cloud_native_postgresql/release_notes.mdx

@@ -6,6 +6,15 @@ product: 'Cloud Native Operator'
 
 History of user-visible changes for Cloud Native PostgreSQL.
 
+## Version 1.5.1
+
+**Release date:** 17 June 2021
+
+Change: 
+
+- Fix a bug with CRD validation preventing auto-update with Operator Deployments on Red Hat OpenShift
+- Allow passing operator's configuration using a Secret.
+
 ## Version 1.5.0
 
 **Release date:** 11 June 2021

merge_sources/kubernetes/cloud_native_postgresql/interactive_demo.mdx

@@ -65,7 +65,7 @@ You will see one node called `minikube`. If the status isn't yet "Ready", wait f
 Now that the Minikube cluster is running, you can proceed with Cloud Native PostgreSQL installation as described in the ["Installation"](installation_upgrade.md) section:
 
 ```shell
-kubectl apply -f https://get.enterprisedb.io/cnp/postgresql-operator-1.5.0.yaml
+kubectl apply -f https://get.enterprisedb.io/cnp/postgresql-operator-1.5.1.yaml
 __OUTPUT__
 namespace/postgresql-operator-system created
 customresourcedefinition.apiextensions.k8s.io/backups.postgresql.k8s.enterprisedb.io created
@@ -245,7 +245,7 @@ curl -sSfL \
   sudo sh -s -- -b /usr/local/bin
 __OUTPUT__
 EnterpriseDB/kubectl-cnp info checking GitHub for latest tag
-EnterpriseDB/kubectl-cnp info found version: 1.5.0 for v1.5.0/linux/x86_64
+EnterpriseDB/kubectl-cnp info found version: 1.5.1 for v1.5.1/linux/x86_64
 EnterpriseDB/kubectl-cnp info installed /usr/local/bin/kubectl-cnp
 ```