I finally got a right-sized flavor for an OpenShift deployment: 25 GB Disk, 4 VCPU, 16 GB Ram. With that, I tore down the old cluster and tried to redeploy. Right now, the deploy is failing at the stage of the controller nodes querying the API port. What is going on?Read more
Before I can run Keystone in a container, I need to initialize the database. This is as true for running in Kubernetes as it was using podman. Here’s how I got keystone-db-init to work.Continue reading
The tools you use should help you grow from newbie to power user. OpenShift’s command line is one such tool. When getting started with Kubernetes development, the new-app option to the oc command line can help movbe you along the spectrum.Continue reading
An earlier port hard coded the IP address and port used for MariaDB connections. I want to pull these out so I can pass them in on the command line when I create the client.Continue reading
Last time I showed how to recreate a WebUI-generated MariaDB deployment from the command line. But how should you really generate it in the first place? Let’s walk through:Continue reading
Web base user interfaces are great at walking a user through tasks they do not know how to perform yet. In my case, I want to launch a MariaDB instance on OpenShift. Eventually, I want to do this from the command line. Here are my steps.
I set up a MariaDB server and wanted to test it out. There are many docs out there about how to set up the client. This is what worked for me.
First, find out the internal IP address of the Database server pod:
oc get pod -l name=mariadb -o json | jq -r '. | .items | .status | .podIP '
In my case, that returned 10.131.0.81. Which lead to this command:
kubectl run -it --rm --image=mariadb:latest --restart=Never mariadb-client -- mysql keystone -h 10.131.0.81 --user keystone -pkeystone