🖼️ Re-add images for flux/M6 chapter

This commit is contained in:
Jérôme Petazzoni
2025-11-04 08:19:09 +01:00
parent 39a71565a0
commit 9f0224bb26
23 changed files with 27 additions and 27 deletions

View File

@@ -48,7 +48,7 @@ k8s@shpod:~$ flux bootstrap github \
class: pic class: pic
![Running Mario](images/M6-running-Mario.gif) ![Running Mario](images/running-mario.gif)
--- ---
@@ -83,7 +83,7 @@ We don't have such kind of things here.😕
class: pic class: pic
![Running Mario](images/M6-running-Mario.gif) ![Running Mario](images/running-mario.gif)
--- ---

View File

@@ -167,13 +167,13 @@ k8s@shpod:~/fleet-config-using-flux-XXXXX$ \
class: pic class: pic
![Running Mario](images/M6-running-Mario.gif) ![Running Mario](images/running-mario.gif)
--- ---
class: pic class: pic
![rocky config files](images/M6-R01-config-files.png) ![rocky config files](images/flux/R01-config-files.png)
--- ---
@@ -300,7 +300,7 @@ class: extra-details
💡 This managed cluster comes with custom `StorageClasses` leveraging on Cloud _IaaS_ capabilities (i.e. block devices) 💡 This managed cluster comes with custom `StorageClasses` leveraging on Cloud _IaaS_ capabilities (i.e. block devices)
![Flux configuration waterfall](images/M6-persistentvolumes.png) ![Flux configuration waterfall](images/flux/persistentvolumes.png)
- a default `StorageClass` is applied if none is specified (like here) - a default `StorageClass` is applied if none is specified (like here)
- for **_🏭PROD_** purpose, ops team might enforce a more performant `StorageClass` - for **_🏭PROD_** purpose, ops team might enforce a more performant `StorageClass`
@@ -310,7 +310,7 @@ class: extra-details
class: pic class: pic
![Flux configuration waterfall](images/M6-flux-config-dependencies.png) ![Flux configuration waterfall](images/flux/flux-config-dependencies.png)
--- ---

View File

@@ -9,7 +9,7 @@ but let's see if we can succeed by just adding manifests in our `Flux` configura
class: pic class: pic
![Flux configuration waterfall](images/M6-flux-config-dependencies.png) ![Flux configuration waterfall](images/flux/flux-config-dependencies.png)
--- ---
@@ -89,7 +89,7 @@ k8s@shpod:~/fleet-config-using-flux-XXXXX$ \
class: pic class: pic
![Running Mario](images/M6-running-Mario.gif) ![Running Mario](images/running-mario.gif)
--- ---
@@ -132,7 +132,7 @@ k8s@shpod:~$ flux reconcile source git movy-app -n movy-test
class: pic class: pic
![Running Mario](images/M6-running-Mario.gif) ![Running Mario](images/running-mario.gif)
--- ---
@@ -170,13 +170,13 @@ And push the modifications…
class: pic class: pic
![MOVY app has an incorrect dataset](images/M6-incorrect-dataset-in-MOVY-app.png) ![MOVY app has an incorrect dataset](images/flux/incorrect-dataset-in-MOVY-app.png)
--- ---
class: pic class: pic
![ROCKY app has an incorrect dataset](images/M6-incorrect-dataset-in-ROCKY-app.png) ![ROCKY app has an incorrect dataset](images/flux/incorrect-dataset-in-ROCKY-app.png)
--- ---
@@ -212,7 +212,7 @@ Please, refer to the [`Network policies` chapter in the High Five M4 module](./4
class: pic class: pic
![Running Mario](images/M6-running-Mario.gif) ![Running Mario](images/running-mario.gif)
--- ---

View File

@@ -89,7 +89,7 @@ Prerequisites are:
class: pic class: pic
![Generating a Github personal access token](images/M6-github-add-token.jpg) ![Generating a Github personal access token](images/flux/github-add-token.jpg)
--- ---
@@ -169,7 +169,7 @@ Here is the result
- `Flux` sets up permissions that allow teams within our organization to **access** the `Github` repository as maintainers - `Flux` sets up permissions that allow teams within our organization to **access** the `Github` repository as maintainers
- Teams need to exist before `Flux` proceeds to this configuration - Teams need to exist before `Flux` proceeds to this configuration
![Teams in Github](images/M6-github-teams.png) ![Teams in Github](images/flux/github-teams.png)
--- ---
@@ -192,13 +192,13 @@ Its configuration is managed through a _Gitops_ workflow sourced directly from o
Let's review our `Flux` configuration files we've created and pushed into the `Github` repository… Let's review our `Flux` configuration files we've created and pushed into the `Github` repository…
… as well as the corresponding components running in our Kubernetes cluster … as well as the corresponding components running in our Kubernetes cluster
![Flux config files](images/M6-flux-config-files.png) ![Flux config files](images/flux/flux-config-files.png)
--- ---
class: pic class: pic
<!-- FIXME: wrong schema --> <!-- FIXME: wrong schema -->
![Flux architecture](images/M6-flux-controllers.png) ![Flux architecture](images/flux/flux-controllers.png)
--- ---

View File

@@ -90,13 +90,13 @@ k8s@shpod:~/fleet-config-using-flux-XXXXX$ \
class: pic class: pic
![Running Mario](images/M6-running-Mario.gif) ![Running Mario](images/running-mario.gif)
--- ---
class: pic class: pic
![Ingress-nginx provisionned a IaaS load-balancer in Scaleway Cloud services](images/M6-ingress-nginx-scaleway-lb.png) ![Ingress-nginx provisionned a IaaS load-balancer in Scaleway Cloud services](images/flux/ingress-nginx-scaleway-lb.png)
--- ---
@@ -141,7 +141,7 @@ k8s@shpod:~/fleet-config-using-flux-XXXXX$ \
class: pic class: pic
![Running Mario](images/M6-running-Mario.gif) ![Running Mario](images/running-mario.gif)
--- ---
@@ -172,7 +172,7 @@ k8s@shpod:~$ \
class: pic class: pic
![Rocky application screenshot](images/M6-rocky-app-screenshot.png) ![Rocky application screenshot](images/flux/rocky-app-screenshot.png)
--- ---

View File

@@ -107,7 +107,7 @@ flux create kustomization
class: pic class: pic
![Running Mario](images/M6-running-Mario.gif) ![Running Mario](images/running-mario.gif)
--- ---

View File

@@ -58,7 +58,7 @@ k8s@shpod:~/fleet-config-using-flux-XXXXX$ flux create kustomization dashboards
class: pic class: pic
![Running Mario](images/M6-running-Mario.gif) ![Running Mario](images/running-mario.gif)
--- ---
@@ -98,7 +98,7 @@ k8s@shpod:~$ flux create secret git flux-system \
class: pic class: pic
![Running Mario](images/M6-running-Mario.gif) ![Running Mario](images/running-mario.gif)
--- ---
@@ -127,7 +127,7 @@ k8s@shpod:~$ k get secret kube-prometheus-stack-grafana -n monitoring \
class: pic class: pic
![Grafana dashboard screenshot](images/M6-grafana-dashboard.png) ![Grafana dashboard screenshot](images/flux/grafana-dashboard.png)
--- ---

View File

@@ -76,7 +76,7 @@ And here we go!
class: pic class: pic
![Running Mario](images/M6-running-Mario.gif) ![Running Mario](images/running-mario.gif)
--- ---

View File

@@ -34,7 +34,7 @@ Several _tenants_ are created
class: pic class: pic
![Multi-tenants clusters](images/M6-cluster-multi-tenants.png ) ![Multi-tenants clusters](images/flux/cluster-multi-tenants.png )
--- ---
@@ -105,7 +105,7 @@ Let's review the `fleet-config-using-flux-XXXXX/clusters/CLOUDY/tenants.yaml` fi
class: pic class: pic
![Running Mario](images/M6-running-Mario.gif) ![Running Mario](images/running-mario.gif)
--- ---

Binary file not shown.

After

Width:  |  Height:  |  Size: 74 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 73 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 186 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 34 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 221 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 69 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 162 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 570 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 278 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 347 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 192 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 70 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 241 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 189 KiB