October 2022 Summaries

Jump boxes or bastion hosts serve as a secure access point to private networks from the public internet, typically using trusted remote access services like RDP or SSH. The author describes how to deploy an OpenSSH server within a Kubernetes cluster to facilitate administrative tasks, highlighting the ease of hosting an SSH server as a Kubernetes pod. The setup involves creating a service account with specific permissions, deploying an instance of the linuxserver/openssh-server image, and exposing it through a load balancer service. To enhance efficiency, the author suggests incorporating kubectl and its configuration into a custom Docker image to ensure persistent availability upon pod recreation. This approach allows for secure and convenient management of Kubernetes clusters, leveraging the bastion host as a reliable tool for DevOps teams handling routine administrative tasks.

Deployment patterns are crucial for minimizing downtime and ensuring smooth operations in development pipelines, and Octopus provides structured ways to implement several of these patterns. Rolling deployments involve releasing updates to one target at a time, reducing risks and allowing easy rollbacks, while blue/green deployments use two production environments to facilitate seamless transitions and simple rollbacks at the cost of complexity and expense. Canary deployments introduce changes to a small section of production targets for testing before a wider rollout, allowing early detection of issues. Multi-region deployments extend releases across various geographical locations using a combination of environments, lifecycles, cloud regions, or tenants, which can be customized in Octopus for order and scheduling preferences. Octopus offers detailed processes to set up these patterns, emphasizing automation, role assignments, and variable management to enhance deployment efficiency and reliability.

Harsh Sabikhi, the Senior Vice President of Revenue at Octopus, discusses his career journey, emphasizing his transition from engineering roles at companies like PTC, Rally Software, GitHub, and HashiCorp to his current position at Octopus. He joined Octopus Deploy to address the challenges of deploying software to production, aiming to streamline this process for organizations. As SVP of Revenue, Harsh oversees the company's go-to-market strategy, which includes sales, customer success, and technical account management, ensuring a seamless customer experience. He is enhancing the sales experience by implementing a named account model for large enterprises, improving the self-service purchasing options on Octopus's website, and partnering with major platforms like Amazon and Microsoft for direct purchases through their marketplaces. Harsh motivates his team by leading from the front, actively engaging with customers and partners, and drawing on his background in electrical engineering and software development, which adds a unique perspective to his leadership style.

Matthew Casperson's ebook on the "10 pillars of pragmatic Kubernetes deployments with Octopus Deploy" serves as a comprehensive guide for modern DevOps teams tasked with delivering more in less time. The ebook focuses on building scalable deployment pipelines using Octopus and Kubernetes, addressing increased team involvement, application deployment, and frequency of deployments. It provides practical implementations that help teams navigate the complexities of modern DevOps environments. The book is designed for readers with basic Kubernetes knowledge and requires access to a Kubernetes cluster and an Octopus instance, offering detailed instructions on the deployment process.

MuleSoft offers a unique software solution for creating custom APIs that interact with both on-premises and cloud-based systems. This guide details the process of deploying a MuleSoft API to a server using Mule Runtime and Octopus Deploy. It begins with downloading necessary software, including Anypoint Studio, which is available as a 30-day trial, and configuring the Mule Community Edition Runtime. The tutorial demonstrates creating a simple "Hello World" API in Anypoint Studio and exporting it as a deployable JAR file using Maven, either from the built-in functionality in Anypoint Studio or through a command-line approach. The deployment process is facilitated by Octopus Deploy, which, despite lacking a specific step for Mule Runtime, can use the Deploy Java Archive step to manage the deployment. The guide also touches on using Postman for API testing and provides instructions for updating API messages using structured configuration variables, enhancing the functionality and flexibility of the API deployment across different environments.

In the blog post, Stephen Heise discusses the challenges and considerations involved in identifying variable usage within Octopus Deploy, a popular DevOps tool. Users often seek to understand where variables are used to determine their purpose, assess the impact of changing values, or safely delete unused variables. The complexity arises from Octostache expressions, a flexible variable substitution syntax that allows for dynamic and creative variable usage, making it difficult to track all possible uses. Two potential approaches to address this issue are explored: a static search that examines code and a deployment-time search capturing variable usage during deployments. However, each method has limitations in capturing all variable usages, particularly in unusual or creative scenarios. While a static search could be implemented through existing tools like PowerShell scripts, the deployment-time search would require significant infrastructure changes. Heise questions whether developing these features would provide enough value to users, given the inherent limitations and complexity, and invites feedback from the community on the matter.

Octopus Deploy is updating its command-line interface (CLI) to address several limitations in the existing system, which has been primarily automation-focused and inconsistent in its command structure and output. The current CLI, built on C# and reliant on the OctopusClients .NET library, faces challenges such as cross-platform compilation difficulties and lack of support for the Executions API. The new CLI, developed in the Go programming language, aims to expand the number of commands and enhance user interaction through an interactive interface, while still prioritizing automation. This redesign is intended to improve the user experience, support more customer-centric workflows, and reduce the constraints of previous design decisions. The development team seeks user feedback on desired features and scenarios to ensure the new CLI meets customer needs. Progress can be tracked on GitHub, with distributables available on package repositories like Chocolatey and Homebrew.

Shawn Sesna discusses a solution for sharing Workers across multiple spaces in Octopus Deploy, which is particularly beneficial for their Samples instance where infrastructure is created and destroyed daily. Initially, the use of dedicated Workers for each space led to inefficiencies and increased costs due to idleness. Consequently, they transitioned to a shared Workers approach, using Terraform to automate the creation and scaling of Workers across AWS, Azure, and GCP. This setup involves gathering a list of all spaces, creating and registering Workers, and then adding them to each space's Worker Pool. By leveraging cloud provider scaling features and automating the process, the team optimized resource usage and reduced costs while maintaining the necessary infrastructure to support their operations.

Octopus Deploy provides a structured approach to transitioning from manual to automated software deployments, particularly useful for legacy systems or complex technologies. By modeling manual deployments through Octopus, users can benefit from enhanced reliability, traceability, and audit compliance, similar to automated processes. This involves creating a checklist of deployment steps, organizing teams responsible for each task, defining lifecycles to control release promotion across environments, and transforming the checklist into a deployment process within Octopus. The system allows for tracking and managing each deployment step, ensuring authorized completion and maintaining detailed logs. While the initial goal may not be automation, this process lays the groundwork, allowing teams to gradually automate steps, improving consistency and efficiency over time.

Each year, the Accelerate State of DevOps Report, a collaborative effort by Google Cloud and DORA, offers valuable insights into the practices and capabilities that drive high performance in software delivery, based on extensive research and survey responses. The 2022 report, sponsored by Octopus Deploy, highlights the crucial role of organizational culture in adopting effective security practices, revealing that high-trust, low-blame environments are more conducive to successful security implementation. It also emphasizes the interconnectedness of DevOps capabilities and their collective impact on software delivery and organizational performance, with new insights on the role of reliability, cloud technology adoption, and a novel respondent categorization. The report continues to underscore the importance of cultural factors over purely technical ones in enhancing security and performance, inviting organizations to focus on cultural improvements to bolster their security posture.

The Executions API is a new enhancement introduced in the Octopus 2022 Q3 release, designed to improve the efficiency of operations such as deployments, release creation, and runbook execution. This initiative emerged from customer feedback regarding performance bottlenecks caused by excessive network traffic between the Octopus CLI and the Octopus REST API. By consolidating multiple network requests into streamlined endpoints, the Executions API significantly reduces traffic and improves scalability, offering a threefold increase in speed compared to previous methods. The API features versioning and camel case schema for improved developer experience, allowing for the use of resource names in message payloads, which eliminates the need for extensive lookups. The Executions API is poised to enhance future integrations and tools, promising faster deployment times for users of Octopus Deploy 2022.3 and the new Octopus CLI.