August 2024 Summaries

A new Kubernetes worker has been introduced to enhance the scalability of deployment infrastructure by executing deployment tasks within Kubernetes clusters. This worker, an extension of the existing Octopus Kubernetes agent, enables the execution of any workload in the cluster, offering an efficient alternative to traditional physical or virtual worker machines. It operates by executing each deployment task in a new Kubernetes Pod, allowing for horizontal scaling, resource allocation, and cost reduction. Users can install the Kubernetes worker using a Helm chart via a command-line or a guided installation wizard on the Octopus web portal. The worker communicates with the Octopus Server using a polling protocol, and it can be customized for specific workload needs through Helm values. Currently available as an early access preview for cloud customers, the worker will soon be released for self-hosted customers, with further details available in the Octopus Deploy documentation and an upcoming webinar.

Shawn Sesna shares his experience of configuring the Octopus Kubernetes agent on an AWS Elastic Kubernetes Service (EKS) cluster using the Elastic File System (EFS) for the storage class. Finding the process challenging due to scattered documentation, he provides a concise guide to streamline the integration of EFS with EKS. The post assumes the reader has an EKS cluster and recommends using the eksctl tool for setup. It details steps for creating an EFS file system, setting up an IAM OIDC provider, and creating an IAM Service Account and Role for the CSI driver. Sesna also describes adding the Amazon EFS CSI Driver to the cluster and creating a StorageClass resource. He addresses potential troubleshooting issues, such as permission errors, and aims to assist others by consolidating the necessary steps in one location, thereby alleviating the frustration of navigating through dispersed AWS documentation.

Octopus has introduced Git protection rules to enhance security and control in Git-based projects by ensuring that only authorized resources are deployed to the correct environments. These new features build on existing tools like Config as Code and the ability to source files from Git repositories, addressing the need for more robust protections in deployment processes. Git protection rules allow users to define custom restrictions on branches and tags, mitigating risks associated with unauthorized or outdated resources. Octopus supports sourcing files from external Git repositories, enabling scenarios like storing scripts for deployment, and also offers project repository rules to manage deployment processes and variables. This feature began rolling out to Cloud instances in late July 2024, with availability for self-hosted customers expected later in the year, and Octopus encourages feedback from users.