Redis: console walkthrough

The same operations as the step-by-step guide, done in the console.

This console page has a guided tour

Click Start the tour beside the create button for a walkthrough that highlights each field as you go.

List

WebHosting > Databases > Redis lists the instances in the selected project.

There is no health column

The Redis operator does not write a status onto the object, so the page has nothing to report. An instance appearing in this list means the object exists, not that the server is running. To confirm it is up, look for a pod named after the instance in the project.

Create

Create Redis opens a guided form with two fields.

• Name - used for the Redis object, the Secret holding its password, and the Service other workloads connect to. Something describing the use, like cache or sessions, reads better than the application name.
• Storage size - defaults to 1Gi. Redis keeps its data in memory; this disk is what lets it survive a restart.

The image, the CPU and memory limits, the storage class and the service type are not exposed. They are set to values that work on this platform, and a wrong storage class silently fails to bind a disk rather than reporting an error.

The password is generated for you

Submitting the form generates a password in your browser, stores it in a Secret named redis-<instance>, and points the server at that Secret. You never type it and it is never shown on screen. Read it from the Secret when an application needs it.

The Secret is created first, then the server. If the Secret fails, no server is created.

Change

The console form creates instances; it does not edit them. Resizing CPU and memory, growing the disk and rotating the password are all done with oc - see Change.

Delete

Use the kebab menu at the end of the row.

The Secret and the disk are not deleted with it

Deleting the instance leaves behind the Secret holding its password and, usually, the volume claim holding its data. Both are separate objects. Remove them yourself when you are done - see Delete - or the disk keeps costing you.

Where the console differs from the CLI

	Console	oc
Password	Generated and stored for you	You create the Secret
Image, limits, storage class	Fixed, not shown	You write them out in full
Readiness	Not shown - the operator reports none	Check the pod and the volume claim
Cleanup	Instance only	You delete the Secret and claim too