June 2025 Summaries

The acquisition of Codefresh provided an opportunity to explore new technology, particularly Argo Workflows, which are crucial to Codefresh's Promotion Flows feature. Argo, comprising four distinct projects, was initially unfamiliar, prompting a project to understand Promotion Flows by integrating HashiCorp Vault for secure secret management. The project involved configuring a Kubernetes Service Account and creating a Slack notification system that retrieves secrets from Vault in a just-in-time manner, demonstrating the process through PowerShell scripts for automation. The experience revealed insights into constructing Promotion Workflows and the underlying mechanics of Argo Workflows, offering a hands-on understanding of their integration and functionality.

Kubernetes clusters with default configurations offer limited deployment strategies, but more advanced options like blue/green and canary deployments can be accessed using a Progressive Delivery controller such as Argo Rollouts. This guide explores how to select specific user groups for canary deployments rather than randomly distributing network requests, a common limitation in default configurations. Two approaches are discussed: static URL routing, which involves creating different URLs for different user groups to control exposure during deployments, and dynamic URL routing using HTTP headers, which allows more flexible and user-specific routing by detecting optional headers to direct specific users to the canary version. While static routing is straightforward and requires no source code changes, it is limited by its rigidity and inability to adjust group assignments mid-deployment. Dynamic routing, on the other hand, offers greater flexibility by enabling on-the-fly changes to user group assignments through headers, making it suitable even for applications with graphical interfaces. Both methods aim to improve the targeting of canary deployments and minimize the impact of potential failures on undesired user groups, though they may necessitate modifications to the application code or network configurations.

The article explores efficient methods for managing multiple Kubernetes clusters using Argo CD Application Sets and emphasizes the use of cluster labels over ad-hoc configurations. It details how Application Sets automate application deployments across various clusters by using cluster and Git generators, allowing for streamlined management without the need for individual YAML configurations. The article critiques the complexity of snowflake server setups, where specific applications are manually enabled or disabled for each cluster, advocating instead for a scalable approach using cluster labels that model cluster groups, thereby reducing maintenance efforts and facilitating easier communication between developers and operators. Through practical scenarios, it illustrates how cluster labels can simplify tasks like deploying applications to clusters based on environment or region, managing configurations with Kustomize overlays or Helm values, and adding or removing clusters without altering application sets, ultimately demonstrating a more automated, efficient process that minimizes manual intervention and supports organizational agility.

The text discusses the evolving needs of application developers in the cloud ecosystem, particularly regarding Kubernetes. While tools for managing Kubernetes clusters have matured, the focus has shifted towards addressing developers' requirements, which are often misunderstood by companies. Developers care more about environment settings and promotions rather than individual clusters or Git hashes, which are often emphasized in existing tools. They prefer systems that allow easy promotion of configurations and container tags simultaneously, reducing deployment failures caused by environmental discrepancies. Continuous Delivery (CD) pipelines are also highlighted as areas needing improvement, as they often lack real-time deployment visibility. The text introduces Codefresh GitOps Cloud as a solution designed with developers in mind, emphasizing application promotions and offering a more developer-friendly approach compared to traditional tools like Argo CD, which do not fully address developers' needs.