-
Notifications
You must be signed in to change notification settings - Fork 471
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
- Loading branch information
1 parent
e3eba55
commit 09a2ed2
Showing
1 changed file
with
56 additions
and
0 deletions.
There are no files selected for viewing
56 changes: 56 additions & 0 deletions
56
content/platforms/kubernetes/tasks/connect-to-admin-console.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
--- | ||
Title: Connect to the admin console | ||
linkTitle: Connect to the admin console | ||
description: Connect to the Redis Enterprise admin console to manage your Redis Enterprise cluster. | ||
weight: 10 | ||
alwaysopen: false | ||
categories: ["Platforms"] | ||
aliases: /platforms/kubernetes/tasks/connect-to-admin-console.md | ||
/platforms/kubernetes/tasks/connect-to-admin-console/ | ||
--- | ||
|
||
The username and password for the Redis Enterprise Software [admin console]({{<relref "/rs/administering/_index.md">}}) are stored in a Kubernetes [secret](https://kubernetes.io/docs/concepts/configuration/secret/). After retrieving your credentials, you can use port forwarding to connect to the admin console. | ||
|
||
{{<note>}} | ||
There are several methods for accessing the admin console. Port forwarding is the simplest, but not the most efficient method for long-term use. You could also use a load balancer service or ingress. | ||
{{</note>}} | ||
|
||
1. Switch to the namespace with your Redis Enterprise cluster (REC). | ||
|
||
```sh | ||
kubectl config set-context --current --namespace=<namespace-of-rec> | ||
``` | ||
|
||
1. Find your cluster name from your list of secrets. | ||
|
||
```sh | ||
kubectl get secret | ||
``` | ||
|
||
In this example, the cluster name is `rec`. | ||
|
||
1. Extract and decode your credentials from the secret. | ||
|
||
```sh | ||
kubectl get secret <cluster-name> -o jsonpath='{.data.username}' | base64 --decode | ||
kubectl get secret <cluster-name> -o jsonpath='{.data.password}' | base64 --decode | ||
``` | ||
|
||
1. Find the port for the REC UI service in the `spec:ports` section of the service definition file. | ||
|
||
```sh | ||
kubectl get service/<cluster-name>-ui -o yaml | ||
``` | ||
|
||
{{<note>}} | ||
The default port is 8843. | ||
{{</note>}} | ||
|
||
1. Use `kubectl port-forward` to forward your local port to the service port. | ||
|
||
```sh | ||
kubectl port-forward service/<cluster-name>-ui <local-port>:<service-port> | ||
``` | ||
|
||
1. View the admin console from a web browser on your local machine at `https://localhost:8443`. | ||
|