From 39a15b3d7dc017edbbb41312dbfb1dae0be370ed Mon Sep 17 00:00:00 2001 From: Ludovic Piot Date: Tue, 10 Jun 2025 19:20:25 +0200 Subject: [PATCH] =?UTF-8?q?=E2=9C=8F=EF=B8=8F=20Clean=20up=20consistency?= =?UTF-8?q?=20about=20how=20we=20evoke=20the=20OPS=20team?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- slides/k8s/M6-T05-ingress-config.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/slides/k8s/M6-T05-ingress-config.md b/slides/k8s/M6-T05-ingress-config.md index ee479257..4c72d0ec 100644 --- a/slides/k8s/M6-T05-ingress-config.md +++ b/slides/k8s/M6-T05-ingress-config.md @@ -26,7 +26,7 @@ We'll use `ingress-nginx` (relying on `NGinX`), quite a popular choice. - It is able to provision IaaS load-balancer in ScaleWay Cloud services - As a reverse-proxy, it is able to balance HTTP connections on an on-premises cluster -**_⚙️OPS_** Team add this new install to its `Flux` config. repo +The **_⚙️OPS_** Team add this new install to its `Flux` config. repo --- @@ -179,10 +179,10 @@ Don't forget to commit! ## Few considerations -- **_⚙️OPS_** team has to decide how to manage name resolution for public IPs +- The **_⚙️OPS_** team has to decide how to manage name resolution for public IPs - Scaleway propose to expose a wildcard domain for its Kubernetes clusters -- Here, we chose that `Ingress-controller` (that makes sense) but `Ingress` as well were managed by **_⚙️OPS_** team. +- Here, we chose that `Ingress-controller` (that makes sense) but `Ingress` as well were managed by the **_⚙️OPS_** team. - It might have been done in many different ways! ---