Join Christian Hernandez, GitOps Extraordinaire, for a journey through how to achieve GitOps in any number of ways. The occasional Red Hatters and special guest will join us too.
Flexible app architectures Uniform deploy and debug No reinvention of core concepts Truly hybrid Operators codify operational knowledge and workflows to automate life-cycle management of containerized applications with Kubernetes Kubernetes-native day 2 management
● Codify operational knowledge and software lifecycle ● Software-as-a-Service consumption model The purpose of Operators 5 Embed ops knowledge from the experts Operator v1.1.2 Deployments StatefulSets Autoscalers Secrets Config maps
● OperatorHub.io launched by Red Hat, AWS, Microsoft and Google ● OpenShift Operator Certification ● OperatorHub integrated into OpenShift 4 COMMUNITY OPERATORS OperatorHub and certified Operators OPENSHIFT CERTIFIED OPERATORS
● Operators ○ Codify Operational/Software-lifecycle knowledge ○ Built on Kubernetes primitives (CRDs) ○ SDK: Golang, Ansible, Helm, more to come! ○ Meant for Automating applications ○ OpenShift 4 is built on top of Operators ● Manage Operators with OLM ○ An operator for Operators ○ Control versions and upgrades ○ Catalog/SaaS experience In Summary 10
● What are Operators, really? ○ Custom Resource saved in YAML ○ Automation triggered by the CR (the YAML) ○ Changes are made by editing the CR (YAML) ○ Other changes are reconciled back to the desired state ○ Easily Replicated to other clusters ● What is GitOps? ○ Manifests are saved in git (YAML) ○ Automation/sync tool reads manifest (YAML) ○ Changes are made by PRing the YAML ○ Other changes are reconciled back to the desired state. ○ Easily Replicated to other clusters So Many Automation Tools! 12
● Operators are YAML Driven ● YAML for the Operator function should live in Git ● The point of demarcation is the handoff of this YAML You manage the manifest with GitOps as you normally would, while allowing the automation of Operators to be performed. The Point Of Demarcation 15