<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>bwarminski</author><text>We&amp;#x27;re using Argo as a replacement for our GoCD based continuous delivery system and it&amp;#x27;s been fantastic. We were about to move onto Concourse and realized we would need to set up the and manage the equivalent of a Kubernetes cluster just to support it. We took a few extra weeks to prototype Argo first and were glad we did.&lt;p&gt;In our use case, the primary deployment model is blue&amp;#x2F;green deploys of VM based microservices on AWS with a bunch of Terraform managed infrastructure gluing them together. The newer class of service we&amp;#x27;re developing right now is container based and has even more infrastructure complexity. Teams manage their own service releases and each group has slight variations in their deploy steps. We need a deploy system that can support the old and new style and remain flexible while providing a migration path.&lt;p&gt;Teams love the flexibility and expressiveness of the workflow definitions. They&amp;#x27;ve begun to move cron jobs onto it as well. Argo is much more lightweight and easy to operate than any other system we had worked with because it leans so heavily on Kubernetes primitives that we already needed to understand. The codebase is also relatively easy to understand, so we&amp;#x27;ve been able to contribute things back to the project while working through the migration.&lt;p&gt;We&amp;#x27;ve taken a cue from the project and begun to consolidate our control plane on CRDs so they can seamlessly integrate with Argo. CRD Operators + Argo are allowing us to consolidate all of the custom deploy&amp;#x2F;config tooling we built over the years onto a common system that is testable and well integrated.&lt;p&gt;It&amp;#x27;s a little early in the project to measure the full effect, but the internal project has a lot of momentum.</text><parent_chain></parent_chain></comment><story><title>Argo: Open source Kubernetes native workflows, events, CI and CD</title><url>https://argoproj.github.io/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>mattashii</author><text>The idea is nice, but if security is one of your concerns, you&amp;#x27;ll probably not want to run this if the docs are even close to representative of the actual application:&lt;p&gt;&amp;gt; 3. Configure the service account to run workflows&lt;p&gt;&amp;gt; For clusters with RBAC enabled, the &amp;#x27;default&amp;#x27; service account is too limited to support features like artifacts, outputs, access to secrets, etc... Run the following command to grant admin privileges to the &amp;#x27;default&amp;#x27; service account in the namespace &amp;#x27;default&amp;#x27;&lt;p&gt;This raises so many red flags. Never give admin rights &amp;#x27;as a default&amp;#x27;.</text><parent_chain></parent_chain></comment><story><title>Argo: Open source Kubernetes native workflows, events, CI and CD</title><url>https://argoproj.github.io/</url></story>