github/container.training
1
0
Fork 0
mirror of https://github.com/jpetazzo/container.training.git synced 2026-07-18 20:39:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix typos and add precisions

Browse Source
This commit is contained in:
Jerome Petazzoni
2019-05-24 19:33:23 -05:00
parent b69119eed4
commit c565dad43c
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
slides/k8s/operators.md
View File

@@ -22,10 +22,14 @@
- A given operator can define one or multiple CRDs
- The controller code (control loop) can run within the cluster or elsewhere
- The controller code (control loop) typically runs within the cluster
(running as a Deployment with 1 replica is a common scenario)
- But it could also run elsewhere
(nothing mandates that the code run on the cluster, as long as it has API access)
---
## Why use operators?
@@ -76,7 +80,7 @@
(Example: [Istio operator](https://operatorhub.io/operator/beta/istio-operator.0.1.6))
- Deploying and managing our applications lifecycles
- Deploying and managing our applications' lifecycles
(more on that later)
@@ -90,7 +94,7 @@
- The operator also runs a *controller* that will watch its resources
- Each time we create/updated/delete a resource, the controller is notified
- Each time we create/update/delete a resource, the controller is notified
(we could write our own cheap controller with `kubectl get --watch`)