From 3d454016495febf5db238e7bbaadecf54c70afb7 Mon Sep 17 00:00:00 2001 From: Patrice Ferlet Date: Thu, 17 Feb 2022 11:38:48 +0100 Subject: [PATCH] Fixup doc --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 804de38..da1bda4 100644 --- a/README.md +++ b/README.md @@ -99,7 +99,7 @@ What can be interpreted by Katenary: - `env_file` list will create a configMap object per environemnt file (⚠ todo: the "to-service" label doesn't work with configMap for now) - some labels can help to bind values, for example: - `katenary.io/ingress: 80` will expose the port 80 in a ingress - - `katenary.io/to-service: VARNAME` will convert the value to a variable `{{ .Release.Name }}-VARNAME` - it's usefull when you want to pass the name of a service as a variable (think about the service name for mysql to pass to a container that wants to connect to this) + - `katenary.io/env-to-service: VARNAME` will convert the value to a variable `{{ .Release.Name }}-VARNAME` - it's usefull when you want to pass the name of a service as a variable (think about the service name for mysql to pass to a container that wants to connect to this) Exemple of a possible `docker-compose.yaml` file: