From b251ff3812e8930c1ea49ea87269a963485c4d27 Mon Sep 17 00:00:00 2001 From: Jerome Petazzoni Date: Wed, 11 Nov 2020 22:46:20 +0100 Subject: [PATCH] --output-watch-events --- slides/k8s/architecture.md | 32 ++++++++++++++++++++++++++++++-- 1 file changed, 30 insertions(+), 2 deletions(-) diff --git a/slides/k8s/architecture.md b/slides/k8s/architecture.md index bec06267..95bc6840 100644 --- a/slides/k8s/architecture.md +++ b/slides/k8s/architecture.md @@ -287,9 +287,9 @@ class: extra-details - "GVK" appears a lot in the API machinery code -- Conversions are possible between different versions +- Conversions are possible between different versions and even between API groups - (and even between API groups; e.g. when Deployments moved from `extensions` to `apps`) + (e.g. when Deployments moved from `extensions` to `apps`) --- @@ -354,6 +354,34 @@ We demonstrated *update* and *watch* semantics. --- +class: extra-details + +## Watch events + +- `kubectl get --watch` shows changes + +- If we add `--output-watch-events`, we can also see: + + - the difference between ADDED and MODIFIED resources + + - DELETED resources + +.exercise[ + +- In one terminal, watch pods, displaying full events: + ```bash + kubectl get pods --watch --output-watch-events + ``` + +- In another, run a short-lived pod: + ```bash + kubectl run pause --image=alpine --rm -ti --restart=Never -- sleep 5 + ``` + +] + +--- + # Other control plane components - API server ✔️