commits.to

https://github.com/fluxcd/image-automation-controller/issues/159#issuecomment-864353312 – this should be documented somewhere in big bold letters with brightly colored circles and crosses, with arrows if necessary. Put it in a PR, the PR does not have to land in order to count this commitment as discharged.

This can go on the Team Hephy blog, and/or be cross-posted on the Flux blog. Show the three ways to install Flux without using the Flux CLI: (1) installing OLM, then installing Flux, per Operator Hub instructions. (show how this is broken) (2) Use https://github.com/operator-framework/kubectl-operator to run `kubectl operator install -n flux-system flux --create-operator-group` which fixes the broken thing from 1, finally (3) Build and deploy locally OpenShift console, then hijack a Bearer token from cluster-admin https://github.com/openshift/console and run Flux install from the OperatorHub in Console. (4) explain why hijacking a bearer token is a terrible idea, and how OpenShift users can skip straight to 3 without the bearer token, but what else they must know. (What else? https://github.com/fluxcd/flux2-multi-tenancy and https://github.com/fluxcd/kustomize-controller/pull/349, https://github.com/fluxcd/flux2/pull/582)

Find out if they would be interested in a 2-day event that was fully asynchronous, general feedback about whether they would consider joining Bug Scrub in the future again, and what changes they would like to see to the structure or organization of the event.

Personal