Redis
The Redis microservice is an in-memory data structure store, used as a distributed, in-memory key–value database, cache or message broker.
It is a supporting microservice that other microservices can use for in-cluster storage. It runs in the a1-cache namespace.
The RedisJSON and RediSearch modules are enabled for the microservice.
Redis Prerequisites
Before deploying the microservice, confirm that a microservice cluster is set up. See Microservice Cluster Setup.
Deploying Redis
To deploy the microservice, run the following commands:
su - assure1
export WEBFQDN=<WebFQDN>
a1helm install <microservice-release-name> assure1/redis -n a1-cache --set global.imageRegistry=$WEBFQDN
In the commands:
-
Note that this microservice must be deployed to the a1-cache namespace rather than a zone-specific namespace.
-
<WebFQDN> is the fully-qualified domain name of the primary presentation server for the cluster.
-
<microservice-release-name> is the name to use for the microservice instance. Oracle recommends using the microservice name (redis) unless you are deploying multiple instances of the microservice to the same cluster.
You can also use the Unified Assurance UI to deploy microservices. See Deploying a Microservice by Using the UI for more information.
Redis CLI
The microservice includes the redis-cli application, which interacts directly with the redis instance. You can access it by running an interactive shell within the running redis instance.
To launch redis-cli and authenticate with TLS, run the following commands:
a1k exec -it redis-master-0 -n a1-cache -- /bin/bash
redis-cli --tls --cert /certs/a1/User-assure1.crt --key /certs/a1/User-assure1.key --cacert /certs/a1/BundleCA.crt
See redis-cli in the Redis documentation for information about running Redis commands with redis-cli.