|
|
|
|
|
by Reitet00
1122 days 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. |
|
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`