handle this automatically in some cases ● Argo CD provides Sync Phases and Waves to address other use cases ○ Three sync phases - Pre-sync, sync, post-sync ○ Within each phase can have multiple waves Kustomize vs Helm vs OpenShift Templates Patching framework Ability to apply yaml directly Some use-cases may work better with templates No support in OpenShift GUI console Great for enterprise teams applications across multiple organizations OpenShift specific templating solution Easy to understand and use First class support in OpenShift GUI console Templates are static, no support for dynamic scripting/variables

teams. weave.works THE GITOPS GUIDE TO BUILDING & MANAGING INTERNAL PLATFORMS 4 ▼ Score for “high use” DevOps evolution Stream-aligned teams are essentially application development teams that build features deploying new features and updates with little or no friction. The internal platform approach Use of internal platforms and level of DevOps evolution Source: Puppet While there are many ways to deliver favorite approach of high-performing DevOps teams is to deploy an internal platform that developers use to create and access the resources they need on their own. THE GITOPS GUIDE TO BUILDING & MANAGING

system configuration state, i.e., infra config code present in Git. This makes rollbacks easier in case your desired state in Git results in system instability for your actual state present in the cluster change to Git with version number 1.0.1 and push those changes. In case 1.0.1 does not bring the expected results, then you can just use “Git revert” to rollback those changes from Git. Then your actual Self-healing abilities − I.e., restarting of the failed containers, replacing, or rescheduling Pods in case of underlying nodes issues • Horizontal scaling capabilities to scale up and down based on CPU

with a lot of familiar concepts that seem unrelated. Is GitOps something that application developers use? Is it for infra- structure folks or system administrators? Is it something you can buy off the shelf changes that have been made. Although Git is a good example of this principle, you don’t need to use Git as your state store. Anything that complies with this principle can be used in GitOps (S3 storage behind manual processes and avoid the drudgery of entering fields into a web form. Instead, they use configuration files to manage every component of the datacenter, from bare metal servers to virtual

development process requires tools that developers know and understand. GitOps is our name for how we use developer tooling to drive operations. GitOps is a way to do Continuous Delivery. More specifically roll out changes to your infrastructure when commits are pushed and approved in Git. It also makes use of diff tools to compare the actual production state with what’s under source control and alerts select a set of tools from the open source ecosystem or from closed source or depending on your use case, you may even combine them. The most difficult part of creating a pipeline is gluing all of the

creating a commit or opening a pull request Specifically for Kubernetes, GitOps says that you must not use `kubectl` to change the cluster state in an ad hoc manner. Instead, the desired state should be defined straightforward GitOps has been heralded as a way to decouple CI from deployments. In the classic use of a CI/CD system, the last step in the pipeline is a deployment step. Classic pipeline all the testing frameworks and libraries needed for the tests. This means that you are forced to use your CI solution again in order to run the smoke tests. The end result is a mixture of CI-CD-CI-CD

to learn new tools. On the pages that follow, we’ll explain exactly what GitOps is and how you can use it to deliver positive results in your organization. How GitOps Boosts Business Performance: entire cluster can be rolled back and rebuilt with ease. The simplest way to implement GitOps is to use Git, since it already includes many advantages such as built-in security guarantees with full audit learn Because Git lies at the centre of the delivery pipeline, developers do not need to learn to use new tools. They can work in a world they know, using pull requests to accelerate deployment and operations

Git to manage Kubernetes more rapidly. Recover in minutes Use Git as the single source of truth to revert/rollback and fork in the case of a catastrophic event. Meet compliance requirements Build complete Kubernetes platforms. By keeping the configuration in Git, developers and operators can use WKP to easily define, administer, and install repeatable platforms with all their add-ons and components Read the Comprehensive GitOps primer weave.works/gitops Watch Weaveworks’ workshops about how to use GitOps on AWS engine https://weaveworks-gitops.awsworkshop. io/05_introduction.html To learn more

gold standard for managing and deploying Kubernetes applications. In this talk, we’ll show you how we use raw Kubernetes, in addition to Helm and Terraform to manage our deployments to a wide range of clusters Argo and Codefresh Description: Never make a manual change again. In this talk we’ll show how to use GitOps to achieve reliable, and fast releases time and time again. Rather than pushing changes, Argo

如何開始實踐 GitOps 1. IaC 2. Automation 3. Code Review & Approve 4. Multi environment 5. CI/CD 6. Use Repository 7. Agile & Iteration DevOps 1. IaC 讓⼀切都成為 Code 2. Automation 盡可能⾃動化 如果不成，就紀錄它！ 3. Code Review & Approve 審查、複閱、檢查、稽核 4. Multi environment 運⽤在所有的環境！ 5. CI/CD ⾃動化的唯⼀觸發點！ 6. Use Repository 分⽀策略、Flow、Workflow 7. Agile & Iteration ⼩粒度、多迭代 Tools VCS CI CD Container Registry