the steps previously handled by large teams must be adopted. The monolithic application should be split up into microservices that can each be owned by a single team. Organizational leaders must also create

yaml. The “what” to change are the overlays or small snippets of YAML to change, e.g., a replica count, volume mounts, etc. The “how” to change are the kustomization/config files. Kustomize file yaml └── overlays ├── dev │ ├── replica-count.yaml │ └── kustomization.yaml ├── production │ ├── replica-count.yaml │ ├── kustomization.yaml └── staging staging ├── kustomization.yaml └── replica-count.yaml JSONNET Jsonnet is a programming language open-sourced by Google that provides configuration management as one of its main features

controlling access and manage- ment of repositories, deployments, and runtimes. Second, note the reference to the desired state. This means that you represent the way you want the system to work in an “end format) but rather in a secret management system. Only a reference to the secret is stored in Git. You can safely store this reference because the reference contains no sensitive information. When the secret store an encrypted version of the secret in your Git repository. The second method is storing a reference of the secret in Git while another platform manages that secret. Both solutions are quite popular

Managed Deployment Pipeline Managed Deployment Pro Consistent Post-Test update of image reference Con Image reference updated in git before integration tests, manage rollback? Inconsistent Con Pipeline structure provides flexibility ○ Overlays can leverage other bases and overlays ○ Overlays can reference remote repositories ● Included with kubernetes since 1.14 ● Validates yaml before deployment

your GitOps tool will start fighting against you. Some classic examples are: ● The replica count if you have an autoscaler in your cluster ● The resource limits if you have an optimizer in your