From fdc58cafda0c1e6da6addd3cdad1e26367efcf90 Mon Sep 17 00:00:00 2001 From: Jerome Petazzoni Date: Sun, 14 Mar 2021 19:21:43 +0100 Subject: [PATCH] =?UTF-8?q?=E2=9D=93=EF=B8=8F=20Add=20some=20quizzes?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- slides/0.yml | 2 ++ slides/k8s/accessinternal.md | 14 ++++++++++++++ slides/k8s/cert-manager.md | 2 ++ slides/k8s/helm-intro.md | 14 ++++++++++++++ 4 files changed, 32 insertions(+) create mode 100644 slides/0.yml diff --git a/slides/0.yml b/slides/0.yml new file mode 100644 index 00000000..36bd3a0e --- /dev/null +++ b/slides/0.yml @@ -0,0 +1,2 @@ +content: +- k8s/netpol.md diff --git a/slides/k8s/accessinternal.md b/slides/k8s/accessinternal.md index a647c38a..d70c882d 100644 --- a/slides/k8s/accessinternal.md +++ b/slides/k8s/accessinternal.md @@ -134,3 +134,17 @@ installed and set up `kubectl` to communicate with your cluster. :EN:- Securely accessing internal services :FR:- Accès sécurisé aux services internes + +:T: Accessing internal services from our local machine + +:Q: What's the advantage of "kubectl port-forward" compared to a NodePort? +:A: It can forward arbitrary protocols +:A: It doesn't require Kubernetes API credentials +:A: It offers deterministic load balancing (instead of random) +:A: ✔️It doesn't expose the service to the public + +:Q: What's the security concept behind "kubectl port-forward"? +:A: ✔️We authenticate with the Kubernetes API, and it forwards connections on our behalf +:A: It detects our source IP address, and only allows connections coming from it +:A: It uses end-to-end mTLS (mutual TLS) to authenticate our connections +:A: There is no security (as long as it's running, anyone can connect from anywhere) diff --git a/slides/k8s/cert-manager.md b/slides/k8s/cert-manager.md index dee9193f..b95949b3 100644 --- a/slides/k8s/cert-manager.md +++ b/slides/k8s/cert-manager.md @@ -242,3 +242,5 @@ class: extra-details :EN:- Obtaining certificates with cert-manager :FR:- Obtenir des certificats avec cert-manager + +:T: Obtaining TLS certificates with cert-manager diff --git a/slides/k8s/helm-intro.md b/slides/k8s/helm-intro.md index 6edd0b62..66385ab8 100644 --- a/slides/k8s/helm-intro.md +++ b/slides/k8s/helm-intro.md @@ -462,3 +462,17 @@ All unspecified values will take the default values defined in the chart. :FR:- Fonctionnement général de Helm :FR:- Installer des composants via Helm :FR:- Helm 2, Helm 3, et le *Helm Hub* + +:T: Getting started with Helm and its concepts + +:Q: Which comparison is the most adequate? +:A: Helm is a firewall, charts are access lists +:A: ✔️Helm is a package manager, charts are packages +:A: Helm is an artefact repository, charts are artefacts +:A: Helm is a CI/CD platform, charts are CI/CD pipelines + +:Q: What's required to distribute a Helm chart? +:A: A Helm commercial license +:A: A Docker registry +:A: An account on the Helm Hub +:A: ✔️An HTTP server