🎨

slides/k8s/M6-M01-adding-MOVY-tenant.md

@@ -192,6 +192,8 @@ pod network is still full mesh and any connection is authorized.
 
 ---
 
+class: extra-details
+
 ## Adding NetworkPolicies to **_🎸ROCKY_** and **_🎬MOVY_** namespaces
 
 `Network policies` may be seen as the firewall feature in the pod network.  

slides/k8s/M6-T02-flux-install.md

@@ -305,7 +305,9 @@ flux-system     kustomization/flux-system       main@sha1:d48291a8      False
 
 ---
 
-### 🔍 Flux -- for more info
+class: extra-details
+
+### Flux -- for more info
 
 Please, refer to the [`Flux` chapter in the High Five M3 module](./3.yml.html#toc-helm-chart-format)
 
@@ -343,13 +345,17 @@ describes where `Flux kustomize-controller` looks for a `kustomization.yaml` fil
 
 ---
 
-### 🔍 Kustomize -- for more info
+class: extra-details
+
+### Kustomize -- for more info
 
 Please, refer to the [`Kustomize` chapter in the High Five M3 module](./3.yml.html#toc-kustomize)
 
 ---
 
-### 🔍 Group / Version / Kind -- for more info
+class: extra-details
+
+### Group / Version / Kind -- for more info
 
 For more info about how Kubernetes resource natures are identified by their `Group / Version / Kind` triplet…  
 … please, refer to the [`Kubernetes API` chapter in the High Five M5 module](./5.yml.html#toc-the-kubernetes-api)

slides/k8s/M6-T05-ingress-config.md

@@ -13,7 +13,9 @@ The regular way to do it in Kubernetes is to configure an `Ingress` resource.
 
 ---
 
-## 🔍 Ingress -- for more info
+class: extra-details
+
+## Ingress -- for more info
 
 Please, refer to the [`Ingress` chapter in the High Five M2 module](./2.yml.html#toc-exposing-http-services-with-ingress-resources)
 
@@ -143,7 +145,7 @@ class: pic
 
 ---
 
-### Here is the result!
+### Here is the result
 
 After Flux reconciled the whole bunch of sources and kustomizations, you should see