March 2023 Summaries

Octopus Deploy's version 2023.2 introduces an enhanced structured variable replacement feature that simplifies the process of injecting Octopus-specific variables into Kubernetes YAML configurations. This update allows developers to use locally tested YAML files without needing to embed Octostache variable templates, thus maintaining clean configurations while enabling customization for different environments. By registering a Kubernetes cluster and creating a project with a "Deploy raw Kubernetes YAML" step, developers can deploy applications like a web server pod and service, adjusting variables such as text and ports according to the deployment environment. The structured variables feature uses a naming convention with colons to target specific values in the configuration, although it does have limitations, such as not supporting large structural code replacements or distinguishing between multiple YAML documents in the same file. This innovation aims to offer a flexible, lightweight method for configuration management, with future enhancements planned for richer configuration experiences using tools like kustomize.

Steve Fenton argues against using maturity models in DevOps, recommending instead a capability model that emphasizes continuous improvement and adaptability to changing business landscapes. Maturity models, which are activity-based and follow a linear, standardized approach, are deemed inappropriate for DevOps due to their rigidity and focus on achieving a fixed end state. In contrast, capability models are outcome-based, dynamic, and contextual, encouraging teams to connect their efforts with measurable results and adapt to their specific scenarios. The DevOps capability model, aligned with DORA metrics, helps organizations identify and implement the capabilities that will most effectively enhance their performance. By using this model, organizations can focus on constant incremental improvements rather than adhering to a pre-determined set of activities, fostering innovation and better alignment with business goals.

Stephen Shamakian, a DevOps Senior Principal Engineer at a leading health solutions company, shares insights from his journey into DevOps, which began in web engineering and automation, leading him to discover Octopus Deploy. He emphasizes that DevOps is a combination of people, processes, and tools, where cultural change, CI/CD process automation, and the right tools are essential for success. Shamakian's organization has standardized its DevOps pipeline using a build-once-deploy-many approach, resolving previous deployment inefficiencies and enhancing auditability through change ticket-controlled production deployments. He identifies the cultural shift and siloed operations as challenging aspects of DevOps but finds the automation that enables quick and reliable deployments the most rewarding. For newcomers, Shamakian advises learning automation and scripting for infrastructure paths and understanding build mechanisms for development paths, while also honing soft skills to communicate technical concepts effectively. He recommends "The Phoenix Project" as a valuable DevOps book and shares his interest in rocket systems, drawing a parallel between software deployment and rocket launches.

GitHub Actions has rapidly become a valuable tool in the continuous integration landscape, enabling users to automate testing, building, and deployment tasks directly within their repositories. With a plethora of community-created actions available, developers can enhance their workflows by utilizing tools like Test Reporter for integrating test results, Build and Push Docker Images for creating and deploying multi-platform Docker builds, and Setup PHP for configuring PHP environments. Other notable actions include GitTools for semantic versioning, Action Automatic Releases for streamlined release management, and PullPreview for deploying live environments for code review. Additionally, the GitHub Marketplace offers Octopus Deploy actions, enhancing deployment automation further. Installing these actions is straightforward, requiring users to find, copy, and paste the relevant code into their repository's configuration files. For those seeking more tailored solutions, the GitHub Marketplace provides a wide range of additional actions to explore.

GitHub Actions offers developers a way to automate workflows within a GitHub repository, and when combined with tools like Octopus Deploy, it enhances continuous delivery through features such as environment visualization and standardized step templates. The article provides a detailed guide on building a Docker image using GitHub Actions, publishing it to Amazon Elastic Container Registry, and deploying it on Amazon Elastic Kubernetes Service using Octopus Deploy. It outlines the necessary setup for AWS, GitHub, and Octopus, including creating access keys, configuring repositories, and setting up deployment targets. The integration of Octopus Deploy provides a more consistent user experience through its UI and its ability to manage releases across various environments. The article encourages users to explore further resources and tools for optimizing continuous integration and deployment workflows.

Terence Wong's article explores the use of GitHub Actions as a tool for DevOps operations, highlighting its ability to build, push, and deploy software directly from a GitHub repository to cloud platforms like Amazon's Elastic Kubernetes Service (EKS). The article delves into the practical steps of setting up a Docker image using GitHub Actions, publishing it to Amazon Elastic Container Registry (ECR), and deploying it to EKS, emphasizing the ease of integrating DevOps processes within the GitHub ecosystem. It also addresses the variability in user experience due to the community-maintained nature of GitHub Actions' step templates, contrasting this with the standardized templates offered by Octopus Deploy, which the article indicates will be discussed further in a subsequent post. Throughout, Wong provides practical examples and insights into the deployment process, while promoting additional resources and tools for further exploration of GitHub Actions and Octopus Deploy in continuous integration and deployment scenarios.

GitHub Actions provides a framework for integrating DevOps processes into any GitHub repository by using workflows, enabling interactions with various services during deployment. This guide details the process of building and pushing the Octopus Deploy underwater app to Amazon Elastic Container Registry (ECR) through GitHub Actions. To follow along, users need an AWS account, a GitHub account, and access to the Octopus underwater app repository. The setup involves creating an access key and an ECR repository in AWS, configuring GitHub secrets for authentication, and creating a workflow file that outlines the steps for deploying the app. The workflow involves checking out the code, authenticating with AWS, and using pre-built step templates to build, tag, and push the Docker image to Amazon ECR. The guide shows how GitHub Actions automatically triggers these steps upon pushes or pull requests to the main branch, and discusses the potential for similar workflows to deploy to other cloud services. The post concludes by mentioning future topics, such as deploying the app to Amazon EKS using GitHub Actions and Octopus Deploy, and offers resources for learning more about these tools.

The Azure VM extension for Tentacle, deprecated in 2021, is set to be removed from the marketplace in late March 2023 due to its incompatibility with newer Tentacle versions and the shift towards ARM templates and script extensions. Users are encouraged to transition to using ARM templates and PowerShell DSC extensions for deploying Tentacles on Windows VMs, ensuring compatibility with the .NET 4.8 runtime required for Tentacle versions from 6.3 onwards. The article provides guidance on preparing DSC configurations and ARM templates for deploying Tentacles, either on new or existing VMs, highlighting the ability to lock Tentacle to version 6.2 for compatibility with older .NET frameworks. The transition to these methods offers users greater control over VM deployment and facilitates smoother Tentacle updates, enhancing the deployment experience.