External feed triggers

Octopus Deploy has introduced external feed triggers that enable automated release processes when new container images or Helm charts are pushed to repositories, enhancing the GitOps approach to Continuous Delivery. This pull-based model allows the Continuous Delivery server to actively compare the desired state from source repositories, like Git, with the actual state in target environments such as Kubernetes clusters, thereby maintaining a continuous reconciliation cycle. By configuring Octopus projects with container dependencies, users can set up external feed triggers that monitor new package releases, reducing configuration needs and risks associated with updating manifest repositories directly. This approach not only streamlines the deployment process across environments but also separates the management of containers and environment configurations from manifest repositories, mitigating issues like drift and security risks. These features support a more efficient, secure, and automated deployment workflow, even for non-Kubernetes environments, by allowing CI systems to focus on artifact building and testing while CD systems handle deployments.