GitOps Goes the World
Music: Gossip - Pop Goes the World (2009)
This week we take a look at GitOps and Policy-as-Code (PaC).
Getting Informed
Fudge Sunday readers might recall the pipeline topic and the shifting left stories previously covered.
Underneath The CNCF Tech Radar
A look at emerging cloud native topics
Fudge Sunday - Once in a Pipeline
A look at FinOps via Fuller, Franklin, Talking Heads, and Cunningham
Clearly there are many Cloud Native Computing Foundation (CNCF) projects. Projects are often the result of seeking answers to questions. But there are still questions to be answered…
- What if everything in the software lifecycle from developer to operations drew from one true source?
- What if everything in software versioning currency extended automation from the source to the service?
Such questions provoked neologisms from version control systems favored by software developers (Git) and IT practitioners presiding over services that express a particular version of software produced by developers (Ops). Or, for short, you could argue the answer to these (and other) questions is increasingly referred to as _GitOps_.
- What if there was a way to ensure security in our software supply chain?
- What if there was a way to anticipate multiple tenants, multiple feature flags, and compliance?
- What if there was a way to draw from Infrastructure as Code (IaC) concepts and apply those to policies associated with use of IaC?
Such questions were provoked companies bringing software into existence using IaC — continuously delivered — securely. Or, for short, you could argue the need for easily maintained and applied policies in the form of code aka _Policy-as-Code_ (PaC).
Find yourself in a situation 🎶
https://opengitops.devAnd now, on to the next CNCF project…
