From b9041d3d3992fcb5d4f8fb46351ade02e5fdfb7e Mon Sep 17 00:00:00 2001 From: Jerome Petazzoni Date: Fri, 29 Oct 2021 18:58:06 +0200 Subject: [PATCH] =?UTF-8?q?=F0=9F=94=A7=20Mention=20Events=20in=20nsplease?= =?UTF-8?q?=20chapter?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- slides/k8s/operators-example.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/slides/k8s/operators-example.md b/slides/k8s/operators-example.md index 170ef555..7f337e07 100644 --- a/slides/k8s/operators-example.md +++ b/slides/k8s/operators-example.md @@ -2,17 +2,16 @@ - Let's look at a simple operator -- It has: +- It does have: - - control loop - - - resource management - - - deployment instructions + - a control loop + - resource lifecycle management + - basic logging - It doesn't have: - CRDs (and therefore, resource versioning, conversion webhooks...) + - advanced observability (metrics, Kubernetes Events) --- @@ -148,3 +147,7 @@ on my needs) to be deployed into its specific Kubernetes Namespace.* - If the algorithms are correct, shell performance won't matter at all (but it will be difficult to keep a resource cache in shell) + +- Improvement idea: this operator could generate *events* + + (visible with `kubectl get events` and `kubectl describe`)