as the infrastructure layer managing the applications. One day there was an incident where a configuration change took down their entire hosting platform, but the DevOps engineers were able to bring back infrastructure stack instead of just one object. We’ve seen that the desired state is pulled from configuration information that is versioned and stored in an immutable storage system. If there is a difference the entire software infrastructure at a datacenter using configuration files that are both ma- chine-readable and human-readable. The configuration files are machine-readable in a structured format (usually

Ecosystems NINAD DESAI STAFF ENGINEER, INFRACLOUD CONTENTS • About GitOps for Kubernetes • Configuration Management in Kubernetes • GitOps for Kubernetes Essentials • Conclusion Git is the most experience. In the last few years, the number of tools and systems needed to manage version control, configuration management, Infrastructure as Code, CI/CD, and observability have drastically increased. This Thus, to improve developer experience, GitOps emerged where infrastructure and application configuration changes revolve around Git, i.e., the version control ecosystem. The focus is entirely on

being generic). ● It requires extra effort to keep all branches in sync (in case of hotfixes or configuration changes). ● It puts unnecessary strain on the CI system that has to check/rebuild/unit test each environment and can quickly lead to configuration duplication or people making commits to specific environments (instead of using shared configuration). For example, if you have 20 git repositories cluster. While you can provide a values.yml file on the fly when a Helm release is installed, a best practice is to also commit the values file to Git. You can have different value values for each

native tools that are “declarative” and that can be treated as code. Declarative means that configuration is guaranteed by a set of facts instead of by a set of instructions. With your application’s continuous integration environment Runs inside the production cluster Read/Write access to configuration repository Read access to image repository Read/Write access to the production cluster GitOps clicking on the Explore tab. For automated deployments and GitOps, there is one additional configuration step that we will cover in part two of this tutorial. Part 1: Spin up a Kubernetes Cluster

have no visibility or record of configuration changes in environments I can’t easily rollback changes to a specific version I can’t audit configuration changes 4 ● All changes are auditable OpenShift and GitOps - A Perfect Match ● OpenShift is a declarative environment ○ Cluster configuration is declared and Operators make it happen ○ Application deployments are declared and Kubernetes Duplication Argo CD enables deployment across multiple clusters, awesome! Wait, how do we manage configuration without copying and pasting yaml everywhere? Kustomize - What is it? Kustomize lets you customize

better way to access these tools and resources that eliminate obstacles. Developers should not have to file a list of support tickets and wait forever to get what they need. It’s a good idea to have a consistent entire software stack through Git and treat your servers as your source code. Every change and configuration is done through a pull request and everyone has access to the application, which can be rolled you should trust the platform you are building on. With GitOps, you can make sure that each configuration change is verified by your peers and automatically tested before it is deployed. Your platform

#IstioCon Target audience ✅ If you want to ... ● play with Istio offerings ● see the actual configuration files ● understand how Istio can be used / installed with other services ● know what multicluster Install into some cluster ● Tweak some simple configuration ● Add / remove offerings you are keen to test and see in action ● Add custom configuration on top of simple setup ● Install in cluster Install into some cluster ● Tweak some simple configuration ● Add / remove offerings you are keen to test and see in action ● Add custom configuration on top of simple setup With requirements such

treat everything as code – from the application code itself to the underlying infrastructure and configuration – you can keep it in version control. This means the desired state and any changes of an entire ecosystem of cloud native tools are declarative, as opposed to imperative, which allows for configuration to be treated as code. It is this declarative nature that enables the infrastructure to be held make crucial decisions before they deploy new features. Features or other updates like cluster configuration can be pushed to Git and then observed in real-time – and rolled back if necessary. This means

Production ⼀條龍 ⼯程師 Configuration Provision Code Deploy CI / CD Production ⼀條龍 ⼯程團隊 Configuration Automation Code Deploy CI / CD Production ⼀條龍 ⼯程團隊 Configuration Automation Ops / Infra GitLab 說的~ GitOps = IaC + MRs + CI/CD Infrastructure as Code Infrastructure System Configuration Application Configuration GitOps = IaC + MRs + CI/CD Merge Requests GitOps = IaC + MRs + CI/CD Continuous

@codefresh ● Predictable - Comprehensive understanding of deployment impact ○ Declarative configuration with a known end state ● Auditable - Traceable changes to infrastructure and applications ○ desired state of configuration ● Pull requests drive all application & infrastructure changes ● Cluster state always matches Git state ○ Tooling should understand and monitor for configuration drift ● Deployments feature development @codefresh Practicing GitOps ● Templating: Helm, Kustomize, and more ● Configuration Drift: Monitors live state against desired state ● Enterprise Ready: SSO, multi-cluster, and