A brief Operator training I gave to my team resulted in these notes. Thanks to many others in the reference section. An Operator codifies the tasks commonly associated with administrating, operating, and supporting an application. The codified tasks are event-driven responses to changes (create-update-delete-time) in the declared state relative to the actual state of an application, using domain knowledge to reconcile the state and report on the status.
This document outlines the installation of the OpenShift on Power, the installation of the Red Hat Single Sign-On Operator and configuring the two to work together on OCP. Thanks to Zhimin Wen who helped in my setup of the OIDC with his great work. Steps Setup OpenShift Container Platform (OCP) 4.x on IBM® Power Systems™ Virtual Server on IBM Cloud using the Terraform based automation code using the documentation provided. You’ll need to update var.tfvars to match your environment and PowerVS Service settings. At the end of the deployment, you see an output pointing to the Bastion Server. Add Hosts Entry Connect via SSH You’re connecting on…
built a demonstration using GoLang, JSON, bcrypt, http client, http server to model an actual IDP. This is a demonstration only; it really helped me setup/understand what’s happening in the RequestHeader.
Debugging weird traffic patterns on the mac, you can use [nettop]. It shows the actual amount of data transferred by the process. It’s very helpful.