reduce duplicated info

Author: kaitlynmichael

content/operate/kubernetes/networking/_index.md

@@ -35,16 +35,14 @@ For Active-Active databases, configure automatic ingress creation:
 
 ## External routing using Redis Enterprise for Kubernetes
 
-Every time a RedisEnterpriseDatabase (REDB), Redis Enterprise Active-Active database (REAADB), or Redis Enterprise cluster (REC) is created, the Redis Enterprise operator automatically creates a [service](https://kubernetes.io/docs/concepts/services-networking/service/) to allow requests to be routed to that resource.
-
-Redis Enterprise supports three [types of services](https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types) for accessing databases: `ClusterIP`, `headless`, or `LoadBalancer`.
-
-By default, the operator creates a `ClusterIP` type service, which exposes a cluster-internal IP and that can only be accessed from within the K8s cluster. For requests to be routed from outside the K8s cluster, you need an [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) (or [route](https://docs.openshift.com/container-platform/4.12/networking/routes/route-configuration.html) if you are using OpenShift). See [kubernetes.io](https://kubernetes.io/docs/) for more details on [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) and [Ingress controllers](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/).
+The Redis Enterprise operator automatically creates Kubernetes services for database access. For external access from outside the cluster, you need to configure additional routing methods:
 
 - To use NGINX or HAProxy Ingress controllers, see [Ingress routing]({{< relref "/operate/kubernetes/networking/ingress" >}}).
 - To use OpenShift routes, see [OpenShift routes]({{< relref "/operate/kubernetes/networking/routes" >}}).
 - To use Istio as an Ingress controller, see [Istio Ingress routing]({{< relref "/operate/kubernetes/networking/istio-ingress" >}})
 
+For comprehensive information about service types, in-cluster access, and connectivity patterns, see [Database connectivity]({{< relref "/operate/kubernetes/networking/database-connectivity" >}}).
+
 ## `ingressOrRouteSpec` for Active-Active databases
 
 Versions 6.4.2 or later of Redis Enterprise for Kubernetes include a feature for ingress configuration. The `ingressOrRouteSpec` field is available in the RedisEnterpriseCluster spec to automatically create an Ingress (or route) for the API service and databases (REAADB) on that REC. See [REC external routing]({{< relref "/operate/kubernetes/networking/ingressorroutespec" >}}) for more details.

content/operate/kubernetes/re-databases/db-controller.md

@@ -108,57 +108,13 @@ kubectl delete redb mydb
 
 ## Connect to a database
 
-After the database controller creates a database, the services for accessing the database are created in the same namespace. By default there are two services, one 'ClusterIP' service and one 'headless' service.  
-Connection information for the database is stored in a Kubernetes [secret](https://kubernetes.io/docs/concepts/configuration/secret/) maintained by the database controller. This secret contains:
+After the database controller creates a database, services for accessing the database are automatically created in the same namespace. Connection information is stored in a Kubernetes [secret](https://kubernetes.io/docs/concepts/configuration/secret/) maintained by the database controller.
 
-- The database port (`port`)
-- A comma separated list of service names (`service_names`)
-- The database password for authenticating (`password`)
+For comprehensive information about connecting to your database, including:
 
-The name of that secret is stored in the database custom resource.
+- Service types and access patterns
+- Retrieving connection information from secrets
+- In-cluster and external access methods
+- Connection examples and troubleshooting
 
-{{<note>}}
-Use these steps to connect to your database from within your K8s cluster. To access your database from outside the K8s cluster, set up the [Ingress]({{< relref "/operate/kubernetes/networking/ingress" >}}) controller or use OpenShift routes.
-{{</note>}}
-
-1. Retrieve the secret name.
-
-    ```sh
-    kubectl get redb mydb -o jsonpath="{.spec.databaseSecretName}"
-    ```
-
-      The database secret name usually takes the form of `redb-<database_name>`, so in our example it will be `redb-mydb`.
-
-1. Retrieve and decode the password.
-
-    ```sh
-    kubectl get secret redb-mydb -o jsonpath="{.data.password}" | base64 --decode
-    ```
-
-1. Retrieve and decode the port number.
-
-    ```sh
-    kubectl get secret redb-mydb -o jsonpath="{.data.port}" | base64 --decode
-    ```
-
-1. Retrieve and decode the service_names.
-
-    ```sh
-    kubectl get secret redb-mydb -o jsonpath="{.data.service_names}" | base64 --decode
-    ```
-
-    You'll need to pick just one service listed here to use for connecting.
-
-1. From a pod within your cluster, use `redis-cli` to connect to your database.
-
-    ```sh
-    redis-cli -h <service_name> -p <port>
-    ```
-
-1. Enter the password you retrieved from the secret.
-
-    ```sh
-    auth <password>
-    ```
-
-    You are now connected to your database!
+See [Database connectivity]({{< relref "/operate/kubernetes/networking/database-connectivity" >}}).