This repository contains Golang programs which are most likely to be of use to fellow OpenShift developers, especially members of the machine-config-operator team. The helpers found here may be of use to you. They may not. They may completely break entirely.
It is worth mentioning that these helpers may get your cluster into a difficult-to-recover-from state. So do not use these on a production OpenShift cluster.
With the exception of the cluster-lifecycle helper, these helpers are now
actively being maintained within the Machine Config Operator repository
described above.
Pre-built binaries for Linux and Mac on both amd64 and aarch64 architectures
are available for download via the GitHub
Releases
page. All one has to do is download them and place them somewhere in your
PATH.
These binaries are built using goreleaser running as a GitHub Action. If you're using a Mac, you'll need to jump through a few hoops to make these work for right now.
In the future, I plan to make each individual binary available for download in addition to the current archive scheme.
Starting with v0.0.21, you can podman pull quay.io/zzlotnik/zacks-openshift-helpers:latest to get the latest version of
these binaries. Images are built for both AMD64 and ARM64 architectures. These
images also contain the latest stable versions of the oc and kubectl
commands since there are some portions of my helper binaries that shell out to
these commands in order to take the path of least resistance.
Full list of tags may be found here.
It is also worth noting that these binaries are also baked into the following images as well, along with a few other of my favorite tools for working with Kubernetes clusters:
quay.io/zzlotnik/toolbox:mco-fedora-43
Note: Although these images are rebuilt daily, there will be up to a 24-hour delay between when the latest binaries are made available here and when they are available in those images.
Libraries and other code within this repository can be removed at any time. This means this repository should not be used as a dependency. Any deleted code shall be preserved within the Git history of this repository.
Any past binaries or container images produced via GitHub Actions will not be actively pruned or deleted. However, they should be used at your own risk.