5 ms·
Having a tool that'd make it easy to run the app locally for development and at the same time have roughly the same files used in production. Docker compose got
by Reitet00 3y ago
Having a tool that'd make it easy to run the app locally for development and at the same time have roughly the same files used in production. Docker compose got this mostly right, compare compose with the complexity of running locally service in micro Kubernetes cluster.
- potatocannon 3y agotilt.dev
- Reitet00 3y agoLooks okay but I was looking for something that wouldn't require learning yet another config language and would rather take k8s yamls that I already have (or require minimal modifications).
- jaguar75 3y agoCheck out https://www.signadot.com/ https://www.signadot.com/. Full disclosure, I'm the founder, but it could help with what you’re looking for.
- Reitet00 3y ago> Define Sandboxes using a simple YAML file, specifying customizations relative to the baseline environment. Maintain these YAML files in your git repository and standardize Sandboxes across your organization. It looks like these yaml files are not k8s files that I already have? Also, is it open source? (I couldn't find a link to source on mobile)
- jaguar75 3y agoYes, these are our (thin) YAML files via which you describe the Sandboxes in terms of deltas from the baseline env. The K8s yaml files remain as the source of truth for your standard deployments. The operator is not open source. Some components like the CLI and Resource plugins are. We do have a free tier, however.
- Reitet00 3y agoOkay, thanks for the explanation!
- ojhughes 3y agoCheckout Skaffold and kustomize as well
- omniglottal 3y agoMinikube
- Reitet00 3y agoMinikube is just one piece but it's not functionally equivalent to `docker compose run` since I'd still have to build and push docker images and edit k8s yamls manually (compose run will build containers and start them, no need to edit anything) .
- peterbecich 3y agoIt would be very useful IMO to be able to easily move a service outside of Kubernetes. The goal is to move the "fast loop" development outside of any container, onto the native system. If I am not mistaken, all of the tools which help this either rebuild a container, or rebuild inside a container, right? Given a Kubernetes application with service names, port forwards, etc., I would like to have an option to automatically convert these configurations into `ExternalName`, external port forwards, etc. This would be transparent to all services, inside and outside Kubernetes. I think it can be done manually today. My colleagues at my last job wrote a helper script; credit to them for the idea. I think it could be built into `kubectl`. i.e. `kubectl apply --externalize serviceA`