Skip to content

Commit

Permalink
Update the docs
Browse files Browse the repository at this point in the history
Signed-off-by: Alexander Schwartz <aschwart@redhat.com>
  • Loading branch information
ahus1 committed Jul 25, 2024
1 parent 9216c29 commit 4df1100
Showing 1 changed file with 10 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -73,15 +73,23 @@ See xref:customizing-deployment.adoc[] for a list of all configuration options.
The Aurora DB cluster is only accessible to ROSA clusters with an established Peering Connection, therefore all debugging
connections must also originate from said clusters. A simple way to connect `psql` to the cluster is to execute the following:

[source,bash]
[.wrap]
[source,bash,subs="+quotes"]
----
kubectl run -i --tty --rm debug --image=postgres:13 --restart=Never -n {{.KC_NAMESPACE_PREFIX}}keycloak -- psql -h postgres -d keycloak -U keycloak
kubectl run -i --tty --rm debug --image=postgres:15 --restart=Never -n *<namespace>* -- psql -h *<....rds.amazonaws.com>* -d keycloak -U keycloak
----

This will create a pod in the Keycloak deployment namespace and establish a connection with the Aurora cluster. A password
prompt will appear on initial connection and you should utilise the password defined in the Secret `keycloak-db-secret`.
Upon exiting the pod shell, the pod will be deleted.

To drop the contents of the database, run the following command. Then restart all Keycloak nodes in all datacenters.

[source,sql]
----
DROP SCHEMA public CASCADE; CREATE SCHEMA public;
----

== Disconnecting ROSA cluster from an individual Aurora Cluster

To remove a Peering Connections between a ROSA cluster and a specific Aurora cluster, execute `./provision/aws/rds/aurora_delete_peering_connection.sh`
Expand Down

0 comments on commit 4df1100

Please sign in to comment.