My Download Engine

Your Gateway to Digital Content


Weaveworks’ closure has thrown the state of GitOps into flux.

Advertisement: Click here to learn how to Generate Art From Text

Weaveworks is soon to be gone. The company’s CEO Alexis Richardson wrote in a Post on LinkedInThe company shut down earlier this week. 

According to Richardson, while the company was bringing in over $10 million in revenue, the sales growth wasn’t consistent. The company needed a longer-term investor and was about to be acquired when the deal fell apart. 

The following follows the Recent AcquisitionsHarness has acquired the intellectual property (IP) and technology of Armory – a CD company whose IP and technology are now owned by Harness. 

Gopal Dommety of OpsMx said that although Weaveworks is one of the original innovators of the concept, it has now spread widely throughout the industry. 

“GitOps is still the right answer for fast, automated, flexible, and secure software delivery and operations,”He said. 

According to Paul Delory of Gartner Research Vice President, the industry is “indebted to them for creating this category,”The following are some of the most common questions that people ask. “clearly that didn’t translate to commercial success.”

Delory attributes it to two main factors. Weaveworks’ Flux open-source Kubernetes-based CD solution, which Weaveworks sponsored, was competing with another open-source GitOps. ArgoCD

“I feel like there was much more interest in ArgoCD of late, which is simpler to use … Functionality-wise, there’s much less daylight between the two products than there used to be,”He said.

Second, it’s possible there’s just not a commercial market for GitOps, even though there’s a lot of hype around this. There are many reasons for this, such as that it’s mainly limited for use with Kubernetes, there is a long setup process before GitOps can even be up and running, and there’s also confusion about who to sell GitOps products to: developers, IT teams, platforms teams, etc. 

Delory argues that, overall, the freely available open source market of GitOps makes it hard to justifiably buy a commercial product. 

“Even if an IT organization is amenable to your sales pitch, you’re still looking at a long, high-touch sales process while you figure out who in a particular IT organization has the desire and the budget to sign the contract,”He said. “That makes a steady stream of venture capital even more critical, while you wait out these long sales cycles. But VC money is harder to come by right now. As Alexis alluded to in his blog post, Weaveworks couldn’t get its hands on enough capital to sustain itself while its technology and sales efforts came to fruition.”

Weaveworks contributed heavily to the Flux open-source project. Many people are wondering what this means for the future. 

Chris Aniszcyk is the CTO of CNCF, the current home of the Flux project. He says that many Flux maintainers are already employed by other companies, and will continue to work on the project. 

“CNCF will do our best to notify our member companies to pitch-in when it comes to these situations like we have in the past,”He said. “The CNCF Technical Oversight Committee (TOC) reviews the health of projects often and in cases where a project is forked or is lacking maintainers, we work with our member community. Not so long ago, the Cortex project ran into issues where Grafana forked it and maintainers were moved to focus on that project. CNCF made a call to our members to see if folks can help and AWS and Red Hat stepped in.”

Richardson also stated in his LinkedIn post, that he worked directly with “several large organizations”Flux is a vital part of the future. 

“The story does not end here – our open source software is used everywhere,”Richardson said. 


‘ Credit:
Original content by “State of GitOps in flux as Weaveworks closes down”

Read the full article here ‘


Your email address will not be published. Required fields are marked *