<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Lin Sun on Medium]]></title>
        <description><![CDATA[Stories by Lin Sun on Medium]]></description>
        <link>https://medium.com/@linsun-unc?source=rss-4d3349d0cab2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*aR6DHazPjk3s6VR_FHiaYg@2x.jpeg</url>
            <title>Stories by Lin Sun on Medium</title>
            <link>https://medium.com/@linsun-unc?source=rss-4d3349d0cab2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:45:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@linsun-unc/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[First Month From Mega-Corporate to Startup]]></title>
            <link>https://linsun-unc.medium.com/first-month-from-mega-corporate-to-startup-70afa23096a1?source=rss-4d3349d0cab2------2</link>
            <guid isPermaLink="false">https://medium.com/p/70afa23096a1</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[istio]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[service-mesh]]></category>
            <dc:creator><![CDATA[Lin Sun]]></dc:creator>
            <pubDate>Wed, 31 Mar 2021 02:49:02 GMT</pubDate>
            <atom:updated>2021-03-31T02:58:50.452Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Why did I change my job?</strong></h3><p>I am an extremely risk-averse person, which you can probably tell by the fact that I worked at IBM for 19 years. Not only that, I don’t believe in debt, and I pay off any debt as fast as I can. I had planned to work at IBM for a few more years and then slowly travel worldwide to explore and learn about different places and cultures.</p><p>Out of all of the negativeness, COVID has freed me from many around-town driving activities or traveling for work or vacation, so I have a lot more time to think these days. I started to think about what is important to me and what makes me happy. Family always comes first, and I also found I enjoy learning and exploring new things. Have you ever had your best ideas while you were on vacation? I believe innovation happens with new environments and new people. While I couldn’t change my home office during a pandemic, I could change my job to create that new environment.</p><p>I have been working on Istio since the beginning of the project, and the project is becoming the Kubernetes for service mesh. It would be unwise for me to work on something completely different. After being impressed by how fast the <a href="http://solo.io/">Solo</a> team delivers and what they offer around service connectivities and Istio, I decided to give it a shot. What could I lose? I could always find another job.</p><h3>Transition of emotions</h3><p>After I decided to leave IBM, I was very sad. I had a fantastic career at IBM and made lots of friends along the way. I had exciting assignments and a side hustle as an inventor. IBM rewarded me very well for my patents — I made enough money to purchase my first house.</p><p>At the same time, I was also very excited yet nervous about the new job. While I am eager about adopting into the new environment, I know the Solo team delivers at rapid speed. Would I be able to fit in? Could I meet their expectations? Could I execute fast enough? How could I be a leader when everyone else knows way more about Solo than me?</p><p>Now that I have survived the first month and feel that I am still trusted and I can continue to deliver, I am no longer as afraid and I’ve learned many things along the way, including our cloud-based payroll &amp; expense systems and many excellent tools, such as <a href="https://github.com/derailed/k9s">k9s</a>, <a href="https://github.com/tmux/tmux/wiki">tmux</a>, <a href="https://concepts.app/en/">concepts</a>, <a href="https://www.descript.com/">descript</a>, etc. I started to create some small projects during the weekends because it was fun. For example, I was super excited about the first IstioCon and made this video the Sunday before the conference:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QMKJQiGVcdLFRL4SZVabuA.png" /><figcaption>from <a href="https://twitter.com/linsun_unc/status/1363584644168482821?s=20">https://twitter.com/linsun_unc/status/1363584644168482821?s=20</a></figcaption></figure><p>I was also very excited about our Deploy Istio to production workshop and created this diagram to illustrate the first lab:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X9yapYIbAd7oXVeW1B-l2w.png" /><figcaption>from <a href="https://twitter.com/linsun_unc/status/1375273326579437569?s=20">https://twitter.com/linsun_unc/status/1375273326579437569?s=20</a></figcaption></figure><h3>Surprises I learned working at a startup</h3><p>I’ve encountered a few surprises coming from a mega-corporate to a startup during my first month:</p><ol><li>Get ready to share your cell phone number. In a big corporation, an employee may share cell phone numbers with their direct manager, but it is otherwise rare. Texting is a standard communication method at a startup, and people may call you without asking for permission.</li><li>Working at a small startup feels like working with a family where we say happy birthday to each other in our slack channel. I felt much welcomed when I joined (Hey — I even made it to the company <a href="https://www.solo.io/our-news/solo-io-announces-general-availability-of-gloo-mesh-enterprise-delivering-a-command-center-for-service-mesh-management/">news announcement</a>!) and have thoroughly enjoyed our social events so far. For example, during a company-wide virtual tea party, we had special guests who taught us the teas’ histories in our tea box, and we made tea together virtually.</li><li>Endorse the culture of execution, then report. There won’t be rounds of meetings to discuss things before any work starts. Startups often have tight deadlines, and execution happens after a brief level set of goals. There are no multi-level approvals involved. Many times I just tell people, “I did this.”</li><li>I feel more motivated and determined at work. The company performance is tied to each of us, and every extra thing I do makes a significant impact. I started to hear people telling me, “You are awesome.” I rewarded them with big shoutouts when they did a good job.</li><li>I feel empowered to think outside the box. Without many rules and policies in place and a very flat reporting structure, it is easier for me to challenge myself to think differently while still feeling trusted.</li></ol><h3>Let us wrap up</h3><p>I hope I provided some interesting perspectives for those thinking about changing jobs. I am glad I was brave enough to push myself outside of my comfort zone. I’m super grateful that the Solo team took a leap of faith and invited me on board. I am happy that I am no longer limited to think and execute within my small matrix in a mega-corporate. I am excited that I get to dream and continue learning in the new environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70afa23096a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Debug Istio components with GoLand]]></title>
            <link>https://linsun-unc.medium.com/debug-istio-components-with-goland-b0f9f9f60384?source=rss-4d3349d0cab2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0f9f9f60384</guid>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[debug]]></category>
            <category><![CDATA[istio]]></category>
            <dc:creator><![CDATA[Lin Sun]]></dc:creator>
            <pubDate>Mon, 18 Mar 2019 16:17:49 GMT</pubDate>
            <atom:updated>2019-03-18T16:17:49.863Z</atom:updated>
            <content:encoded><![CDATA[<p>Sometimes you may find it useful to attach a debugger to a process and step through the code. When everything is running locally on your laptop, it is fairly easy to debug and step through the code. However, sometimes code is not running locally as it needs to interact with other services. In this article I will show you how I setup an environment to debug Istio processes.</p><p>Below are the few steps to I used to debug <a href="http://github.com/istio/istio">Istio</a> components, using <a href="https://github.com/istio/istio/tree/release-1.1/pilot">istio-pilot</a> and <a href="https://www.jetbrains.com/go/">GoLand</a> as an example. While I used Istio component as an example, the same technique and flow can be used to debug other Golang deployments that require interaction with other services in Kubernetes.</p><p>Environments I used:</p><ol><li>MacOS High Sierra v10.13.4.</li><li>A Kubernetes v1.13.0 cluster from minikube v0.34.1, based on the <a href="https://preliminary.istio.io/docs/setup/kubernetes/prepare/platform-setup/minikube/">minikube setup</a> instruction for Istio.</li><li>GoLand IDE v2018.3.</li><li>Installed all prerequisites from Istio <a href="https://github.com/istio/istio/wiki/Dev-Guide">development guide</a>.</li></ol><p>Sample s: <a href="https://github.com/linsun/debug-istio/tree/master/pilot">https://github.com/linsun/debug-istio/tree/master/pilot</a></p><h4>1. Produce the debug docker image</h4><p>Copy the dlvdebugger into the image and change the entry point to start the pilot-discovery process using the dlv debugger. I had the dlv file for ubuntu locally on my laptop and I copied it to the Docker image. I also installed the latest golang (v1.12 at the time of this writeup) in the Docker image. My code base is at Istio v1.1 release candidate 5level thus I used <em>docker.io/istio/pilot:1.1.0-rc.5</em> as my base Docker image.</p><pre>From docker.io/istio/pilot:1.1.0-rc.5<br><br>EXPOSE 40000<br><br>ADD files/dlv /root/go/bin/dlv<br>RUN sudo cp /root/go/bin/dlv /usr/local/bin/dlv<br>RUN chmod +x /usr/local/bin/dlv<br>ENTRYPOINT [&quot;/usr/local/bin/dlv&quot;, &quot;--listen=:40000&quot;, &quot;--headless=true&quot;, &quot;--api-version=2&quot;, &quot;exec&quot;, &quot;/usr/local/bin/pilot-discovery&quot;, &quot;--&quot;]</pre><p>The Dockerfile and dlv files are available <a href="https://github.com/linsun/debug-istio/tree/master/pilot">here in my GitHub</a>. Build the Docker image and push it to your image registry, e.g.</p><pre>docker build -t docker.io/linsun/pilot-rc5-debug:latest .<br>docker push docker.io/linsun/pilot-rc5-debug:latest</pre><h4>2. Leverage the new Docker image and expose the debug port</h4><p>Generate a istio-minimal.yaml file from the <a href="https://preliminary.istio.io/docs/setup/kubernetes/install/helm/#option-1-install-with-helm-via-helm-template">minimal istio</a> profile:</p><pre>helm template $HOME/istio-fetch/istio --name istio --namespace istio-system --values $HOME/istio-fetch/istio/values-istio-minimal.yaml &gt; istio-minimal.yaml</pre><p>Edit the istio-pilot deployment in your istio yaml and add the snippet below on the discovery container to expose a debug port number, e.g. 40000.</p><pre>          ports:<br>          - containerPort: 8080<br>          - containerPort: 15010<br>          - containerPort: 15011<br><strong>          - containerPort: 40000<br>            name: debug<br>            protocol: TCP</strong></pre><p>While you are at the file, also edit the discovery container to use the newly created debug docker image and change the imagePullPolicy configuration to Always .</p><pre>      containers:<br>        - name: discovery<br>          <strong>image: &quot;docker.io/linsun/pilot-rc5-debug:latest&quot;</strong><br>          <strong>imagePullPolicy: Always</strong></pre><p>Redeploy the istio yaml file which should redeploy the istio-pilotdeployment in your kubernetes cluster.</p><p>kubectl apply -f istio-minimal.yaml</p><h4>3. Setup port forward</h4><p>Setup port forwarding to forward the istio-pilot pod’s port 40000 to a unique port on localhost, e.g.</p><pre>kubectl -n istio-system port-forward $(kubectl -n istio-system get pod -l app=pilot -o jsonpath=&#39;{.items[0].metadata.name}&#39;) 40000:40000</pre><h4>4. Remote debug the code!</h4><p>Launch GoLand and open your Istio source code folder that you have cloned from the <a href="http://github.com/istio/istio">istio repository</a>. Setup breakpoint and click <strong><em>Run</em></strong>-&gt;<strong><em>Edit Configuration</em></strong> to create a remote pilot configuration based on the <strong><em>Go Remote</em></strong> template, like below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MDz3Zi47eP6igjumvdmOhg.png" /></figure><p>Click <strong><em>Run</em></strong> -&gt; <strong><em>Debug Remote Pilot</em></strong> to attach the debugger to the remote istio-pilotvia localhost:40000. You should be able to step through the code now!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KlZBrRS5AqeW3y_skN9fTg.png" /></figure><h4>Other things I have tried:</h4><ul><li>I had wanted to write this blog using <a href="https://code.visualstudio.com/">Visual Studio Code</a> but I could not get the remote debugging working and discovered that Goland worked really nicely. Visual Studio Code local debugging works fine for me.</li><li><a href="https://www.telepresence.io/">Telepresence</a> is a great idea however I could not get the steps described in the <a href="https://www.telepresence.io/tutorials/kubernetes">tutorial</a> working.</li></ul><p>One thing I haven’t had chance to explore is <a href="https://medium.com/solo-io/introducing-kubesquash-remotely-debug-your-kubernetes-pods-f3e3391eaf16">KubeSquash</a>, I hope I will get to try it soon. If you like this blog, click on the clap button. Enjoy the live debugging! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0f9f9f60384" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installing Helm Charts on IBM Bluemix Container Service]]></title>
            <link>https://linsun-unc.medium.com/installing-the-wordpress-chart-on-ibm-bluemix-container-service-769169d698ec?source=rss-4d3349d0cab2------2</link>
            <guid isPermaLink="false">https://medium.com/p/769169d698ec</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[helm]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[bluemix]]></category>
            <category><![CDATA[ibm-cloud]]></category>
            <dc:creator><![CDATA[Lin Sun]]></dc:creator>
            <pubDate>Thu, 27 Apr 2017 22:27:17 GMT</pubDate>
            <atom:updated>2017-04-28T19:16:01.074Z</atom:updated>
            <content:encoded><![CDATA[<p>As I explained in my previous <a href="https://medium.com/@linsun_unc/four-things-i-am-excited-about-the-new-ibm-bluemix-container-service-9f5c6971aaf9">blog</a>, IBM Bluemix Container Service provides native Kubernetes experience. <a href="https://github.com/kubernetes/helm">Helm</a> is an interesting tool to manage Kubernetes charts. <a href="https://github.com/kubernetes/charts">Charts</a> are curated Kubernetes applications, designed to work with Helm. I like to think of Kubernetes charts as cooking recipes, however, I need Helm to create my family’s favorite dishes out of these recipes, as Helm allows me to customize the recipes to create exactly what my family wants.</p><p>For this, I recommend you to deploy a paid IBM Bluemix Container Service cluster. Your kubectl should be configured to work with the cluster. If you don’t, you can follow <a href="https://console.ng.bluemix.net/docs/containers/cs_cluster.html#cs_cluster_ui">these steps</a> to deploy your cluster and <a href="https://console.ng.bluemix.net/docs/containers/cs_cli_install.html#cs_cli_install">these steps</a> to setup the bx and kubectl CLI. It is also important to make sure you have permissions to deploy persistent storage as the <a href="https://github.com/kubernetes/charts/tree/master/stable/wordpress">WordPress chart</a> uses persistent storage by default. Let’s begin the fun journey:</p><p>1. Install Helm: <a href="https://github.com/kubernetes/helm/blob/master/docs/install.md">https://github.com/kubernetes/helm/blob/master/docs/install.md</a></p><p>2. Install the WordPress chart:</p><pre>helm install --name my-wordpress-release --set wordpressUsername=admin,wordpressPassword=password,mariadb.mariadbRootPassword=secretpassword,persistence.storageClass=ibmc-file-bronze,mariadb.persistence.storageClass=ibmc-file-bronze stable/wordpress</pre><p>Note the simple parameters I passed into helm install to specify the name of the installation, and the configuration parameters based on the WordPress chart’s <a href="https://github.com/kubernetes/charts/blob/master/stable/wordpress/values.yaml">values.yaml</a> file. I had to use a specific storage class given IBM Bluemix Container Service doesn’t support the alpha storage class (yet).</p><p>3. Wait a minute or two to allow everything to reach running. Follow the output from the helm install command to locate the load balancer service IP.</p><pre># linsun at linsun in ~/workspace/k8s-yamls on git:master ✖︎ [16:30:48]</pre><pre>→ export SERVICE_IP=$(kubectl get svc --namespace default my-wordpress-release-wordpress -o jsonpath=&#39;{.status.loadBalancer.ingress[0].ip}&#39;)</pre><p>4. Open your favorite browser and visit <a href="http://$service_ip/admin"><em>http://$SERVICE_IP/admin</em></a> or <a href="http://$service_ip/admin"><em>http://$SERVICE_IP/</em></a></p><p>That’s it! You should have an awesome working WordPress application running now, just like the one below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1sZrQAtIdZq2dL2RMYbncQ.png" /></figure><p>Now let’s look at the set of Kubernetes resources that are deployed as the result of the WordPress chart installation.</p><pre>→ kubectl get deployment,pvc,secrets,svc,pods</pre><pre>NAME                                     DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE</pre><pre>deploy/my-wordpress-release-mariadb     1         1         1            1           5h</pre><pre>deploy/my-wordpress-release-wordpress   1         1         1            1           5h</pre><pre>NAME                                  STATUS    VOLUME                                     CAPACITY   ACCESSMODES   STORAGECLASS       AGE</pre><pre>pvc/my-wordpress-release-mariadb     Bound     pvc-e869506a-2abd-11e7-90d4-82fbcdd809af   20Gi       RWO           ibmc-file-bronze   5h</pre><pre>pvc/my-wordpress-release-wordpress   Bound     pvc-e8689f1f-2abd-11e7-90d4-82fbcdd809af   20Gi       RWO           ibmc-file-bronze   5h</pre><pre>NAME                                      TYPE                                  DATA      AGE</pre><pre>secrets/my-wordpress-release-mariadb     Opaque                                2         5h</pre><pre>secrets/my-wordpress-release-wordpress   Opaque                                3         5h</pre><pre>NAME                                  CLUSTER-IP     EXTERNAL-IP     PORT(S)                      AGE</pre><pre>svc/my-wordpress-release-mariadb     10.10.10.176   &lt;none&gt;          3306/TCP                     5h</pre><pre>svc/my-wordpress-release-wordpress   10.10.10.171   169.46.90.147   80:30420/TCP,443:32287/TCP   5h</pre><pre>NAME                                                  READY     STATUS    RESTARTS   AGE</pre><pre>po/my-wordpress-release-mariadb-1596346107-fxdrg     1/1       Running   1          5h</pre><pre>po/my-wordpress-release-wordpress-1704943544-0rbzs   1/1       Running   1          5h</pre><p>Holy cow, that is a lot of resources, including 2 persistent volume claims! As you can see, with Helm and Helm charts, users can easily deploy interesting applications like WordPress onto Kubernetes with one simple command -heml install, with their preferred ways as long as the configuration parameters are exposed in the values.yaml file. For example, for the WordPress chart, I can choose to enable ingress, change service type, disable persistence, or configure CPU and memory for the pods, etc.</p><p>Tools like Helm and charts are fascinating as they enable developers to quickly deploy curated Kubernetes applications and share them with many other users for reuse in each user’s preferred way. I look forward to deploying more charts on my Kubernetes cluster and possibly even make charts to share with you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=769169d698ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Four Exciting Things About the New IBM Bluemix Container Service]]></title>
            <link>https://linsun-unc.medium.com/four-things-i-am-excited-about-the-new-ibm-bluemix-container-service-9f5c6971aaf9?source=rss-4d3349d0cab2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f5c6971aaf9</guid>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[bluemix]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Lin Sun]]></dc:creator>
            <pubDate>Fri, 14 Apr 2017 01:36:23 GMT</pubDate>
            <atom:updated>2017-04-27T21:46:53.179Z</atom:updated>
            <content:encoded><![CDATA[<p>On March 20th, Kubernetes beta support was made available in <a href="https://www.ibm.com/cloud-computing/bluemix/containers">IBM Bluemix Container Service</a>. I have been using the new IBM Bluemix Container Service for a few weeks, from deploying the guestbook example to migrating the <a href="https://github.com/estesp/flightassist/">flightassist</a> Cloud Foundry application to it. Below is the top few things I am excited about it.</p><blockquote>Native Kubernetes experience</blockquote><p>I have been a big fan of Kubernetes, given its architecture is based on my favorite search engine and proved out to scale well. I also love the vivid open communities behind Kubernetes. Having the native Kubernetes experience is huge as it allows users to seamlessly move their workload from/to any cloud provider that supports native Kubernetes APIs.</p><blockquote>Really simple to get started with a free Kubernetes cluster</blockquote><p>You can use either the UI or CLI to deploy a free Kubernetes cluster easily. If you are not a CLI fan, I would recommend you go to <a href="http://bluemix.net/">bluemix.net</a>, login, find Containers in Bluemix Catalog, and follow the flow to deploy your free cluster.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FGBvpNEwXb4XVm%2Ftwitter%2Fiframe&amp;src_secure=1&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FGBvpNEwXb4XVm%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FGBvpNEwXb4XVm%2Fgiphy.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="480" height="300" frameborder="0" scrolling="no"><a href="https://medium.com/media/f563268e55a9c82a9ba3292820aa1dc7/href">https://medium.com/media/f563268e55a9c82a9ba3292820aa1dc7/href</a></iframe><blockquote>Bluemix Service Integration, let’s add cognitive to your application!</blockquote><p>One of the biggest advantages today’s developers have is the variety of Cloud services that they can leverage at their fingertips. For example, Bluemix offers more than 100 services, including many cognitive services, like Watson. The Bluemix service integration provided by IBM Bluemix Container Service allows users to leverage Watson and many other services to build highly available, cognitive, and innovative solutions in the Cloud!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FQVUlP9fWiNZ1S%2Ftwitter%2Fiframe&amp;src_secure=1&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FQVUlP9fWiNZ1S%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FQVUlP9fWiNZ1S%2Fgiphy.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="480" height="300" frameborder="0" scrolling="no"><a href="https://medium.com/media/9338594380a72ef3259e4d49b4ada3a1/href">https://medium.com/media/9338594380a72ef3259e4d49b4ada3a1/href</a></iframe><blockquote>The architecture of the Bluemix Container Service</blockquote><p>The master components of your deployed Kubernetes cluster are highly available and fully managed by IBM. It is fascinating that the master components for every cluster are deployed as Kubernetes deployments in the IBM Bluemix Container Service Kubernetes infrastructure. This approach intelligently leverages the Kubernetes’ known rich operation capabilities to monitor, recover, and roll out a newer version of the master components for all Kubernetes clusters.</p><p>In closing, I hope these four highlights get you excited about the IBM Bluemix Container Service! Visit <a href="http://bluemix.net/">bluemix.net</a> and give it a try! If you liked this post, please consider clicking that green heart on the left or sharing it on Twitter, Facebook, or LinkedIn.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f5c6971aaf9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>