#Iteration with local kube

1 messages · Page 1 of 1 (latest)

exotic ruin
#

I certainly don't want to rebootstrap Kube every time I build and stage my app in

drowsy depot
#

they don't need to be in the same session, no. You can keep your kube cluster running in one session, and iterate your app in a different one

exotic ruin
#

Is the local registry the bridge here?

#

e.g. build and publish to the registry

drowsy depot
#

one thing to take into account though is that since your kube cluster will be "stateful", you'll have to take care of garbage collection and idempotency yourself as you're not starting from scratch every time

#

yes, the registry would be the bridge

exotic ruin
#

Got it, yes, I think dealing with side effects is hopefully straightforward. I could see a gc module handling that. Maybe a hook on publishing to the local registry or something