“When you start doing things in a cloud-native way, old rules don’t apply”
Cloud development led us first to DevOps. But some are already declaring DevOps as the new legacy and that a new paradigm is needed to meet the needs of cloud-native development Enter GitOps. Initially proposed by Alexis Richardson, GitOps offers to be the new community of practice where we push code not containers and perform operations by pull request.
The most valuable concept that falls under the GitOps umbrella is the Mean Time to Recovery (MTTR). Simply put: If your system failed completely, how long would you take to get it up and running from scratch? Using GitOps, Alexis’ team can recover in five minutes. Five minutes. That underlines the ultimate promise of GitOps.
For Jenkins users, configuration-as-code is the new way to achieve this. Jenkins X rethinks CI/CD in the cloud and uses git as a source of truth and ensures mean-time-to-recovery is a priority from the start.
SEE ALSO: GitOps, Jenkins, and Jenkins X
We caught up with Tracy Miranda, Director of Open Source Community for CloudBees at JAX London 2018 to talk about the concept behind GitOps, how Jenkins X fits into this rather new approach and more.
Here are some quotes from the interview:
- Lots of people are saying the term DevOps has become overused.
- What DevOps was to cloud, GitOps is to cloud-native.
- DevOps was really good when we moved to the cloud but now when talking about going cloud-native, we need something new; GitOps is the next level.
- When you start doing things in a cloud-native way, old rules don’t apply.
- Jenkins X was designed with the idea of GitOps in mind.
- Jenkins X builds on Kubernetes but it really simplifies it.
- Jenkins X takes away the choice but it saves you time by making decisions for you
Learn more about Jenkins X here.
The post “What DevOps was to cloud, GitOps is to cloud-native” appeared first on JAXenter.
Source : JAXenter
