Congratulations!

[Valid Atom 1.0] This is a valid Atom 1.0 feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://feeds.feedburner.com/OctopusDeploy

  1. <feed xmlns="http://www.w3.org/2005/Atom">
  2.  <title type="text">Octopus Deploy</title>
  3.  <subtitle type="text">Automated deployment platform</subtitle>
  4.  <id>https://octopus.com/feed</id>
  5.  <updated>2025-06-16T06:20:36.9374123Z</updated>
  6.  <link rel="alternate" href="https://octopus.com/blog" />
  7.  <link rel="self" href="https://octopus.com/feed" />
  8.  <entry>
  9.    <id>https://octopus.com/blog/ephemeral-environments</id>
  10.    <title type="text">Help shape Ephemeral Environments</title>
  11.    <published>2025-06-23T14:00:00Z</published>
  12.    <updated>2025-06-16T06:08:21.7366756Z</updated>
  13.    <author>
  14.      <name>harriet.alexander@octopus.com, Octopus Deploy</name>
  15.    </author>
  16.    <link href="https://octopus.com/blog/ephemeral-environments" />
  17.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-06/ephemeral-environments/blog-ephemeralenvironments25.png" alt="Banner showing a parent environment branching to two ephemeral environments while two illustrated developers point to the child nodes against a blue-green gradient background." /&gt;&lt;/p&gt;
  18.  
  19. &lt;p&gt;In the fast-paced world of software development, few phrases provoke as much frustration as “it works on my machine”. It’s the ultimate debugging roadblock. Your code works flawlessly in your local environment, but everything breaks when it merges. But what if there was a way to ensure your code wasn’t just “working on your machine” but on an environment that mirrors your production environment before you merge?&lt;/p&gt;
  20.  
  21. &lt;p&gt;In this post, I introduce our solution—Ephemeral Environments.&lt;/p&gt;
  22.  
  23. &lt;h2 id="what-are-ephemeral-environments"&gt;What are Ephemeral Environments?&lt;/h2&gt;
  24.  
  25. &lt;p&gt;We've been hard at work developing Ephemeral Environments, tailored for modern development workflows. These environments are automatically generated and linked to feature branches created through pull requests (PRs). They offer a temporary space for testing code changes without affecting the main lifecycle environments.&lt;/p&gt;
  26.  
  27. &lt;p&gt;The primary goal is to &lt;em&gt;shift left&lt;/em&gt; in the development process: identifying issues earlier when they are easier and less costly to address. This then minimizes surprises later in the workflow.&lt;/p&gt;
  28.  
  29. &lt;h2 id="how-ephemeral-environments-will-work"&gt;How Ephemeral Environments will work&lt;/h2&gt;
  30.  
  31. &lt;ul&gt;
  32. &lt;li&gt;Feature branch-based: When you create a pull request (PR) from your feature branch, the ephemeral environment automatically spins up.&lt;/li&gt;
  33. &lt;li&gt;Temporary by design: After you close or merge the PR, the environment spins down in a hassle-free manner.&lt;/li&gt;
  34. &lt;li&gt;Designed for early feedback: The feature will provide developers and collaborators with early integration testing, UI validation, and fast feedback loops.&lt;/li&gt;
  35. &lt;/ul&gt;
  36.  
  37. &lt;h2 id="why-you-should-get-excited"&gt;Why you should get excited&lt;/h2&gt;
  38.  
  39. &lt;p&gt;Catching issues earlier in the development lifecycle leads to better software, faster delivery, and happier teams. Here’s why we’re excited about Ephemeral Environments—and why we think you will be, too:&lt;/p&gt;
  40.  
  41. &lt;ul&gt;
  42. &lt;li&gt;Fewer environment bottlenecks: Don’t waste time waiting for staging slots or shared resources. Every feature branch gets its own environment.&lt;/li&gt;
  43. &lt;li&gt;Increased confidence in merges: Know your code works before merging into the main branch, so there are fewer surprises and regressions.&lt;/li&gt;
  44. &lt;li&gt;Seamless feedback loops: Ephemeral Environments are dynamic and easy to share. This increases collaboration across teams and stakeholders.&lt;/li&gt;
  45. &lt;/ul&gt;
  46.  
  47. &lt;h2 id="have-your-say-and-get-early-access-to-ephemeral-environments"&gt;Have your say and get early access to Ephemeral Environments&lt;/h2&gt;
  48.  
  49. &lt;p&gt;We’re building this feature to make pull request workflows smarter, faster, and more reliable— but we'd love your feedback.&lt;/p&gt;
  50.  
  51. &lt;p&gt;Whether you want to sign up for a product demo, participate in our alpha testing, or simply get notified when early access is available, we want to hear from you.&lt;/p&gt;
  52.  
  53. &lt;h3 id="whats-in-it-for-you"&gt;What’s in it for you?&lt;/h3&gt;
  54.  
  55. &lt;ul&gt;
  56. &lt;li&gt;Get early access: Get access to the ephemeral environment feature before it’s widely available.&lt;/li&gt;
  57. &lt;li&gt;Influence design: Your feedback will directly shape how we refine the feature, ensuring it meets real-world workflows.&lt;/li&gt;
  58. &lt;/ul&gt;
  59.  
  60. &lt;h2 id="how-to-sign-up"&gt;How to sign up&lt;/h2&gt;
  61.  
  62. &lt;p&gt;&lt;a href="https://octopusdeploy.typeform.com/to/ZOia9Aje" rel="nofollow"&gt;Register your interest via our form&lt;/a&gt;.&lt;/p&gt;
  63.  
  64. &lt;p&gt;We're hoping to release ephemeral environments in all instances later this year.&lt;/p&gt;
  65.  
  66. &lt;p&gt;Happy deployments!&lt;/p&gt;
  67. </content>
  68.  </entry>
  69.  <entry>
  70.    <id>https://octopus.com/blog/announcing-the-first-state-of-gitops-report</id>
  71.    <title type="text">The State of GitOps report: Exploring effective GitOps</title>
  72.    <published>2025-06-17T14:00:00Z</published>
  73.    <updated>2025-06-16T06:20:36.9374123Z</updated>
  74.    <author>
  75.      <name>steve.fenton@octopus.com, Octopus Deploy</name>
  76.    </author>
  77.    <link href="https://octopus.com/blog/announcing-the-first-state-of-gitops-report" />
  78.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-06/announcing-the-first-state-of-gitops-report/what-is-gitops-2025.png" alt="Person holds magnifying glass over GitOps logo, surrounded by icons for declarative, versioned and immutable, pulled automatically, and continuously reconciled." /&gt;&lt;/p&gt;
  79.  
  80. &lt;p&gt;We're thrilled to announce the release of the &lt;a href="https://octopus.com/publications/state-of-gitops-report"&gt;State of GitOps report&lt;/a&gt;. This report is the first to explore how practitioners apply GitOps concepts in the real world. Based on data from 660 survey responses and interviews with a panel of experts and practitioners, our goal was to understand what &amp;quot;good&amp;quot; GitOps looks like, explore different adoption styles, and analyze whether GitOps delivers the expected benefits.&lt;/p&gt;
  81.  
  82. &lt;p&gt;Combining version control, developer practices, and an automated reconciliation loop, GitOps can deliver a secure and auditable way to drive system state with human-readable files. While teams with well-established GitOps practices are seeing a return on their investment, those who haven't achieved a sufficient depth and breadth of adoption are struggling to beat the j-curve to get the benefits. This is where the State of GitOps report can help.&lt;/p&gt;
  83.  
  84. &lt;h2 id="four-key-findings"&gt;Four key findings&lt;/h2&gt;
  85.  
  86. &lt;p&gt;Our research explored various aspects of GitOps adoption and its impact, and we've uncovered 4 key findings:&lt;/p&gt;
  87.  
  88. &lt;ol&gt;
  89. &lt;li&gt;&lt;strong&gt;Better software delivery:&lt;/strong&gt; High-performing GitOps teams demonstrated higher software delivery performance, as measured by the DORA 4 key metrics (change failure rate, time to recover, deployment frequency, and lead time for changes).&lt;/li&gt;
  90. &lt;li&gt;&lt;strong&gt;Increased reliability:&lt;/strong&gt; These high-performing teams also reported the best reliability records, based on user satisfaction, meeting uptime targets, and avoiding slowdowns and outages.&lt;/li&gt;
  91. &lt;li&gt;&lt;strong&gt;Security and compliance:&lt;/strong&gt; We found a clear link between GitOps maturity (how many practices teams adopt) and achieving security and compliance benefits.&lt;/li&gt;
  92. &lt;li&gt;&lt;strong&gt;Adoption is increasing:&lt;/strong&gt; Most organizations (93%) plan to continue or increase their GitOps adoption, indicating strong confidence in the approach.&lt;/li&gt;
  93. &lt;/ol&gt;
  94.  
  95. &lt;p&gt;The report delves into the nuances of adoption, distinguishing between 'breadth' (the extent across production systems) and 'depth' (how many practices are implemented and how well).&lt;/p&gt;
  96.  
  97. &lt;p&gt;We found that GitOps is most often used for application or service deployments (79%), application configurations (73%), and infrastructure (57%). We also challenge the idea that GitOps is &lt;em&gt;only&lt;/em&gt; for Kubernetes, with 26% of organizations applying it to other technology stacks.&lt;/p&gt;
  98.  
  99. &lt;h2 id="the-gitops-model"&gt;The GitOps model&lt;/h2&gt;
  100.  
  101. &lt;p&gt;A significant part of the report introduces the GitOps Model, outlining the 6 practices we found necessary for successful adoption and positive outcomes:&lt;/p&gt;
  102.  
  103. &lt;ol&gt;
  104. &lt;li&gt;Declarative desired state&lt;/li&gt;
  105. &lt;li&gt;Human readable format&lt;/li&gt;
  106. &lt;li&gt;Responsive code review&lt;/li&gt;
  107. &lt;li&gt;Version control&lt;/li&gt;
  108. &lt;li&gt;Automatic pull&lt;/li&gt;
  109. &lt;li&gt;Continuous reconciliation&lt;/li&gt;
  110. &lt;/ol&gt;
  111.  
  112. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-06/announcing-the-first-state-of-gitops-report/gitops-model.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-06/announcing-the-first-state-of-gitops-report/gitops-model.png' class="img-fluid center" alt='The 6 GitOps practices drive DevOps outcomes for software delivery, reliability, and wellbeing' /&gt;&lt;/a&gt;&lt;/p&gt;
  113.  
  114. &lt;p&gt;We developed a GitOps score based on how closely organizations align with these practices and found organizations with higher scores are most likely to obtain the benefits of GitOps. This means teams with higher scores were significantly more likely to report:&lt;/p&gt;
  115.  
  116. &lt;ul&gt;
  117. &lt;li&gt;Increased security&lt;/li&gt;
  118. &lt;li&gt;Prevention of configuration drift&lt;/li&gt;
  119. &lt;li&gt;Improved auditability&lt;/li&gt;
  120. &lt;li&gt;Easier compliance&lt;/li&gt;
  121. &lt;li&gt;Reduced elevated access&lt;/li&gt;
  122. &lt;/ul&gt;
  123.  
  124. &lt;p&gt;The ability to recreate applications from version control is also strongly linked to higher scores.&lt;/p&gt;
  125.  
  126. &lt;h2 id="gitops-practices-and-devops-outcomes"&gt;GitOps practices and DevOps outcomes&lt;/h2&gt;
  127.  
  128. &lt;p&gt;Beyond specific GitOps benefits, the report also examines the relationship between GitOps and broader DevOps outcomes, like software delivery performance, reliability, and even wellbeing. Higher GitOps scores correlate positively with these outcomes.&lt;/p&gt;
  129.  
  130. &lt;p&gt;It's essential to be aware of the potential &amp;quot;j-curve&amp;quot; effect when adopting new practices like GitOps. You might see an initial dip in performance as you introduce new skills and practices, but sticking with it leads to significant long-term gains. The 6 GitOps practices are mutually supportive; leaving one out can create gaps in the effectiveness of others.&lt;/p&gt;
  131.  
  132. &lt;p&gt;Of course, adopting GitOps isn't without its challenges. The report identifies potential &amp;quot;trip hazards&amp;quot;, like the risk of accidental resource deletion, leaking secrets in version control, overloading version control systems, and gaps in deployment processes or access controls. Understanding these pitfalls and adopting protective measures, like dry-runs, approval workflows, secret management tools, and robust access control, is crucial.&lt;/p&gt;
  133.  
  134. &lt;p&gt;The State of GitOps Report is a comprehensive baseline for where GitOps stands today. It offers valuable insights into the practices that drive success and helps you understand how to improve your own outcomes.&lt;/p&gt;
  135.  
  136. &lt;p&gt;We encourage you to &lt;a href="https://octopus.com/publications/state-of-gitops-report"&gt;dive into the full report&lt;/a&gt; to explore the findings, understand the GitOps model, and identify areas for continuous improvement on your GitOps journey.&lt;/p&gt;
  137.  
  138. &lt;p&gt;Happy deployments!&lt;/p&gt;
  139. </content>
  140.  </entry>
  141.  <entry>
  142.    <id>https://octopus.com/blog/inside-devops-oluwateniola-olubowale</id>
  143.    <title type="text">Inside DevOps with Oluwateniola Olubowale from United Capital</title>
  144.    <published>2025-06-16T14:00:00Z</published>
  145.    <updated>2025-06-13T06:33:09.8433565Z</updated>
  146.    <author>
  147.      <name>joanna.wyganowska@octopus.com, Octopus Deploy</name>
  148.    </author>
  149.    <link href="https://octopus.com/blog/inside-devops-oluwateniola-olubowale" />
  150.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-06/inside-devops-oluwateniola-olubowale/img-blog-inside-inside-devops-750x400-oluwateniola-1x-no-title.png" alt="Photo of Oluwateniola Olubowale" /&gt;&lt;/p&gt;
  151.  
  152. &lt;p&gt;This post is the next in our &lt;a href="https://octopus.com/blog/tag/Inside%20DevOps"&gt;Inside DevOps series&lt;/a&gt;, where we share lessons learned from those on the frontlines of DevOps.&lt;/p&gt;
  153.  
  154. &lt;p&gt;Hear from &lt;a href="https://www.linkedin.com/in/oluwateniola-olubowale-362905200/" rel="nofollow"&gt;Oluwateniola Olubowale&lt;/a&gt;, DevOps Engineer at United Capital, a leading African financial and investment banking group.&lt;/p&gt;
  155.  
  156. &lt;p&gt;&lt;strong&gt;What is DevOps to you? How do you define it?&lt;/strong&gt;&lt;/p&gt;
  157.  
  158. &lt;p&gt;&lt;em&gt;Oluwateniola:&lt;/em&gt;  DevOps represents a fundamental cultural shift rather than just a technical discipline. It’s about fostering close collaboration between development and operations teams to deliver high-quality software at speed. It emphasizes automation, transparency, and continuous feedback, all aimed at driving measurable business outcomes.&lt;/p&gt;
  159.  
  160. &lt;p&gt;&lt;strong&gt;How did your DevOps journey start?&lt;/strong&gt;&lt;/p&gt;
  161.  
  162. &lt;p&gt;&lt;em&gt;Oluwateniola:&lt;/em&gt;  It began when I transitioned from a backend development role to one that required more involvement with infrastructure and deployment processes. I became increasingly curious about the delays and inefficiencies that occurred after code was written. This curiosity led me to explore Continuous Integration, containerization, and Infrastructure as Code (IaC)—areas that gradually shaped my path into DevOps.&lt;/p&gt;
  163.  
  164. &lt;p&gt;&lt;strong&gt;What’s the most challenging part of DevOps?&lt;/strong&gt;&lt;/p&gt;
  165.  
  166. &lt;p&gt;&lt;em&gt;Oluwateniola:&lt;/em&gt; The biggest challenge often lies in changing organizational culture. Encouraging teams to adopt a shared sense of ownership, prioritize automation, and embrace continuous learning can take time. Tools and pipelines can be implemented, but achieving true cross-functional collaboration requires leadership, patience, and clear communication.&lt;/p&gt;
  167.  
  168. &lt;p&gt;&lt;strong&gt;What’s the most rewarding part of DevOps?&lt;/strong&gt;&lt;/p&gt;
  169.  
  170. &lt;p&gt;&lt;em&gt;Oluwateniola:&lt;/em&gt; It’s incredibly fulfilling to see deployment processes evolve from being high-risk and manual to being streamlined, automated, and dependable. Knowing that you’ve helped build systems that allow developers to deliver confidently and recover gracefully from failure makes the work meaningful.&lt;/p&gt;
  171.  
  172. &lt;p&gt;&lt;strong&gt;What DevOps trend have you been following lately?&lt;/strong&gt;&lt;/p&gt;
  173.  
  174. &lt;p&gt;&lt;em&gt;Oluwateniola:&lt;/em&gt; Recently, I’ve been following the rise of GitOps and Platform Engineering. GitOps offers a powerful, declarative approach to managing infrastructure and application deployments, while Platform Engineering focuses on building internal developer platforms (IDPs) that improve scalability and developer experience.&lt;/p&gt;
  175.  
  176. &lt;p&gt;&lt;strong&gt;What are some DevOps best practices your organization has implemented?&lt;/strong&gt;&lt;/p&gt;
  177.  
  178. &lt;p&gt;&lt;em&gt;Oluwateniola:&lt;/em&gt; Our team has embraced several best practices, including Infrastructure as Code with Terraform, Continuous Integration and Continuous Delivery, automated testing, and the use of blue/green deployments. We also use centralized logging and observability, using tools like the ELK Stack and Prometheus with Grafana. Regular retrospectives are part of our process to ensure continuous improvement.&lt;/p&gt;
  179.  
  180. &lt;p&gt;&lt;strong&gt;What’s the biggest challenge Octopus has helped you with?&lt;/strong&gt;&lt;/p&gt;
  181.  
  182. &lt;p&gt;&lt;em&gt;Oluwateniola:&lt;/em&gt; Octopus has played a critical role in standardizing and simplifying our deployment workflows. It has brought consistency across environments, improved auditability, and significantly reduced manual intervention. With Octopus, we’ve been able to automate complex deployments while maintaining visibility and control.&lt;/p&gt;
  183.  
  184. &lt;p&gt;&lt;strong&gt;What advice would you give someone just starting their DevOps journey?&lt;/strong&gt;&lt;/p&gt;
  185.  
  186. &lt;p&gt;&lt;em&gt;Oluwateniola:&lt;/em&gt; Focus on the principles before the tools. Understand the value of collaboration, automation, and Continuous Delivery. Start small, learn version control, build simple CI/CD pipelines, and iterate. Most importantly, don’t be afraid to make mistakes; each challenge is an opportunity to learn and grow.&lt;/p&gt;
  187.  
  188. &lt;p&gt;&lt;strong&gt;What DevOps book would you recommend reading?&lt;/strong&gt;&lt;/p&gt;
  189.  
  190. &lt;p&gt;&lt;em&gt;Oluwateniola:&lt;/em&gt; &lt;a href="https://octopus.com/devops/reading-list/#the-phoenix-project"&gt;The Phoenix Project&lt;/a&gt; by Gene Kim remains one of the most accessible and insightful introductions to DevOps. It conveys key concepts through relatable storytelling. For a deeper dive, &lt;a href="https://octopus.com/devops/reading-list/#the-devops-handbook"&gt;The DevOps Handbook&lt;/a&gt; by Gene Kim, Jez Humble, Patrick Debois, and John Willis offers a comprehensive, practical guide to implementing DevOps practices.&lt;/p&gt;
  191.  
  192. &lt;p&gt;&lt;strong&gt;What’s one thing about you that might surprise us?&lt;/strong&gt;&lt;/p&gt;
  193.  
  194. &lt;p&gt;&lt;em&gt;Oluwateniola:&lt;/em&gt; I originally aspired to become a marine engineer. That foundation in systems thinking and design eventually led me to software engineering. Today, instead of engines and vessels, I focus on building and optimizing robust software systems, but the problem-solving mindset remains the same.&lt;/p&gt;
  195.  
  196. &lt;p&gt;&lt;strong&gt;Thank you for sharing your insights with us, Oluwateniola!&lt;/strong&gt;&lt;/p&gt;
  197.  
  198. &lt;div class="alert alert-info"&gt;&lt;p&gt;If you’d like to be featured in our series, &lt;a href="https://octopus.com/blog/tag/Inside%20DevOps" class="alert-link"&gt;Inside DevOps&lt;/a&gt;, please reach out to &lt;a href="https://www.linkedin.com/in/joannawyganowska/" class="alert-link" rel="nofollow"&gt;Joanna on LinkedIn&lt;/a&gt; to set up a time for a quick chat.&lt;/p&gt;
  199. &lt;/div&gt;
  200. </content>
  201.  </entry>
  202.  <entry>
  203.    <id>https://octopus.com/blog/beyond-skeleton-pipelines-who-owns-software-pipelines</id>
  204.    <title type="text">Beyond skeleton pipelines: who owns your software pipeline?</title>
  205.    <published>2025-06-11T14:00:00Z</published>
  206.    <updated>2025-06-06T03:51:36.4237762Z</updated>
  207.    <author>
  208.      <name>matthew.allford@octopus.com, Octopus Deploy</name>
  209.    </author>
  210.    <link href="https://octopus.com/blog/beyond-skeleton-pipelines-who-owns-software-pipelines" />
  211.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-06/beyond-skeleton-pipelines-who-owns-software-pipelines/blogimage-highperformancedevopstoolchain-2023.png" alt="Stylized image of two people doing maintenance work on a DevOps infinity symbol with a cog and timer at its center." /&gt;&lt;/p&gt;
  212.  
  213. &lt;p&gt;Your current software delivery processes are probably working fine. They build your code, maybe run a test or two, and get your software to production. That's no small achievement, but here's a question that might make you pause.&lt;/p&gt;
  214.  
  215. &lt;p&gt;When did someone last spend time improving them?&lt;/p&gt;
  216.  
  217. &lt;p&gt;If you're like many software teams I've worked with, the answer is probably &amp;quot;not recently&amp;quot;. Maybe not ever.&lt;/p&gt;
  218.  
  219. &lt;p&gt;I've worked with developer teams at different maturity levels and have repeatedly seen this pattern. Great development teams who are busy building software but aren't large enough to have platform teams or dedicated operational folk responsible for the software delivery process. They typically start with a template from their cloud provider, delivery tooling vendor, or, these days, their favorite AI LLM. Initially, it gets the job done, but I refer to these as skeleton pipelines—the bare minimum framework to ship code.&lt;/p&gt;
  220.  
  221. &lt;p&gt;Skeleton pipelines are a great starting point. They get you from nothing to shipping code quickly, but your pipelines are living, breathing artifacts. Before long, they need some meat added to the skeleton to provide functionality beyond the basics and make your delivery process robust and delightful.&lt;/p&gt;
  222.  
  223. &lt;p&gt;I've seen when teams experience friction with their software release process, but don't treat it as a bug or feature improvement that needs to be logged, prioritized, and worked on. If your deployment pipelines are responsible for delivering your product to customers, shouldn't you treat them as part of your product? When was the last time someone added a pipeline improvement to your backlog or spent time making your deployment process better?&lt;/p&gt;
  224.  
  225. &lt;p&gt;The important shift is treating delivery process improvements as regular development work, not spare-time projects that inevitably get pushed aside.&lt;/p&gt;
  226.  
  227. &lt;h2 id="the-ownership-vacuum"&gt;The ownership vacuum&lt;/h2&gt;
  228.  
  229. &lt;p&gt;Ask any group of engineers, &amp;quot;Who owns your software delivery pipelines?&amp;quot; and I bet you'll get different answers. When writing this post, I put that question into a search engine and reviewed the discussions, which weren't surprising. Some say developers should own what they build, others insist it's up to platform or DevOps engineers. Then there's the view that everyone is responsible because DevOps is about everyone working together. My observation is that often, no one owns it, and that's when it becomes a problem.&lt;/p&gt;
  230.  
  231. &lt;p&gt;The distinction that matters isn't really about ownership. It's about accountability. Someone needs to be accountable for ensuring your delivery process evolves, improves, and supports your organization with shipping software rather than being a friction-filled process people loathe working with. Without that accountability, pipelines can easily become unmanaged components that gradually deteriorate until they become technical debt and a bottleneck instead of an enabler.&lt;/p&gt;
  232.  
  233. &lt;p&gt;There's no one-size-fits-all answer for who should own and be accountable for your pipelines. You must discuss and agree based on your maturity, size, team structure, and individual skill sets. The important thing is that it is discussed and agreed upon, and not left to assumptions. Ask yourself now if everyone on the team knows how and where to raise an issue with the deployment process today. If the answer is no, then start there. Determine who's responsible and establish clear channels for pipeline feedback, problems, and improvements.&lt;/p&gt;
  234.  
  235. &lt;h2 id="the-cost-of-skeleton-pipelines"&gt;The cost of skeleton pipelines&lt;/h2&gt;
  236.  
  237. &lt;p&gt;This ownership vacuum creates predictable problems I've seen many times. Teams fall into the &amp;quot;if it ain't broke, don't fix it&amp;quot; mentality, leaving pipelines as-is for months or years. The issue is that what worked well 6, 12, or 18 months ago likely isn't fit for purpose today. New tooling and techniques exist now that didn't then. Your team will likely ship more frequently—or at least want to—and handle more complex deployments than when you first created that pipeline. The infrastructure you're deploying to has likely changed. Different developers and engineers might work at your company who didn't before. You're missing out on tooling and practices that could:&lt;/p&gt;
  238.  
  239. &lt;ul&gt;
  240. &lt;li&gt;Save weekly hours&lt;/li&gt;
  241. &lt;li&gt;Bring new functionality to your software delivery lifecycle that adds business value&lt;/li&gt;
  242. &lt;li&gt;Catch issues before they become customer problems&lt;/li&gt;
  243. &lt;/ul&gt;
  244.  
  245. &lt;p&gt;Worse, they often become single points of knowledge. Whoever initially sets up the pipeline is the only person who understands how it works. When that person leaves or gets pulled onto other projects, your team inherits a mysterious system everyone fears touching.&lt;/p&gt;
  246.  
  247. &lt;p&gt;Fragile pipelines break at the worst possible moments. They miss opportunities to catch issues early, optimize build times, have predictable outcomes, or provide better feedback to developers. Maybe, most importantly, they frustrate your team and slow down what they're supposed to enable: shipping great software and products.&lt;/p&gt;
  248.  
  249. &lt;h2 id="you-cant-afford-to-ignore-this"&gt;You can't afford to ignore this&lt;/h2&gt;
  250.  
  251. &lt;p&gt;&amp;quot;We're too busy building features to worry about pipeline improvements.&amp;quot; Sound familiar? It's a common pushback I hear from teams, and I get it. When trying to ship products and keep customers happy, spending time on what feels like an internal process is often considered a luxury you can't afford.&lt;/p&gt;
  252.  
  253. &lt;p&gt;Platform teams are getting a lot of attention lately, and for good reason, as they work well for larger organizations. But if your company doesn't need everything else a platform team typically handles, creating one just for pipeline ownership is unnecessary. The reality is that you don't need a dedicated platform team to own your pipelines. You can borrow their mindset by treating your delivery process as part of your product. Pipeline improvements get backlog items, performance issues get bug tickets, and deployment pain points get the same attention as user-reported problems.&lt;/p&gt;
  254.  
  255. &lt;p&gt;Start by paying attention to where your process hurts. If deployments make you nervous, your team loathes &amp;quot;release day&amp;quot;, when releases fail for mysterious reasons or when you're manually testing things your team can automate. These pain points are your roadmap for high-value improvements.&lt;/p&gt;
  256.  
  257. &lt;h2 id="making-the-investment"&gt;Making the investment&lt;/h2&gt;
  258.  
  259. &lt;p&gt;Improvements may include:&lt;/p&gt;
  260.  
  261. &lt;ul&gt;
  262. &lt;li&gt;Adding vulnerability scanning during builds&lt;/li&gt;
  263. &lt;li&gt;Configuring integration tests against ephemeral infrastructure&lt;/li&gt;
  264. &lt;li&gt;Properly storing and versioning your deployment artifacts&lt;/li&gt;
  265. &lt;li&gt;Implementing flexible approval workflows&lt;/li&gt;
  266. &lt;li&gt;Creating a robust deployment strategy&lt;/li&gt;
  267. &lt;li&gt;Measuring deployment metrics&lt;/li&gt;
  268. &lt;/ul&gt;
  269.  
  270. &lt;p&gt;I'm not giving you a shopping list of things to do. Instead, I recognize that &amp;quot;you don't know what you don't know&amp;quot; because I've been there too, and you may be experiencing issues you didn't know there were solutions to.&lt;/p&gt;
  271.  
  272. &lt;p&gt;We have a white paper titled &lt;a href="https://octopus.com/whitepapers/ten-pillars-of-pragmatic-deployments"&gt;The ten pillars of pragmatic deployments&lt;/a&gt;. I bring this to your attention not for a checklist of everything you should do but for insight into what we think good deployments look like based on years of experience building a deployment automation tool. The ideas discussed in this post might help you enhance your software delivery process today or provide insight into issues and solutions you may not have been aware of.&lt;/p&gt;
  273.  
  274. &lt;h2 id="take-ownership"&gt;Take ownership&lt;/h2&gt;
  275.  
  276. &lt;p&gt;It's easy to overlook software delivery pipelines. They're usually out of sight until they get in your way, kind of like plumbing. It's invisible when it works and catastrophic when it doesn't. Excellent plumbing supports everything in your house to function smoothly, and great delivery processes do the same for your product development.&lt;/p&gt;
  277.  
  278. &lt;p&gt;Claim ownership of your software delivery processes and ensure someone is accountable for their care and feeding. Talk to your engineers involved in developing and releasing software, and find out where the pain is. Implement easy-to-use feedback loops, add pipeline improvements to your backlog, and treat deployment pain points as bugs worth investing in and fixing.&lt;/p&gt;
  279.  
  280. &lt;p&gt;Your future self and team will thank you when your next deployment goes smoothly instead of keeping everyone up after hours or nervously huddling around a few pizzas doing your monthly release with crossed fingers.&lt;/p&gt;
  281.  
  282. &lt;p&gt;Happy deployments!&lt;/p&gt;
  283. </content>
  284.  </entry>
  285.  <entry>
  286.    <id>https://octopus.com/blog/changes-to-enterprise</id>
  287.    <title type="text">New to our Enterprise tier</title>
  288.    <published>2025-06-09T14:00:00Z</published>
  289.    <updated>2025-05-30T00:46:41.6398725Z</updated>
  290.    <author>
  291.      <name>michelle.obrien@octopus.com, Octopus Deploy</name>
  292.    </author>
  293.    <link href="https://octopus.com/blog/changes-to-enterprise" />
  294.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-06/changes-to-enterprise/additions_and_improvements_to_enterprise_offering_2025_1500x800.jpg" alt="People in front of a building with icons around them representing security and data." /&gt;&lt;/p&gt;
  295.  
  296. &lt;p&gt;This quarter, we challenged ourselves to make small but impactful changes to our enterprise offering. In Octopus Server 2025.2, we added:&lt;/p&gt;
  297.  
  298. &lt;ul&gt;
  299. &lt;li&gt;Global deployment freezes&lt;/li&gt;
  300. &lt;li&gt;Priority deployments&lt;/li&gt;
  301. &lt;li&gt;ITSM for runbooks &lt;/li&gt;
  302. &lt;/ul&gt;
  303.  
  304. &lt;p&gt;We also added new capabilities to the Deployment Freeze and Priority Deployments features.&lt;/p&gt;
  305.  
  306. &lt;p&gt;In this post, I take you through the changes to our Enterprise tier.&lt;/p&gt;
  307.  
  308. &lt;h2 id="deployment-freezes"&gt;Deployment freezes&lt;/h2&gt;
  309.  
  310. &lt;p&gt;From Octopus Server 2025.2, all enterprise customers have access to both global freezes and our new project-level freezes.&lt;/p&gt;
  311.  
  312. &lt;p&gt;Project freezes provide an entry level to deployment freezes with lower permission requirements. They empower your teams to create their own freezes for projects without needing administrator permissions. &lt;a href="https://octopus.com/docs/deployments/deployment-freezes/project-deployment-freezes"&gt;Read more about project freezes in our docs&lt;/a&gt;.&lt;/p&gt;
  313.  
  314. &lt;p&gt;Recent enhancements to our Deployment Freeze feature include:&lt;/p&gt;
  315.  
  316. &lt;ul&gt;
  317. &lt;li&gt;Recurring deployment freezes—so you can create maintenance windows.&lt;/li&gt;
  318. &lt;li&gt;Freeze by tenant—for more granular freezes.&lt;/li&gt;
  319. &lt;/ul&gt;
  320.  
  321. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-06/changes-to-enterprise/global-freeze.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-06/changes-to-enterprise/global-freeze.png' class="img-fluid center" alt='Create Deployment Freeze window showing new functionality of recurring freezes' /&gt;&lt;/a&gt;&lt;/p&gt;
  322.  
  323. &lt;h2 id="priority-deployments"&gt;Priority deployments&lt;/h2&gt;
  324.  
  325. &lt;p&gt;Our Priority Deployments feature provides 2 ways to automate deployment priority:&lt;/p&gt;
  326.  
  327. &lt;ol&gt;
  328. &lt;li&gt;Prioritize the deployment when creating a new deployment.&lt;/li&gt;
  329. &lt;li&gt;Prioritize an environment in a lifecycle phase. This prioritizes all deployments to the environments in the lifecycle.&lt;/li&gt;
  330. &lt;/ol&gt;
  331.  
  332. &lt;p&gt;In 2025.2, we expanded priority deployments to runbooks. This makes it easier to proactively manage your task queue. Individual runbooks inherit the lifecycle priority, or you can prioritize individuals runs on an adhoc basis.&lt;/p&gt;
  333.  
  334. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-06/changes-to-enterprise/priority-runbooks.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-06/changes-to-enterprise/priority-runbooks.png' class="img-fluid center" alt='New Runbook run window showing new functionality of Priority Deployments for Runbooks' /&gt;&lt;/a&gt;&lt;/p&gt;
  335.  
  336. &lt;h2 id="itsm-for-runbooks"&gt;ITSM for runbooks&lt;/h2&gt;
  337.  
  338. &lt;p&gt;You can now create ITSM change requests from your runbooks. This is particularly useful if you use runbooks to provision infrastructure and need to attach change requests to progress through the relevant approvals. You can choose which runbooks you'd like to be change-controlled in your ITSM settings.&lt;/p&gt;
  339.  
  340. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-06/changes-to-enterprise/itsm-runbooks.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-06/changes-to-enterprise/itsm-runbooks.png' class="img-fluid center" alt='ITSM settings window showing new functionality of ITSM for Runbooks' /&gt;&lt;/a&gt;&lt;/p&gt;
  341.  
  342. &lt;h2 id="whats-next"&gt;What's next?&lt;/h2&gt;
  343.  
  344. &lt;p&gt;We also have more exciting changes coming soon to our Enterprise tier.&lt;/p&gt;
  345.  
  346. &lt;h3 id="standardized-reusable-and-flexible-deployment-processes-with-process-templates"&gt;Standardized, reusable, and flexible deployment processes with Process Templates&lt;/h3&gt;
  347.  
  348. &lt;p&gt;Process Templates will soon be available as an early access preview (EAP) for enterprise customers. This gives teams reusable blocks of steps to use as blueprints to reduce process duplication and standardize best practices across pipelines.&lt;/p&gt;
  349.  
  350. &lt;p&gt;Platform teams can update and roll out changes to these templates from a new area in Octopus, the Platform Hub, making them easier to maintain in the long term. Some steps will also be flexible, so teams have the freedom to diverge without sacrificing quality or compliance.&lt;/p&gt;
  351.  
  352. &lt;p&gt;This is the first feature from our Blueprints and Guardrails set of capabilities, letting you automate compliance and standardize best practices across your organization's deployment processes. Keep an eye on &lt;a href="https://roadmap.octopus.com/tabs/2-planned" rel="nofollow"&gt;our roadmap&lt;/a&gt; for what else the team has planned, including:&lt;/p&gt;
  353.  
  354. &lt;ul&gt;
  355. &lt;li&gt;Deployment Policies&lt;/li&gt;
  356. &lt;li&gt;Project Templates&lt;/li&gt;
  357. &lt;/ul&gt;
  358.  
  359. &lt;h2 id="interested-in-upgrading-to-the-enterprise-tier"&gt;Interested in upgrading to the Enterprise tier?&lt;/h2&gt;
  360.  
  361. &lt;p&gt;Please contact our helpful &lt;a href="mailto:sales@octopus.com" rel="nofollow"&gt;Sales team&lt;/a&gt;.&lt;/p&gt;
  362.  
  363. &lt;p&gt;Happy deployments!&lt;/p&gt;
  364. </content>
  365.  </entry>
  366.  <entry>
  367.    <id>https://octopus.com/blog/octopus-datadog-integration</id>
  368.    <title type="text">Introducing the Octopus Datadog integration</title>
  369.    <published>2025-06-08T14:00:00Z</published>
  370.    <updated>2025-06-10T00:17:27.6392689Z</updated>
  371.    <author>
  372.      <name>tegan.ali@octopus.com, Octopus Deploy</name>
  373.    </author>
  374.    <link href="https://octopus.com/blog/octopus-datadog-integration" />
  375.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-06/octopus-datadog-integration/img-blog-datadog-octopus-integration-2025.png" alt="Octopus and Datadog logos connected by plugs with little stars around the connection." /&gt;&lt;/p&gt;
  376.  
  377. &lt;p&gt;Octopus is a best-of-breed platform that provides Continuous Delivery at scale and integrates with all your tools across the software delivery pipeline. Datadog is the best-of-breed monitoring platform that monitors, secures, and provides alerts for all the tools in your DevOps stack. This includes infrastructure monitoring, application performance, and software delivery pipelines.&lt;/p&gt;
  378.  
  379. &lt;p&gt;Now, with the Octopus Datadog integration, it's even easier to use Octopus and Datadog together.&lt;/p&gt;
  380.  
  381. &lt;p&gt;The Octopus Datadog integration monitors Octopus deployments through the Datadog Agent. This gives customers using Datadog and Octopus visibility across their entire CI/CD pipeline, helping you correlate data, to find and solve issues faster.&lt;/p&gt;
  382.  
  383. &lt;p&gt;In this post, we introduce the Octopus Datadog integration. We explain how it helps orchestrate the insights from all your tools and connect the dots when something goes wrong.&lt;/p&gt;
  384.  
  385. &lt;h2 id="the-need-for-better-observability-across-your-entire-pipeline"&gt;The need for better observability across your entire pipeline&lt;/h2&gt;
  386.  
  387. &lt;p&gt;Without robust monitoring in place, it’s challenging to get visibility across your entire CI/CD pipeline and connect problems with the issues that caused them. Sometimes you don’t even have access to all the systems in your stack.&lt;/p&gt;
  388.  
  389. &lt;p&gt;For teams using Kubernetes, you might get an alert when an issue arises, but often you won’t have access to the Kubernetes cluster. You're left making guesses and assumptions based on what changed.&lt;/p&gt;
  390.  
  391. &lt;p&gt;If you’re using legacy systems, it’s a struggle to debug your systems when few, if any, people on the team have in-depth knowledge about them anymore. Plugins fall out of date, and performance and reliability begin to wane, so issues arise more often. It can take days to find and fix problems. This has flow-on effects for other work, like urgent security patches, and slows down releases, affecting due dates.&lt;/p&gt;
  392.  
  393. &lt;p&gt;Modern tools and practices are better designed to prevent issues from occurring and make troubleshooting easier, but it’s still difficult to get visibility across your entire CI/CD pipeline without an observability tool. We also know that many organizations are modernizing over time, so they rely on a mix of modern and heritage technologies. Luckily, both Datadog and Octopus provide best-of-breed solutions for monitoring and delivering software at scale, regardless of technology.&lt;/p&gt;
  394.  
  395. &lt;h2 id="monitoring-and-observability-in-octopus"&gt;Monitoring and observability in Octopus&lt;/h2&gt;
  396.  
  397. &lt;p&gt;Octopus already provides great visibility into all your deployments on our dashboards. You can see the stage, environment, and state of each deployment across multiple repositories in one place. You can also dive into the details of your projects and releases from the bird's-eye view of your dashboard.&lt;/p&gt;
  398.  
  399. &lt;p&gt;This year, we strengthened our observability and monitoring with &lt;a href="https://octopus.com/blog/kubernetes-live-object-status"&gt;Kubernetes Live Object Status&lt;/a&gt;, which gives you real-time updates about the state of your applications running on Kubernetes. You can:&lt;/p&gt;
  400.  
  401. &lt;ul&gt;
  402. &lt;li&gt;Get the live status of your applications on the main and project dashboards.&lt;/li&gt;
  403. &lt;li&gt;Get the list of all deployed objects and their live status.&lt;/li&gt;
  404. &lt;li&gt;Review object events, logs, and manifests running in a cluster.&lt;/li&gt;
  405. &lt;li&gt;Compare the applied (desired) and live (currently running) manifests for any Kubernetes object.&lt;/li&gt;
  406. &lt;/ul&gt;
  407.  
  408. &lt;p&gt;Octopus's &lt;a href="https://octopus.com/docs/insights"&gt;DevOps Insights&lt;/a&gt; uses DORA metrics to tell you exactly how you're performing, so you can find areas for improvement in your deployment processes.&lt;/p&gt;
  409.  
  410. &lt;h2 id="why-use-octopus-and-datadog-together"&gt;Why use Octopus and Datadog together?&lt;/h2&gt;
  411.  
  412. &lt;p&gt;While Octopus provides visibility and monitoring for your deployments at scale, it can be hard to correlate data across the entirety of your CI/CD pipeline when things happen in systems outside your deployment pipeline.&lt;/p&gt;
  413.  
  414. &lt;p&gt;That’s where Datadog helps. It monitors everything in your stack, covering all infrastructure, systems, apps, and services in one place.&lt;/p&gt;
  415.  
  416. &lt;p&gt;Used together, Octopus and Datadog become part of your world-class pipeline, with both tools supporting software at scale and integrating with any technology. You get a single pane of glass for monitoring, making it easier to track, visualize, and improve key metrics across all projects.&lt;/p&gt;
  417.  
  418. &lt;h2 id="better-observability-and-faster-recovery"&gt;Better observability and faster recovery&lt;/h2&gt;
  419.  
  420. &lt;p&gt;The new Octopus Datadog integration makes it easy for Datadog to collect metrics from Octopus so you can centralize your monitoring.&lt;/p&gt;
  421.  
  422. &lt;p&gt;For DevOps and platform engineers, you can track the performance of your teams’ pipelines and visualize key metrics across all projects in one place.&lt;/p&gt;
  423.  
  424. &lt;p&gt;For site reliability engineers (SREs) and operations folks, the Octopus Datadog integration lets you monitor your applications running in production. You can see logs, detect issues fast, and debug issues with critical context to resolve them quickly.&lt;/p&gt;
  425.  
  426. &lt;p&gt;If you’re deploying to Kubernetes but don’t have access to the Kubernetes cluster, you can check the status in Octopus using Kubernetes Live Object Status. Using both Octopus and Datadog, you can see what’s broken, then easily redeploy in Octopus using &lt;a href="https://octopus.com/docs/runbooks"&gt;runbooks&lt;/a&gt; to roll back or forward.&lt;/p&gt;
  427.  
  428. &lt;p&gt;If you’re using heritage systems, Datadog monitors those, too, and provides alerts so you can find issues fast. You can easily redeploy in Octopus to fix configuration values that teams sometimes change directly. Octopus also lets you restart web servers quickly and reliably with runbooks.&lt;/p&gt;
  429.  
  430. &lt;h2 id="how-the-integration-works"&gt;How the integration works&lt;/h2&gt;
  431.  
  432. &lt;p&gt;The Octopus Datadog integration monitors Octopus deployments through the Datadog Agent.&lt;/p&gt;
  433.  
  434. &lt;p&gt;The Datadog Agent collects:&lt;/p&gt;
  435.  
  436. &lt;ul&gt;
  437. &lt;li&gt;Metrics used for performance monitoring, like average deployment time per environment, and deployment failure rate for a project.&lt;/li&gt;
  438. &lt;li&gt;Deployment logs, which are useful for debugging failed deployments.&lt;/li&gt;
  439. &lt;li&gt;Server logs, which provide diagnostic information about the Octopus server.&lt;/li&gt;
  440. &lt;/ul&gt;
  441.  
  442. &lt;p&gt;After the integration is set up to send data to Datadog, you can use out-of-the-box dashboards to get an overview of each deployment by project. Build monitors alert you of notable events, like a failed deployment, so you can take action promptly. Octopus's &lt;a href="https://octopus.com/docs/security/users-and-teams/auditing/audit-stream#configure-audit-stream"&gt;audit log stream&lt;/a&gt; can further enrich this data, which you can combine within Datadog for more insights.&lt;/p&gt;
  443.  
  444. &lt;h2 id="see-the-integration-in-action"&gt;See the integration in action&lt;/h2&gt;
  445.  
  446. &lt;iframe width="560" height="315" src="https://www.youtube.com/embed/3Ct0Kuvj6NI?si=Zvt1bcSi60mSdtpd" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen&gt;&lt;/iframe&gt;
  447.  
  448. &lt;h2 id="who-can-use-the-integration"&gt;Who can use the integration&lt;/h2&gt;
  449.  
  450. &lt;p&gt;The integration is available to any Octopus and Datadog customers with &lt;a href="https://www.datadoghq.com/dg/enterprise/it-infrastructure-monitoring/" rel="nofollow"&gt;Datadog’s Infrastructure Monitoring&lt;/a&gt;.&lt;/p&gt;
  451.  
  452. &lt;p&gt;The metrics sent from the integration, the dashboard, and the monitors, are all standard as part of the integration. (Logs collected from the integration are subject to &lt;a href="https://docs.datadoghq.com/account_management/billing/pricing/#log-management" rel="nofollow"&gt;logs pricing with Datadog&lt;/a&gt;.)&lt;/p&gt;
  453.  
  454. &lt;p&gt;To set up the Octopus Datadog integration, &lt;a href="https://docs.datadoghq.com/integrations/octopus_deploy/" rel="nofollow"&gt;follow the simple instructions provided by Datadog&lt;/a&gt;.&lt;/p&gt;
  455.  
  456. &lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt;
  457.  
  458. &lt;p&gt;Datadog is a best-of-breed monitoring and observability platform, letting you see inside any stack, any app, at any scale, anywhere. When integrated with Octopus as a best-of-breed Continuous Delivery platform, you get world-class observability and CD that let you find problems fast, recover rapidly, and deliver software quickly and reliably at scale.&lt;/p&gt;
  459.  
  460. &lt;p&gt;If you're already using both Octopus and Datadog, you can set up the integration by following the &lt;a href="https://docs.datadoghq.com/integrations/octopus_deploy/" rel="nofollow"&gt;instructions in Datadog's docs&lt;/a&gt;.&lt;/p&gt;
  461.  
  462. &lt;p&gt;If you're a Datadog customer interested in using Octopus for your Continuous Delivery, you can &lt;a href="https://octopus.com/start"&gt;sign up for a free Octopus trial&lt;/a&gt; or &lt;a href="https://octopus.com/lp/schedule-a-demo"&gt;request a demo&lt;/a&gt;.&lt;/p&gt;
  463.  
  464. &lt;p&gt;You can also see the Octopus Datadog integration in action by visiting us at DASH, Datadog’s annual observability conference, in New York City, June 10–11, 2025. We’ll be at booth S-7.&lt;/p&gt;
  465.  
  466. &lt;p&gt;Happy deployments!&lt;/p&gt;
  467. </content>
  468.  </entry>
  469.  <entry>
  470.    <id>https://octopus.com/blog/terraform-provider-release</id>
  471.    <title type="text">V1.0 release of the Octopus Deploy Terraform Provider</title>
  472.    <published>2025-06-04T14:00:00Z</published>
  473.    <updated>2025-06-02T08:05:04.7310873Z</updated>
  474.    <author>
  475.      <name>venkatesh.vasudevan@octopus.com, Octopus Deploy</name>
  476.    </author>
  477.    <link href="https://octopus.com/blog/terraform-provider-release" />
  478.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-06/terraform-provider-release/img-terraform-provider-2025.png" alt="Terraform branded crane lifting an Octopus branded box." /&gt;&lt;/p&gt;
  479.  
  480. &lt;p&gt;The Octopus Deploy Terraform Provider has officially reached version 1.0. This release introduces expanded capabilities, fixes long-standing bugs, and provides improved documentation.&lt;/p&gt;
  481.  
  482. &lt;p&gt;In this post, I take you through the key updates and features included in this release.&lt;/p&gt;
  483.  
  484. &lt;h2 id="expanded-terraform-provider-capabilities"&gt;Expanded Terraform Provider capabilities&lt;/h2&gt;
  485.  
  486. &lt;p&gt;Version 1.0 brings substantial improvements to managing Octopus Deploy resources through Terraform. Earlier versions of the Provider lacked support for creating all resource types available in the Octopus UI. We addressed this limitation, enabling comprehensive resource management directly from Terraform. While we support most resources now, there are still a few exclusions. These are intentional and thoroughly &lt;a href="https://registry.terraform.io/providers/OctopusDeploy/octopusdeploy/latest/docs" rel="nofollow"&gt;documented&lt;/a&gt; for transparency.&lt;/p&gt;
  487.  
  488. &lt;h2 id="clearer-documentation-with-practical-examples"&gt;Clearer documentation with practical examples&lt;/h2&gt;
  489.  
  490. &lt;p&gt;For a better user experience, we updated the &lt;a href="https://registry.terraform.io/providers/OctopusDeploy/octopusdeploy/latest/docs" rel="nofollow"&gt;documentation&lt;/a&gt; to include detailed examples and best practices for using the Terraform Provider effectively. We outlined 5 key scenarios to guide you. The documentation found at &lt;a href="https://registry.terraform.io/providers/OctopusDeploy/octopusdeploy/latest/docs" rel="nofollow"&gt;the Terraform registry&lt;/a&gt; now also has examples for all data sources and resources.&lt;/p&gt;
  491.  
  492. &lt;h2 id="bug-fixes-and-improvements"&gt;Bug fixes and improvements&lt;/h2&gt;
  493.  
  494. &lt;p&gt;We resolved several long-standing bugs in this release. This improves the Provider and ensures a more stable and reliable experience.&lt;/p&gt;
  495.  
  496. &lt;ul&gt;
  497. &lt;li&gt;New deployment process resource: We made it easier to define and manage deployment processes by making each step its own resource. We also introduced a step order resource so you can easily manage the deployment process step order. You can find out more info on how it works in the &lt;a href="https://registry.terraform.io/providers/OctopusDeploy/octopusdeploy/latest/docs" rel="nofollow"&gt;official docs&lt;/a&gt;.&lt;/li&gt;
  498. &lt;li&gt;Migration to Terraform framework: Transitioning from the Terraform SDK to the framework has improved safety, reliability, and adaptability for future updates.&lt;/li&gt;
  499. &lt;li&gt;Adoption of semantic versioning (SemVer): The Provider now adheres strictly to SemVer principles. This helps you manage version changes more predictably.&lt;/li&gt;
  500. &lt;/ul&gt;
  501.  
  502. &lt;h2 id="migration-guidance"&gt;Migration guidance&lt;/h2&gt;
  503.  
  504. &lt;p&gt;As this is a major version release, some breaking changes may require updates to existing configurations. To help with this transition, we have a &lt;a href="https://registry.terraform.io/providers/OctopusDeploy/octopusdeploy/latest/docs" rel="nofollow"&gt;comprehensive migration guide&lt;/a&gt;. Please review it carefully before upgrading your environments.&lt;/p&gt;
  505.  
  506. &lt;h3 id="provider-migrated-to-octopus-deploy-repository"&gt;Provider migrated to Octopus Deploy repository&lt;/h3&gt;
  507.  
  508. &lt;p&gt;The Terraform Provider has always lived in our OctopusDeployLabs repository, which signalled that it was an experimental integration. We decided to move it to our &lt;a href="https://github.com/octopusdeploy" rel="nofollow"&gt;official repository&lt;/a&gt;, elevating it as a core integration.&lt;/p&gt;
  509.  
  510. &lt;h2 id="version-controlled-projects-and-the-terraform-provider"&gt;Version-controlled projects and the Terraform Provider&lt;/h2&gt;
  511.  
  512. &lt;p&gt;We observed customers using Terraform and version control together to manage their projects and runbooks. While they're both powerful tools, combining them led to unexpected behaviours that can break instances.&lt;/p&gt;
  513.  
  514. &lt;p&gt;To ensure stability, we’re taking a clear stance: from version 1.0 onwards, you can manage your Octopus projects or runbooks using &lt;em&gt;either&lt;/em&gt; version control or Terraform—but not both.&lt;/p&gt;
  515.  
  516. &lt;p&gt;If you try to manage a version-controlled project or runbook with Terraform, the Provider will return an error. We designed this change to protect your instance and ensure predictable behavior when managing your Octopus instance.&lt;/p&gt;
  517.  
  518. &lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt;
  519.  
  520. &lt;p&gt;The v1.0 release solidifies the Octopus Deploy Terraform Provider as a robust tool for managing your Octopus instance as code. By simplifying resource management and improving documentation, teams can work more efficiently with the Terraform provider&lt;/p&gt;
  521.  
  522. &lt;p&gt;For detailed information on all changes and enhancements, please &lt;a href="https://registry.terraform.io/providers/OctopusDeploy/octopusdeploy/latest/docs" rel="nofollow"&gt;read the docs&lt;/a&gt; or visit the Terraform registry page for the Provider.&lt;/p&gt;
  523.  
  524. &lt;p&gt;Happy deployments!&lt;/p&gt;
  525. </content>
  526.  </entry>
  527.  <entry>
  528.    <id>https://octopus.com/blog/new-leadership-code</id>
  529.    <title type="text">Our new leadership code</title>
  530.    <published>2025-05-28T14:00:00Z</published>
  531.    <updated>2025-05-27T01:41:21.1030452Z</updated>
  532.    <author>
  533.      <name>orli.remez@octopus.com, Octopus Deploy</name>
  534.    </author>
  535.    <link href="https://octopus.com/blog/new-leadership-code" />
  536.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-05/new-leadership-code/img-blog-leadership-code-2025.png" alt="Stylized image of people scaling a rock in the clouds, helping each other up, with 2 people at the top" /&gt;&lt;/p&gt;
  537.  
  538. &lt;p&gt;Octopus has changed a lot in the past few years. We’ve grown to over 300 people, now spread across 17 countries and time zones. A year ago, we joined forces with Codefresh, and we’re still finding our rhythm as we bring together different ways of working, cultures, and perspectives.&lt;/p&gt;
  539.  
  540. &lt;p&gt;Our managers reflect this diversity—different backgrounds, different strengths, and different approaches. And while that makes us stronger, it also makes leadership more complex. We’re moving fast, navigating change daily, and building the plane as we fly it.&lt;/p&gt;
  541.  
  542. &lt;p&gt;In the midst of this momentum, we realized something important: to stay grounded in who we are and focused on where we’re headed, we needed a shared foundation. A way to align on what great leadership looks like &lt;em&gt;here&lt;/em&gt;, &lt;em&gt;now&lt;/em&gt;, at Octopus.&lt;/p&gt;
  543.  
  544. &lt;p&gt;Enter: the Leadership CODE.&lt;/p&gt;
  545.  
  546. &lt;p&gt;Octopus was founded with a philosophy of creating a working environment where employees can &lt;a href="https://octopus.com/company/careers"&gt;do the best work of their lives&lt;/a&gt;, and our leaders are key in maintaining and strengthening this culture in the face of our growth and development. As time went by, we understood we were missing a framework to help them do that, so we put our heads together to come up with our new Leadership CODE. The process of its creation was much more meaningful than I had expected, so we're excited to share its story with you.&lt;/p&gt;
  547.  
  548. &lt;h2 id="the-leadership-code-concept"&gt;The Leadership CODE concept&lt;/h2&gt;
  549.  
  550. &lt;p&gt;There are countless leadership behaviors and skills out there, and just like with values, none are inherently wrong. But part of leading well is knowing how to focus. As we grow and evolve as a company, we recognize the need to align on the &lt;em&gt;core&lt;/em&gt; leadership principles that matter most right now, at this particular stage in our journey.&lt;/p&gt;
  551.  
  552. &lt;p&gt;That’s what inspired the Leadership CODE. Our idea was to create a simple, concrete, and actionable guide to help leaders at Octopus balance delivering on ambitious goals while staying deeply committed to their people and to our values.&lt;/p&gt;
  553.  
  554. &lt;p&gt;The CODE isn’t meant to capture every great leadership trait—it’s a purposeful selection of the principles we believe leaders should &lt;strong&gt;embrace and model today&lt;/strong&gt;, to help us scale thoughtfully, collaborate effectively, and stay true to what makes Octopus special.&lt;/p&gt;
  555.  
  556. &lt;p&gt;In essence, the CODE serves as a shared leadership language. It helps us set clear expectations, strengthen consistency across teams, and support each other as we tackle tough challenges. It’s also a way to reflect our values in how we lead every day—intentionally, and together.&lt;/p&gt;
  557.  
  558. &lt;h2 id="how-we-built-it"&gt;How we built it&lt;/h2&gt;
  559.  
  560. &lt;p&gt;Creating the Leadership CODE was as meaningful as the outcome itself. We started by gathering insights from across the organization—through surveys and interviews with all managers and senior leaders—to uncover what makes leadership successful at Octopus. Leading themes we found were humility, trust, and clear communication, alongside the need to foster contagious energy and leadership by example.&lt;/p&gt;
  561.  
  562. &lt;p&gt;After we analyzed the data, we focused on  defining principles that could act as a shared leadership vocabulary  to promote the themes we discovered. These practices focused on effective communication,  aligning on priorities, and modeling the behaviors we want to see across the organization. This shared language, our CODE, is the basis for building trust, breaking down silos, and enabling collaboration.&lt;/p&gt;
  563.  
  564. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-05/new-leadership-code/code-process.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-05/new-leadership-code/code-process.png' class="img-fluid center" alt='Leadership code process' /&gt;&lt;/a&gt;&lt;/p&gt;
  565.  
  566. &lt;h2 id="the-code"&gt;The CODE&lt;/h2&gt;
  567.  
  568. &lt;p&gt;Our CODE relies on 5 guiding principles:&lt;/p&gt;
  569.  
  570. &lt;ul&gt;
  571. &lt;li&gt;Be humble and stay curious&lt;/li&gt;
  572. &lt;li&gt;Level up the team&lt;/li&gt;
  573. &lt;li&gt;Communicate directly, and with anyone&lt;/li&gt;
  574. &lt;li&gt;Aim for the greater good&lt;/li&gt;
  575. &lt;li&gt;Make it happen&lt;/li&gt;
  576. &lt;/ul&gt;
  577.  
  578. &lt;p&gt;Each principle is more than just a statement—it’s a call to action. When we set out to define these, we didn’t just want to say &lt;em&gt;what good leadership looks like&lt;/em&gt;. We also felt it was equally important to clarify &lt;em&gt;what it doesn’t look like&lt;/em&gt;.&lt;/p&gt;
  579.  
  580. &lt;p&gt;This was intentional. In fast-moving environments like ours, ambiguity can lead to misalignment. So we wanted to provide more clarity, not in the form of rigid rules, but as &lt;strong&gt;guidance leaders can interpret thoughtfully for themselves&lt;/strong&gt;. These are starting points, not the full story. We trust our leaders to bring their own judgment and experience to the table.&lt;/p&gt;
  581.  
  582. &lt;h3 id="be-humble-and-stay-curious"&gt;Be humble and stay curious&lt;/h3&gt;
  583.  
  584. &lt;p&gt;Leadership means staying open—open to learning, to being wrong, and to hearing perspectives different from your own. It’s about listening thoughtfully, admitting when you don’t have all the answers, and being willing to adapt.&lt;/p&gt;
  585.  
  586. &lt;p&gt;What it means:&lt;/p&gt;
  587.  
  588. &lt;ul&gt;
  589. &lt;li&gt;You actively listen and ask thoughtful questions.&lt;/li&gt;
  590. &lt;li&gt;You admit when you don’t know something and seek help.&lt;/li&gt;
  591. &lt;li&gt;You embrace change and adapt as you learn.&lt;/li&gt;
  592. &lt;/ul&gt;
  593.  
  594. &lt;p&gt;What it doesn’t mean:&lt;/p&gt;
  595.  
  596. &lt;ul&gt;
  597. &lt;li&gt;Getting stuck in endless exploration without making progress.&lt;/li&gt;
  598. &lt;li&gt;Using curiosity as a shield to avoid decisions.&lt;/li&gt;
  599. &lt;li&gt;Blindly accepting others’ ideas without critical thinking.&lt;/li&gt;
  600. &lt;/ul&gt;
  601.  
  602. &lt;h3 id="level-up-the-team"&gt;Level up the team&lt;/h3&gt;
  603.  
  604. &lt;p&gt;At Octopus, great leaders grow great people. It’s about empowering others, building their confidence, and setting them up to thrive. You lead by example, support experimentation, and share in the team’s success.&lt;/p&gt;
  605.  
  606. &lt;p&gt;What it means:&lt;/p&gt;
  607.  
  608. &lt;ul&gt;
  609. &lt;li&gt;You care about your team’s growth—both personally and professionally.&lt;/li&gt;
  610. &lt;li&gt;You walk the talk by modeling the standards you expect from others.&lt;/li&gt;
  611. &lt;li&gt;You trust your team to own their work and support them in their endeavors.&lt;/li&gt;
  612. &lt;/ul&gt;
  613.  
  614. &lt;p&gt;What it doesn’t mean:&lt;/p&gt;
  615.  
  616. &lt;ul&gt;
  617. &lt;li&gt;Micromanaging or stepping in unnecessarily.&lt;/li&gt;
  618. &lt;li&gt;Abandoning your team under the guise of trust.&lt;/li&gt;
  619. &lt;li&gt;Needing to have all the answers yourself.&lt;/li&gt;
  620. &lt;/ul&gt;
  621.  
  622. &lt;h3 id="communicate-directly-and-with-anyone"&gt;Communicate directly, and with anyone&lt;/h3&gt;
  623.  
  624. &lt;p&gt;We believe communication is a leadership superpower. It’s not just about speaking clearly—it’s about creating space for honest dialogue, listening with intent, and maintaining transparency at every level.&lt;/p&gt;
  625.  
  626. &lt;p&gt;What it means:&lt;/p&gt;
  627.  
  628. &lt;ul&gt;
  629. &lt;li&gt;You speak and listen openly, clearly, and respectfully.&lt;/li&gt;
  630. &lt;li&gt;You ask for and give honest feedback on a regular basis.&lt;/li&gt;
  631. &lt;li&gt;You’re transparent about challenges and work collaboratively to address them.&lt;/li&gt;
  632. &lt;/ul&gt;
  633.  
  634. &lt;p&gt;What it doesn’t mean:&lt;/p&gt;
  635.  
  636. &lt;ul&gt;
  637. &lt;li&gt;Being harsh or blunt under the guise of honesty.&lt;/li&gt;
  638. &lt;li&gt;Using feedback to criticize instead of constructively build.&lt;/li&gt;
  639. &lt;li&gt;Tuning out opinions you disagree with.&lt;/li&gt;
  640. &lt;/ul&gt;
  641.  
  642. &lt;h3 id="aim-for-the-greater-good"&gt;Aim for the greater good&lt;/h3&gt;
  643.  
  644. &lt;p&gt;Leadership isn’t about ego—it’s about making an impact that benefits everyone. We lead in service of our team, our customers, and our overall mission. Great leaders look beyond personal accolades and focus on the bigger picture.&lt;/p&gt;
  645.  
  646. &lt;p&gt;What it means:&lt;/p&gt;
  647.  
  648. &lt;ul&gt;
  649. &lt;li&gt;You prioritize the collective success of the team and company over personal recognition.&lt;/li&gt;
  650. &lt;li&gt;You collaborate effectively toward shared goals.&lt;/li&gt;
  651. &lt;li&gt;You act with unwavering integrity at all times.&lt;/li&gt;
  652. &lt;/ul&gt;
  653.  
  654. &lt;p&gt;What it doesn’t mean:&lt;/p&gt;
  655.  
  656. &lt;ul&gt;
  657. &lt;li&gt;Burning yourself out for the team.&lt;/li&gt;
  658. &lt;li&gt;Ignoring the value of personal wins.&lt;/li&gt;
  659. &lt;li&gt;Dismissing the importance of small progress—it all counts.&lt;/li&gt;
  660. &lt;/ul&gt;
  661.  
  662. &lt;h3 id="make-it-happen"&gt;Make it happen&lt;/h3&gt;
  663.  
  664. &lt;p&gt;Leaders at Octopus drive real impact. We don’t just talk about ideas—we turn plans into action. Our approach is about taking ownership, making decisive choices, and moving with purpose to deliver results.&lt;/p&gt;
  665.  
  666. &lt;p&gt;What it means:&lt;/p&gt;
  667.  
  668. &lt;ul&gt;
  669. &lt;li&gt;You own your outcomes and see your initiatives through to completion.&lt;/li&gt;
  670. &lt;li&gt;You make smart, timely decisions that align with our company goals.&lt;/li&gt;
  671. &lt;li&gt;You bring enthusiasm and focus to tackle challenges head-on.&lt;/li&gt;
  672. &lt;/ul&gt;
  673.  
  674. &lt;p&gt;What it doesn’t mean:&lt;/p&gt;
  675.  
  676. &lt;ul&gt;
  677. &lt;li&gt;Rushing into decisions without a clear plan.&lt;/li&gt;
  678. &lt;li&gt;Taking on too much and risking burnout.&lt;/li&gt;
  679. &lt;li&gt;Engaging in busy work that lacks tangible impact.&lt;/li&gt;
  680. &lt;/ul&gt;
  681.  
  682. &lt;h2 id="whats-next"&gt;What’s next?&lt;/h2&gt;
  683.  
  684. &lt;p&gt;Creating the CODE was only the beginning. We now have a lot of work to embed these principles into daily leadership practices. This includes:&lt;/p&gt;
  685.  
  686. &lt;ul&gt;
  687. &lt;li&gt;Mentor and provide feedback to the company leaders on following the CODE.&lt;/li&gt;
  688. &lt;li&gt;When assessing potential new leaders, understand if they can embrace the CODE and embody its principles.&lt;/li&gt;
  689. &lt;li&gt;Challenging ourselves as leaders by regularly reflecting on our actions and identifying ways to better support our people and the company.&lt;/li&gt;
  690. &lt;li&gt;Fostering a culture of accountability, where feedback is a two-way conversation and leaders at all levels strive to improve continuously.&lt;/li&gt;
  691. &lt;/ul&gt;
  692.  
  693. &lt;p&gt;By making the CODE central to how we hire, develop, and assess leaders, we aim to build a leadership culture that supports our people and drives Octopus toward its long-term goals.&lt;/p&gt;
  694.  
  695. &lt;h2 id="reflections"&gt;Reflections&lt;/h2&gt;
  696.  
  697. &lt;p&gt;This journey reinforced my belief that leadership is  a collaborative effort. By defining and sharing our expectations, we set our leaders up for success and create a culture where everyone can thrive.&lt;/p&gt;
  698.  
  699. &lt;p&gt;Whether you’re a leader yourself or aspire to become one, my advice is simple: take the time to define what leadership means to you personally. It’s one of the most impactful ways to ensure alignment, growth, and success.&lt;/p&gt;
  700.  
  701. &lt;p&gt;If you’re curious to learn more about Octopus and how we’re building our future, stay tuned for more stories from our People team.&lt;/p&gt;
  702.  
  703. &lt;h2 id="watch-our-leadership-code-video"&gt;Watch our Leadership CODE video&lt;/h2&gt;
  704.  
  705. &lt;p&gt;Watch our Leadership CODE video with Octopus's leaders, below. You'll also find a section on the &lt;a href="https://handbook.octopus.com/getting-oriented/leadership-code" rel="nofollow"&gt;Leadership CODE in our public handbook&lt;/a&gt;.&lt;/p&gt;
  706.  
  707. &lt;iframe width="560" height="315" src="https://www.youtube.com/embed/eZ4COGt5Gwk?si=1TDQyGyH0dE2TZ7y" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen&gt;&lt;/iframe&gt;
  708.  
  709. &lt;p&gt;Happy deployments!&lt;/p&gt;
  710. </content>
  711.  </entry>
  712.  <entry>
  713.    <id>https://octopus.com/blog/what-gitops-changes-about-elevated-access</id>
  714.    <title type="text">What GitOps changes about elevated access</title>
  715.    <published>2025-05-26T14:00:00Z</published>
  716.    <updated>2025-05-26T02:25:26.6478411Z</updated>
  717.    <author>
  718.      <name>matthew.allford@octopus.com, Octopus Deploy</name>
  719.    </author>
  720.    <link href="https://octopus.com/blog/what-gitops-changes-about-elevated-access" />
  721.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-05/what-gitops-changes-about-elevated-access/blogimage-whatisgitops-2025.png" alt="Person holds magnifying glass over GitOps logo, surrounded by icons for declarative, versioned and immutable, pulled automatically, and continuously reconciled." /&gt;&lt;/p&gt;
  722.  
  723. &lt;p&gt;Recently, we surveyed the industry to gain insights into the adoption and challenges of real-world GitOps, with the results forming the &lt;a href="https://octopus.com/publications/state-of-gitops-report"&gt;State of GitOps report&lt;/a&gt;. While reviewing the trends and results, the data around one key finding jumped out at me:&lt;/p&gt;
  724.  
  725. &lt;blockquote class="blockquote"&gt;
  726. &lt;p&gt;GitOps reduces elevated access&lt;/p&gt;
  727. &lt;/blockquote&gt;
  728.  
  729. &lt;p&gt;Overall, 66% of respondents agreed. Among organizations with higher GitOps maturity, agreement rose to 77%, but interestingly, there was also a slight increase in disagreement among the highest performers.&lt;/p&gt;
  730.  
  731. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-05/what-gitops-changes-about-elevated-access/gitops-reduces-elevated-access.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-05/what-gitops-changes-about-elevated-access/gitops-reduces-elevated-access.png' class="img-fluid center" alt='Bar chart showing responses to ‘GitOps reduces elevated access’ across groups with different GitOps maturity scores.' /&gt;&lt;/a&gt;&lt;/p&gt;
  732.  
  733. &lt;p&gt;So, does GitOps change or reduce the need for elevated environment access, and should it?&lt;/p&gt;
  734.  
  735. &lt;h2 id="how-gitops-shifts-access-away-from-infrastructure"&gt;How GitOps shifts access away from infrastructure&lt;/h2&gt;
  736.  
  737. &lt;p&gt;The 4 GitOps principles encourage you to avoid manually logging into environments and performing tasks. The goal is to manage system state declaratively through version-controlled configuration and apply those states automatically using reconciliation agents.&lt;/p&gt;
  738.  
  739. &lt;p&gt;If fully embraced, GitOps agents continuously observe the system state, correcting any drift by reapplying the desired state defined in version control. Continuous reconciliation discourages manual changes and automatically reverses them if they occur.&lt;/p&gt;
  740.  
  741. &lt;p&gt;In traditional operations teams, access to systems with SSH or tools like kubectl is common, but operating in a mature GitOps model should make these break-glass exceptions.&lt;/p&gt;
  742.  
  743. &lt;p&gt;Most survey respondents agree that GitOps should reduce the need for privileged production access by replacing hands-on changes with declarative, auditable workflows.&lt;/p&gt;
  744.  
  745. &lt;h2 id="rethinking-what-elevated-access-means-with-gitops"&gt;Rethinking what elevated access means with GitOps&lt;/h2&gt;
  746.  
  747. &lt;p&gt;So why might some respondents to the survey disagree that embracing GitOps reduces elevated access?&lt;/p&gt;
  748.  
  749. &lt;p&gt;At lower maturity levels, teams may treat Git as a safe, developer-focused system. But as Git becomes the source of truth for managing production infrastructure and applications, a key question emerges:&lt;/p&gt;
  750.  
  751. &lt;blockquote class="blockquote"&gt;
  752. &lt;p&gt;If a developer can change a manifest in Git for a production environment, does that emulate elevated access?&lt;/p&gt;
  753. &lt;/blockquote&gt;
  754.  
  755. &lt;p&gt;In a GitOps model, Git becomes the control plane, meaning write access to a production configuration in Git, especially with automatic reconciliation, becomes a form of production access.&lt;/p&gt;
  756.  
  757. &lt;p&gt;High performers likely consider GitOps secure when configuring repositories well and implementing mature environment promotion workflows. However, Git isn't the only sensitive surface in GitOps architecture. You must also secure the reconciliation controller and supporting workflow or promotion tooling with the same level of rigor. Together, these systems form the modern delivery pipeline and deserve the same access scrutiny once reserved for direct infrastructure.&lt;/p&gt;
  758.  
  759. &lt;p&gt;High performers likely aren't ignoring or rejecting GitOps' security benefits, but instead acknowledge that you must treat Git itself as a sensitive operational boundary now more than ever. It's now one of several critical control points in the delivery process that need strict governance.&lt;/p&gt;
  760.  
  761. &lt;p&gt;Interestingly, these same high performers agreed that GitOps reduces overall elevated access. So, the takeaway isn't contradiction; it's maturity. High-performing teams see GitOps as secure only when Git, the reconciliation controller, and supporting environment progression tooling are all treated as critical access points, with the appropriate controls in place.&lt;/p&gt;
  762.  
  763. &lt;h2 id="handling-exceptions-to-the-gitops-model"&gt;Handling exceptions to the GitOps model&lt;/h2&gt;
  764.  
  765. &lt;p&gt;In the early stages of adopting GitOps, it's common for DevOps engineers, platform engineers, and even developers to rely on familiar tools like &lt;code&gt;kubectl&lt;/code&gt; to inspect or tweak clusters and applications directly. Especially in learning environments and environments early in the deployment process, like dev, this is precisely what they'll do. This approach lets them rely on familiar tools while gaining confidence in GitOps practices.&lt;/p&gt;
  766.  
  767. &lt;p&gt;The ultimate goal is for nobody to have direct access to production environments, even if read-only.&lt;/p&gt;
  768.  
  769. &lt;p&gt;In the &lt;a href="https://octopus.com/publications/state-of-gitops-report"&gt;State of GitOps report&lt;/a&gt;, we surfaced 6 core practices of GitOps:&lt;/p&gt;
  770.  
  771. &lt;ul&gt;
  772. &lt;li&gt;Declarative desired state&lt;/li&gt;
  773. &lt;li&gt;Human-readable format&lt;/li&gt;
  774. &lt;li&gt;Responsive code review&lt;/li&gt;
  775. &lt;li&gt;Version control&lt;/li&gt;
  776. &lt;li&gt;Automatic pull&lt;/li&gt;
  777. &lt;li&gt;Continuous reconciliation&lt;/li&gt;
  778. &lt;/ul&gt;
  779.  
  780. &lt;p&gt;You won't embrace all of these GitOps practices on day one, and that's ok. As we learned from the DevOps movement, embracing a GitOps infrastructure and application delivery approach involves continuous improvement, learning, tweaking, and time.&lt;/p&gt;
  781.  
  782. &lt;p&gt;With that said, even at high maturity levels with GitOps where you implement many or all of the practices, there may still be valid scenarios where folks need elevated access. For example, emergency responses (break-glass scenarios) or debugging complex or unreproducible issues.&lt;/p&gt;
  783.  
  784. &lt;p&gt;In these cases, it's crucial to have:&lt;/p&gt;
  785.  
  786. &lt;ul&gt;
  787. &lt;li&gt;Break-glass procedures. Documented steps for requesting, granting, and revoking temporary access. These should include automated expiration, require multi-party approval, and be used only in exceptional circumstances.&lt;/li&gt;
  788. &lt;li&gt;Audit trails. You must log every access event, recording who accessed and changed what, when, and why.&lt;/li&gt;
  789. &lt;li&gt;Controlled suspension of reconciliation. Sometimes, you must temporarily disable the GitOps agent to prevent it from overwriting a manual change made during incident response. You should log and time-bound this suspension, and include procedures to reconcile safely afterward.&lt;/li&gt;
  790. &lt;li&gt;Post-incident recovery. After manual intervention, have a defined process for reconciling the system back to the desired state, committing required changes to Git, and re-enabling automatic reconciliation.&lt;/li&gt;
  791. &lt;/ul&gt;
  792.  
  793. &lt;p&gt;These situations should be rare. Ideally, releases have already passed through multiple environments that closely mirror production in both infrastructure and configuration. If you experience an issue where you find your developers or engineers need to access environments directly, after the issue gets resolved, question why. Could they have achieved the same outcome by using other systems and tooling? Is there an element of education and training required? Is there a need to implement supplementary tooling or processes to help troubleshoot and resolve issues that surface after deployment? Work on fixing it, and implementing that fix in your process so it doesn't occur again.&lt;/p&gt;
  794.  
  795. &lt;p&gt;Releasing to production shouldn't be a production.&lt;/p&gt;
  796.  
  797. &lt;h2 id="the-evolving-access-conversation"&gt;The evolving access conversation&lt;/h2&gt;
  798.  
  799. &lt;p&gt;GitOps won't immediately eliminate the need for you to have a process for elevated production access, but it should help make it an exception rather than a routine operation. You must treat Git and GitOps tooling with the same care and control as production infrastructure. The fundamentals still apply; they apply in more places and different places than you're used to.&lt;/p&gt;
  800.  
  801. &lt;p&gt;As you mature your GitOps adoption, the conversation shifts from &amp;quot;do we still need access?&amp;quot; to &amp;quot;are we securing the new access surface and tooling?&amp;quot;.&lt;/p&gt;
  802.  
  803. &lt;p&gt;Happy deployments!&lt;/p&gt;
  804. </content>
  805.  </entry>
  806.  <entry>
  807.    <id>https://octopus.com/blog/design-journey-kubernetes-live-status</id>
  808.    <title type="text">The surprising design journey behind Kubernetes Live Object Status</title>
  809.    <published>2025-05-21T14:00:00Z</published>
  810.    <updated>2025-05-20T06:36:23.3548478Z</updated>
  811.    <author>
  812.      <name>kirsten.schwarzer@octopus.com, Octopus Deploy</name>
  813.    </author>
  814.    <link href="https://octopus.com/blog/design-journey-kubernetes-live-status" />
  815.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-05/design-journey-kubernetes-live-status/img-blog-design-journey-kubernetes-live-status.png" alt="Stylized image of a designer thinking about the Kubernetes live status interface." /&gt;&lt;/p&gt;
  816.  
  817. &lt;p&gt;For the past 2 years, we've been talking to customers about their biggest headaches when deploying to Kubernetes.&lt;/p&gt;
  818.  
  819. &lt;p&gt;A recurring theme has been the challenge of knowing what’s actually happening with your applications at any given moment.&lt;/p&gt;
  820.  
  821. &lt;p&gt;With Kubernetes, things can change unexpectedly. A Pod might go down, your cluster could run out of resources, or something might break even though your deployment was successful. When this happens, our users would need to look for information in other tools or use commands like &lt;code&gt;kubectl logs&lt;/code&gt; to diagnose what went wrong.&lt;/p&gt;
  822.  
  823. &lt;p&gt;But most developers aren't Kubernetes experts and don't feel confident using &lt;code&gt;kubectl&lt;/code&gt;. They often have to wait for a platform team with specialized Kubernetes knowledge, leading to frustrating delays. Platform teams can get stuck in firefighting mode and lose valuable time for more strategic projects.&lt;/p&gt;
  824.  
  825. &lt;p&gt;With these challenges in mind, we aimed to create a tool for developers to troubleshoot their Kubernetes applications.&lt;/p&gt;
  826.  
  827. &lt;p&gt;Here’s how we designed Kubernetes Live Object Status and how a few unexpected discoveries shaped our choices.&lt;/p&gt;
  828.  
  829. &lt;h2 id="integrating-versus-separating-live-status"&gt;Integrating versus separating live status&lt;/h2&gt;
  830.  
  831. &lt;p&gt;The first big choice was whether to create separate dashboards for live status or integrate it into our existing dashboards. We used low-fidelity wireframes to explore both options and get early feedback from Octopus leaders.&lt;/p&gt;
  832.  
  833. &lt;p&gt;Ultimately, we didn't want to create a separate space for Kubernetes. Our users often have many different applications they want to see on a single screen.&lt;/p&gt;
  834.  
  835. &lt;p&gt;We decided to let you toggle between live and deployment status on your main Octopus dashboard. To improve usability, your preference gets saved in the browser for your next visit.&lt;/p&gt;
  836.  
  837. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-05/design-journey-kubernetes-live-status/live-status-main-dashboard.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-05/design-journey-kubernetes-live-status/live-status-main-dashboard.png' class="img-fluid center" alt='Octopus main dashboard' /&gt;&lt;/a&gt;&lt;/p&gt;
  838.  
  839. &lt;p&gt;Integrating live status into existing dashboards lets us extend it to other types of applications in future. While that's not currently on our roadmap, we'd love to hear if it’s something you'd find useful.&lt;/p&gt;
  840.  
  841. &lt;h2 id="using-established-status-indicators"&gt;Using established status indicators&lt;/h2&gt;
  842.  
  843. &lt;p&gt;Instead of creating new status indicators, we started with existing statuses from Argo CD, a popular open-source Kubernetes tool. We knew that we had an upcoming project to integrate with Argo CD and leveraging its statuses would let us integrate more seamlessly.&lt;/p&gt;
  844.  
  845. &lt;p&gt;However, we had to make a few modifications to fit the Octopus model. Our team added extra statuses for applications because Octopus deployments determine the Kubernetes desired state. After a successful deployment, we compare the desired state with the live status to determine if an application is out of sync.&lt;/p&gt;
  846.  
  847. &lt;p&gt;We also decided to combine the Argo CD sync and health status to simplify it for users.&lt;/p&gt;
  848.  
  849. &lt;p&gt;We ended up with 2 sets of live statuses, one for applications and one for Kubernetes objects.&lt;/p&gt;
  850.  
  851. &lt;h2 id="evolving-with-user-feedback"&gt;Evolving with user feedback&lt;/h2&gt;
  852.  
  853. &lt;p&gt;During the first few weeks of EAP, we encountered an issue where customers saw out-of-sync more often than they expected. It turns out that resources can regularly be out of sync for reasons that aren't actually important.&lt;/p&gt;
  854.  
  855. &lt;p&gt;We quickly realised that we needed to separate sync status from health status instead of combining them.&lt;/p&gt;
  856.  
  857. &lt;p&gt;Our first instinct was to simplify the experience, but that's the reality of building real software—once it's out in the wild and customers start using it, you realize there's complexity for a reason.&lt;/p&gt;
  858.  
  859. &lt;p&gt;Our team did a quick pivot to separate health status from sync status for both applications and objects.&lt;/p&gt;
  860.  
  861. &lt;p&gt;You can &lt;a href="https://octopus.com/docs/kubernetes/live-object-status#application-status"&gt;read our documentation&lt;/a&gt; to explore the updated status model.&lt;/p&gt;
  862.  
  863. &lt;p&gt;We also introduced a setting that prioritizes health status on the dashboards as a default. We’re planning extra work in this space to give users more granular control and better visibility of both statuses.&lt;/p&gt;
  864.  
  865. &lt;p&gt;This surprising lesson is a great example of why we try to ship early and get customer feedback as soon as possible. It’s something you can’t easily test or replicate with a prototype and a usability study.&lt;/p&gt;
  866.  
  867. &lt;h2 id="adding-a-new-live-status-page"&gt;Adding a new live status page&lt;/h2&gt;
  868.  
  869. &lt;p&gt;In addition to the dashboards, we created a dedicated live status page for each project, environment, and tenant combination. This gives you an easily shareable link for a specific application that you can bookmark or share with your team.&lt;/p&gt;
  870.  
  871. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-05/design-journey-kubernetes-live-status/live-status-sync-health-status.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-05/design-journey-kubernetes-live-status/live-status-sync-health-status.png' class="img-fluid center" alt='Live status page with sync and health status' /&gt;&lt;/a&gt;&lt;/p&gt;
  872.  
  873. &lt;h2 id="choosing-the-object-visualization"&gt;Choosing the object visualization&lt;/h2&gt;
  874.  
  875. &lt;p&gt;We considered multiple ways to visualize your Kubernetes objects and key information about them.&lt;/p&gt;
  876.  
  877. &lt;p&gt;Some tools use flow-style diagrams to show the hierarchy and relationships between objects. But this approach, while visually appealing in demos, can get very messy and hard to read at scale. It was important to consider what this would look like with hundreds or even thousands of objects.&lt;/p&gt;
  878.  
  879. &lt;p&gt;That's why we opted for a tree grid, which gives us the best of both worlds. It lets us show information with high density, so even if you have many objects, it's still easy to scan. You can also use the advanced filters panel to reduce the list to objects with specific states and kinds. And it still shows the relationship between objects through hierarchical expanders.&lt;/p&gt;
  880.  
  881. &lt;h2 id="diagnosing-object-issues"&gt;Diagnosing object issues&lt;/h2&gt;
  882.  
  883. &lt;p&gt;The key to creating a single place to troubleshoot is to provide enough information to find the cause without needing to switch between tools.&lt;/p&gt;
  884.  
  885. &lt;p&gt;During a usability study for this feature, we asked users to troubleshoot an application, starting from the main dashboard. Those were the only instructions they received.&lt;/p&gt;
  886.  
  887. &lt;p&gt;Users immediately navigated to the live status page and looked for events and logs without any extra prompting. This was surprising to a few of us, but not to our team’s Senior Cloud Engineer, who had spent years debugging Kubernetes issues himself.&lt;/p&gt;
  888.  
  889. &lt;p&gt;The usability study made us realize that events and logs were key capabilities we needed to deliver on this feature's promise.&lt;/p&gt;
  890.  
  891. &lt;p&gt;When viewing the live status page, you can now click on an object’s name to get more details. This action opens a drawer with 4 tabs:&lt;/p&gt;
  892.  
  893. &lt;ul&gt;
  894. &lt;li&gt;Summary&lt;/li&gt;
  895. &lt;li&gt;Events&lt;/li&gt;
  896. &lt;li&gt;Logs&lt;/li&gt;
  897. &lt;li&gt;Manifest&lt;/li&gt;
  898. &lt;/ul&gt;
  899.  
  900. &lt;h2 id="interacting-with-kubernetes-logs-and-events"&gt;Interacting with Kubernetes logs and events&lt;/h2&gt;
  901.  
  902. &lt;p&gt;Kubernetes events can be quite verbose, so we wanted to make it easy to find the issue you're looking for. It was important to add filters based on the type of event, especially if you're only looking for warnings.&lt;/p&gt;
  903.  
  904. &lt;p&gt;The event row shows a snippet of the message to make it easily scannable. But we also have an expandable element that lets you read the full message and see the first and last seen dates.&lt;/p&gt;
  905.  
  906. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-05/design-journey-kubernetes-live-status/live-kubernetes-events.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-05/design-journey-kubernetes-live-status/live-kubernetes-events.png' class="img-fluid center" alt='Kubernetes events drawer' /&gt;&lt;/a&gt;&lt;/p&gt;
  907.  
  908. &lt;p&gt;The engineers on our team felt strongly that it was important to deliver a great experience interacting with logs. We added a few nice touches, like highlighting a row when you hover over it and including toggles for:&lt;/p&gt;
  909.  
  910. &lt;ul&gt;
  911. &lt;li&gt;Showing the previous container&lt;/li&gt;
  912. &lt;li&gt;Timestamp visibility&lt;/li&gt;
  913. &lt;li&gt;Line wrapping&lt;/li&gt;
  914. &lt;/ul&gt;
  915.  
  916. &lt;p&gt;We opted to keep things simple for refresh behaviour and give users more granular control.&lt;/p&gt;
  917.  
  918. &lt;p&gt;Because the logs are live, we didn't want things to move and scroll while you were looking at them. We decided to provide a refresh button you can use to update the logs without unexpected behaviour.&lt;/p&gt;
  919.  
  920. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-05/design-journey-kubernetes-live-status/live-kubernetes-logs.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-05/design-journey-kubernetes-live-status/live-kubernetes-logs.png' class="img-fluid center" alt='Kubernetes logs drawer' /&gt;&lt;/a&gt;&lt;/p&gt;
  921.  
  922. &lt;p&gt;A small but significant design choice, championed by the engineers on our team, was using a monospace font. This differentiates the actual machine output from the rest of the Octopus interface.&lt;/p&gt;
  923.  
  924. &lt;p&gt;We wanted users to know that this was the raw output from their cluster and that they could trust it.&lt;/p&gt;
  925.  
  926. &lt;h2 id="inspecting-and-comparing-manifests"&gt;Inspecting and comparing manifests&lt;/h2&gt;
  927.  
  928. &lt;p&gt;On the Manifest tab, you can see the YAML currently running in your cluster and compare it to your last deployment.&lt;/p&gt;
  929.  
  930. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-05/design-journey-kubernetes-live-status/live-manifest-diff.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-05/design-journey-kubernetes-live-status/live-manifest-diff.png' class="img-fluid center" alt='Kubernetes live manifest diff' /&gt;&lt;/a&gt;&lt;/p&gt;
  931.  
  932. &lt;p&gt;You’ll notice the diff view looks quite similar to other developer tools you've used before. That's on purpose.&lt;/p&gt;
  933.  
  934. &lt;p&gt;The fourth heuristic of &lt;a href="https://www.nngroup.com/articles/consistency-and-standards/" rel="nofollow"&gt;Jakob Nielsen’s ten usability heuristics&lt;/a&gt; is to maintain consistency and adhere to standards. We worked from the assumption that our users spend more time in other tools than they spend using Octopus.&lt;/p&gt;
  935.  
  936. &lt;p&gt;This means there are conventions from other tools that our users have already gotten used to. Instead of making you learn a new way to do things, we tried to incorporate existing patterns from popular tools you interact with daily.&lt;/p&gt;
  937.  
  938. &lt;p&gt;That's exactly what we did with the design for diffs.&lt;/p&gt;
  939.  
  940. &lt;h2 id="a-surprisingly-useful-addition-the-deployment-timeline"&gt;A surprisingly useful addition: The deployment timeline&lt;/h2&gt;
  941.  
  942. &lt;p&gt;We originally created the deployment timeline to simplify navigation between Octopus deployments and the live status page.&lt;/p&gt;
  943.  
  944. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-05/design-journey-kubernetes-live-status/deployment-timeline.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-05/design-journey-kubernetes-live-status/deployment-timeline.png' class="img-fluid center" alt='Deployment timeline' /&gt;&lt;/a&gt;&lt;/p&gt;
  945.  
  946. &lt;p&gt;After sharing a mockup in our internal Slack, Paul Stovell, our CEO, commented that we should add a redeploy button to it. That would let you quickly roll back to a previous successful release if you see an issue with the live status. That’s how we (accidentally) designed a feature that helps close the loop from diagnosing an issue to actually fixing it.&lt;/p&gt;
  947.  
  948. &lt;p&gt;This project had many interesting twists and turns, but my favorite has to be the surprising usefulness of the deployment timeline.&lt;/p&gt;
  949.  
  950. &lt;p&gt;Being able to diagnose an issue is helpful, but redeploying and seeing your application running again takes it a step further. Empowering developers to fix their own apps is exactly why we built Kubernetes Live Object Status.&lt;/p&gt;
  951.  
  952. &lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt;
  953.  
  954. &lt;p&gt;I hope this post has given you a fun behind-the-scenes look at how we design new features at Octopus.&lt;/p&gt;
  955.  
  956. &lt;p&gt;We talk to customers, try out different solutions, test them, and release small iterations so we can get feedback quickly.&lt;/p&gt;
  957.  
  958. &lt;p&gt;Sometimes, we learn unexpected lessons when our features get used in the real world, and sometimes, serendipity leads to a great idea.&lt;/p&gt;
  959.  
  960. &lt;h3 id="how-to-get-kubernetes-live-object-status"&gt;How to get Kubernetes live object status&lt;/h3&gt;
  961.  
  962. &lt;p&gt;If you’ve used the feature and have feedback to share, please send us a message in the #kubernetes channel in our &lt;a href="https://oc.to/CommunitySlack" rel="nofollow"&gt;Community Slack&lt;/a&gt;. We’d love to hear from you.&lt;/p&gt;
  963.  
  964. &lt;p&gt;If you haven't tried it out yet, you can install the latest version of the Kubernetes agent. It includes the Octopus Kubernetes monitor, which gets live status from the cluster.&lt;/p&gt;
  965.  
  966. &lt;p&gt;Happy deployments!&lt;/p&gt;
  967. </content>
  968.  </entry>
  969.  <entry>
  970.    <id>https://octopus.com/blog/automatic-rollbacks-last-resort</id>
  971.    <title type="text">Automatic rollbacks are a last resort</title>
  972.    <published>2025-05-15T14:00:00Z</published>
  973.    <updated>2025-05-15T08:29:01.8123494Z</updated>
  974.    <author>
  975.      <name>steve.fenton@octopus.com, Octopus Deploy</name>
  976.    </author>
  977.    <link href="https://octopus.com/blog/automatic-rollbacks-last-resort" />
  978.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-05/automatic-rollbacks-last-resort/blogimage-modernrollbackstratgies-2023.png" alt="4 release boxes labelled 1.1 to 1.4, the 3rd with a green tick, 4th on fire with a red cross. A rocket travels back from 1.4 to 1.3." /&gt;&lt;/p&gt;
  979.  
  980. &lt;p&gt;People often say they want the ability to roll back software automatically when something goes wrong. This sounds simple enough, but there aren't many scenarios where an automatic rollback is desirable.&lt;/p&gt;
  981.  
  982. &lt;p&gt;Many causes of deployment failures will also prevent a rollback. For example, if a credential has expired preventing part of the deployment, this will also fail during the rollback process. Someone may also need to make decisions based on what operations succeeded before the deployment stopped, like changes to database state.&lt;/p&gt;
  983.  
  984. &lt;p&gt;There are 3 insights from modern software delivery that all contribute to the fall from grace of automatic rollbacks:&lt;/p&gt;
  985.  
  986. &lt;ul&gt;
  987. &lt;li&gt;We have a better understanding of resilience in our sociotechnical systems&lt;/li&gt;
  988. &lt;li&gt;Continuous Delivery makes it easier to roll forward&lt;/li&gt;
  989. &lt;li&gt;Progressive delivery provides better mechanisms&lt;/li&gt;
  990. &lt;/ul&gt;
  991.  
  992. &lt;h2 id="the-role-of-resilience"&gt;The role of resilience&lt;/h2&gt;
  993.  
  994. &lt;p&gt;One of the crucial ideas from the Lean movement is that automation is improved if there are mechanisms to halt operation and ask for human intervention, instead of continuing automatic operation. This was termed &lt;em&gt;autonomation&lt;/em&gt;, or automation with a human touch.&lt;/p&gt;
  995.  
  996. &lt;p&gt;Although automatic rollbacks sound like something that would make your software more reliable, this is a situation where resilience is needed. Resilience is something humans excel in.&lt;/p&gt;
  997.  
  998. &lt;p&gt;To put it another way, you can plan-in a certain level of robustness to your deployment process. For example, you could test credentials before starting the deployment. Each time you discover a new kind of failure, you can learn from it and improve how it's handled. For all the things you haven't thought of, resilience is required.&lt;/p&gt;
  999.  
  1000. &lt;p&gt;Human-driven resilience provides the crucial knowledge needed to improve robustness. Organizations that flag the problem to a human end up with an appropriate resolution to the issue at hand, and knowledge of how to make the system more robust. Automatically rolling back removes this opportunity to learn, as conditions for observing the problem may have been lost.&lt;/p&gt;
  1001.  
  1002. &lt;h2 id="continuous-delivery-fewer-bugs-and-faster-recovery"&gt;Continuous Delivery: Fewer bugs and faster recovery&lt;/h2&gt;
  1003.  
  1004. &lt;p&gt;If rollbacks are a priority in your organization, it's likely a signal that you're missing crucial technical practices. Working in small batches is made possible by frequently committing changes to the main branch so they can be automatically validated. This increases confidence that the new software version is deployable.&lt;/p&gt;
  1005.  
  1006. &lt;p&gt;The longer you practice Continuous Delivery, the more robust your deployment pipeline becomes. Additionally, if something does slip through, you can quickly roll forward to a new software version that has a fix (and some new tests that stop it from happening again). This is very different from using an expedited process for an urgent fix. Continuous Delivery lets you use the standard process for all changes, because it's already swift.&lt;/p&gt;
  1007.  
  1008. &lt;p&gt;Most bugs you encounter in a Continuous Delivery process aren't critical. There may be an edge case you missed, some scenario that you might not decide to support, or cosmetic issues. Normal feedback cycles can handle these. When a change is more urgent, you can still resolve it by deploying a new software version.&lt;/p&gt;
  1009.  
  1010. &lt;p&gt;Continuous Delivery progresses the same build artifact through each environment, and it includes validation steps to make sure the software works to the extent you have defined tests. The deployment process itself is being tested at least as often as the software, because you're using the same automated process to deploy to pre-production environments.&lt;/p&gt;
  1011.  
  1012. &lt;p&gt;This means the kind of problems you encounter will be transient issues or unexpected events. Let's get those to an expert.&lt;/p&gt;
  1013.  
  1014. &lt;h2 id="progressive-delivery-provides-better-strategies"&gt;Progressive delivery provides better strategies&lt;/h2&gt;
  1015.  
  1016. &lt;p&gt;Progressive delivery techniques include deployment strategies, like blue/green and canary deployments, and feature flags.&lt;/p&gt;
  1017.  
  1018. &lt;p&gt;Deployment strategies include mechanisms to verify the software. Blue/green deployments provide a failback option, and canary deployments let you pause the rollout to limit the impact of an issue. Feature flags take this a step further by providing a runtime mechanism to switch features on and off, or swap feature implementations.&lt;/p&gt;
  1019.  
  1020. &lt;h2 id="the-last-resort"&gt;The last resort&lt;/h2&gt;
  1021.  
  1022. &lt;p&gt;Rollbacks don't always return you to a previous system state. They can return you to a state you've never tested or operated before. The software version may have been tested, but not with your current database or other dependencies. What other software has moved forward that may no longer be compatible with the previous version?&lt;/p&gt;
  1023.  
  1024. &lt;p&gt;Redeploying a previous software version should be a last resort, and it ought to have human supervision as there may be many other knock-on effects of moving in reverse. You may fix a bug only to re-open a security vulnerability, or revert to a software version that isn't compatible with the current database schema or some crucial API.&lt;/p&gt;
  1025.  
  1026. &lt;p&gt;When you use modern software engineering practices like Continuous Delivery, modern deployment strategies, and feature flags, the appeal of automatic rollbacks is greatly diminished. Bringing human resilience to play results in the creation of increasingly robust systems for testing, deployment, and operation of software.&lt;/p&gt;
  1027.  
  1028. &lt;p&gt;You can read more about this in the white paper, &lt;a href="https://octopus.com/whitepapers/modern-deployment-and-rollback-strategies"&gt;Modern deployment and rollback strategies&lt;/a&gt; by Bob Walker. It provides advice on the architectural patterns that support better deployments, the trade-offs of different approaches, and how to select the right approach.&lt;/p&gt;
  1029.  
  1030. &lt;p&gt;Happy deployments!&lt;/p&gt;
  1031. </content>
  1032.  </entry>
  1033.  <entry>
  1034.    <id>https://octopus.com/blog/financial-industry-compliance</id>
  1035.    <title type="text">Financial industry compliance, the DevOps way</title>
  1036.    <published>2025-04-30T14:00:00Z</published>
  1037.    <updated>2025-05-02T07:19:31.6340815Z</updated>
  1038.    <author>
  1039.      <name>steve.fenton@octopus.com, Octopus Deploy</name>
  1040.    </author>
  1041.    <link href="https://octopus.com/blog/financial-industry-compliance" />
  1042.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-04/financial-industry-compliance/blog-img-fsi-2025-1500x800.png" alt="Building with three pillars and dollar symbol surrounded by icons that represent security and compliance." /&gt;&lt;/p&gt;
  1043.  
  1044. &lt;p&gt;If you work in the financial industry, you know there can sometimes be a high burden of regulation. This is understandable when you consider the risk of financial loss and how it can impact people's lives. But if you don't take the right approach to compliance, it can become a time and energy leak that threatens your ability to compete in the market.&lt;/p&gt;
  1045.  
  1046. &lt;p&gt;The best compliance teams look for ways to protect the organization and its customers from risk without overburdening teams with bureaucratic procedures. You want compliance set to maximum, and the ability to deliver high-quality, valuable software set to maximum. You don't want some compromise between the two.&lt;/p&gt;
  1047.  
  1048. &lt;h2 id="good-compliance-sounds-like-devops"&gt;Good compliance sounds like DevOps&lt;/h2&gt;
  1049.  
  1050. &lt;p&gt;If you know DevOps, this will sound familiar. Traditional managers saw software delivery as a compromise between throughput (creating and improving software features) and stability (keeping everything working). They measured developers on throughput and ops teams on stability, then wondered why there was so much conflict between them.&lt;/p&gt;
  1051.  
  1052. &lt;p&gt;Just as the solution to the software delivery problem was to align both teams to the shared goal of throughput and stability, you must do the same with other desirable system qualities, like security and compliance.&lt;/p&gt;
  1053.  
  1054. &lt;p&gt;Rather than calling this DevSecOps or DevSecCompOps, we can call it DevOps because everything that relates to software fitness is part of DevOps.&lt;/p&gt;
  1055.  
  1056. &lt;p&gt;The non-DevOps way is for stability to be an afterthought and compliance to be an ominous late reaction to an upcoming audit. The DevOps way is to make these part of the daily work, automate as much as possible, and deliver the outcome of compliance instead of the frantic output of audit theater.&lt;/p&gt;
  1057.  
  1058. &lt;p&gt;It's about being safe and secure, not looking safe and secure.&lt;/p&gt;
  1059.  
  1060. &lt;h2 id="compliance-automation"&gt;Compliance automation&lt;/h2&gt;
  1061.  
  1062. &lt;p&gt;You can approach compliance by copying what other organizations are doing. Most organizations have a spreadsheet with obliquely referenced requirements that developers are regularly asked to update and evidence. Who doesn't love an ORG-05.15-ACCESS-CONTROL line item in a spreadsheet?&lt;/p&gt;
  1063.  
  1064. &lt;p&gt;However, the best compliance teams I've worked with took a different approach. They spent more time educating developers like me about the reasons for these requirements so we could find ways to satisfy them, collect evidence, and keep customers safe.&lt;/p&gt;
  1065.  
  1066. &lt;p&gt;This meant we considered compliance needs when writing features, selecting tools, or changing our process. When we looked at tools for builds, deployments, and monitoring, ease of meeting compliance needs and automation of evidence collection were part of the buying decision.&lt;/p&gt;
  1067.  
  1068. &lt;p&gt;This isn't just about making audits easy; it's about making compliance easy, and it's about making the desired outcomes of compliance more likely. Your toolchain can do much of the heavy lifting, leaving you to show and tell during an audit while listening out for opportunities to make things even better.&lt;/p&gt;
  1069.  
  1070. &lt;h2 id="how-octopus-supports-easy-compliance"&gt;How Octopus supports easy compliance&lt;/h2&gt;
  1071.  
  1072. &lt;p&gt;Octopus has many features that ease your compliance burden and increase safety, from enterprise-grade access controls and audit trails to innovative automation. Let's take a quick tour of some crucial compliance features:&lt;/p&gt;
  1073.  
  1074. &lt;ul&gt;
  1075. &lt;li&gt;Role-based access control&lt;/li&gt;
  1076. &lt;li&gt;Extensive audit trails&lt;/li&gt;
  1077. &lt;li&gt;IT service management integrations&lt;/li&gt;
  1078. &lt;li&gt;Octolint&lt;/li&gt;
  1079. &lt;li&gt;Runbooks&lt;/li&gt;
  1080. &lt;/ul&gt;
  1081.  
  1082. &lt;h3 id="role-based-access-control"&gt;Role-based access control&lt;/h3&gt;
  1083.  
  1084. &lt;p&gt;Octopus Deploy has fine-grained role-based access controls (RBAC) that integrate with single sign-on (SSO) providers. You can define roles and permissions to control who can change deployment processes, runbooks, and other configurations. You can also define who can access the automation for different projects and environments.&lt;/p&gt;
  1085.  
  1086. &lt;p&gt;You can use RBAC to prevent unauthorized changes and enforce segregation of duties. You can also safely create self-service actions, like letting testers deploy to the test environment or clear a web cache to speed up their testing without giving them more extensive permissions.&lt;/p&gt;
  1087.  
  1088. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-04/financial-industry-compliance/role-based-access.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-04/financial-industry-compliance/role-based-access.png' class="img-fluid center" alt='A list of built-in user roles.' /&gt;&lt;/a&gt;&lt;/p&gt;
  1089.  
  1090. &lt;h3 id="extensive-audit-trail"&gt;Extensive audit trail&lt;/h3&gt;
  1091.  
  1092. &lt;p&gt;Octopus automatically captures a detailed audit log for all significant system events. This includes deployments, configuration changes, user access events, and more. Octopus records every action that changes a state, including who initiated it.&lt;/p&gt;
  1093.  
  1094. &lt;p&gt;These tamper-resistant audit logs let you demonstrate the changes made to applications or infrastructure. When you need to delve into the audit trail, it's easy to filter actions by user or by a specific area in Octopus, like spaces, projects, environments, event types, and more.&lt;/p&gt;
  1095.  
  1096. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-04/financial-industry-compliance/audit-trail.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-04/financial-industry-compliance/audit-trail.png' class="img-fluid center" alt='The audit trail screen shows recent changes, deployments, and runbook runs and has filters to easily find what you need.' /&gt;&lt;/a&gt;&lt;/p&gt;
  1097.  
  1098. &lt;h3 id="it-service-management-integrations"&gt;IT service management integrations&lt;/h3&gt;
  1099.  
  1100. &lt;p&gt;Our integrations with ServiceNow and Jira Service Management remove manual hand-offs between Octopus and your IT service management (ITSM) platform. This makes it easy to ensure changes have the appropriate approval before progressing.&lt;/p&gt;
  1101.  
  1102. &lt;p&gt;The integrations automatically create change requests associated with a deployment. You can block deployments until the change gets approved. This increases compliance, as no unapproved changes get deployed to production—but it does so without creating toil for the developers.&lt;/p&gt;
  1103.  
  1104. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-04/financial-industry-compliance/approval-flow.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-04/financial-industry-compliance/approval-flow.png' class="img-fluid center" alt='When a protected environment is selected, the integration with ITSM tools is triggered and a change approval is created and linked. The deployment continues when the change is approved in the ITSM tool.' /&gt;&lt;/a&gt;&lt;/p&gt;
  1105.  
  1106. &lt;h3 id="octolint"&gt;Octolint&lt;/h3&gt;
  1107.  
  1108. &lt;p&gt;Octolint is a tool that scans your Octopus instance and recommends improvements to your setup. It detects potential issues such as perpetual API keys, shared Git user names, and unused deployment targets.&lt;/p&gt;
  1109.  
  1110. &lt;p&gt;Instead of manually auditing for good practices, Octolint can automatically scan and report on items that need your attention.&lt;/p&gt;
  1111.  
  1112. &lt;pre&gt;&lt;code class="language-text"&gt;[OctoLintDefaultProjectGroupChildCount] The default project group contains 79 projects. You may want to organize these projects into additional project groups.
  1113. [OctoLintEmptyProject] The following projects have no runbooks and no deployment process: Azure Octopus test
  1114. [OctoLintTooManySteps] The following projects have 20 or more steps: K8s Yaml Import 2
  1115. &lt;/code&gt;&lt;/pre&gt;
  1116.  
  1117. &lt;h3 id="runbooks"&gt;Runbooks&lt;/h3&gt;
  1118.  
  1119. &lt;p&gt;Financial institutions need good plans for both daily operations and emergencies. Octopus Runbooks help with this. You can turn routine and emergency operations tasks into reusable automations for things like:&lt;/p&gt;
  1120.  
  1121. &lt;ul&gt;
  1122. &lt;li&gt;Database maintenance&lt;/li&gt;
  1123. &lt;li&gt;Restarting systems&lt;/li&gt;
  1124. &lt;li&gt;Applying urgent fixes&lt;/li&gt;
  1125. &lt;li&gt;Recovering backed-up data&lt;/li&gt;
  1126. &lt;/ul&gt;
  1127.  
  1128. &lt;p&gt;Automated runbooks are safer and more reliable, reducing the need for broad distribution of elevated access. Runbooks in Octopus also log changes and runs to the standard Octopus audit trail. You can also use runbooks to automate compliance tasks like recovery testing, audit reporting, or probing firewall ports.&lt;/p&gt;
  1129.  
  1130. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-04/financial-industry-compliance/operations-overview.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-04/financial-industry-compliance/operations-overview.png' class="img-fluid center" alt='A list of runbooks that have been triggered and whether they succeeded.' /&gt;&lt;/a&gt;&lt;/p&gt;
  1131.  
  1132. &lt;h2 id="octopus-loves-compliance"&gt;Octopus loves compliance&lt;/h2&gt;
  1133.  
  1134. &lt;p&gt;Octopus has many features that reduce the compliance burden and help you build security, privacy, and compliance into your DevOps process. As an organization, Octopus also maintains compliance with ISO 27001:2013, SOC 2 Type II, and SOC 3 with regular third-party audits and technical assessments for security, safety, and privacy. You can find out more about this in our &lt;a href="https://trust.octopus.com/" rel="nofollow"&gt;trust center&lt;/a&gt;.&lt;/p&gt;
  1135.  
  1136. &lt;p&gt;Tools that reduce the compliance burden are crucial to organizations in the financial industry or other regulated and safety-critical environments. Your toolchain can help maintain innovation and compliance just like it brings you throughput and stability.&lt;/p&gt;
  1137.  
  1138. &lt;p&gt;Happy deployments!&lt;/p&gt;
  1139. </content>
  1140.  </entry>
  1141.  <entry>
  1142.    <id>https://octopus.com/blog/oidc-external-feeds</id>
  1143.    <title type="text">OpenID Connect authentication for external feeds</title>
  1144.    <published>2025-04-28T14:00:00Z</published>
  1145.    <updated>2025-04-28T05:57:04.6523446Z</updated>
  1146.    <author>
  1147.      <name>grace.rehn@octopus.com, Octopus Deploy</name>
  1148.    </author>
  1149.    <link href="https://octopus.com/blog/oidc-external-feeds" />
  1150.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-04/oidc-external-feeds/generic-oidc-banner-img.png" alt="Keys on a keychain above a recycling bin." /&gt;&lt;/p&gt;
  1151.  
  1152. &lt;p&gt;We recently updated our external feeds to support OpenID Connect (OIDC) authentication.&lt;/p&gt;
  1153.  
  1154. &lt;p&gt;Octopus can now use OAuth 2.0 to access your container feeds. This means you won’t have to manage or rotate credentials manually. This includes OIDC support for AWS, Azure, and Google Container Registries (GCR).&lt;/p&gt;
  1155.  
  1156. &lt;p&gt;This is especially beneficial for AWS Elastic Container Registries (ECR), where authentication tokens expire after 12 hours. OIDC eliminates the need for stored access keys by generating fresh credentials at deployment time.&lt;/p&gt;
  1157.  
  1158. &lt;p&gt;This feature is now available for our Cloud customers and will be available to our self-hosted customers in June in Octopus 2025.2.&lt;/p&gt;
  1159.  
  1160. &lt;p&gt;In this post, I explain how OIDC external feeds work and how to set them up for each provider.&lt;/p&gt;
  1161.  
  1162. &lt;h2 id="why-use-oidc-external-feeds-in-octopus"&gt;Why use OIDC external feeds in Octopus?&lt;/h2&gt;
  1163.  
  1164. &lt;p&gt;Using OIDC with external feeds removes the need to store and rotate credentials. During deployment, Octopus requests short-lived credentials to authenticate with your container registry. This improves security and simplifies credential management.&lt;/p&gt;
  1165.  
  1166. &lt;p&gt;You can also customize the OIDC subject to include the space and feed. This helps enforce access control by ensuring tokens issued by Octopus are only valid for the intended feed and space. Here's an example subject claim: &lt;code&gt;space:default:feed:feed-name&lt;/code&gt;.&lt;/p&gt;
  1167.  
  1168. &lt;p&gt;For more information on generating subjects and OAuth flows, check out our &lt;a href="https://octopus.com/docs/infrastructure/accounts/openid-connect"&gt;OpenID Connect docs&lt;/a&gt;.&lt;/p&gt;
  1169.  
  1170. &lt;h2 id="aws-elastic-container-registry-ecr"&gt;AWS Elastic Container Registry (ECR)&lt;/h2&gt;
  1171.  
  1172. &lt;p&gt;You can now select OpenID Connect as an authentication method when setting up an AWS ECR feed in Octopus. This is a great fit if you want to avoid managing access keys and use short-lived credentials instead.&lt;/p&gt;
  1173.  
  1174. &lt;p&gt;To get started, create an IAM role with a trust policy that allows &lt;code&gt;sts:AssumeRoleWithWebIdentity&lt;/code&gt;. When configuring your OIDC external feed, you need to provide the Role ARN and Audience. Octopus uses these values to request temporary ECR credentials at deployment time.&lt;/p&gt;
  1175.  
  1176. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-04/oidc-external-feeds/aws-ecr-oidc-details.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-04/oidc-external-feeds/aws-ecr-oidc-details.png' class="img-fluid center" height="auto" width="500" alt='Screenshot of the AWS ECR OIDC Credentials form fields.' /&gt;&lt;/a&gt;&lt;/p&gt;
  1177.  
  1178. &lt;p&gt;If you're new to this setup, take a look at our &lt;a href="https://octopus.com/docs/packaging-applications/package-repositories/guides/container-registries/amazon-ec2-container-services#adding-an-aws-openid-connect-ecr-external-feed"&gt;AWS Elastic Container Registry docs&lt;/a&gt;.&lt;/p&gt;
  1179.  
  1180. &lt;h2 id="azure-container-registry-acr"&gt;Azure Container Registry (ACR)&lt;/h2&gt;
  1181.  
  1182. &lt;p&gt;OIDC is now supported for authentication with Azure Container Registry in Octopus. This removes the need for client secrets by using federated credentials instead.&lt;/p&gt;
  1183.  
  1184. &lt;p&gt;To set it up, create an app registration in Azure and add a federated credential. To configure your feed in Octopus, make sure to add the Client ID, Tenant ID, and Audience from your identity provider. Octopus uses these to request a token from Azure. This ensures it can securely authenticate with your container registry.&lt;/p&gt;
  1185.  
  1186. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-04/oidc-external-feeds/azure-oidc-details.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-04/oidc-external-feeds/azure-oidc-details.png' class="img-fluid center" height="auto" width="500" alt='Screenshot of the ACR OIDC Credentials form fields.' /&gt;&lt;/a&gt;&lt;/p&gt;
  1187.  
  1188. &lt;p&gt;For full setup instructions, check out our &lt;a href="https://octopus.com/docs/packaging-applications/package-repositories/guides/container-registries/azure-container-services#adding-an-azure-container-registry-with-openid-connect-as-an-octopus-external-feed"&gt;Azure Container Registry docs&lt;/a&gt;.&lt;/p&gt;
  1189.  
  1190. &lt;h2 id="google-container-registry-gcr"&gt;Google Container Registry (GCR)&lt;/h2&gt;
  1191.  
  1192. &lt;p&gt;Octopus now supports OIDC authentication for Google Container Registry via Workload Identity Federation. This means you no longer need to manage service account keys.&lt;/p&gt;
  1193.  
  1194. &lt;p&gt;Start by configuring a Workload Identity Pool and an OIDC provider in Google Cloud. Then, create a trust configuration. This links the subject and audience from Octopus to a Google service account. In Octopus, set up a GCR external feed and provide the Audience and the registry URL. Octopus uses these to exchange its token for temporary credentials during deployment.&lt;/p&gt;
  1195.  
  1196. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-04/oidc-external-feeds/google-oidc-details.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-04/oidc-external-feeds/google-oidc-details.png' class="img-fluid center" height="auto" width="500" alt='Screenshot of the GCR OIDC Credentials form fields.' /&gt;&lt;/a&gt;&lt;/p&gt;
  1197.  
  1198. &lt;p&gt;For more guidance, see our &lt;a href="https://octopus.com/docs/packaging-applications/package-repositories/guides/container-registries/google-container-registry#adding-an-openid-connect-google-container-registry-to-octopus"&gt;Google Container Registry docs&lt;/a&gt;.&lt;/p&gt;
  1199.  
  1200. &lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt;
  1201.  
  1202. &lt;p&gt;OIDC external feeds bring security and flexibility to your deployments by removing the need for static credentials. This method is consistent with modern cloud practices and gives you more control over your feeds. With support for AWS, Azure, and Google registries, Octopus makes it easy to integrate secure, token-based authentication into your pipelines.&lt;/p&gt;
  1203.  
  1204. &lt;p&gt;We hope you give it a try, and let us know what you think. If you have any questions or feedback, we’d love to hear from you in the comments below.&lt;/p&gt;
  1205.  
  1206. &lt;p&gt;Happy deployments!&lt;/p&gt;
  1207. </content>
  1208.  </entry>
  1209.  <entry>
  1210.    <id>https://octopus.com/blog/kubernetes-live-object-status</id>
  1211.    <title type="text">Introducing Kubernetes Live Object Status</title>
  1212.    <published>2025-04-16T14:00:00Z</published>
  1213.    <updated>2025-04-16T08:32:15.1625697Z</updated>
  1214.    <author>
  1215.      <name>nick.josevski@octopus.com, Octopus Deploy</name>
  1216.    </author>
  1217.    <link href="https://octopus.com/blog/kubernetes-live-object-status" />
  1218.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-04/kubernetes-live-object-status/kubernetes-live-object-status-2024-1500x800.png" alt="Stylized image of Kubernetes Live Object status in the Octopus UI showing a healthy status." /&gt;&lt;/p&gt;
  1219.  
  1220. &lt;p&gt;Kubernetes is rapidly becoming the dominant platform for hosting and running applications.&lt;/p&gt;
  1221.  
  1222. &lt;p&gt;At Octopus, we want to provide the best experience for deploying and monitoring your applications on Kubernetes.&lt;/p&gt;
  1223.  
  1224. &lt;p&gt;To make your deployments to Kubernetes simpler, faster, and safer, Octopus has a deployment target called the Kubernetes agent. The Kubernetes agent is a small, lightweight application you install into your Kubernetes cluster.&lt;/p&gt;
  1225.  
  1226. &lt;p&gt;Kubernetes Live Object Stataus—our Kubernetes monitor—is the next major expansion of this deployment agent's capabilities.&lt;/p&gt;
  1227.  
  1228. &lt;h2 id="post-deployment-monitoring"&gt;Post-deployment monitoring&lt;/h2&gt;
  1229.  
  1230. &lt;p&gt;Monitoring is an important part of the deployment process and is even more important for Kubernetes. It gives you confidence that your applications are running as expected.&lt;/p&gt;
  1231.  
  1232. &lt;p&gt;When troubleshooting an unhealthy app, you often need to use a combination of tools and login credentials to figure out what's going wrong. That can be quite fiddly, especially with Kubernetes. Your Octopus Deploy instance already has these credentials and awareness of your applications, similar to runbooks. We're aiming to make Octopus the first port of call as you and your team continuously deliver software.&lt;/p&gt;
  1233.  
  1234. &lt;p&gt;We roll up the combined status for the objects in a given release, per environment, into a single live status.&lt;/p&gt;
  1235.  
  1236. &lt;p&gt;&lt;figure&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-04/kubernetes-live-object-status/klos-project-view.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-04/kubernetes-live-object-status/klos-project-view.png' class="img-fluid" height="auto" width="500" alt='Project view with live status' /&gt;&lt;/a&gt;&lt;figcaption&gt;Project view with live status&lt;/figcaption&gt;&lt;/figure&gt;&lt;/p&gt;
  1237.  
  1238. &lt;h2 id="if-youre-already-using-the-kubernetes-agent"&gt;If you're already using the Kubernetes agent&lt;/h2&gt;
  1239.  
  1240. &lt;p&gt;If you already use the Kubernetes agent, your upgrade path will be simple.&lt;/p&gt;
  1241.  
  1242. &lt;h3 id="upgrading-your-agents-to-the-version-containing-the-monitor"&gt;Upgrading your agents to the version containing the monitor&lt;/h3&gt;
  1243.  
  1244. &lt;p&gt;We're working on a one-click upgrade process you can access in Octopus Deploy.&lt;/p&gt;
  1245.  
  1246. &lt;p&gt;If you can’t wait until then, you can upgrade existing Kubernetes agents by running a Helm command on your cluster. &lt;a href="https://octopus.com/docs/kubernetes/live-object-status/installation#upgrading-an-existing-kubernetes-agent"&gt;See our documentation for all the details&lt;/a&gt;.&lt;/p&gt;
  1247.  
  1248. &lt;h2 id="new-to-using-octopus-for-kubernetes-deployments"&gt;New to using Octopus for Kubernetes deployments?&lt;/h2&gt;
  1249.  
  1250. &lt;p&gt;After you install the agent, it registers itself with Octopus Server as a new deployment target. This lets you deploy your applications and manifests into that cluster, without the need for workers, external credentials, or custom tooling. All new installations of the agent will have the monitor enabled.&lt;/p&gt;
  1251.  
  1252. &lt;h3 id="installing-the-agent"&gt;Installing the agent&lt;/h3&gt;
  1253.  
  1254. &lt;p&gt;The Kubernetes agent gets packaged and installed via a Helm chart. This makes managing the agent very simple and makes automated installation easy.&lt;/p&gt;
  1255.  
  1256. &lt;p&gt;The Kubernetes monitoring component comes along for the ride. &lt;a href="https://octopus.com/docs/kubernetes/live-object-status/installation#upgrading-an-existing-kubernetes-agent"&gt;See our docs for detailed instructions&lt;/a&gt;.&lt;/p&gt;
  1257.  
  1258. &lt;p&gt;&lt;figure&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-04/kubernetes-live-object-status/kubernetes-agent-wizard-config.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-04/kubernetes-live-object-status/kubernetes-agent-wizard-config.png' class="img-fluid" height="auto" width="500" alt='Kubernetes agent wizard configuration options' /&gt;&lt;/a&gt;&lt;figcaption&gt;Kubernetes agent configuration options&lt;/figcaption&gt;&lt;/figure&gt;&lt;/p&gt;
  1259.  
  1260. &lt;h2 id="new-to-octopus-deploy-entirely"&gt;New to Octopus Deploy entirely?&lt;/h2&gt;
  1261.  
  1262. &lt;p&gt;How exciting! Welcome to scalable, simple, and safe Kubernetes CD with Octopus.&lt;/p&gt;
  1263.  
  1264. &lt;p&gt;Octopus is one user-friendly tool for developers to deploy, verify, and troubleshoot their apps. Platform engineers use this powerful tool to fully automate Continuous Delivery, manage configuration templates, and implement compliance, security, and auditing best practices.&lt;/p&gt;
  1265.  
  1266. &lt;p&gt;We empower your teams to spend less time managing and troubleshooting Kubernetes deployments and more time shipping new features to improve your software.&lt;/p&gt;
  1267.  
  1268. &lt;p&gt;Octopus models environments out-of-the-box and reduces the need for custom scripting. You define your deployment process once and reuse it for all your environments. You can go to production confidently as your process has already worked in other environments.&lt;/p&gt;
  1269.  
  1270. &lt;p&gt;If you’re interested in trying it out, sign up for a &lt;a href="https://octopus.com/start"&gt;free 30-day trial&lt;/a&gt;.&lt;/p&gt;
  1271.  
  1272. &lt;h3 id="getting-started-with-the-agent-and-monitor"&gt;Getting started with the agent and monitor&lt;/h3&gt;
  1273.  
  1274. &lt;p&gt;The Octopus Kubernetes agent targets are a mechanism for executing Kubernetes steps and monitoring application health from inside the target Kubernetes cluster, rather than via an external API connection.&lt;/p&gt;
  1275.  
  1276. &lt;p&gt;Like the Octopus Tentacle, the Kubernetes agent is a small, lightweight application that's installed into the target Kubernetes cluster.&lt;/p&gt;
  1277.  
  1278. &lt;p&gt;You install the Kubernetes agent using Helm via the octopusdeploy/kubernetes-agent chart. For the complete details, see our docs about &lt;a href="https://octopus.com/docs/kubernetes/targets/kubernetes-agent#installing-the-kubernetes-agent"&gt;installing the Kubernetes agent&lt;/a&gt;.&lt;/p&gt;
  1279.  
  1280. &lt;h3 id="when-can-i-use-it"&gt;When can I use it?&lt;/h3&gt;
  1281.  
  1282. &lt;p&gt;The Kubernetes agent is available now as an Early Access Preview (EAP) in Octopus Cloud! If you don’t see the feature available, please reach out and we can fast-track your cloud instance getting this release.&lt;/p&gt;
  1283.  
  1284. &lt;p&gt;Remember this is an opt-in upgrade for existing Octopus agents installed on your cluster(s). &lt;a href="https://octopus.com/docs/kubernetes/live-object-status/installation#upgrading-an-existing-kubernetes-agent"&gt;See this documentation page for all the details&lt;/a&gt;.&lt;/p&gt;
  1285.  
  1286. &lt;p&gt;&lt;figure&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-04/kubernetes-live-object-status/kubernetes-agent-wizard-config.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-04/kubernetes-live-object-status/kubernetes-agent-wizard-config.png' class="img-fluid" height="auto" width="500" alt='Kubernetes agent as deployment targets' /&gt;&lt;/a&gt;&lt;figcaption&gt;Kubernetes agent as deployment targets&lt;/figcaption&gt;&lt;/figure&gt;&lt;/p&gt;
  1287.  
  1288. &lt;h2 id="how-we-built-kubernetes-live-object-status"&gt;How we built Kubernetes Live Object Status&lt;/h2&gt;
  1289.  
  1290. &lt;p&gt;To facilitate a potentially large flow of new data coming to Octopus Server, a separate and non-disruptive web host runs alongside the main host. This isolation level gives us confidence that this is an additive feature and if there are performance complications, they'll get isolated and managed with minimal impact on Octopus Server's regular operations.&lt;/p&gt;
  1291.  
  1292. &lt;p&gt;The cluster-based monitoring capability uses two values to identify the incoming request:&lt;/p&gt;
  1293.  
  1294. &lt;ul&gt;
  1295. &lt;li&gt;The client certificate thumbprint&lt;/li&gt;
  1296. &lt;li&gt;An installation ID in the request headers&lt;/li&gt;
  1297. &lt;/ul&gt;
  1298.  
  1299. &lt;p&gt;Octopus Server uses a long-lived bearer token as a shared secret for authentication. The token gets generated when the monitoring capability installs in the cluster and registers with Octopus Server. This token is rotatable by customers and only valid for use on the gRPC endpoint.&lt;/p&gt;
  1300.  
  1301. &lt;p&gt;This allowed us to build gRPC services to handle the data flowing from the monitoring agent in the Kubernetes clusters. &lt;a href="https://grpc.io/" rel="nofollow"&gt;gRPC&lt;/a&gt; is a modern open-source high-performance remote procedure call (RPC) framework. This is the first time we’re using gRPC as part of an Octopus feature.&lt;/p&gt;
  1302.  
  1303. &lt;p&gt;In the cluster, alongside the Octopus Kubernetes agent, we have this new component that's responsible for the monitoring aspect. It sits in the cluster and monitors the deployed resources, pumping relevant live-status data back out over gRPC to Octopus Deploy.&lt;/p&gt;
  1304.  
  1305. &lt;p&gt;As we also run Octopus Deploy in Kubernetes for our self-hosted customers, we have a new nginx-based ingress configuration to help with partitioning and scalability. To find out more have a look at &lt;a href="https://www.youtube.com/watch?v=DH7YDySEPHU" rel="nofollow"&gt;how we use Kubernetes for Octopus Cloud&lt;/a&gt;.&lt;/p&gt;
  1306.  
  1307. &lt;h3 id="written-in-go"&gt;Written in Go&lt;/h3&gt;
  1308.  
  1309. &lt;p&gt;This is the first large-scale feature our team has built in &lt;a href="https://go.dev/" rel="nofollow"&gt;Golang&lt;/a&gt; in Octopus. This has given us access to a large set of great libraries built for Kubernetes. Examples include Helm packages and the Argo GitOps engine. Our team got the expertise uplift from the Codefresh engineers who are now part of Octopus.&lt;/p&gt;
  1310.  
  1311. &lt;p&gt;The GitOps engine is a flexible library with enough configuration and extension points for us to save very specific information on a per-resource basis. This helps us get the right information out of the cluster and back to Octopus. Go is also the de facto programming language for Kubernetes.&lt;/p&gt;
  1312.  
  1313. &lt;p&gt;We're exploring options to open-source parts of our implementation. Stay tuned for when that’s all decided, as we'll have a follow-up blog post. The likely first step will be making the source available for inspection. This is part of offering more transparency into the tools we’re asking customers to run in the security context of their clusters.&lt;/p&gt;
  1314.  
  1315. &lt;h2 id="whats-coming-next"&gt;What's coming next&lt;/h2&gt;
  1316.  
  1317. &lt;p&gt;Today’s release is the EAP. The list below represents capabilities we think are worth adding next (though it's not the complete list). If you have thoughts and opinions, please reach out to us in the comments section below or on our &lt;a href="https://octopus.com/slack"&gt;community Slack&lt;/a&gt;. &lt;/p&gt;
  1318.  
  1319. &lt;ul&gt;
  1320. &lt;li&gt;Terraform-based setup&lt;/li&gt;
  1321. &lt;li&gt;Support Kubernetes API targets&lt;/li&gt;
  1322. &lt;li&gt;Self-hosting (this feature is only available on Octopus Cloud)&lt;/li&gt;
  1323. &lt;li&gt;Octopus HA (multi-node server) support&lt;/li&gt;
  1324. &lt;li&gt;Custom health checks&lt;/li&gt;
  1325. &lt;li&gt;Orphan and drift detection&lt;/li&gt;
  1326. &lt;/ul&gt;
  1327.  
  1328. &lt;h3 id="this-looks-cool-but-what-if-i-dont-deploy-to-kubernetes"&gt;This looks cool, but what if I don’t deploy to Kubernetes?&lt;/h3&gt;
  1329.  
  1330. &lt;p&gt;Currently, there are no plans to extend this beyond Kubernetes deployments. Please let us know where and why you'd like to use this monitoring capability.&lt;/p&gt;
  1331.  
  1332. &lt;h2 id="let-us-know-your-thoughts"&gt;Let us know your thoughts&lt;/h2&gt;
  1333.  
  1334. &lt;p&gt;We're excited to see how you use this monitoring feature. Please let us know in the comments section below or on our &lt;a href="https://octopus.com/slack"&gt;community Slack&lt;/a&gt; what new opportunities this opens up for your application delivery objectives.&lt;/p&gt;
  1335.  
  1336. &lt;p&gt;Happy deployments!&lt;/p&gt;
  1337. </content>
  1338.  </entry>
  1339.  <entry>
  1340.    <id>https://octopus.com/blog/measuring-cd-and-devops-measurement-types</id>
  1341.    <title type="text">The 3 measurement types from Measuring Continuous Delivery and DevOps</title>
  1342.    <published>2025-04-02T14:00:00Z</published>
  1343.    <updated>2025-03-31T06:59:49.1639323Z</updated>
  1344.    <author>
  1345.      <name>steve.fenton@octopus.com, Octopus Deploy</name>
  1346.    </author>
  1347.    <link href="https://octopus.com/blog/measuring-cd-and-devops-measurement-types" />
  1348.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-04/measuring-cd-and-devops-measurement-types/blog-generic-statistics-metrics-v2-2025-750x400-x2.jpg" alt="Person standing in front of floating rectangles that contain different metrics." /&gt;&lt;/p&gt;
  1349.  
  1350. &lt;p&gt;Your continuous improvement process sits neatly between a system of measurements. You can use metrics to generate focus areas where you need to improve and use the metrics again to track your progress.&lt;/p&gt;
  1351.  
  1352. &lt;p&gt;The perfect metrics would be real-world organization outcomes that update in real time as you try adjustments. The reality is that perfect metrics don't exist. The outcomes that are crucial to your organization tend to move slowly and imperceptibly in response to an improvement. Moving from monthly to weekly deployments won't immediately bring a rush of new customers, but delivering small batches regularly does help improve outcomes like this in the long run.&lt;/p&gt;
  1353.  
  1354. &lt;p&gt;In the absence of perfect metrics, we can still create a helpful measurement system by finding small responsive numbers that predict changes for the big-ticket items. Industry research can help us with this, as many relationships have been found between software delivery and organizational success.&lt;/p&gt;
  1355.  
  1356. &lt;p&gt;Our white paper, &lt;a href="https://octopus.com/whitepapers/measuring-continuous-delivery-and-devops"&gt;Measuring Continuous Delivery and DevOps&lt;/a&gt;, examines metric design and provides ways to power continuous improvement with numbers and techniques like statement-based assessments.&lt;/p&gt;
  1357.  
  1358. &lt;p&gt;This post summarizes 3 types of measurement from the white paper:&lt;/p&gt;
  1359.  
  1360. &lt;ol&gt;
  1361. &lt;li&gt;Leading versus lagging indicators&lt;/li&gt;
  1362. &lt;li&gt;Instrumented versus perceptual data&lt;/li&gt;
  1363. &lt;li&gt;System versus survey data&lt;/li&gt;
  1364. &lt;/ol&gt;
  1365.  
  1366. &lt;h2 id="leading-versus-lagging-indicators"&gt;1. Leading versus lagging indicators&lt;/h2&gt;
  1367.  
  1368. &lt;p&gt;Leading indicators help you predict future performance. You can use their early signals to predict changes in performance and take action to adjust the future outcome.&lt;/p&gt;
  1369.  
  1370. &lt;p&gt;Lagging indicators tell you what happened in the past, but rather than being predictive, they're typically factual.&lt;/p&gt;
  1371.  
  1372. &lt;p&gt;When you monitor a software system, leading indicators help you take action before a system becomes unavailable. For example, tracking CPU use lets us see when a feature uses too many resources and puts other features at risk. This lets you scale your resources or switch off the feature before the problem affects customers.&lt;/p&gt;
  1373.  
  1374. &lt;p&gt;If you wait for a lagging indicator, like screen loading times, your users will notice the problem before you do. That doesn't mean you shouldn't measure lagging indicators, as these show the &lt;em&gt;system's real performance&lt;/em&gt;. Leading indicators can alert you to a potential problem earlier, but they may change for reasons you don't expect.&lt;/p&gt;
  1375.  
  1376. &lt;p&gt;This explains the importance of using leading and lagging indicators to measure software delivery capability. The leading indicators help you react earlier, but the lagging indicators tell you the actual state of the whole value stream.&lt;/p&gt;
  1377.  
  1378. &lt;p&gt;The most important measurements to your organization are likely to be lagging indicators. For example, your organization cares about &lt;em&gt;revenue&lt;/em&gt;. This measurement tells you about money that has (or hasn't) come into the business. A predictive indicator, like net promoter score (NPS), can help you spot problems that might affect future revenue, but the money that turns up is a cold, hard fact.&lt;/p&gt;
  1379.  
  1380. &lt;p&gt;Leading indicators are often imperfect. We accept this because we value the ability to take action sooner. You should combine leading and lagging indicators to measure Continuous Delivery, DevOps, and software delivery performance.&lt;/p&gt;
  1381.  
  1382. &lt;h2 id="instrumented-versus-perceptual-data"&gt;2. Instrumented versus perceptual data&lt;/h2&gt;
  1383.  
  1384. &lt;p&gt;Instrumented data is a measurement you can collect automatically, like temperature. Perceptual data covers the human experience, like if the temperature is comfortable for you.&lt;br /&gt;
  1385. Instrumented data is popular because it's easy to get. However, perceptual data can capture complex relationships across many factors.&lt;/p&gt;
  1386.  
  1387. &lt;p&gt;When you ask someone if a room temperature is comfortable, their answer goes beyond measurable temperature. The answer could include factors like:&lt;/p&gt;
  1388.  
  1389. &lt;ul&gt;
  1390. &lt;li&gt;Humidity&lt;/li&gt;
  1391. &lt;li&gt;Outdoor conditions&lt;/li&gt;
  1392. &lt;li&gt;Their activity&lt;/li&gt;
  1393. &lt;li&gt;Clothing&lt;/li&gt;
  1394. &lt;li&gt;Personal preference&lt;/li&gt;
  1395. &lt;/ul&gt;
  1396.  
  1397. &lt;p&gt;If you ask employees if they feel energized or burned out, they report feeling burned out before their productivity drops.&lt;/p&gt;
  1398.  
  1399. &lt;p&gt;Most organizations are good at collecting instrumented data. You should become just as good at collecting perceptual data as it often provides uniquely nuanced insights.&lt;/p&gt;
  1400.  
  1401. &lt;h2 id="system-versus-survey-data"&gt;3. System versus survey data&lt;/h2&gt;
  1402.  
  1403. &lt;p&gt;If a team uses an internal tracking tool for features and a customer-facing tool to capture bugs, for example, you must collect data from both systems. If you only collect metrics from the internal tracking system, this work will get prioritized and optimized at the cost of customer-reported issues.&lt;/p&gt;
  1404.  
  1405. &lt;p&gt;You must also ensure teams use tools as expected. In factories with time clocks, it was common for the first worker to clock their colleagues in to stop them from getting in trouble. According to the clock, worked hours would be far more than the actual hours, and any decisions based on this data were likely wrong.&lt;/p&gt;
  1406.  
  1407. &lt;p&gt;In modern work tracking systems, users can mark work as complete before deploying it to production, which can lead to inaccurate lead times.&lt;/p&gt;
  1408.  
  1409. &lt;p&gt;Survey data needs more effort, but it can capture a richness of information not available from a system. You can collect perceptual data from surveys and instrumented data you can't get from a system. For example, if you haven't installed tools to support deployment automation, you could use a survey to ask how often a team deploys to production.&lt;/p&gt;
  1410.  
  1411. &lt;p&gt;When designing your surveys, consider the frequency and effort needed to respond. It helps if you coordinate your efforts to avoid flooding people with surveys from different parts of the organization.&lt;/p&gt;
  1412.  
  1413. &lt;p&gt;You may need some statistical skills to account for bias and help establish significant relationships in the data.&lt;/p&gt;
  1414.  
  1415. &lt;p&gt;For both system and survey data, if the organization isn't a safe space for honest feedback, the data will be what people believe to be the 'correct answer'.&lt;/p&gt;
  1416.  
  1417. &lt;p&gt;People can manipulate system data as easily as survey data. Marking work as complete before it becomes overdue and then tracking the work outside the system to finish it, for example.&lt;/p&gt;
  1418.  
  1419. &lt;p&gt;You can't measure a complex system (like the software delivery process) on system data alone. You should use both system and survey data in your measurement approach. Use the natural conflicts to discover and fix weaknesses in your measurement approach.&lt;/p&gt;
  1420.  
  1421. &lt;h2 id="its-all-about-improvement"&gt;It's all about improvement&lt;/h2&gt;
  1422.  
  1423. &lt;p&gt;The techniques in the white paper, &lt;a href="https://octopus.com/whitepapers/measuring-continuous-delivery-and-devops"&gt;Measuring Continuous Delivery and DevOps&lt;/a&gt;, can help reveal improvement opportunities. They provide a mechanism to design your improvements deliberately and scientifically. If you make a change to increase deployment rates but instead deploy less, you know the change didn't have the intended effect and can try something else.&lt;/p&gt;
  1424.  
  1425. &lt;p&gt;Over time, you need to respond to weaker signals rather than believing there are no further improvements to make. Teams and organizations that continuously improve will outperform those that think they're done.&lt;/p&gt;
  1426.  
  1427. &lt;p&gt;You can &lt;a href="https://octopus.com/whitepapers/measuring-continuous-delivery-and-devops"&gt;download the free white paper&lt;/a&gt; to learn more.&lt;/p&gt;
  1428.  
  1429. &lt;p&gt;Happy deployments!&lt;/p&gt;
  1430. </content>
  1431.  </entry>
  1432.  <entry>
  1433.    <id>https://octopus.com/blog/removing-sha1-tentacles</id>
  1434.    <title type="text">Removing support for SHA-1 certificates in Octopus Tentacles</title>
  1435.    <published>2025-03-26T14:00:00Z</published>
  1436.    <updated>2025-03-25T04:09:01.1320879Z</updated>
  1437.    <author>
  1438.      <name>simon.canning@octopus.com, Octopus Deploy</name>
  1439.    </author>
  1440.    <link href="https://octopus.com/blog/removing-sha1-tentacles" />
  1441.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-03/removing-sha1-tentacles/security.png" alt="Blue DevOps infinity diagram outlined in green with a green security shield over the right top-hand corner." /&gt;&lt;/p&gt;
  1442.  
  1443. &lt;p&gt;In 2017, we &lt;a href="https://octopus.com/blog/shattered"&gt;discussed&lt;/a&gt; the implications of the &lt;a href="https://shattered.io/" rel="nofollow"&gt;SHA-1 Shattered Collision&lt;/a&gt; and what that meant for the Octopus Server to Tentacle communication channel. At the same time, we made &lt;a href="https://octopus.com/docs/security/cve/shattered-and-octopus-deploy"&gt;product updates&lt;/a&gt; to ensure that SHA-256 was used when new self-signed certificates were generated for versions of &lt;a href="https://octopus.com/blog/octopus-release-3-14"&gt;Octopus 3.14&lt;/a&gt;.&lt;/p&gt;
  1444.  
  1445. &lt;p&gt;We've now decided to remove SHA-1 support. Fortunately, most customers use SHA-256 certificates, but some still use SHA-1 certificates.&lt;/p&gt;
  1446.  
  1447. &lt;p&gt;In this post, I outline how this deprecation affects different customers. I also provide a timeline of what to expect and how to regenerate new SHA-256 certificates.&lt;/p&gt;
  1448.  
  1449. &lt;h2 id="understanding-communication-between-octopus-server-and-tentacles"&gt;Understanding communication between Octopus Server and Tentacles&lt;/h2&gt;
  1450.  
  1451. &lt;p&gt;Security is paramount in modern software deployment environments. Octopus implements strong security measures for communication between the Octopus Server and its Tentacles.&lt;/p&gt;
  1452.  
  1453. &lt;p&gt;Here’s a deep dive into how this communication is established, the role of TLS, and the rationale behind using self-signed certificates out of the box.&lt;/p&gt;
  1454.  
  1455. &lt;h3 id="secure-communication-via-tls"&gt;Secure communication via TLS&lt;/h3&gt;
  1456.  
  1457. &lt;p&gt;When Octopus Server communicates with its Tentacles—the agents that handle deployment tasks—this interaction is always conducted over a secure Transport Layer Security (TLS) connection. TLS ensures the data exchanged between the 2 entities remains confidential and tamper-proof. Each server and Tentacle possess a unique public/private key pair crucial to establishing a secure and trusted link.&lt;/p&gt;
  1458.  
  1459. &lt;p&gt;The Octopus Server’s thumbprint gets sent to the Tentacle during the configuration process. This thumbprint is a unique identifier for the Server's certificate, establishing a trusting relationship between the Server and the Tentacle. Conversely, the Tentacle informs the Octopus Server of its thumbprint. As a result, commands issued by the server get accepted exclusively by those Tentacles it recognizes and trusts, and vice versa.&lt;/p&gt;
  1460.  
  1461. &lt;p&gt;This setup ensures that only legitimate entities can issue or accept commands, significantly enhancing the security of your deployment processes.&lt;/p&gt;
  1462.  
  1463. &lt;h3 id="the-use-of-self-signed-certificates"&gt;The use of self-signed certificates&lt;/h3&gt;
  1464.  
  1465. &lt;p&gt;A common question about Octopus Deploy’s security model is why it defaults to using self-signed certificates instead of certificates issued by a Certificate Authority (CA). At first glance, using self-signed certificates may seem less secure, but there are several compelling reasons for this choice:&lt;/p&gt;
  1466.  
  1467. &lt;ol&gt;
  1468. &lt;li&gt;&lt;em&gt;Customized trust relationships&lt;/em&gt;: The self-signed approach allows for precise trust management. When you set up a Tentacle, you manually input the Octopus Server's thumbprint. This process means that every connection is verified individually, ensuring authenticity. The connection is aborted if the server's identity cannot be confirmed through its thumbprint.&lt;/li&gt;
  1469. &lt;li&gt;&lt;em&gt;Operational efficiency&lt;/em&gt;: Using self-signed certificates simplifies the installation and setup, particularly in automated environments. Instead of relying on a CA to generate certificates, which can introduce delays and complexities, Tentacles can quickly generate their certificates upon installation. Additionally, importing existing certificates can be streamlined, facilitating the automation of Tentacle installation.&lt;/li&gt;
  1470. &lt;/ol&gt;
  1471.  
  1472. &lt;div class="alert alert-info"&gt;&lt;p&gt;We're &lt;a href="https://roadmap.octopus.com/c/194-tentacle-certificate-management-improvements" class="alert-link" rel="nofollow"&gt;open to feedback&lt;/a&gt; about how this decision affects your ability to manage your Octopus Server and Tentacles at scale. We're particularly interested in hearing from customers who'd like to discuss their current credential management and rotation practices.&lt;/p&gt;
  1473. &lt;/div&gt;
  1474.  
  1475. &lt;h3 id="how-it-all-comes-together"&gt;How it all comes together&lt;/h3&gt;
  1476.  
  1477. &lt;p&gt;When a Tentacle is registered with the Octopus Server, the 2 entities exchange their thumbprints, identifying their certificates. This process lays the foundation for a secure and trusted relationship. When the Octopus Server connects to a Tentacle, it checks that the Tentacle presents a valid certificate matching the expected thumbprint. This verification process is reciprocal; the Tentacle similarly checks that the connection originates from a trusted Octopus Server. If any discrepancies arise, the connection is immediately rejected.&lt;/p&gt;
  1478.  
  1479. &lt;p&gt;This model mirrors principles in other secure communication protocols, like SSH, used in UNIX systems, providing a robust and familiar security framework.&lt;/p&gt;
  1480.  
  1481. &lt;h2 id="how-can-i-determine-if-im-affected"&gt;How can I determine if I’m affected?&lt;/h2&gt;
  1482.  
  1483. &lt;p&gt;Below is an example command that will print out the machines (deployment target Tentacles) with sha1RSA set as their certificate signature algorithm. You'll need to replace the &lt;code&gt;instance-name&lt;/code&gt; with your instance name or the full URL if you’re a self-host customer, &lt;code&gt;space-id&lt;/code&gt; with a space ID (e.g., &lt;code&gt;Spaces-1&lt;/code&gt;), and replace the API key with a key that has at least the MachineView permission.&lt;/p&gt;
  1484.  
  1485. &lt;pre&gt;&lt;code&gt;curl -H &amp;quot;X-Octopus-Apikey: API-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&amp;quot; -H &amp;quot;Accept: application/json&amp;quot; &amp;quot;https://&amp;lt;instance-name&amp;gt;.octopus.app/api/&amp;lt;space-id&amp;gt;/machines&amp;quot; |  jq '.Items .[] | select(.Endpoint.CertificateSignatureAlgorithm==&amp;quot;sha1RSA&amp;quot;)'
  1486. &lt;/code&gt;&lt;/pre&gt;
  1487.  
  1488. &lt;p&gt;For more detail, read about &lt;a href="https://octopus.com/blog/api-bash-jq#using-the-octopus-api-with-bash-and-jq"&gt;using the Octopus API with Bash and jq&lt;/a&gt;. Alternatively, you can &lt;a href="https://octopus.com/blog/interacting-with-the-octopus-deploy-api-using-powershell"&gt;interact with the Octopus Deploy API using PowerShell&lt;/a&gt;.&lt;/p&gt;
  1489.  
  1490. &lt;h2 id="do-i-have-to-wait-for-a-new-octopus-server-or-tentacle-version"&gt;Do I have to wait for a new Octopus Server or Tentacle version?&lt;/h2&gt;
  1491.  
  1492. &lt;p&gt;No, you do not. You can take action now. Octopus has supported SHA-256 certificates for Server to Tentacle communications since the &lt;a href="https://octopus.com/blog/octopus-release-3-14"&gt;3.14 release in June 2017&lt;/a&gt;.&lt;/p&gt;
  1493.  
  1494. &lt;h2 id="what-do-i-need-to-do"&gt;What do I need to do?&lt;/h2&gt;
  1495.  
  1496. &lt;p&gt;To configure a Tentacle to use a new certificate, ensure your Tentacle version is on the latest version and &lt;a href="https://octopus.com/docs/security/octopus-tentacle-communication/regenerate-certificates-with-octopus-server-and-tentacle#ConfiguringATentacleToUseANewCertificate"&gt;follow the instructions in our docs&lt;/a&gt;.&lt;/p&gt;
  1497.  
  1498. &lt;h2 id="what-is-the-deprecation-schedule"&gt;What is the deprecation schedule?&lt;/h2&gt;
  1499.  
  1500. &lt;p&gt;Below are details of the deprecation schedule, depending on the Octopus product and operating system your server runs on.&lt;/p&gt;
  1501.  
  1502. &lt;h3 id="octopus-cloud-customers"&gt;Octopus Cloud customers&lt;/h3&gt;
  1503.  
  1504. &lt;p&gt;We plan to start emailing affected customers about the deprecation on March 31, 2025, and give at least 60 days' notice before we switch off support for SHA-1 on June 1, 2025. After that point, any deployment target or worker still using SHA-1 Tentacle will no longer be able to connect to Octopus Cloud. We plan to give reminders regularly, including 30 days, 7 days, and a final warning. You can take action now.&lt;/p&gt;
  1505.  
  1506. &lt;h3 id="octopus-server-linux-container-customers"&gt;Octopus Server Linux container customers&lt;/h3&gt;
  1507.  
  1508. &lt;p&gt;We plan to release an in-product configuration option to turn on/off the SHA-1 Tentacle support in Octopus Server 2025.2 and remove support for SHA-1 Tentacles in the subsequent Octopus Server 2025.3 release. These changes will impact Octopus Server Linux container customers only.&lt;/p&gt;
  1509.  
  1510. &lt;p&gt;As a self-hosted customer, you control the update cycle of your Octopus Server and, therefore, have some flexibility around how and when to perform the appropriate updates. We recommend you take action as soon as possible.&lt;/p&gt;
  1511.  
  1512. &lt;h3 id="octopus-server-windows-customers"&gt;Octopus Server Windows customers&lt;/h3&gt;
  1513.  
  1514. &lt;p&gt;There are no immediate required actions for Octopus Server Windows self-hosted customers. This is because we can continue to support SHA-1 certificates using supported operating systems and runtime environments for the time being.&lt;/p&gt;
  1515.  
  1516. &lt;p&gt;As a self-hosted customer, you control the update cycle of your Octopus Server and, therefore, have some flexibility around how and when to perform updates. We still recommend you take action and move off SHA-1 certificates as soon as possible.&lt;/p&gt;
  1517.  
  1518. &lt;h3 id="future-work"&gt;Future work&lt;/h3&gt;
  1519.  
  1520. &lt;p&gt;In the future, we expect to add features in Octopus Server to support automatically regenerating certificates on the Octopus Server and all Tentacles. We're currently in the discovery phase of this work. We're particularly interested in hearing from customers who would like to &lt;a href="https://roadmap.octopus.com/c/194-tentacle-certificate-management-improvements" rel="nofollow"&gt;discuss their current credential management and rotation practices&lt;/a&gt;.&lt;/p&gt;
  1521.  
  1522. &lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt;
  1523.  
  1524. &lt;p&gt;Removing support for SHA-1 certificates in Octopus Tentacles is part of our commitment to deliver secure software deployment environments. It enables us to continue to support modern operating systems and runtime environments. &lt;/p&gt;
  1525.  
  1526. &lt;p&gt;While most customers have moved to the more secure SHA-256 certificates, it's crucial for those still using SHA-1 to understand the implications of this deprecation. The communication between Octopus Server and Tentacles relies on secure TLS connections and self-signed certificates, promoting customized trust relationships and operational efficiency. As the move towards stronger cryptographic algorithms continues, we encourage customers to regenerate their certificates to align with best practices. &lt;/p&gt;
  1527.  
  1528. &lt;p&gt;We &lt;a href="https://roadmap.octopus.com/c/194-tentacle-certificate-management-improvements" rel="nofollow"&gt;welcome feedback about credential management and practices&lt;/a&gt; to ensure the Octopus platform meets your needs effectively. This transition bolsters security measures, further safeguarding the deployment processes critical to businesses.&lt;/p&gt;
  1529.  
  1530. &lt;p&gt;Happy deployments!&lt;/p&gt;
  1531. </content>
  1532.  </entry>
  1533.  <entry>
  1534.    <id>https://octopus.com/blog/scoped-tenant-variables</id>
  1535.    <title type="text">Scoped tenant variables</title>
  1536.    <published>2025-03-24T14:00:00Z</published>
  1537.    <updated>2025-03-21T03:18:14.6240937Z</updated>
  1538.    <author>
  1539.      <name>susan.pan@octopus.com, Octopus Deploy</name>
  1540.    </author>
  1541.    <link href="https://octopus.com/blog/scoped-tenant-variables" />
  1542.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-03/scoped-tenant-variables/blogimage-variable-tenants-ui-dashboard-2024.png" alt="Graphic image of woman viewing scoped tenant variables page." /&gt;&lt;/p&gt;
  1543.  
  1544. &lt;p&gt;We recently improved tenant variables by introducing scoped tenant variables.&lt;/p&gt;
  1545.  
  1546. &lt;p&gt;&lt;a href="https://octopus.com/docs/tenants/tenant-variables"&gt;Common tenant variables&lt;/a&gt; are great for managing variables within tenants. Assigning a common tenant variable means that every connected project has access to that variable. This is great for deploying and managing multi-tenanted deployments at scale, and simplifies deployments by using the same value for every connected environment. We wanted to create more flexibility by letting customers set different common variable values for each environment across all tenant projects. Scoped common tenant variables aim to solve this.&lt;/p&gt;
  1547.  
  1548. &lt;p&gt;Assigning environment scopes to your common tenant variables will make variable management across tenant projects so much simpler.&lt;/p&gt;
  1549.  
  1550. &lt;p&gt;In this post, I walk you through how to scope tenant variables and discuss the integration capabilities.&lt;/p&gt;
  1551.  
  1552. &lt;p&gt;These updates are now available to our Cloud customers and will be available to self-hosted customers from v2025.2.&lt;/p&gt;
  1553.  
  1554. &lt;h2 id="why-should-i-scope-tenant-variables"&gt;Why should I scope tenant variables?&lt;/h2&gt;
  1555.  
  1556. &lt;p&gt;Previously, there were both constraints and differences in how you managed tenant variables  for environments. &lt;/p&gt;
  1557.  
  1558. &lt;ul&gt;
  1559. &lt;li&gt;Tenant project variables required one value per project environment. &lt;/li&gt;
  1560. &lt;li&gt;Tenant common variables were limited to one value across all environments connected to a tenant. &lt;/li&gt;
  1561. &lt;/ul&gt;
  1562.  
  1563. &lt;p&gt;Now, you can scope common variables to environments as needed. This means they can be unscoped (variable applies to all connected environments), singly-scoped, or multi-scoped. &lt;/p&gt;
  1564.  
  1565. &lt;p&gt;The ability to assign scopes to tenant variables creates more simplicity and flexibility with variable management. For example, to assign different variable values for different environments across all tenant projects, you previously had to create a tenant for each environment. You could then set a common variable for each tenant. Now, you simply set multiple common variables with the appropriate environment scope. &lt;/p&gt;
  1566.  
  1567. &lt;p&gt;This is particularly useful if your non-production environments all share one value, while production has a separate value. Maintaining variables becomes more straightforward as you only need to update values once.&lt;/p&gt;
  1568.  
  1569. &lt;h2 id="how-to-assign-scopes-to-your-tenant-variables"&gt;How to assign scopes to your tenant variables&lt;/h2&gt;
  1570.  
  1571. &lt;p&gt;You can set tenant variables from the projects page and from the tenants page. To set tenant common variables from the project page, you need to create a tenant with a connected project and connected environments. Then you create a variable set with a variable template and connect it to the tenanted project.&lt;/p&gt;
  1572.  
  1573. &lt;ul&gt;
  1574. &lt;li&gt;Select the &lt;strong&gt;Tenant Variables&lt;/strong&gt; page from the sidebar and click on the &lt;strong&gt;Common Templates&lt;/strong&gt; tab.&lt;/li&gt;
  1575. &lt;/ul&gt;
  1576.  
  1577. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-03/scoped-tenant-variables/scoped-tenant-vars-view.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-03/scoped-tenant-variables/scoped-tenant-vars-view.png' class="img-fluid center" alt='Screenshot of common tenant variables tab on tenant variables page.' /&gt;&lt;/a&gt;&lt;/p&gt;
  1578.  
  1579. &lt;ul&gt;
  1580. &lt;li&gt;To add a new tenant variable, select the overflow menu and click &lt;strong&gt;Add&lt;/strong&gt;.&lt;/li&gt;
  1581. &lt;li&gt;Type in a value and select the environments in the &lt;strong&gt;Scope&lt;/strong&gt; column. Click &lt;strong&gt;Save&lt;/strong&gt;.&lt;/li&gt;
  1582. &lt;/ul&gt;
  1583.  
  1584. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-03/scoped-tenant-variables/scoped-tenant-vars-add-new.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-03/scoped-tenant-variables/scoped-tenant-vars-add-new.png' class="img-fluid center" alt='Screenshot of adding a new tenant variable on tenant variables page.' /&gt;&lt;/a&gt;&lt;/p&gt;
  1585.  
  1586. &lt;ul&gt;
  1587. &lt;li&gt;The page should now show the new tenant variable values and scopes.&lt;/li&gt;
  1588. &lt;/ul&gt;
  1589.  
  1590. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-03/scoped-tenant-variables/scoped-tenant-vars.png' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-03/scoped-tenant-variables/scoped-tenant-vars.png' class="img-fluid center" alt='Screenshot showing new scoped tenant variables on tenant variables page.' /&gt;&lt;/a&gt;&lt;/p&gt;
  1591.  
  1592. &lt;p&gt;Unscoped variables apply to all environments with no explicitly scoped variables. &lt;a href="https://octopus.com/docs/projects/variables/getting-started#scoping-variables"&gt;See our docs for more information on scoping variables&lt;/a&gt;.&lt;/p&gt;
  1593.  
  1594. &lt;h3 id="migrating-existing-tenant-variables"&gt;Migrating existing tenant variables&lt;/h3&gt;
  1595.  
  1596. &lt;p&gt;Existing tenant variables will automatically get migrated to the new scoped tenant variables when upgraded to 2025.2. The migration will scope tenant project variables to the previous single scope and common variables will be unscoped. This ensures your deployments can proceed without making any changes. After your instance detects scoped tenant variables in use, it will prevent the use of the old tenant variable endpoint. &lt;/p&gt;
  1597.  
  1598. &lt;div class="alert alert-warning"&gt;&lt;p&gt;We'll deprecate the endpoint &lt;code&gt;tenants/{tenantId}/tenantvariables&lt;/code&gt; from 2026.2.&lt;/p&gt;
  1599. &lt;/div&gt;
  1600.  
  1601. &lt;p&gt;We introduced 2 new endpoints for GET/UPDATE requests for scoped tenant variables. These will replace the use of the endpoint above:&lt;/p&gt;
  1602.  
  1603. &lt;ul&gt;
  1604. &lt;li&gt;&lt;code&gt;tenants/{tenantId}/projectvariables&lt;/code&gt;&lt;/li&gt;
  1605. &lt;li&gt;&lt;code&gt;tenants/{tenantId}/commonvariables&lt;/code&gt;&lt;/li&gt;
  1606. &lt;/ul&gt;
  1607.  
  1608. &lt;h2 id="automation-and-integration"&gt;Automation and integration&lt;/h2&gt;
  1609.  
  1610. &lt;p&gt;Scoped tenant variables are now supported through our .NET, TypeScript, and Go clients. &lt;a href="https://octopus.com/docs/octopus-rest-api/getting-started#api-clients"&gt;See our docs for more information on our API clients&lt;/a&gt;.&lt;/p&gt;
  1611.  
  1612. &lt;p&gt;Octopus CLI will also support the use of scoped tenant variables. As our CLI matches tenant variables on the variable's name and environment, the tenant variable update function currently doesn't support changing variable scopes of existing tenant variables. To select the correct tenant variable, you must specify the exact scope.&lt;/p&gt;
  1613.  
  1614. &lt;p&gt;Our Terraform provider doesn't currently support the new scoped tenant variables. If you'd like this to be supported, please don't hesitate to &lt;a href="https://octopus.com/support"&gt;get in contact&lt;/a&gt; with us.&lt;/p&gt;
  1615.  
  1616. &lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt;
  1617.  
  1618. &lt;p&gt;Scoped tenant variables give you finer control of your tenant variables. Now, you can simply assign a scope to your tenant variables and watch the magic happen.&lt;/p&gt;
  1619.  
  1620. &lt;p&gt;To get started or learn more, you can read our &lt;a href="https://octopus.com/docs/tenants/tenant-variables"&gt;tenant variables documentation&lt;/a&gt;.&lt;/p&gt;
  1621.  
  1622. &lt;p&gt;Happy deployments!&lt;/p&gt;
  1623. </content>
  1624.  </entry>
  1625.  <entry>
  1626.    <id>https://octopus.com/blog/revamping-careers-page</id>
  1627.    <title type="text">Revamping our careers page: More than just a makeover</title>
  1628.    <published>2025-03-17T14:00:00Z</published>
  1629.    <updated>2025-03-13T06:47:03.7470649Z</updated>
  1630.    <author>
  1631.      <name>stephanie.king@octopus.com, Octopus Deploy</name>
  1632.    </author>
  1633.    <link href="https://octopus.com/blog/revamping-careers-page" />
  1634.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-03/revamping-careers-page/blog-revamp-careers-page-2025-750x400-x1.png" alt="Painters painting and revealing the careers webpage, with sticky notes around the image featuring photos of Octopus employees." /&gt;&lt;/p&gt;
  1635.  
  1636. &lt;p&gt;If you’ve been through a website redesign, you know it’s a lot like refactoring old code. You start with confidence that it should be an easy fix, and before you know it, you’re knee-deep in overhaul and questioning how you got here.&lt;/p&gt;
  1637.  
  1638. &lt;p&gt;Our &lt;a href="https://octopus.com/company/careers"&gt;careers page&lt;/a&gt; revamp was no different. Before the redesign, our page was fine. It was functional, informative, and technically accurate. But with the evolution of Octopus over the last few years, it wasn’t quite us anymore. So we did what many DevOps teams do when faced with legacy infrastructure—we rebuilt it.&lt;/p&gt;
  1639.  
  1640. &lt;h2 id="why-we-overhauled-the-page"&gt;Why we overhauled the page&lt;/h2&gt;
  1641.  
  1642. &lt;p&gt;The careers page is part of a larger, strategic effort to strengthen our employer brand. It isn’t just a recruitment tool but an integral piece of our broader employer strategy. Just as we want customers to know and trust the Octopus brand, we want potential employees to have a clear sense of who we are and what it means to work here.&lt;/p&gt;
  1643.  
  1644. &lt;p&gt;A talent team should think of their careers page as far more than just a list of open jobs and advertisement space. It’s the first (and sometimes only) impression, a handshake, and a small window into what it truly means to work at your company. From the content to the emotions visitors leave with, a careers page should tell a story. It should give potential candidates a real sense of the culture, values, and experience of being part of the team.&lt;/p&gt;
  1645.  
  1646. &lt;p&gt;At Octopus, we aren’t just hiring people to fill roles. We’re inviting folks into our authentic, people-centric, and transparent culture, where we want them to do the best work of their lives. We think about the people joining our company like pieces of a much bigger puzzle, or individual threads in the organic, human fabric we’re intentionally weaving—each one adding depth, strength, and uniqueness to the whole. That feeling isn’t easy to capture with stock photos and generic content.&lt;/p&gt;
  1647.  
  1648. &lt;p&gt;When I started at Octopus in 2022, I began advocating for more talent engagement, a revamped careers page, and deeper investment in employer branding. This year, I challenged our team to consider:&lt;/p&gt;
  1649.  
  1650. &lt;ul&gt;
  1651. &lt;li&gt;Does our careers page reflect who we truly are?&lt;/li&gt;
  1652. &lt;li&gt;Would we want to apply to Octopus based on what we see at first glance?&lt;/li&gt;
  1653. &lt;li&gt;Is it easy (and exciting!) for people to picture themselves on our team?&lt;/li&gt;
  1654. &lt;li&gt;Are we giving candidates a real feel for our culture, or just listing jobs?&lt;/li&gt;
  1655. &lt;li&gt;Does every word, image, and detail make people want to be part of this journey?&lt;/li&gt;
  1656. &lt;/ul&gt;
  1657.  
  1658. &lt;p&gt;With each question, it became clear that we'd barely scratched the surface of what was possible. So, we set out to build something that not only showcases our opportunities but also captures the spirit of working at Octopus.&lt;/p&gt;
  1659.  
  1660. &lt;h2 id="whats-changed"&gt;What’s changed?&lt;/h2&gt;
  1661.  
  1662. &lt;ul&gt;
  1663. &lt;li&gt;A more human touch - You’ll see more real Octonauts sharing their experiences because culture isn’t something you describe; it’s something you show.&lt;/li&gt;
  1664. &lt;li&gt;Remote work, represented - As a remote-first company, we made it clear how we work, collaborate, and keep things fun across multiple timezones.&lt;/li&gt;
  1665. &lt;li&gt;A careers page with personality - No corporate jargon or fluff. It's just an authentic, engaging, and maybe even slightly quirky look at life at Octopus.&lt;/li&gt;
  1666. &lt;li&gt;More than just jobs - We’re shining a light on what it truly means to work at Octopus, from career growth to the perks that matter, with more transparency than ever.&lt;/li&gt;
  1667. &lt;/ul&gt;
  1668.  
  1669. &lt;h3 id="the-partnerships-that-made-this-possible"&gt;The partnerships that made this possible&lt;/h3&gt;
  1670.  
  1671. &lt;p&gt;This wasn’t just a talent team project. It was a multi-threaded, strategic effort with collaboration across teams and partners.&lt;/p&gt;
  1672.  
  1673. &lt;ul&gt;
  1674. &lt;li&gt;Our marketing team and Octonaut volunteers - From content creation to branding, many Octonauts generously gave their time to shape how we tell our story. Their insights, feedback, and participation helped make our careers page a true reflection of life at Octopus. Our marketing team dove in heads first to make this a seamless experience and were invaluable in the making of our careers page.&lt;/li&gt;
  1675. &lt;li&gt;Adam Marsh from Moment2Moment - Our incredible on-set videographer in Australia, who captured the heart of Octopus through film. His keen eye and ability to bring our genuine, unscripted moments made all the difference in our careers video.&lt;/li&gt;
  1676. &lt;li&gt;Yoram Pollack from Visual Trigger - A true visionary behind the storytelling, video editing, and overall concept execution. Yoram took our initial ideas and let us share our stories with him so he could transform them into something beyond what we imagined, making our dream careers page a reality.&lt;/li&gt;
  1677. &lt;/ul&gt;
  1678.  
  1679. &lt;p&gt;We're grateful to everyone who played a part. We built an experience that reflects who Octonauts are and why people should be excited to join us.&lt;/p&gt;
  1680.  
  1681. &lt;h2 id="explore-life-at-octopus"&gt;Explore life at Octopus&lt;/h2&gt;
  1682.  
  1683. &lt;p&gt;Our new &lt;a href="https://octopus.com/company/careers"&gt;careers page&lt;/a&gt; isn’t just about listing jobs. It’s about showing what makes Octopus a special place to work. Whether you’re an engineer, a sales pro, a marketer, or just curious about our culture, we invite you to explore, get to know our team, and see if Octopus feels like a great fit for you to do the best work of your life.&lt;/p&gt;
  1684.  
  1685. &lt;p&gt;We’d love to hear what you think. If you’ve crafted your own careers page, what was your strategy? If you have feedback as a job seeker, send it our way. If you’re thinking about joining us, what are you waiting for? &lt;a href="https://octopus.com/company/careers"&gt;Dive on in!&lt;/a&gt; And if you’re as excited as we are, maybe start practicing your best “I just landed my dream job” happy dance!&lt;/p&gt;
  1686.  
  1687. &lt;p&gt;Happy deployments!&lt;/p&gt;
  1688. </content>
  1689.  </entry>
  1690.  <entry>
  1691.    <id>https://octopus.com/blog/trust-security-customer-protection</id>
  1692.    <title type="text">Building trust through security—our commitment to customer protection</title>
  1693.    <published>2025-03-10T14:00:00Z</published>
  1694.    <updated>2025-03-07T04:49:58.3967164Z</updated>
  1695.    <author>
  1696.      <name>simon.canning@octopus.com, Octopus Deploy</name>
  1697.    </author>
  1698.    <link href="https://octopus.com/blog/trust-security-customer-protection" />
  1699.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-03/trust-security-customer-protection/security.png" alt="A stylized Octopus and shield icon." /&gt;&lt;/p&gt;
  1700.  
  1701. &lt;p&gt;Our top priority at Octopus Deploy is ensuring our customers can deploy safely and securely. We're proud that 4000+ customers &lt;a href="https://octopus.com/company/trust"&gt;trust us&lt;/a&gt; and our products to deliver their changes into production. We take that responsibility seriously, and our &lt;a href="https://octopus.com/security/disclosure"&gt;security guiding principles&lt;/a&gt; prioritize our customers' security interests over ours.&lt;/p&gt;
  1702.  
  1703. &lt;p&gt;In this post, I walk you through our most recent product security updates.&lt;/p&gt;
  1704.  
  1705. &lt;h2 id="product-security-enhancements"&gt;Product security enhancements&lt;/h2&gt;
  1706.  
  1707. &lt;p&gt;We’re happy to announce improvements to the Octopus Server in 2025.1, which have already rolled out to Octopus Cloud customers. We made changes to our encryption support across data at rest and in transit. These changes provide you with enhanced security, lower network latency, and the potential for improved operational efficiency.&lt;/p&gt;
  1708.  
  1709. &lt;p&gt;The changes include:&lt;/p&gt;
  1710.  
  1711. &lt;ul&gt;
  1712. &lt;li&gt;Using AES-256 by default for Master Key encryption of sensitive data in the Octopus database for all new server instances.&lt;/li&gt;
  1713. &lt;li&gt;Adding TLS 1.3 support to Octopus Server and Octopus Cloud for the Octopus Tentacle communication channel.&lt;/li&gt;
  1714. &lt;/ul&gt;
  1715.  
  1716. &lt;h2 id="security-and-compliance-programs"&gt;Security and compliance programs&lt;/h2&gt;
  1717.  
  1718. &lt;p&gt;We're dedicated to maintaining and continuously improving our security and compliance programs alongside &lt;a href="https://roadmap.octopus.com" rel="nofollow"&gt;continued product improvements&lt;/a&gt;. We undergo regular third-party audits and technical assessments of our data security to ensure privacy and safety.&lt;/p&gt;
  1719.  
  1720. &lt;p&gt;Our security credentials include:&lt;/p&gt;
  1721.  
  1722. &lt;ul&gt;
  1723. &lt;li&gt;SOC 2 Type II: This demonstrates the robustness of our controls around security, privacy, availability, and confidentiality in Octopus. It reflects our commitment to earning and maintaining customer trust in our product and service.&lt;/li&gt;
  1724. &lt;li&gt;ISO 27001:2013: This certifies that Octopus’s information security management system meets industry-standard requirements for protecting customers’ information.&lt;/li&gt;
  1725. &lt;/ul&gt;
  1726.  
  1727. &lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt;
  1728.  
  1729. &lt;p&gt;At Octopus, security is everybody's business. We're continuously making product improvements to meet the security needs of our customers. We're also dedicated to security and compliance programs. We pride ourselves on making Octopus a secure product for our customers.&lt;/p&gt;
  1730.  
  1731. &lt;p&gt;Happy deployments!&lt;/p&gt;
  1732. </content>
  1733.  </entry>
  1734.  <entry>
  1735.    <id>https://octopus.com/blog/config-as-code-runbooks</id>
  1736.    <title type="text">Configuration as Code for Runbooks</title>
  1737.    <published>2025-03-03T14:00:00Z</published>
  1738.    <updated>2025-02-20T04:17:48.0779407Z</updated>
  1739.    <author>
  1740.      <name>harriet.alexander@octopus.com, Octopus Deploy</name>
  1741.    </author>
  1742.    <link href="https://octopus.com/blog/config-as-code-runbooks" />
  1743.    <content type="html">&lt;p&gt;&lt;img src="https://i.octopus.com/blog/2025-03/config-as-code-runbooks/img-configascode-runbooks-2024.png" alt="Graphic of a woman sitting on a large stack of books while working on laptop, surrounded by large, three-dimensional curly braces." /&gt;&lt;/p&gt;
  1744.  
  1745. &lt;p&gt;Config as Code for Runbooks is officially landing as part of Octopus 2025.1. This feature gives you a seamless, version-controlled way to manage your runbooks.&lt;/p&gt;
  1746.  
  1747. &lt;p&gt;You can run, create, and track your runbooks in your chosen Git repository, bringing your runbooks together with your deployment process. This means fewer places to make changes and provides more control over your workflows.&lt;/p&gt;
  1748.  
  1749. &lt;h2 id="why-config-as-code-for-runbooks"&gt;Why Config as Code for Runbooks?&lt;/h2&gt;
  1750.  
  1751. &lt;p&gt;&lt;a href="https://octopus.com/docs/runbooks"&gt;Octopus Runbooks&lt;/a&gt; automates routine and emergency operations tasks. Storing your runbooks in your Git repo with your application code, deployment process, and non-sensitive variables unlocks the full power of version control.&lt;/p&gt;
  1752.  
  1753. &lt;ul&gt;
  1754. &lt;li&gt;Store your runbooks in your Git repo to stay in sync. You can make and test changes alongside your app code, so your code and operational processes never get out of sync.&lt;/li&gt;
  1755. &lt;li&gt;Store your runbooks in Git to version-control your operational tasks. This way, you can manage versions with minimal effort. If you need to roll back or retrieve an earlier configuration, you can run the runbook for a specific commit or tag.&lt;/li&gt;
  1756. &lt;li&gt;Access the complete history for auditability. You can review all changes via pull requests, providing a full history of all changes to your runbooks.&lt;/li&gt;
  1757. &lt;li&gt;Rollback easily. Mistakes happen! But with version control in place, it's easier than ever to revert to a previous version of your runbooks. The complete history lets you track and manage past configurations.&lt;/li&gt;
  1758. &lt;/ul&gt;
  1759.  
  1760. &lt;h2 id="how-to-use-config-as-code-for-runbooks"&gt;How to use Config as Code for Runbooks&lt;/h2&gt;
  1761.  
  1762. &lt;p&gt;Version control is a requirement for Config as Code for Runbooks.&lt;/p&gt;
  1763.  
  1764. &lt;ul&gt;
  1765. &lt;li&gt;If your projects are version-controlled, the setup and migration is quick and easy. You'll also find using Config as Code for Runbooks natural. Following Git principles will make the process straightforward.&lt;/li&gt;
  1766. &lt;li&gt;If you're not using version control yet, you can enable it and start using Config as Code for Runbooks. &lt;a href="https://octopus.com/docs/projects/version-control/converting"&gt;See our docs for a guide on enabling version control for your project&lt;/a&gt;.&lt;/li&gt;
  1767. &lt;/ul&gt;
  1768.  
  1769. &lt;h3 id="migrating-existing-runbooks"&gt;Migrating existing runbooks&lt;/h3&gt;
  1770.  
  1771. &lt;p&gt;If you use Octopus Runbooks, we have a tool to help you migrate to Config as Code for Runbooks.&lt;/p&gt;
  1772.  
  1773. &lt;ul&gt;
  1774. &lt;li&gt;Migration process: When you start the migration, Octopus moves your published runbooks to a new folder, &lt;code&gt;/runbooks&lt;/code&gt;, in your chosen repository. This folder stores the published snapshot and configuration from the runbook.&lt;/li&gt;
  1775. &lt;li&gt;Octopus migrates any draft versions of your runbook to a separate sub-folder &lt;code&gt;/runbooks/migrated-draft&lt;/code&gt;. You won't see these in the UI, but you can access them by moving them into the main runbooks folder using a pull request (PR).&lt;/li&gt;
  1776. &lt;li&gt;History retention: You don't need to worry about losing your history. The UI will still show your existing runbook runs.&lt;/li&gt;
  1777. &lt;/ul&gt;
  1778.  
  1779. &lt;p&gt;&lt;a href='#' data-featherlight='https://i.octopus.com/blog/2025-03/config-as-code-runbooks/configascode.gif' class='zoom' data-title=''&gt;&lt;img src='https://i.octopus.com/blog/2025-03/config-as-code-runbooks/configascode.gif' class="img-fluid center" alt='GIF of Runbooks migration process. Starting on the Runbook list, user opens the wizard, reviews changes, creates new branch, uses default commit message, reviews the migration, and completes it. Next, the Runbooks list screen automatically refreshes showing a branch selector and alert with unmigrated drafts.' /&gt;&lt;/a&gt;&lt;/p&gt;
  1780.  
  1781. &lt;h2 id="new-in-config-as-code-for-runbooks"&gt;New in Config as Code for Runbooks&lt;/h2&gt;
  1782.  
  1783. &lt;p&gt;There are a few tweaks to how Runbooks work in the Config as Code setup. We made these adjustments to improve functionality and streamline your workflow. If you're curious about these changes, &lt;a href="https://octopus.com/blog/introducing-config-as-code-runbooks"&gt;read our post, Introducing Config as Code for Runbooks&lt;/a&gt;.&lt;/p&gt;
  1784.  
  1785. &lt;div class="alert alert-info"&gt;&lt;p&gt;These changes apply exclusively to Config as Code for Runbooks. If you're not using version control, they won't impact your runbooks.&lt;/p&gt;
  1786. &lt;/div&gt;
  1787.  
  1788. &lt;h2 id="conclusion"&gt;Conclusion&lt;/h2&gt;
  1789.  
  1790. &lt;p&gt;Config as Code for Runbooks has been one of our most highly requested features. Our community wanted it, and we're excited to deliver it.&lt;/p&gt;
  1791.  
  1792. &lt;p&gt;Putting runbooks in your Git repos with your app code simplifies DevOps workflow management. It ensures everything is version-controlled and fully auditable. To see it in action, you can &lt;a href="https://www.youtube.com/watch?v=oRWKDUzYBYA" rel="nofollow"&gt;watch our webinar&lt;/a&gt;.&lt;/p&gt;
  1793.  
  1794. &lt;p&gt;Config as Code for Runbooks has rolled out to Cloud customers and will be available soon for self-hosted customers in the 2025.1 release. We can't wait for you to try it out and experience the benefits for yourself.&lt;/p&gt;
  1795.  
  1796. &lt;p&gt;Happy deployments!&lt;/p&gt;
  1797. </content>
  1798.  </entry>
  1799. </feed>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid Atom 1.0" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//feeds.feedburner.com/OctopusDeploy

Home · About · News · Docs · Terms

 
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda