From c565dad43c5f184cf201c36d199ff2e35a35f6de Mon Sep 17 00:00:00 2001 From: Jerome Petazzoni Date: Fri, 24 May 2019 19:33:23 -0500 Subject: [PATCH] Fix typos and add precisions --- slides/k8s/operators.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/slides/k8s/operators.md b/slides/k8s/operators.md index 66253edb..b3dbf6b4 100644 --- a/slides/k8s/operators.md +++ b/slides/k8s/operators.md @@ -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`)