2 years ago

Category: Microsoft, Kubernetes, github

Engineers from GitHub, Microsoft, CodeFresh, https://www.weave.works/?utm_content=inline-mention, https://www.openshift.com/try?utm_content=inline-mention and other cloud native-savvy companies have banded together to put together a set of definitions and conformance specifications for https://thenewstack.io/what-is-gitops-and-why-it-might-be-the-next-big-thing-for-devops/. “A lot of people think that they’re doing GitOps because they’re using git and they’re doing pull requests and pushing changes out,” said https://www.linkedin.com/in/leonardomurillo, a co-chair of the GitOps working group.

GitOps must meet these four requirements, according to the group: Declarative: A https://github.com/open-gitops/documents/blob/v1.0.0/GLOSSARY.md#software-system managed by GitOps must have its desired state expressed https://github.com/open-gitops/documents/blob/v1.0.0/GLOSSARY.md#declarative-description.

“The only way for you to introduce change in your system is by creating a new version of your desired state,’ Murillo added.

The GitOps model could be far-reaching, extending beyond application management to uniform management of clusters and even entire operating environments.