<?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 Mike Treadway on Medium]]></title>
        <description><![CDATA[Stories by Mike Treadway on Medium]]></description>
        <link>https://medium.com/@mike.treadway?source=rss-4b702e69ded1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wiO96FNnh8c063SIWXNz0g.jpeg</url>
            <title>Stories by Mike Treadway on Medium</title>
            <link>https://medium.com/@mike.treadway?source=rss-4b702e69ded1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:24:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mike.treadway/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[Why is my Node.js app performing slowly and why am I waiting on my beer?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://faun.pub/why-is-my-node-js-app-performing-slowly-and-why-am-i-waiting-on-my-beer-724c8fc38089?source=rss-4b702e69ded1------2"><img src="https://cdn-images-1.medium.com/max/984/1*mg5JfzZSqWq956JlhWcOqw.jpeg" width="984"></a></p><p class="medium-feed-snippet">Down-to-earth explanation on why one frequently overlooked area of a Node.js application can cause performance problems in production.</p><p class="medium-feed-link"><a href="https://faun.pub/why-is-my-node-js-app-performing-slowly-and-why-am-i-waiting-on-my-beer-724c8fc38089?source=rss-4b702e69ded1------2">Continue reading on FAUN.dev()  »</a></p></div>]]></description>
            <link>https://faun.pub/why-is-my-node-js-app-performing-slowly-and-why-am-i-waiting-on-my-beer-724c8fc38089?source=rss-4b702e69ded1------2</link>
            <guid isPermaLink="false">https://medium.com/p/724c8fc38089</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Mike Treadway]]></dc:creator>
            <pubDate>Mon, 19 Jul 2021 14:28:12 GMT</pubDate>
            <atom:updated>2021-07-20T18:48:08.698Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Simple Things to Make Your Kubernetes Cluster More Secure]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://faun.pub/simple-things-to-make-your-kubernetes-cluster-more-secure-d1ad1f14db87?source=rss-4b702e69ded1------2"><img src="https://cdn-images-1.medium.com/max/800/0*dwdZBXYCIUXDZ8eM.jpg" width="800"></a></p><p class="medium-feed-snippet">Let&#x2019;s face it. You&#x2019;re not 100% comfortable with Kubernetes yet. Have you thought about security? Here are a few simple things you can&#x2026;</p><p class="medium-feed-link"><a href="https://faun.pub/simple-things-to-make-your-kubernetes-cluster-more-secure-d1ad1f14db87?source=rss-4b702e69ded1------2">Continue reading on FAUN.dev()  »</a></p></div>]]></description>
            <link>https://faun.pub/simple-things-to-make-your-kubernetes-cluster-more-secure-d1ad1f14db87?source=rss-4b702e69ded1------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1ad1f14db87</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Mike Treadway]]></dc:creator>
            <pubDate>Sun, 22 Sep 2019 16:25:26 GMT</pubDate>
            <atom:updated>2019-09-23T14:49:51.450Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[5 Tips for Building Container Friendly Applications]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://faun.pub/5-tips-for-building-container-friendly-applications-9920db4f3dc9?source=rss-4b702e69ded1------2"><img src="https://cdn-images-1.medium.com/max/640/0*W8Jpl1dFsAd08Pak.jpg" width="640"></a></p><p class="medium-feed-snippet">When building new applications, follow these tips to make your application more cloud native and container friendly.</p><p class="medium-feed-link"><a href="https://faun.pub/5-tips-for-building-container-friendly-applications-9920db4f3dc9?source=rss-4b702e69ded1------2">Continue reading on FAUN.dev()  »</a></p></div>]]></description>
            <link>https://faun.pub/5-tips-for-building-container-friendly-applications-9920db4f3dc9?source=rss-4b702e69ded1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9920db4f3dc9</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[containers]]></category>
            <dc:creator><![CDATA[Mike Treadway]]></dc:creator>
            <pubDate>Fri, 05 Jul 2019 18:34:28 GMT</pubDate>
            <atom:updated>2019-07-08T10:04:26.298Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Making Apache Cassandra on IBM Cloud Kubernetes Production Ready — Part II]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://faun.pub/making-apache-cassandra-on-ibm-cloud-kubernetes-production-ready-part-ii-e8d954d04f65?source=rss-4b702e69ded1------2"><img src="https://cdn-images-1.medium.com/max/600/1*aTRx9kmPiL11PjfG7XHmwA.jpeg" width="600"></a></p><p class="medium-feed-snippet">The following is final part in a series on advanced issues when taking Cassandra to Production on Kubernetes.</p><p class="medium-feed-link"><a href="https://faun.pub/making-apache-cassandra-on-ibm-cloud-kubernetes-production-ready-part-ii-e8d954d04f65?source=rss-4b702e69ded1------2">Continue reading on FAUN.dev()  »</a></p></div>]]></description>
            <link>https://faun.pub/making-apache-cassandra-on-ibm-cloud-kubernetes-production-ready-part-ii-e8d954d04f65?source=rss-4b702e69ded1------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8d954d04f65</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[cassandra]]></category>
            <dc:creator><![CDATA[Mike Treadway]]></dc:creator>
            <pubDate>Sun, 19 May 2019 20:41:07 GMT</pubDate>
            <atom:updated>2019-07-21T11:03:09.465Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Making Apache Cassandra on IBM Cloud Kubernetes Production Ready— Part I]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://faun.pub/making-apache-cassandra-on-ibm-cloud-kubernetes-production-ready-part-i-f8a775b43672?source=rss-4b702e69ded1------2"><img src="https://cdn-images-1.medium.com/max/1276/1*8GF0-lvY-nj0mvOjYmj2qw.png" width="1276"></a></p><p class="medium-feed-snippet">The following is a continuation of a previous article and addresses more advanced issues when taking Cassandra to Production on Kubernetes.</p><p class="medium-feed-link"><a href="https://faun.pub/making-apache-cassandra-on-ibm-cloud-kubernetes-production-ready-part-i-f8a775b43672?source=rss-4b702e69ded1------2">Continue reading on FAUN.dev()  »</a></p></div>]]></description>
            <link>https://faun.pub/making-apache-cassandra-on-ibm-cloud-kubernetes-production-ready-part-i-f8a775b43672?source=rss-4b702e69ded1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8a775b43672</guid>
            <category><![CDATA[cassandra]]></category>
            <category><![CDATA[ibm-cloud]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Mike Treadway]]></dc:creator>
            <pubDate>Sun, 10 Mar 2019 19:12:30 GMT</pubDate>
            <atom:updated>2019-07-19T16:56:14.384Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Deploying a Cassandra Cluster in Kubernetes on IBM Cloud]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://faun.pub/deploying-a-cassandra-cluster-in-kubernetes-on-ibm-cloud-59e840c1a9b7?source=rss-4b702e69ded1------2"><img src="https://cdn-images-1.medium.com/max/748/1*ndnj_Zi1y1SwxoYPolkL0Q.jpeg" width="748"></a></p><p class="medium-feed-snippet">Kubernetes is great for stateless applications, but what about running databases such as Cassandra? Come learn how easy it is in IBM Cloud.</p><p class="medium-feed-link"><a href="https://faun.pub/deploying-a-cassandra-cluster-in-kubernetes-on-ibm-cloud-59e840c1a9b7?source=rss-4b702e69ded1------2">Continue reading on FAUN.dev()  »</a></p></div>]]></description>
            <link>https://faun.pub/deploying-a-cassandra-cluster-in-kubernetes-on-ibm-cloud-59e840c1a9b7?source=rss-4b702e69ded1------2</link>
            <guid isPermaLink="false">https://medium.com/p/59e840c1a9b7</guid>
            <category><![CDATA[apache-cassandra]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[ibm-cloud]]></category>
            <dc:creator><![CDATA[Mike Treadway]]></dc:creator>
            <pubDate>Sun, 17 Feb 2019 16:58:50 GMT</pubDate>
            <atom:updated>2019-07-19T16:18:14.155Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Helm Charts for More Complex Projects and How to Secure Them]]></title>
            <link>https://faun.pub/helm-charts-for-more-complex-projects-and-how-to-secure-them-a1dfde804226?source=rss-4b702e69ded1------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1dfde804226</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[helm-chart]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Mike Treadway]]></dc:creator>
            <pubDate>Sun, 03 Feb 2019 17:02:17 GMT</pubDate>
            <atom:updated>2020-02-10T16:59:11.430Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gOVMMUG43gpXisFht_xjJg.jpeg" /></figure><p>Helm is a great tool for automating deployments on Kubernetes because it allows you to describe the state of your deployment in a parameterized way, and takes care of applying those changes in an <a href="https://en.wikipedia.org/wiki/Idempotence">idempotent</a> way. I also love how you ran rollback those changes if needed because it tracks the differences in each deployment and stores that information in Kubernetes. Helm charts exist for many applications and can really improve your productivity when needing to deploy them in Kubernetes. But what about those of us that are authoring and deploying more complex applications or components across multiple environments and clusters? How you organize and structure your charts can make a world of difference in how easy it is to run and maintain them. The recipe I’m outlining in this post is how we’re currently using Helm in the portal and micro-services platform in IBM Services for Managed Applications.</p><h4>Background</h4><p>At IBM Services for Managed Applications, we run a portal platform and microservices framework that gives customers the ability to interact with their managed services via a browser or via API. This platform allows teams to independently develop, deploy, and maintain their application and/or service independently of the others, so a consistent ecosystem for these components to run in is extremely important. While these applications and services are independently deployed and maintained, they do have dependencies on things like monitoring, databases, configuration, secrets, etc. We’ve created a Helm chart that builds out all of these dependencies so that once deployed in a new cluster or environment, teams have that needed ecosystem to deploy their applications and services into.</p><h4>Challenges</h4><p>Using IBM Cloud Kubernetes allows us to quickly create and scale Kubernetes clusters as needed as we expand our global footprint. Unfortunately, each cluster is confined to the region it was deployed in. This means that in order to have a presence in US-South and US-East, we need have completely separate clusters that have no knowledge of each other. It follows that we need to deploy our platform chart twice; once in each region, each with their own set of configurations.</p><p>We also have multiple environments. Not only do we have a Production environment, but we also have On-Deck, Staging, and Development environments. We probably could have found a way to have a single cluster for all environments, but each environment had its own requirements in terms of access policy, availability, network configuration, etc. It was just easier to isolate the clusters than increase complexity with segmentation within a single cluster.</p><p>There are some configuration values that are not sensitive and can be checked into source control. However, there are several things in our platform that are sensitive and cannot be checked into source control. Things like OAuth secrets, database credentials, API keys, etc. What we needed was a way to persist this information in source control, but in such a way that it didn’t expose this items and only a select few could access them.</p><p>To summarize, the top issues we were facing:</p><ul><li>Multiple Kubernetes clusters, in various regions globally.</li><li>Multiple environments (Production, Staging, etc.)</li><li>Securely storing our configuration in source control.</li></ul><h4>Helm Chart Structure</h4><p>Defining a solid structure for the Helm chart can make a world of difference in how you deploy them in the various environments. For us, we created a hierarchical structure to store the configuration values in, with the Environment at the top, followed up the region/location.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/418/1*xTIrJo8Mpb0jjT5c5VStRg.png" /></figure><p>With this structure, we put common configuration for the environment, directly in the ./env/{environment} directory, and region specific configuration in the ./env/{environment}/{region} directory. When we run Helm, we just specify the appropriate <em>values.yaml</em> files for the region and environment we’re deploying to. We realized at the beginning that manually passing this information in via command line was error prone, so we wrote an automation script to do that for us (more on that later). In our situation, it just so happen the sensitive information was common across the environment, and did not differ between regions. This is why you see a <em>secrets.yaml</em> file for the environment, and a <em>values.yaml</em> file for the region.</p><p>The services-platform directory is the actual Helm chart, and the setup and util directories contain helper scripts to install Helm, configure Kubernetes networking, etc.</p><p>To deploy or upgrade a chart with this structure, it would like this:</p><pre>$ helm upgrade -i platform ./services-platform --install -f ./env/staging/us-south/values.yaml -f ./env/staging/secrets.yaml</pre><p>As you can see, it allows flexibility but it’s not something you’d want to hand type every time.</p><h4>Securing the Configuration</h4><p>For sensitive information, we’re using the <a href="https://github.com/futuresimple/helm-secrets">helm-secrets</a> plugin. This plugin provides arguments that will encrypt/decrypt a secrets file, and provides a wrapper command that will decrypt the secrets file, pass the commands on to Helm, and delete the decrypted file. The encryption and decryption are handled with <a href="https://github.com/mozilla/sops/blob/master/README.rst">SOPS</a> and a number of supported encryption algorithms. In our case, we use PGP. Each environment has it’s own key pair, and a select few have the private key installed on their local machine. When helm-secrets see’s a <em>secrets.yaml</em> file, it looks for a corresponding <em>.sops.yaml</em> file that tells helm-secrets what the encryption algorithm and public key is. Here’s an example of what it looks like in it’s encrypted state:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2da5a8a591381a88eb60568b286857e8/href">https://medium.com/media/2da5a8a591381a88eb60568b286857e8/href</a></iframe><p>What’s nice about this is you can see the yaml structure within the file, which makes it really easy to reference when building your chart. To edit the file, you run a helm-secrets command that will decrypt the file and open it up in your default text editor, and re-encrypt it when the editor saves the file and exits. For example, to edit the secrets file I run $ helm secrets edit ./env/staging/secrets.yaml. This decrypt the file and opens the decrypted file in my default editor. After saving the file and closing, helm-secrets will re-encrypt it the new file. Another thing to note, is that when if the private key is password protected, helm-secrets will prompt you for the password when decrypting the file, whether that be for editing, or actually applying the chart to a Kubernetes cluster.</p><p>Instead of using the normal helm command, we now use helm-wrapper. The update deployment command now looks like this:</p><pre>$ helm-wrapper upgrade -i platform ./services-platform --install -f ./env/staging/us-south/values.yaml -f ./env/staging/secrets.yaml</pre><h4>Automation</h4><p>Referencing in the various configuration files depending on your environment and region is definitely error prone. Not to mention, in order to apply the Helm chart, there are a series of steps you have to perform to be logged in and authenticated with IBM Cloud. I simplified this process by writing a deployment bash script. When given the environment and region, the script performs the following actions:</p><ul><li>Targets the appropriate IBM Cloud Resource Group</li><li>Sets the appropriate IBM Cloud Region.</li><li>Obtains the kubectl configuration and applies it.</li><li>Validates that the current kubectl settings are applied by comparing the output of a kubectl command to some settings obtained from the IBM Cloud CLI.</li><li>Runs helm-secrets passing in the appropriate environment and region configuration values.</li></ul><p>The usage of the script is very straightforward.</p><pre>foo@bar:~$ ./deploy.sh -h<br>Usage:<br>        deploy.sh {ENVIRONMENT} {REGION}<br><br>Example:<br>        deploy.sh production us-south<br><br>foo@bar:~$</pre><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5abed466f824af96e6ed4aa1fa857c1d/href">https://medium.com/media/5abed466f824af96e6ed4aa1fa857c1d/href</a></iframe><p>The setup.sh script is run once for a new cluster to add the tiller account for Helm, install Helm on the cluster, and add the helm-secrets plugin.</p><p>There are a few assumptions here with the script. It currently assumes that there’s a one-to-one relationship between your Kubernetes cluster and your environment. This works for us for now, but there may need to be more intelligence in the script if you plan on hosting multiple environments within the same Kubernetes cluster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/727/0*Piks8Tu6xUYpF4DU" /></figure><p><strong>Join our community Slack and read our weekly Faun topics ⬇</strong></p><figure><a href="https://www.faun.dev/join/?utm_source=medium.com%2Ffaun&amp;utm_medium=medium&amp;utm_campaign=faunmediumbanner"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oSdFkACJxs5iy1oR" /></a></figure><h4>If this post was helpful, please click the clap 👏 button below a few times to show your support for the author! ⬇</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1dfde804226" width="1" height="1" alt=""><hr><p><a href="https://faun.pub/helm-charts-for-more-complex-projects-and-how-to-secure-them-a1dfde804226">Helm Charts for More Complex Projects and How to Secure Them</a> was originally published in <a href="https://faun.pub/">FAUN.dev() 🐾</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Simple Caching in Microservices is Not Enough]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@mike.treadway/when-simple-caching-in-microservices-is-not-enough-fd2aea9e951f?source=rss-4b702e69ded1------2"><img src="https://cdn-images-1.medium.com/max/1200/1*W0JWckNTlJkC0XwAgRROnQ.jpeg" width="1200"></a></p><p class="medium-feed-snippet">In memory caching for your microservices is a great way to improve your services&#x2019;s performance. Come explore life beyond simple caching&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@mike.treadway/when-simple-caching-in-microservices-is-not-enough-fd2aea9e951f?source=rss-4b702e69ded1------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@mike.treadway/when-simple-caching-in-microservices-is-not-enough-fd2aea9e951f?source=rss-4b702e69ded1------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd2aea9e951f</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Mike Treadway]]></dc:creator>
            <pubDate>Sun, 23 Dec 2018 15:57:12 GMT</pubDate>
            <atom:updated>2018-12-23T15:57:12.874Z</atom:updated>
        </item>
    </channel>
</rss>