pyronicide
Joined 17 years ago
Karma
455
Submissions
50
Member since
Aug 15
Recent submissions
Comment · 5 years ago
Comment · 8 years ago
Check out ksonnet, it is closer to what you're looking for. (https://ksonnet.io/)
Comment · 8 years 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 .
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)
- Telepresence - extend the cluster network locally (https://www.telepresence.io/)
- Forge - end to end development through deployment (https://forge.sh/)
How are you planning on managing the publishing workflow for non-devs? Marketing and docs teams tend to struggle quite a bit with git specific flows.