WIP: Test release

[kingdonb]

Testing these beta / non-canonical releases here:

• Test release (2.23.11 / 2.24.0-beta.6) kingdonb/hephy-workflow-beta#2

Related:

• WIP: Test release builder#74
• WIP: test release slugbuilder#28
• WIP: test release controller#175
• WIP: test release dockerbuilder#15
• WIP: test release slugrunner#14
• WIP: test release postgres#19
• WIP: test release fluentd#22
• WIP: Test release redis#8
• WIP: test release logger#10
• WIP: test release minio#13
• WIP: Test release monitor#18
• WIP: Test release nsqd#17
• WIP: test release registry#9
• WIP: test release registry-proxy#5
• WIP: test release registry-token-refresher#13
• WIP: Test release router#78
• WIP: test release workflow-manager#7
• Tested with a tweak to use the controller image from kingdonb/controller:git-7beda111

We can see that all put together and working, deployed via Flux with continuous semver policy-driven upgrades here:

• https://github.com/kingdonb/bootstrap-repo/tree/main/apps/hephy
• https://github.com/kingdonb/bootstrap-repo/tree/main/clusters/hephy-staging/hephy

[kingdonb]

That's everything for now. I added kingdonb/hephy-workflow-beta#2 so we can review these changes all in one place, (it's clear from the diff that some changes are bad and should not be reverted)

This is the release tooling we've been missing in the past, the only drawback is I'm publishing charts to test. So it's nice that the repo is called "beta" so nobody confuses it with release charts. (Yes... that will work...)

[kingdonb]

Someone still must test the default config. I have a feeling there's an error in this file:

https://github.com/kingdonb/hephy-workflow-beta/pull/2/files#diff-3d8993cbbaef0b362c1c60e6264fcf1d767c6cc42f370985f264a17b179e2a0fR7

Or maybe it's fine. IDK if an empty annotations: is going to parse fine or if it's going to blow something up. I have only tested this config with the custom controller image and with global.use_native_ingress: true

I can test this later on, it's just challenging to test because I only have one Kubernetes node still pinned to 1.23.x with Docker Engine for CRI, (so I guess I should also test on newer versions of Kubernetes and with containerd.)

We should come up with a configuration that works on modern Kubernetes, even if it needs to deprecate Docker Builder.

But I would much prefer to publish a release with Docker Builder transitioned to directly leverage either Buildkitd or Kaniko!

[kingdonb]

I included this PR in a postscript note from the October Team Hephy Open Roadmap, which happened asynchronously in the Slack. If you're having trouble reaching us, or not able to get on the Slack, please bear with us. Within a few months, I think we should have every one of our static sites re-homed on Fermyon Cloud 🤞

https://blog.teamhephy.info/blog/posts/attic/how-hard-can-it-be-static-sites-on-fermyon-cloud

Watch this space