2 ms·
This article is pretty focused on the build type of k8s developer tools. There are other types as well that can fit into specific places in your workflow. Joe B
by pyronicide 9y ago
This article is pretty focused on the build type of k8s developer tools. There are other types as well that can fit into specific places in your workflow. Joe Beda does a fantastic high level overview of the different types in last week's #tgik8s: https://www.youtube.com/watch?v=QW85Y0Ug3KY https://www.youtube.com/watch?v=QW85Y0Ug3KY .
Here's a couple tools that try to tackle this problem in different ways:
- Ksync - `docker run -v local:remote` for your k8s cluster (https://github.com/vapor-ware/ksync https://github.com/vapor-ware/ksync)
- Telepresence - extend the cluster network locally (https://www.telepresence.io/ https://www.telepresence.io/)
- Forge - end to end development through deployment (https://forge.sh/ https://forge.sh/)
- alberteinstein 9y agoYes, ksync and telepresence lets you develop on k8s cluster as if you were doing on the local system. Haven't looked at forge yet. These tools are really useful when you're writing code dependent on other components or features on the cluster (like DNS). They save you a lot of port forward, environment variable hassles. Gives high velocity development flows, which were quite long build-push-deploy workflows earlier.
- iooi 9y agoThanks for linking to that video, do you follow any other series or blogs to learn more about K8s?