IngwiePhoenix on Nostr: Why kubernetes? - Docker Compose on steroids (and painkiller deficit) - Deploy ...
Why kubernetes?
- Docker Compose on steroids (and painkiller deficit)
- Deploy jenkins, make Jenkins build images, deploy images to registry.
- Point deployment at registry.
- Make jenkins update builds on it's own.
- Now Jenkins will cycle through things!
I want to implement this for RISC-V images as well as for Nostr things; like building super optimized smol images (i.e. statically compiled, distroless, strfry - or nsecbunkerd images with a most minimal footprint and such).
Down the road I want to explore interacting with the API programmatically; i.e. make a controller that creates nsec/npub pairs for deployments that request one - or send important notifications via DM. o.o
I have plans, and my work needs me to know kubernetes. So might as well commit 100%. When it's all done I will have a 5 node cluster, with 4x ARM and 1x RISC-V =)
... did I mention that I _might_ have an SBC addiction...? dem things are too much fun o-o
- Docker Compose on steroids (and painkiller deficit)
- Deploy jenkins, make Jenkins build images, deploy images to registry.
- Point deployment at registry.
- Make jenkins update builds on it's own.
- Now Jenkins will cycle through things!
I want to implement this for RISC-V images as well as for Nostr things; like building super optimized smol images (i.e. statically compiled, distroless, strfry - or nsecbunkerd images with a most minimal footprint and such).
Down the road I want to explore interacting with the API programmatically; i.e. make a controller that creates nsec/npub pairs for deployments that request one - or send important notifications via DM. o.o
I have plans, and my work needs me to know kubernetes. So might as well commit 100%. When it's all done I will have a 5 node cluster, with 4x ARM and 1x RISC-V =)
... did I mention that I _might_ have an SBC addiction...? dem things are too much fun o-o