automation/scripting, declarative environment minimizes or eliminates this need ● Declarations are yaml files which are easily stored and managed in git OpenShift GitOps Principles ● Separate application source yaml everywhere? Kustomize - What is it? Kustomize lets you customize raw, template-free YAML files for multiple purposes, leaving the original YAML untouched and usable as is. ● Kustomize is a patching all environments DEVELOPING ON Kubernetes ● Dedicated GitOps view ● View all app groupings ● Drill into app grouping details to get visibility into the composition and status of the applications/workloads

deployments along with their associated metrics. On the other hand, anybody should be able to drill down and look at a specific deployment and the business value it contains, along with the exact

has fostered a whole new way of thinking about application deployment, because con- figuration files are used to declare the creation of container instances and dictate how the platform goes on to deploy 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 YAML) maintain them easily and immediately understand what they define. You can think of configuration files as the “code” for the infrastructure. Thus, Infrastructure as code lets administrators leave behind

CONFIGURATION DRIFT DETECTION A GitOps approach suggests that your declarative configuration files and application code should be stored together in the Git repository. This is what we call the and SRE teams are adopting GitOps so that you can store all your infrastructure configuration files as code. GitOps innately has Infrastructure as code as one of its characteristics. STRONGER below: HELM Helm is based on the parameterized templating approach where all resource definition files of applications are templated to make them customizable based on the requirement. Nowadays, it is

microservice repo and in that repo, you bundle your application code along with deployment YAML manifest files or a Helm chart that define how your application will run in your cluster. When you push that code com/microservices-demo/microservices-demo - This is the repo that stores the Kubernetes configuration files for the application. The Weave Cloud deployment agent automatically updates the front- end YAML manifest ssh URL with the path to the YAML files for the microservices-demo: SSH URL: git@github.com:/microservices-demo Path to YAML files: deploy/kubernetes/manifests

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 challenges detail with ready-to-be-used configuration files. #IstioCon What is covered in the talk ● Istio multicluster installation and setup ● All configurations in files ● Traffic management offerings in action

│ ├── ingress.yaml │ ├── prometheusrule.yaml │ ├── deployment.yaml │ └── service.yaml ├── files ## templates 依赖的各种文件 │ ├── http-probe.sh │ ├── offline

staging- api, testing-api, pre-prod-api, Prod-api) 6 解決辦法? •寫5份deployment 的yaml 嗎？ •需要維護5份yaml files •一份deployment yaml在用sed replace嗎? •容易出錯 •把他打包成Helm chart嗎？在帶入variable 嗎？ •複雜度過高 7 Kustomize

GitOps is based on the declarative nature of Kubernetes and its automatic deployment of committed files. GitOps leverages these attributes according to the four following principles: Kubernetes is just

workload by defining every application and infrastructure resource as declarative configuration files, allowing for rapid, repeatable, and error-free provisioning of infrastructure. Popular tooling