Target Audience ● Topics covered / NOT covered ● About Istio Multicluster ● Brief brush up on Istio resources ● First Demo ● About GitOps ● Second Demo ● What’s Next? #IstioCon Who is Ryota? ● Find me at 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 with other business applications, where 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 as: ● Multicluster ● GitOps integration

Seamless Kubernetes deployment to any cloud or on-premises environment Autoscaling of cloud resources One-click updates for platform, services, and applications OpenShift and GitOps - A Perfect Match master syncPolicy: automated: prune: false selfHeal: false ● Argo CD Application is a Custom Resource (CR) that defines the app in a declarative manner ● Application definition includes: and overlays. ● A base is a directory with a kustomization.yaml file that contains a set of resources and associated customization. ○ A base has no knowledge of an overlay and can be used in multiple

between environments 1.4. Modeling multi-environment configurations 1.5. Auto-scaling and dynamic resources 1.6. GitOps rollbacks 1.7. Observability 1.8. Auditing 1.9. Running at scale 1.10. GitOps modeling multi-environment configurations 5. GitOps breaks down with auto-scaling and dynamic resources 6. There is no standard practice for GitOps rollbacks 7. Observability for GitOps (and Git) easy answer​ on what is the correct approach. GitOps breaks down with auto-scaling and dynamic resources One of the critical points in GitOps is that after a deployment has finished the cluster state

First, a system in this context is defined as one or more runtime environments consisting of resources under management, the manage- ment agents within each runtime, and the policies for controlling scale their application instances to take advantage of the seemingly unlimited amount of compute resources provided by cloud comput- ing. The old methods of managing and configuring infrastructure wouldn’t manifests are stored inside Git. So the question often becomes, “How do I declaratively describe my resources in Git without copying and pasting the same YAML everywhere?” It might seem like you’ll have to

developer experience is to leverage the internal platform approach. An internal platform helps to get resources to developers on-demand and in a secure way. FAANG and startup companies are increasingly building administrator. In the modern era, however, developers require on-demand access to a variety of tools and resources that enable them to be more productive and deliver applications more quickly. The tools and services just about providing better tools. It’s about providing a better way to access these tools and resources that eliminate obstacles. Developers should not have to file a list of support tickets and wait

CI and Connect a Container Registry Part 4: Let’s Get Started with GitOps Further Resources 11 14 21 23 31 36 eBook 3 GitOps in Practice A “you build it, you own it” development With the operator pattern, an agent acts on behalf of the cluster. It listens to events relating to custom resource changes, and then applies those changes based on a deployment policy. The agent is responsible is running on it. 1. Step through the setup screens and choose Generic Kubernetes. 2. Run the custom command that appears on your master node. After running the command, you will see several objects

and Cloud-Native Buildpacks Extend to use community Kubernetes builds strategies or your own custom builds Kubernatives-native image build Supports multiple build strategies Extend with additional cycles Everything lifecycled as container images No interoperability with Kubernetes resources Native Kubernetes resources Admin manages persistence Platform manages persistence Config baked into CI engine

has adequate resources available, the updated cluster state will depend only on the desired state. Kubernetes deployments can also be extended and automated using Kubernetes Custom Resource Definitions

infrastructure and application configuration in the repository to detect when the Kubernetes cluster resources should automatically update based on config changes. GitOps Operator Infrastructure Code Application implementing IaC tooling and best practices. The process involves managing and provisioning infrastructure resources using code rather than manual processes or interactive configuration tools. Ultimately this means These tools provide the necessary capabilities to define, provision, and manage infrastructure resources using code. Designing Your GitOps Strategy | 11 3 KEY ELEMENTS FOR YOUR GITOPS STRATEGY

details related to infrastructure changes such as Responsible users Deployment data time Affected resources Etc. The GitOps approach also helps to streamline the management of authentication and authorization infrastructure is a part of the CI/CD pipeline, individual developers do not require direct access to resources, hence not needing credentials to access said resource. This also makes it necessary for users the time of execution in the pipeline. This further enforces strict access controls to underlying resources reducing attack vectors to the infrastructure. However, we have to properly implement GitOps as