`kubectl set image [...]` to update the image that kubernetes is using
Or, even better, you can just set up CI to do everything on commit/push.
For the last static site I deployed, I just tossed Caddy on k8s and set up the git module. I commit, push, hit f5, and my site is already there. There's a ton of ways you can use kubernetes, which is probably part of the adoption problem.
Along with this a lot of people fail to also take into consideration flow that is NOT the happy path.
With k8s and a proper build system, you can roll back easily if you introduce a bug or something doesn't work. More importantly if your site doesn't start up in any specific way you deploy it, k8s won't even start a new pod.
Everything sounds all fine and dandy if all you think about is the happy path.
- `jekyll build` to build `_site`
- `neocities push _site` to recursively upload modified files in _site