Comment by killingtime74
10 days ago
Myself I already pre-provisioned a kubernetes cluster and it just makes new manifests and deploys there. Less dangerous, less things for it to fail at. The networking is already setup. The costs are known/fixed (unless you autoscale in the cloud). It's much faster to deploy.
Same same... i have prepared a sample config file with most of most common k8s object types as examples and just use that as a skill. I have given it access to my test cluster. I have configured my own container registry as well. Claude generates perfect deployment artifacts every single time. Works superbly well. I use k3s btw.
Same, I love k3s, so convenient for baremetal self hosted
Im running like upwards of 30 difference services(mixed types) on a single 6$/m contabo instance lol ... such a pleasant ci/cd experience.. no messy webhooks or complicated scripts on integrations... just 2-3 hardcoded commands and plain old k8s config files.. love it.
Fair enough, is this mainly for running services or do you use it for dev loop too?
both. local k8s (Rancher desktop) for devloop integration tests, remote k8s for running services. Helm chart to bootstrap cluster services like CRDs and Cloudflare tunnel.