From 03e9ed762ee8c11bd88fbc7be3260e923c8a8920 Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Mon, 14 Nov 2022 04:45:04 +0000 Subject: [PATCH] update demo version --- .../1/interactive_demo.mdx | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/product_docs/docs/postgres_for_kubernetes/1/interactive_demo.mdx b/product_docs/docs/postgres_for_kubernetes/1/interactive_demo.mdx index 36fdddfe266..6cd3c99fefd 100644 --- a/product_docs/docs/postgres_for_kubernetes/1/interactive_demo.mdx +++ b/product_docs/docs/postgres_for_kubernetes/1/interactive_demo.mdx @@ -76,7 +76,7 @@ You will see one node called `k3d-k3s-default-server-0`. If the status isn't yet Now that the Kubernetes cluster is running, you can proceed with EDB Postgres for Kubernetes installation as described in the ["Installation and upgrades"](installation_upgrade.md) section: ```shell -kubectl apply -f https://get.enterprisedb.io/cnp/postgresql-operator-1.17.0.yaml +kubectl apply -f https://get.enterprisedb.io/cnp/postgresql-operator-1.18.0.yaml __OUTPUT__ namespace/postgresql-operator-system created customresourcedefinition.apiextensions.k8s.io/backups.postgresql.k8s.enterprisedb.io created @@ -197,7 +197,7 @@ spec: localeCollate: C owner: app enableSuperuserAccess: true - imageName: quay.io/enterprisedb/postgresql:14.5 + imageName: quay.io/enterprisedb/postgresql:15.0 instances: 3 logLevel: info maxSyncReplicas: 0 @@ -350,7 +350,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.17.0 for v1.17.0/linux/x86_64 +EnterpriseDB/kubectl-cnp info found version: 1.18.0 for v1.18.0/linux/x86_64 EnterpriseDB/kubectl-cnp info installed /usr/local/bin/kubectl-cnp ``` @@ -363,7 +363,7 @@ Cluster Summary Name: cluster-example Namespace: default System ID: 7140379538380623889 -PostgreSQL Image: quay.io/enterprisedb/postgresql:14.5 +PostgreSQL Image: quay.io/enterprisedb/postgresql:15.0 Primary instance: cluster-example-1 Status: Cluster in healthy state Instances: 3 @@ -389,9 +389,9 @@ cluster-example-3 0/5000060 0/5000060 0/5000060 0/5000060 00:00:00 00:00 Instances status Name Database Size Current LSN Replication role Status QoS Manager Version Node ---- ------------- ----------- ---------------- ------ --- --------------- ---- -cluster-example-1 33 MB 0/5000060 Primary OK BestEffort 1.17.0 k3d-k3s-default-server-0 -cluster-example-2 33 MB 0/5000060 Standby (async) OK BestEffort 1.17.0 k3d-k3s-default-server-0 -cluster-example-3 33 MB 0/5000060 Standby (async) OK BestEffort 1.17.0 k3d-k3s-default-server-0 +cluster-example-1 33 MB 0/5000060 Primary OK BestEffort 1.18.0 k3d-k3s-default-server-0 +cluster-example-2 33 MB 0/5000060 Standby (async) OK BestEffort 1.18.0 k3d-k3s-default-server-0 +cluster-example-3 33 MB 0/5000060 Standby (async) OK BestEffort 1.18.0 k3d-k3s-default-server-0 ``` !!! Note "There's more" @@ -441,8 +441,8 @@ Not available yet Instances status Name Database Size Current LSN Replication role Status QoS Manager Version Node ---- ------------- ----------- ---------------- ------ --- --------------- ---- -cluster-example-2 33 MB 0/6000F58 Primary OK BestEffort 1.17.0 k3d-k3s-default-server-0 -cluster-example-3 33 MB 0/60000A0 Standby (file based) OK BestEffort 1.17.0 k3d-k3s-default-server-0 +cluster-example-2 33 MB 0/6000F58 Primary OK BestEffort 1.18.0 k3d-k3s-default-server-0 +cluster-example-3 33 MB 0/60000A0 Standby (file based) OK BestEffort 1.18.0 k3d-k3s-default-server-0 ``` ...the failover process has begun, with the second pod promoted to primary. Once the failed pod has restarted, it will become a replica of the new primary: @@ -480,9 +480,9 @@ cluster-example-3 0/6004CD8 0/6004CD8 0/6004CD8 0/6004CD8 00:00:00 00:00 Instances status Name Database Size Current LSN Replication role Status QoS Manager Version Node ---- ------------- ----------- ---------------- ------ --- --------------- ---- -cluster-example-2 33 MB 0/6004CD8 Primary OK BestEffort 1.17.0 k3d-k3s-default-server-0 -cluster-example-1 33 MB 0/6004CD8 Standby (async) OK BestEffort 1.17.0 k3d-k3s-default-server-0 -cluster-example-3 33 MB 0/6004CD8 Standby (async) OK BestEffort 1.17.0 k3d-k3s-default-server-0 +cluster-example-2 33 MB 0/6004CD8 Primary OK BestEffort 1.18.0 k3d-k3s-default-server-0 +cluster-example-1 33 MB 0/6004CD8 Standby (async) OK BestEffort 1.18.0 k3d-k3s-default-server-0 +cluster-example-3 33 MB 0/6004CD8 Standby (async) OK BestEffort 1.18.0 k3d-k3s-default-server-0 ```