December 2024 Summaries

Kubernetes has significantly transformed the deployment landscape over the past decade by enhancing continuous delivery (CD) best practices, which aim to deploy quickly in response to business needs while minimizing deployment friction. These practices, though predating Kubernetes, are amplified by its ability to provide easily isolated test environments and manage containers, ensuring consistency and reliability across deployment processes. Key CD principles include always being ready to deploy to production, building once and deploying everywhere, including all components in automated testing, and using the same deployment processes in testing and production environments. Kubernetes supports these principles by offering a declarative system that abstracts underlying infrastructure, uses container versioning, and provides tools for consistent deployment across environments. Additionally, the integration of tools like Helm, Kustomize, and ArgoCD enables seamless and dynamic deployments, ensuring robust and efficient software release management in modern ecosystems.

In the upcoming 2025.1 release, Octopus is set to introduce Generic OpenID Connect (OIDC) accounts, enhancing the ability to authenticate with third-party systems that support OAuth 2.0 and JSON Web Tokens (JWTs). This new feature will enable Octopus to act as a client by contributing a JWT as a variable to deployments, providing flexibility in authentication for services like HashiCorp Vault and Google Cloud's Workload Identity Federation. The Generic OIDC accounts allow users to configure specific fields like audience and subject generation, ensuring compatibility with target services. For HashiCorp Vault, this includes setting up JWT configuration to manage secrets securely, whereas for Google Cloud, it involves matching the subject generator and audience with the Workload Identity Federation setup. This innovation facilitates secure access to cloud resources and the management of secrets without relying on static credentials, promising a scalable and secure authentication solution for various integrations. These accounts will soon be available for Octopus Cloud customers, with self-hosted users also gaining access upon the release, offering a significant enhancement to deployment pipelines by supporting flexible and secure OAuth 2.0 JWT flows.

Kubernetes has transformed application development and management, allowing organizations to scale and automate deployments efficiently, but it also introduces complexities when managing hundreds of microservices across various environments. Octopus has focused on simplifying Kubernetes deployments by integrating Kubernetes-native tools and best practices, such as declarative configurations and Git as a source of truth. Over 400 organizations use Octopus for regular Kubernetes deployments, benefiting from enhanced features like Kubernetes Object Status, Helm integration, and Git triggers. In 2023 and 2024, Octopus introduced features such as Kubernetes Object Status, sourcing configuration files from Git, and the Kubernetes agent to facilitate workerless deployments. Looking ahead to 2025, Octopus plans to enhance its offerings with Kubernetes Live Status, manifest inspection, and integration with Argo CD and Argo Rollouts, aiming to provide real-time insights and simplify deployment verification and troubleshooting. The platform emphasizes a centralized configuration template approach, enabling flexibility and control, while also supporting automation through triggers and orchestration projects to manage large-scale microservices deployments.

Git triggers, a new feature introduced by Octopus, streamline the deployment process by automating the creation of releases based on changes in Git repositories, thus supporting a pull-based deployment model aligned with GitOps practices. This feature eliminates the need for explicit CI steps to create releases, offering flexibility and efficiency in deploying applications and managing infrastructure directly from Git. Git triggers are particularly beneficial for teams using tools like Helm, Kustomize, and Terraform, as they allow for seamless deployment updates and infrastructure alignment with the latest Git commits. They are simple to set up in Octopus, with the system checking repositories every three minutes for new commits, and can be configured to trigger releases based on specific changes, such as commits to particular folders. This innovation not only simplifies deployment workflows but also accelerates feedback loops and enhances alignment with modern development practices, making it an essential tool for teams adopting GitOps methodologies.

Steve Fenton's presentation at SHIPPED24 explores the evolution of value measurement in software delivery, emphasizing the importance of outcome-based metrics over traditional activity or speed-focused measures. He outlines a framework for effective DevOps metrics, highlighting the need for a balanced approach to visibility, lifespan, and elevation of metrics to ensure they drive genuine improvement without distracting from broader goals. Fenton argues that while high throughput can aid rapid learning and experimentation, true success in software products is achieved by focusing on user-centric outcomes rather than merely increasing work speed. He advises using metrics to connect technical efforts with human impacts, suggesting that a nuanced measurement system can lead to more impactful results with less effort.

Octopus has introduced a feature allowing users to deactivate tenants, which will exclude them from license calculations while still permitting edits, in response to customer feedback. This new capability, expected to be available to Cloud customers soon and self-hosted ones in the 2025.1 release, enables users to manage tenant states on the Tenant Settings page, with support for the Terraform provider and CLI. Deployments and runbook runs are restricted to enabled tenants, automatically filtering out deactivated ones, and attempts to deploy to deactivated tenants through the CLI or API will result in errors. The deactivation feature offers increased flexibility and control over deployments, aiding in managing licensing requirements and organizing environments, while ensuring historical configurations remain accessible. Octopus encourages feedback on this feature to understand its impact on user processes and to inform future improvements.