Flux OCIRepository: the GitOps that stopped using Git
Flux has shifted its GitOps approach from using Git as the primary source to utilizing OCI registries. This change allows for a more efficient and secure method of managing configurations by treating the registry as the source of truth. The move aims to simplify the process and enhance security by removing the complexities associated with Git authentication and history management.
- ▪Flux now uses OCI registries instead of Git for managing configurations.
- ▪The new approach eliminates the need for the cluster to pull from Git, reducing overhead.
- ▪By using content-addressed delivery, the exact configuration used in staging can be guaranteed to be the same in production.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3723238) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Ilia Gusev Posted on May 20 • Originally published at podostack.com Flux OCIRepository: the GitOps that stopped using Git #kubernetes #gitops #devops #cncf Originally published on Podo Stack Ask ten platform engineers what GitOps means and at least eight will say "the cluster pulls manifests from Git." That's the part everyone remembers, and it's the part Flux is quietly walking away from. The new default isn't Git.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
