<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Continuous Delivery on Random Musings</title><link>https://chengl.com/tags/continuous-delivery/</link><description>Recent content in Continuous Delivery on Random Musings</description><generator>Hugo</generator><language>en-us</language><copyright>Cheng Long</copyright><lastBuildDate>Sun, 30 Jul 2017 16:07:37 +0000</lastBuildDate><atom:link href="https://chengl.com/tags/continuous-delivery/index.xml" rel="self" type="application/rss+xml"/><item><title>kubectl Authentication Made Simple</title><link>https://chengl.com/post/kubectl-authentication-made-simple/</link><pubDate>Mon, 30 Jan 2017 09:25:00 +0000</pubDate><guid>https://chengl.com/post/kubectl-authentication-made-simple/</guid><description>&lt;p&gt;While working on a continuous delivery pipeline to automate deployment to Google Container Engine (GKE), I found that getting &lt;code&gt;kubectl&lt;/code&gt; to work is very &lt;a href="https://kubernetes.io/docs/user-guide/sharing-clusters/#manually-generating-kubeconfig"&gt;complex&lt;/a&gt;&lt;a href="http://stackoverflow.com/questions/40426071/kubectl-access-to-google-cloud-container-engins-fails"&gt;and&lt;/a&gt;&lt;a href="http://stackoverflow.com/questions/40408321/whats-the-cli-authentication-process-as-of-google-container-engine-kubernetes-1"&gt;convoluted&lt;/a&gt;, especially when it needs to be &lt;a href="https://circleci.com/docs/continuous-deployment-with-google-container-engine/"&gt;noninteractive&lt;/a&gt;. So I want to find out the easiest way to get &lt;code&gt;kubectl&lt;/code&gt; working noninteractively.&lt;/p&gt;
&lt;p&gt;Assuming that &lt;code&gt;gcloud&lt;/code&gt; and &lt;code&gt;kubectl&lt;/code&gt; are already installed but not necessarily setup, &lt;strong&gt;ONLY&lt;/strong&gt; two commands are needed to get &lt;code&gt;kubectl&lt;/code&gt; working noninteractively (verified with Google Cloud SDK 141.0.0 and kubectl 1.5.2)&lt;/p&gt;</description></item><item><title>Docker Workflow</title><link>https://chengl.com/post/docker-workflow/</link><pubDate>Wed, 25 May 2016 09:07:00 +0000</pubDate><guid>https://chengl.com/post/docker-workflow/</guid><description>&lt;p&gt;In my previous posts, I demoed how to orchestrate Docker with &lt;a href="https://chengl.com/orchestrating-docker-using-swarm/"&gt;Swarm&lt;/a&gt; and &lt;a href="https://chengl.com/orchestrating-docker-with-kubernetes/"&gt;Kubernetes&lt;/a&gt;. They all assume the Docker image &lt;a href="https://hub.docker.com/r/chenglong/simple-node/"&gt;chenglong/simple-node&lt;/a&gt; is already there and ready to be deployed. But how to develop that image in the first place? How to streamline and automate the process of developing it on local machine, building and testing it on Continuous Integration (CI) server, and finally deploying to production?&lt;/p&gt;
&lt;p&gt;This post introduces one possible Docker workflow.&lt;/p&gt;</description></item></channel></rss>