Recently, I started a leadership position on a new squad focused on OpenShift on IBM Power Systems. Two of my teammates have posted blogs about their work: I hope you found these as useful as I did. Best wishes, PB
As many know, Go is a designed to build architecture and operating system specific binaries. These architecture and operating system specific binaries are called a target. One can target GOARCH=ppc64le GOOS=linux go build to build for the specific OS. There is a nice little tweak which considers the architectures version and optimizes the selection of the ASM (assembler code) uses when building the code.
As many know, Go is a designed for performance with an emphasis on memory management and garbage collection. When used within cgroups with Kubernetes and Red Hat OpenShift Go maximizes for the available memory on the node and the available processors. This approach, as noted by Uber’s automaxprocs, a shared system can see slightly degraded performance when allocated CPUs are not limited to the actually available CPUs (e.g., a prescribed limit).
Here are my notes for setting up the SIG’s nfs-provisioner. You should follow these directions to setup the nfs-provisioner
[openshift-install-power](https://github.com/ocp-power-automation/openshift-install-power) – this is a small recipe for deploying the latest code with the UPI from master branch @ my repo
I recently had to work with the Kubernetes Topology Manager and OpenShift. Here is a braindump on Topology Manager
I needed to switch from calico to flannel. Here is the recipe I followed to setting up Kubernetes 1.25.2 on a Power 10 using Flannel.
You see there is an issue with the unpacking your operator in the Operator Hub. Recreate the Job that does the download by recreating the job and subscription. Find the Job (per RH 6459071) 2. Reset the download the Job 3. Recreate your Subscription and you’ll see more details on the Job’s failure. Keep an eagle eye on the updates as it rolls over quickly. You’ve seen how to restart the download/pull through job.
tips and tricks on building a cluster-api image