Merge pull request #534 from klgill/Docs-MinorFixes

updated dataplane operator and databaseUser field
openstack-k8s-operators · Jul 19, 2024 · 9087d51 · 9087d51
2 parents aa6e213 + 0afadf4
commit 9087d51
Show file tree

Hide file tree

Showing 3 changed files with 2 additions and 3 deletions.
diff --git a/docs_user/modules/proc_adopting-autoscaling.adoc b/docs_user/modules/proc_adopting-autoscaling.adoc
@@ -44,7 +44,7 @@ ifeval::["{build}" == "downstream"]
       listenerImage: "registry.redhat.io/rhosp-dev-preview/openstack-aodh-listener-rhel9:18.0"
 endif::[]
       passwordSelectors:
-      databaseUser: aodh
+      databaseAccount: aodh
       databaseInstance: openstack
       memcachedInstance: memcached
 EOF

diff --git a/docs_user/modules/proc_adopting-key-manager-service.adoc b/docs_user/modules/proc_adopting-key-manager-service.adoc
@@ -32,7 +32,6 @@ spec:
     template:
       databaseInstance: openstack
       databaseAccount: barbican
-      databaseUser: barbican
       rabbitMqClusterName: rabbitmq
       secret: osp-secret
       simpleCryptoBackendSecret: osp-secret

diff --git a/docs_user/modules/proc_performing-a-fast-forward-upgrade-on-compute-services.adoc b/docs_user/modules/proc_performing-a-fast-forward-upgrade-on-compute-services.adoc
@@ -4,7 +4,7 @@
 
 Compute services rolling upgrade cannot be done during adoption,
 there is in a lock-step with Compute control plane services, because those are managed independently by data plane ansible and Kubernetes Operators.
-Compute service operator and Dataplane Operator ensure upgrading
+The Compute service operator and OpenStack Operator ensure upgrading
 is done independently of each other, by configuring
 `[upgrade_levels]compute=auto` for Compute services. Compute control plane
 services apply the change right after custom resource (CR) is patched. Compute data plane services will catch up the same config change with ansible deployment later on.