Octopus and GitOps (internal)

[mcasperson]

Read the RFC (Internal post)

We want your feedback to determine if this feature is a good fit for Octopus. Some questions are:

• Is integrating Octopus with GitOps workflows like those used by ArgoCD and Flux valuable?
• Does the idea of writing templates to a git repository make sense?
• Will these proposed features solve problems you have seen customers encountering?
• Would first class GitOps support be valuable for your teams in terms of sales, marketing, or solutions?

[mcasperson]

I caught up with @ryanrousseau to discuss these pitches, these are the notes:

• We don’t see many customers running Flux or Argo today.
• When Flux or Ago come up in discussions, it is because they are being considered for K8s deployments, or some other teams have implemented them in their own skunkworks projects.
• We’re not losing sales because we can’t integrate with Flux and Argo.
• This pitch only solves for “left of the git repo”, so any team looking to “do GitOps” still needs to have the appropriate tooling “right of the repo”. This can make our solution hard to explain and sell.
• GitOps is a nebulous term and an immature platform, and it may be too early to offer concrete implementations.
• Generally speaking Ryan is suspicious of GitOps as a practice (I tend to agree).
• We are likely better off adopting a wait and see approach with GitOps.