Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Draft, Gitkube, Helm, Ksonnet, Metaparticle, Skaffold – Comparison of K8s Tools

blog.hasura.io

Post reply on HN
Print view View original

1–10 of 23 posts

Re: Draft, Gitkube, Helm, Ksonnet, Metaparticle, Skaffold – Comparison of K8s Tools

#3

Post by pyronicide »

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/)

Re: Draft, Gitkube, Helm, Ksonnet, Metaparticle, Skaffold – Comparison of K8s Tools

#4

Post by tirumaraiselvan »

mmillin wrote: post #2

One tool not mentioned in the article is Jenkins X [0]. It leverages some of the technologies from draft to create a GitOps workflow for full build-push-deploy with CI and CD. [0] http://jenkins-x.io/

One thing that differentiates these tools from Jenkins x is that they have synchronous flows rather than async webhooks model as in Jenkins x. The sync model is more apt for immediate feedback which you need in development phase.

Re: Draft, Gitkube, Helm, Ksonnet, Metaparticle, Skaffold – Comparison of K8s Tools

#5

Post by alberteinstein »

pyronicide wrote: post #3

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 c…

Yes, 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.

Re: Draft, Gitkube, Helm, Ksonnet, Metaparticle, Skaffold – Comparison of K8s Tools

#8

Post by _5meq »

irickt wrote: post #7
p3llin0r3 wrote: post #6

https://keel.sh/ is also a great release manager / chatops framework. edit: I had keel.io which is some random company. The site I wanted was keel.sh

spam? Link is about portfolio analysis.

I'm not spam! Also keel is completely free and open source!

Edit: I now see what happened, fixed.

Post reply on HN