top | item 45384325

(no title)

kritr | 5 months ago

I don’t see this article actually arguing against GitOps. It just argues that the policies in place for GitOps need to make sense for the environment you’re developing in.

Obviously, the level of auditing and reviewing for infrastructure changes in a Prod environment make no sense for a Sandbox environment, and there’s nothing in GitOps that implies these need to be the same.

Ideally at every phase of development, you have very legible infrastructure that can be shared and iterated on by a team. The CI pipelines backing this should offer rapid turnaround times, and things should be easy to test.

All things which the general GitOps concept still works in tandem with.

discuss

order

RockieYang|5 months ago

Usually GitOps have flow like checkout => modify => commit => push => PR => merge => check result. Even if we remove the merge step, still have flow modify => commit => push => check result. In which the commit & push still could be removed