github/container.training
1
0
Fork 0
mirror of https://github.com/jpetazzo/container.training.git synced 2026-09-06 03:07:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

✏️ Clean up consistency about how we evoke the OPS team

Browse Source
This commit is contained in:
Ludovic Piot
2025-06-10 19:20:25 +02:00
parent 3f5eaae6b9
commit 023a9d0346
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
slides/k8s/M6-T05-ingress-config.md
+3 -3
View File
@@ -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!
---