That moment when you think you should finally set up a #kubernetes #prow instance for fun.

And you google: "setting up my own prow instance"

And scroll down and find your own #blog post about how you got it done back in 2020.

Welp that was very surprising.

Wanted! Looking for companies and individuals who know how to fix this.

I want to connect with you to discuss such matters.

Small projects available, plus larger tenders soon.

Connect or contact me.

#projects #rightsofway #footpath #bridleway #activetravel #ELMS #PROW

@nalum #fluxcd v2 + #Mozilla #sops + #Vault is nice! I prefer it over #argoCD (I heard that AWS moved away from argo to flux).

For managing k8s resources I prefer simple and small controllers written in Go listening only to small subset of resources instead of what #kyverno is doing: intercepting every kubernetes api server traffic, which might be a bottleneck or a single point of failure, which I would avoid. But not sure, have not much experience with it.

I use mostly #kubebuilder code generators which I prefer over Operator Framework. Only unit-testing with the K8s fake client is not possible to an extend I would expect...
So we try to get more integration tests in our pipeline via ephemeral Kind/minikube/... clusters via #prow - which is not that straight forward...