Since the advent of DevOps in 2009, the Pandora box of XOps has been opened: AIOPS, DataOps, DevSecops, BizDevOps, and of course, Gitops, which has been popular in recent years. Unfortunately, on the eve of the Year of the Dragon, we**eworks, the theorists of Gitops, fell. Back on February 5th, just when everyone was looking forward to the Spring Festival holiday, the news of the imminent collapse of We**eWorks Company swept the cloud native technology circle. Alexis Richardson, CEO of We**eWorks, posted a message on LinkedIn:
Translate this passage directly into Chinese with chatgpt: Hello everyone, I am very sorry to announce - officially - we**eworks will close its doors and cease commercial operations. Customers and partners will work with a financial trustee that we will announce shortly. The company has achieved double-digit turnover (more than $10 million) and has more than doubled the number of new product logos in 2023. However, this sales growth is volatile, and as a result, our cash position is unpredictable. We need a partner or investor for long-term growth. In the end, a very promising M&A process with a larger company ran aground at the last minute. Therefore, we decided to close. I can only apologize to everyone for this difficult turn of events. I can say that shouldn't happen, but I know we're not alone in this market. Larger ships have also been lost. The We**Eworks team is a special team and it's been a long and difficult journey. I know everyone is very motivated to do their best for our customers, our open source community, and each other. You guys are doing a great job and you can be proud. We will always have a common story. Our story is very exciting - from the very beginning of the container, born with difficulty. The day someone successfully runs kubernetes on Azure for the first time. The beginnings of the CNCF. The day we struck out the system with one click. The first months of the pandemic. Then there's the investment and the work we've done to solve the gitops problem for many amazing enterprise clients. Of course, there were difficult moments, but we solved them together for the most part. You share all of this, and everyone deserves fond memories of their work and the privilege of knowing that you are all among the best. The story doesn't end here – our open-source software is everywhere. I'm working with several large organizations to make sure cncf flux is in the healthiest condition it can be. More on that later. I'd like to invite anyone who reads this and wants to know what's next or help, please reach out to me! Thank you. We will not stop exploring, and the end of all our explorations will be to reach the place where we started and get to know this place for the first time. Reading between the lines, it can also be seen that although We**Eworks has a certain revenue (tens of millions of dollars), the instability of the market has also made the operation of We**Eworks difficult, and finally had to make the decision to close We**Eworks Company, but its open-source project on Gitops Flux will continue to run healthily (because it was donated to CNCF). Founded in 2014 with more than 200 employees and $36 million in funding, We**eWorks proposed the concept of Gitops in 2017 based on their experience in cloud computing and open-sourced Flux, a project related to Gitops. In recent years, Gitops has also been popular in China, and many companies with cloud-native transformation are using Gitops to achieve CD. According to gitopsTech Definition of Gitops: Gitops is a continuous deployment of cloud-native applications. Gitops can help improve the R&D experience for R&D personnel, because they only need to use their own familiar tools (Git or even IDEs) to develop without having to learn other complex tools. gitops is a way of implementing continuous deployment for cloud native applications. it focuses on a developer-centric experience when operating infrastructure, by using tools developers are already familiar with, including git and continuous deployment tools.Kelsey Hightower, a well-known Kubernetes evangelist and Google engineer, explains Gitops as a versioned CI CD on top of a declarative infrastructure layer. This allows you to deliver your application without having to write scripts. gitops: versioned ci/cd on top of declarative infrastructure. stop scripting and start shipping.Gitops has three core philosophies:Everything is **: Because gitops wants to make everything (applications, infrastructure) **, and then use git for version control. Changes to applications or infrastructure are also made through Git. Because around this point there are IAC (Infrastructure as Code), Security Policy as Code, and so on. The security policy is **.
git is a single source of truthIn :gitops, all changes are initiated from the git side (such as JiHu Gitlab), so that version control can be carried out, which is convenient for security and auditing.
The declarative system is the base: One of the characteristics of a declarative system is that it can automatically sync the desired state of the application (and infrastructure) with the actual state.
The closure of We**eWorks is a sad thing for the entire industry, but the Gitops concept it proposed is not going to go away with the fall of We**Eworks. Because the concept of Gitops does greatly simplify the deployment of cloud-native applications, and its open-source tool for implementing Gitops, Flux, will not die, because it is donated to the CNCF ** Association, and the open source community will continue to maintain the Flux project. In addition, in addition to We**eWorks, there are other companies or products that can implement Gitops, such as CodeFresh's Argocd and JiHu Gitlab's KAS (Kubernetes Agent Server). 
JiHu GitLab itself is a Git platform, and its own capabilities are naturally in line with the concept of Gitops, and you can use JiHu GitLab to version control the most advanced applications or infrastructure. 
In this case, JiHu Gitlab can be directly integrated with two tools related to Gitops: Flux or Argocd. Use JiHu GitLab as the single trusted source of Git, and Flux or Argocd to implement the application deployment function of Gitops. For this part, please refer to the previous technical article: JiHu GitLab and ArgoCD Integration Implementation of Gitops
JiHu GitLab integrates with Flux to implement Gitops
Of course, JiHu Gitlab's built-in KAS can also implement Gitops:
For more information, see the technical article Implementing Gitops with Kubernetes Agent Server. As mentioned earlier, Gitops is all about everything, and one of the important concepts is that IAC (Infrastructure) GitLab can not only host IAC-related files, but also perform security scans for IAC. For more information, please refer to the technical article JiHu GitLab IAC Security Scan to ensure cloud-native security. For more information about the best technical practices in the DevOps industry, please visit [JiHu GitLab] or search the official website of JiHu Gitlab.