<story><title>Show HN: Gitkube – Deploy to Kubernetes Using Git Push</title><url>https://gitkube.sh/</url></story><parent_chain></parent_chain><comment><author>praseodym</author><text>We’ve been using a similar solution for a while now: pushes to GitHub trigger Travis CI to build a Docker images. These get pushed to Docker Hub or Quay, which triggers a webhook to Keel.sh[1] running in our Kubernetes cluster. Keel then updates the Kubernetes deployment to perform a rolling update of the application.&lt;p&gt;1: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;keel.sh&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;keel.sh&lt;/a&gt;</text></comment>
<story><title>Show HN: Gitkube – Deploy to Kubernetes Using Git Push</title><url>https://gitkube.sh/</url></story><parent_chain></parent_chain><comment><author>lima</author><text>Red Hat&amp;#x27;s OpenShift[1] Kubernetes distribution can do this too - you even get a webhook for GitHub copy and paste.&lt;p&gt;Kubernetes is a toolbox, not a product. There&amp;#x27;s so much you have to set up yourself (build system, registry, security, logging stack, metrics...). That&amp;#x27;s fine if you&amp;#x27;re in the business of selling Kubernetes itself, but otherwise, most teams should use something like OpenShift and not re-invent the wheel.&lt;p&gt;[1]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;openshift&amp;#x2F;origin&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;openshift&amp;#x2F;origin&lt;/a&gt;</text></comment>