Why Gitops aren’t ready for mainstream (yet)

Since it was built in 2017, Gitops has been deployed across distributed containers, especially for organizations building microservices orchestrated by Kubernetes, such as devops, infrastructure as code, CI / CD principles, etc. It has emerged as a natural evolution of the latest software development practices. Recent fashion.

However, there are still some important cultural and technical hurdles that the industry must overcome to enable Gitops to achieve truly mainstream adoption of agile and DevOps practices on a historical scale.

What are Gitops?

Gitops extends devops primarily by treating the infrastructure as code. This allows you to treat both your application and its underlying infrastructure as code and store it in a version control system (probably Git) to provide both dev and ops with a single source of truth. This allows you to push all changes to declarative code and perform a series of automated steps to correct deviations from the desired state.

Everything sounds great in theory, but InfoWorld at this stage among companies known to be tampering with Gitops practices (Peloton, Volvo, Ticketmaster, Just Eat, etc.) I didn’t feel like talking to him. Jim Mercer, Research Director of IDC’s DevOps Solution Practices, said:

“”[Gitops] After the acquisition of Argo CD creator Applatix in 2018, Mukulika Kapas, product management director of the internal developer platform of the fintech company Intuit, an early adopter of Gitops, said:

Instead, smaller cloud-native organizations are beginning to investigate the potential of Gitops to improve the software delivery process, while larger organizations are becoming more prevalent in cloud-native practices, such as greenfield digital initiatives and research. You may be considering Gitops in your pocket. Development center.

Copyright © 2021 IDG Communications, Inc.

Why Gitops aren’t ready for mainstream (yet)

Source link Why Gitops aren’t ready for mainstream (yet)

Related Articles

Back to top button