Pulumi Kubernetes Operator Summary 18 Chapter 3–Templating Everything in Git Kustomize Helm Operators Combining Tools Summary The Path to GitOps | 3 Contents 22 Chapter also work with Helm [2.2] and Kustomize [2.3] to render the YAML produced by those tools before applying them to the Kubernetes cluster. (We’ll look at Helm and Kustomize more closely in upcoming chapters GitOps Toolkit, and were based on controllers. These components include the source controller, the Kustomize controller, the Helm controller, the notification controller, and the image automation controller

triggered from Git Tools of the Trade https://argoproj.github.io/argo-cd https://kustomize.io/ Argo CD Kustomize Argo CD - What is It? Argo CD is a declarative, GitOps continuous delivery tool state with git repos ● Works with a variety of Kubernetes deployment tools including: ○ Helm ○ Kustomize ○ Ksonnet/Jsonnet ○ Directories of yaml ● It is not a CI tool What is an Argo CD Application into it ○ Deploy required infrastructure before application (try to avoid this) ● Tools like kustomize and helm will handle this automatically in some cases ● Argo CD provides Sync Phases and Waves

memcached-sample app.kubernetes.io/part-of: memcached-operator app.kubernetes.io/managed-by: kustomize app.kubernetes.io/created-by: memcached-operator name: memcached-sample spec: size: 3 OpenShift ${OPERATOR_IMAGE:-""} operator_pull_policy: ${OPERATOR_PULL_POLICY:-"Always"} kustomize: ${KUSTOMIZE_PATH:-kustomize} env: K8S_AUTH_KUBECONFIG: ${KUBECONFIG:-"~/.kube/config"} verifier: make run 命令： 输出示例 出示例 现在，Operator 会监控 CR 的事件，创建 CR 将触发您的 Ansible 角色运行。 $ make install /usr/bin/kustomize build config/crd | kubectl apply -f - customresourcedefinition.apiextensions.k8s.io/memcacheds.cache

yaml #Required ``` KUSTOMIZE Apart from the Parameterized Templating, another approach to manage is Overlay Configuration. Kustomize is a configuration management tool based based on this approach one. Kustomize works off a concept of “where, what, and how” to refactor specific Kubernetes manifests. The “where” to refactor/change are the base manifests, e.g., a deployment replica count, volume mounts, etc. The “how” to change are the kustomization/config files. Kustomize file structure example: ├── base │ ├── deployment.yaml │ ├── kustomization.yaml └── overlays

complex rollouts ● Rollback and rollforward to any Git commit ● Manifest templating support (Helm, Kustomize, etc) ● Visual insight into sync status and history OPENSHIFT GITOPS 29 An application scoped Configures webhooks for Tekton Pipelines for CI ● Configures Argo CD for deployment to environments ● Kustomize for environment-specific configs ● Integration with secret managers $ kam bootstrap $ kam environment

can and should focus on feature development @codefresh Practicing GitOps ● Templating: Helm, Kustomize, and more ● Configuration Drift: Monitors live state against desired state ● Enterprise Ready: