<?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 Vini Vasundharan on Medium]]></title>
        <description><![CDATA[Stories by Vini Vasundharan on Medium]]></description>
        <link>https://medium.com/@vinivasundharan2011?source=rss-5b49be0b266e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*f--kj8ZOZN9B4xrm.</url>
            <title>Stories by Vini Vasundharan on Medium</title>
            <link>https://medium.com/@vinivasundharan2011?source=rss-5b49be0b266e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:31:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vinivasundharan2011/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[Knowing Armory CDaaS]]></title>
            <link>https://medium.com/@vinivasundharan2011/knowing-armory-cdaas-f2f74363fa22?source=rss-5b49be0b266e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2f74363fa22</guid>
            <category><![CDATA[spinnaker]]></category>
            <category><![CDATA[gitops]]></category>
            <category><![CDATA[continuous-deployment]]></category>
            <category><![CDATA[armory]]></category>
            <dc:creator><![CDATA[Vini Vasundharan]]></dc:creator>
            <pubDate>Mon, 10 Jul 2023 15:46:04 GMT</pubDate>
            <atom:updated>2023-07-11T14:06:36.429Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.armory.io/">Armory</a> is a name I came across when I started working with <a href="https://spinnaker.io/">Spinnaker</a>. Anyone who has worked with this open source giant would know that it is not an easy solution to be tamed (I bow to all people out there who got its grip). Armory offers support in dealing with this tool, big KUDOS to the support engineers, you guys are really awesome ❤️❤️</p><p>As we could imagine, Armory needs other ways of making money, which brings us to their <a href="https://docs.armory.io/cd-as-a-service/">Armory CDaaS</a> solution.</p><p>Last week I (also my team) had an opportunity to see a demo from their CDaaS. I am a big time fan of ArgoCD and the features offered, and not to forget that it is <strong>FREE</strong>. Now probably, my mindset for the demo is kind of understandable.</p><figure><img alt="https://docs.armory.io/cd-as-a-service/" src="https://cdn-images-1.medium.com/max/1024/0*qAgUehXT5SVnX3lf.png" /><figcaption>(Taken from documentation)</figcaption></figure><p><a href="https://www.linkedin.com/in/bmappen/">Ben Mappen</a>, the co-founder of Armory, kicks off the meeting with a very interesting comparison of different CD solutions. Ben knew that we were looking at ArgoCD as our preferred solution, so the comparison also focused on that part quite well. (As I remember, he actually started off with a series of questions with regards to ArgoCD, and then the introduction 😂)</p><p>Now comes the show stopper of the meeting, the <strong>TECH DEMO, </strong>a well-prepared, to-the-point, non-boring demo. Cheers to Stephen. (Me and my team all agreed on this about the demo)</p><p><strong>What I learned during the demo?</strong></p><ol><li>Initial setup<br>It is an undemanding installation of the agent on the clusters using kubectl or helm (I m not going to explain the complete technical details, as they have it documented pretty well)</li><li>On-boarding applications<br>We all love YAML; they did not want to disappoint us either; the application/deployment configuration is on a single yaml file, which can be called using the Armory cli or from any CI tool. We define the stages, the clusters that it has to be deployed on etc in this one file, our single source of truth for a deployment/application on Armory.</li></ol><p>Does this make Armory stand out? Not really; but with the features that you can configure on the said YAML.</p><ol><li>Deployment strategy: An OOTB <strong>blue-green</strong> and <strong>canary</strong> deployment. The strategy is configurable(many parameters that can be configured) within the application/deployment file.</li><li>Environment propogation: This is one of the most sought out features when thinking about a CD solution. They have a well designed solution on how the <strong>stage propogation</strong> can work. Be it adding dependencies among stages, or webhooks back to your pipeline to trigger an integration test, or a manual approval for a stage, they got it all covered.</li><li>Rollbacks: Here we have the possibility to group services together as a single unit, and can undergo a rollback in one step. This is also taken into consideration when doing canary deployments for instance, to distribute load.</li></ol><p>There were absolutely more features and technical details that were presented, these were some of them that really caught my attention.</p><p><em>I can not always talk about the happy part</em> 😔😔</p><p>Something that I would have wished to see is the Infrastructure drift detection which I always liked when using ArgoCD; however given Armory’s ability to orchestrate the deployment end-to-end from every commit we can rest assured we’ll maintain the latest changes. Also, given that Armory can deploy as-is, you could always complement Argo with Armory as the cross-environment orchestration to get the best of both worlds. Besides that, the tool currently doesnt support native helm unless the manifests are rendered(Its easy to render the manifest outside of the tool, so not really a disadvantage). If you are up for a demo in a few months, I m sure they would have this tackled as well.</p><p>The best part above all is their willingness to take suggestions from the crowd to make a better product.</p><p>I would highly recommend <a href="https://go.armory.io/signup/">trying</a> out their solution (I was able to make a sample deploy with help of the documentation), or asking for a demo if you are looking for a SaaS CD solution with GitOps in mind.</p><p><em>(And I do not work for Armory 😛😛)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2f74363fa22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A day at IBM that I would never forget]]></title>
            <link>https://medium.com/@vinivasundharan2011/a-day-at-ibm-that-i-would-never-forget-4b547e3d6dcc?source=rss-5b49be0b266e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b547e3d6dcc</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[working-culture]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Vini Vasundharan]]></dc:creator>
            <pubDate>Wed, 05 Jul 2023 08:12:17 GMT</pubDate>
            <atom:updated>2023-07-05T08:12:17.881Z</atom:updated>
            <content:encoded><![CDATA[<p>Story writing, let alone writing has never been my forte, has anything been my forte until now is a good question for sometime later.</p><p>Recently I was chatting with a fairly new colleague in my team, it reminded me of my Cloud journey with IBM. I remember my first project at IBM being a DevOps Engineer, little did I know what I was supposed to do. Cloud. Terraform. Helm. Kubernetes. Service. Deployment. Jenkins. Ingress. I had really no clue what I was dealing with. (I do not blame the IBM interview process here, but this is a story I might have told many people on how I made this career choice)</p><p>Getting back, I get my first task in the project, as you can already imagine, I f**k it up big time, the task was fairly simple (to avoid a lot of embarassment, I m saving the task to myself). I get a call from my team lead/Architect, and he tells in the best possible way that I m stupid and he is very disappointed in me. Obviously I feel very bad and I run out of words.</p><p>What did I do wrong? I was afraid to ask for help, I was afraid to say that I did not understand what was expected of me, I was afraid of looking dumb, I was waiting to frame the “right question”, <strong><em>I just got exhausted in the process</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*EBCRO-GtFZkObXB-yRXvmA.jpeg" /></figure><p>I learned the hard way, that I can ask <strong><em>any¹ </em></strong>question, I don’t have to be the “<strong><em>know it all</em></strong>” before asking. This opened up a whole new level of learning for me. I m <em>very grateful </em>to all the people I have worked with and many other peers outside of work, who never turned their back to my questions, and helped me being a DevOps.. Platform.. Cloud.. Site Reliability.. Infrastructure.. <strong><em>ENGINEER</em>.</strong></p><blockquote>We always say there are no stupid questions, but do we encourage to ask that trivial question?</blockquote><p>[1] “any” doesnt define to anything and everything, the frame is of course professional, if someone would take the face value :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b547e3d6dcc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>