February 2024 Summaries

Codefresh has announced its merger with Octopus Deploy, a leader in the Continuous Delivery industry, marking a significant milestone in Codefresh's journey since its founding in 2014. This strategic alliance aims to combine the strengths of both companies—Octopus Deploy's expertise in virtual machines, Windows, and Kubernetes, and Codefresh's focus on cloud-native and GitOps tooling—to standardize and automate deployments across various application types. The merger is driven by a shared vision of simplifying and scaling software delivery, supported by similar company cultures and values. This collaboration promises enhanced continuous delivery automation for diverse applications, from traditional data center setups to modern cloud-native environments, benefiting customers and communities like open-source and Argo through expanded contributions and resources. As Codefresh co-founder reflects on the journey, he emphasizes the importance of people in building successful ventures and expresses enthusiasm for the future, inviting stakeholders to engage with the detailed announcement and Q&A provided.

Octopus Deploy has acquired Codefresh in a strategic move to create an enhanced continuous delivery (CD) and continuous integration (CI) platform that caters to a wide range of applications, including VMs, Windows, and cloud-native applications. Codefresh will continue to operate independently, maintaining its existing platform and adding new features, particularly in CI, GitOps, and app promotions, with no immediate changes to contracts or pricing structures. Customers can expect continued support and improvements, and there will be no disruptions or significant migration tasks as the platforms integrate. The acquisition aims to develop a comprehensive CI/CD and GitOps platform that supports users throughout their software delivery processes, with assurances that data management practices will remain unchanged.

A leading telecommunications provider successfully transitioned from a traditional Continuous Integration (CI) system, Bamboo, to a modern Internal Developer Portal using Codefresh and Port, aiming to enhance the developer experience by creating a seamless, cloud-native environment for software delivery. The migration involved establishing a single interface for managing deployments and artifacts, allowing developers to focus on essential tasks without unnecessary operational complexities. The solution leveraged Port as the interface and catalog provider, and Codefresh as the automation engine, ensuring a smooth transition with minimal disruption to existing workflows. The new setup not only standardized Codefresh as the CI/CD platform across the sub-organization but also provided a customizable dashboard that catered to the specific needs of developers, paving the way for future innovations like GitOps. This case highlights the potential for combining multiple tools to achieve a successful migration, demonstrating Codefresh's capability to integrate with Internal Developer Portals for customized and efficient workflow solutions.

The article details the process of deploying the open-source password manager Padloc to Kubernetes using a suite of tools including GitHub, Docker, Codefresh, and Argo CD. It outlines the creation of an integrated deployment workflow that separates application code from Kubernetes manifests in different repositories, allowing for controlled access and changes. The process involves setting up a Continuous Integration (CI) pipeline to test and build Docker images, which are then deployed to development and production environments. The pipeline includes a manual approval step before production deployment to ensure application stability. The article emphasizes the advantages of using Codefresh for enhanced visibility and management of deployments across environments, highlighting features like easy promotion of releases and detailed deployment timelines.

The article from the "Codefresh in the Wild" series outlines a hands-on journey of deploying the Kubernetes application "starbase-80" using a variety of tools including GitHub, Docker, AWS, Codefresh, Argo CD, and Terraform. It offers a detailed account of integrating these tools to establish an efficient end-to-end deployment workflow, emphasizing the use of Infrastructure as Code (IaC) via Terraform for setting up the infrastructure and employing Helm for deploying the application. The process involves setting up a pipeline with Codefresh to build and test the application, and utilizing Argo CD for GitOps-based deployments, allowing for customization across different environments. The article reflects on the learning experiences encountered during the setup, highlighting the importance of IaC for efficient management, the ease and complexity of using Helm charts, and the benefits of maintaining everything in Git for traceability and version control. It concludes with a note on continuous learning and improvement through practical experience and troubleshooting.

The article describes the process of deploying the open-source diagramming application draw.io to Kubernetes using a comprehensive CI/CD workflow involving tools such as GitHub, Docker, Helm, Codefresh, Argo Rollouts, and Argo CD. The team begins by forking the draw.io repository and creating a Helm chart to enhance interaction with Argo CD. A Codefresh CI pipeline is set up to build and test the application, employing Cypress for testing and integrating Slack for approval processes. The pipeline includes updating the Argo CD manifest with a new image version, followed by deploying it using Argo CD and Argo Rollouts, implementing a canary deployment strategy for progressive delivery. The article highlights the use of Codefresh's UI for managing deployments and emphasizes the integration of GitOps principles, resulting in a streamlined and effective deployment process.

The article details the process of deploying "Pastr," a simple URL shortener, to Kubernetes using a variety of tools including GitHub, Docker, AWS, Codefresh, Argo CD, and Kustomize, as part of the "Codefresh in the Wild" series. The authors aim to explore CI/CD and GitOps methodologies by integrating these tools to build an end-to-end deployment workflow. The project begins with forking "Pastr" into a public GitHub repository and setting up a Codefresh CI pipeline that triggers builds on code changes and schedules nightly builds for security updates using Cron triggers. Notifications for build errors are configured to ensure immediate feedback, and unit tests are run to prevent faulty code from progressing. The process involves building Docker images, updating Kubernetes manifests, and using Codefresh GitOps for seamless application deployment. The article highlights the GitOps Environment Dashboard for managing environments and deployments, offering a live overview of application statuses and deployment details. The documentation of this process serves as a guide and inspiration for others in the tech community, providing a robust deployment pipeline for "Pastr" and a template for adopting best practices in CI/CD and GitOps.

GitOps is a set of best practices that extend Infrastructure As Code (IAC) by using Git as the source of truth for Kubernetes configuration, driving tools like Argo CD, Flux, and the Codefresh deployment platform. A key challenge in adopting GitOps in Kubernetes environments is secret management, as traditional practices keep secrets in external systems such as Hashicorp Vault, conflicting with GitOps' principle of storing everything in Git. This article explores how to inject secrets from AWS Secrets Manager into Codefresh/Argo CD applications using the Argo CD Vault Plugin, which allows fetching secrets from various backends including AWS Secrets Manager. The process involves installing the Vault plugin in a Codefresh runtime, modifying configuration files, and linking Kubernetes secrets with AWS secrets, ensuring they are dynamically updated without being hardcoded in Git. While Argo CD doesn’t automatically update secrets from AWS, solutions like cron jobs can refresh them regularly. The article emphasizes that the described setup is durable through Codefresh runtime updates and highlights alternative methods for secret management, such as the External Secret Operator, which can autonomously refresh secrets.

Since the launch of Codefresh's GitOps platform and the Enterprise version of Argo CD and Argo Rollouts, the company has significantly enhanced its offerings, including the addition of Argo Workflows, to improve software delivery across various environments. These enhancements have enabled users to deploy more frequently, recover from failures more quickly, and reduce deployment time. Recently, Codefresh introduced environment management, allowing teams to model and manage applications across multiple environments with ease, offering customizable promotions and simplified comparisons. The company also provides popular GitOps training and certification programs, fostering a growing community. As maintainers of the Argo Project, Codefresh remains deeply invested in advancing GitOps practices. The upcoming ArgoCon and KubeCon events will showcase the latest advancements, highlighting the potential for 2024 to be a pivotal year for GitOps environments, emphasizing streamlined, visible, and verifiable software delivery processes.

Progressive delivery is a deployment strategy that involves gradually shifting production traffic to new application versions without downtime, with Argo Rollouts serving as a Kubernetes controller to facilitate such deployments through methods like blue/green and canary releases. While straightforward for stateless applications, using Argo Rollouts with stateful services like databases or queues requires additional configuration to prevent preview versions from inadvertently accessing production resources. A solution involves leveraging the Kubernetes Downward API to pass ephemeral labels to applications, allowing them to distinguish between "preview" and "stable" modes and directing them to appropriate resources. This requires the application to automatically reload its configuration when labels change, a capability that must be implemented by developers using suitable libraries for their programming language. An example using RabbitMQ demonstrates how this setup can prevent preview applications from accessing production queues, instead directing them to separate, designated queues. The process also includes promoting new versions to stable status by updating labels, with applications automatically adjusting their configurations to use production resources, showcasing a sophisticated approach to managing progressive deployments in Kubernetes environments.