From 85f1b2d43c6d6965cac43c37cbc22e402bd667a9 Mon Sep 17 00:00:00 2001 From: Patrice Ferlet Date: Fri, 19 Apr 2024 11:28:27 +0200 Subject: [PATCH] Fixes the ingress doc --- doc/docs/usage.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/docs/usage.md b/doc/docs/usage.md index 0b955ef..dae8059 100644 --- a/doc/docs/usage.md +++ b/doc/docs/usage.md @@ -126,10 +126,11 @@ services: ### Declare ingresses -It's very common to have an `Ingress` on web application to deploy on Kuberenetes. The `katenary.io/ingress` declare the -port to bind. +It's very common to have an Ingress resource on web application to deploy on Kuberenetes. It allows to expose the +service to the outside of the cluster (you need to install an ingress controller). + +Katenary can create this resource for you. You just need to declare the hostname and the port to bind. -# ... ```yaml services: webapp: @@ -137,6 +138,7 @@ services: ports: 8080:5050 labels: katenary.v3/ingress: |- + # the target port is 5050 wich is the "service" port port: 5050 hostname: myapp.example.com ```