Shulou(Shulou.com)05/31 Report--

This article to share with you is about GitOps working group project refers to what, Xiaobian think quite practical, so share with you to learn, I hope you can read this article after some gains, not much to say, follow Xiaobian to see it.

The goal of the GitOps WG is to provide companies and individuals with the skills, knowledge, and capabilities to implement GitOps tools and methodologies to simplify the operation and management of infrastructure and cloud-native applications.

The initial task of the group will be to issue a GitOps manifesto that clearly defines the principles and technical aspects of GitOps. The GitOps Manifesto will be vendor and implementation-neutral and aims to build a common understanding of the GitOps system based on shared principles rather than individual perspectives. The second goal is to encourage innovation by clarifying technical outcomes rather than the code, testing, or organizational elements needed to implement them.

More and more people adopt GitOps

The GitOps Working Group was formed as a result of accelerated adoption of GitOps tools and methodologies by users of Amazon, Codefresh, GitHub, Microsoft, Weaveworks, and hundreds of other leading global companies that are adopting GitOps. This, coupled with the CNCF user community recommendation for Flux[2], indicates that GitOps is rapidly becoming the preferred method for operating modern cloud-native infrastructure and applications. The CNCF user community reports that development, DevOps, and operations teams that adopt GitOps tools and follow best practices have improved productivity, stability, reliability, and security in their cloud-native environments.

What is GitOps and why?

If you're new to GitOps, it builds and iterates on ideas extracted from DevOps and infrastructure as code, starting with Martin Fowler's comprehensive Continuous Integration overview [3] and offering the freedom to choose tools based on your particular use case.

There are many benefits for individuals, teams, and organizations implementing GitOps, including:

Improved developer and operational productivity Enhanced developer experience Improved stability Greater reliability Consistency and standardization Robust security GitOps principles

To give participants in the cloud-native ecosystem a clear understanding of what GitOps means and to further realize these benefits, the working group's creators defined five core principles for GitOps practice.

The five principles of GitOps are as follows:

Declarative configuration: All resources managed through the GitOps process must be fully represented declaratively. Versioning, immutable storage: Declarative descriptions are stored in repositories that support immutability, versioning, and version history. For example, git. Automated delivery: Delivery of declarative descriptions, from repository to runtime environment, is fully automated. Software Agents: Coordinators maintain system state and apply resources described in declarative configurations. Closed loop: Actions are performed based on differences between the declarative configuration of version control and the actual state of the target system. Open Working Group

The founders of the GitOps Working Group are creating a neutral working group to clearly define the principles of GitOps--guiding meaning--for better interoperability between tools. With a clear definition, personal GitOps certification programs will also be possible.

The GitOps Working Group announced today that its founders are inviting companies and individuals active in the fast-growing GitOps ecosystem to join this new community and help it succeed as a standard!

About GitOps Declaration

The founders of the GitOps working group envisioned creating a GitOps manifesto that would make it easier for companies to understand the key principles of GitOps while driving interoperability among the tools that embody those principles.

How to participate

With the announcement of the GitOps working group, the founders hope to invite other companies to join the working group to contribute to the adoption of GitOps by the community and across cloud-native landscapes. You can get involved in several ways:

Watch or tag this repository to keep it updated. Attend a working group meeting (schedule coming soon). Open a question [4] and let us know how you use GitOps and any important considerations we should include. Add #wg-gitops to CNCF Slack [5]

We will review all outstanding issues and PRs at our regular working group meetings (schedule coming soon).

Timeline

The founders of the GitOps Working Group aim to, first, form the Working Group in the fourth quarter of 2020 and, second, establish the GitOps Manifesto V1 by the end of March 2021. If you are interested in keeping up with any new developments, please visit Follow this repository.

additional information

The CNCF App Delivery SIG documents GitOps principles as an OSS project and supports WG GitOps.

The above is what the GitOps working group project refers to. Xiaobian believes that some knowledge points may be seen or used in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.