Spent hours iterating over a skeleton repo for my new blog.

Built a Github Actions > Docker Container > Helm Chart > Kubernetes Deployment pipeline for the new blog and website.

Completely refactored my infrastructure monorepo.

Upgraded all helm chart versions, migrated a test app from nginx-ingress to nginx-gateway (the new “better ingress API” for Kubernetes), all containers now run unprivileged.

Finalized texts, translations, structure and visuals of the company website I’ll launch soon.

I haven’t even used up the 5USD bonus I got for paying 10USD.

You have to help it out sometimes, you have to be clear in your instructions but once you’ve got the hang of it, it feels like you have your own JARVIS.

nostr:nevent1qqs2es6ajehy7fwypme3pkqq9eev2prk0lla5ekmzgzrmat6c8ued5czyqd9el63rrg8rgk963jngue6hw0nmn0ugxeymvqn9lpqm0cpca0hsqcyqqqqqqgpr3mhxue69uhkummnw3ex2mrp0yhxx6tjvd6k6tnnwpskxegmmkuj9

Reply to this note

Please Login to reply.

Discussion

For example: I provided instructions for the installation and configuration of the nginx-gateway-fabric helm chart and it didn’t understand that flux (CI) needed a special oci repo type. I provided an example from the docs and it just worked it out on its own. It did the entire “side by side” configuration to prevent conflicts with nginx-ingress by itself.

As long you know what you’re doing, it’s like having a few junior engineers at your disposal that just need some oversight and code review here an there.

Could I have done all this by myself? Sure. But it would’ve taken longer to write down all the YAML by hand, grasp all dependencies in my repos and hunt down the right Github Actions snippets by myself. Instead, I read about a quarter of a (albeit short) book while enjoying coffee in the sun.