From 1d2b196686896a525848b1f533cb2fe384098875 Mon Sep 17 00:00:00 2001 From: Daniel McKnight Date: Mon, 15 Jan 2024 16:35:32 -0800 Subject: [PATCH] Fix outdated ingress deployment note --- Helm_Deployment.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Helm_Deployment.md b/Helm_Deployment.md index 200dc988..b258c546 100644 --- a/Helm_Deployment.md +++ b/Helm_Deployment.md @@ -20,14 +20,14 @@ provide any necessary configuration parameters; when complete, the specified `output_path` will be populated with Helm charts to deploy. ### Ingress -An NGINX ingress chart is provided at `/ingress-nginx`. `values.yaml` -may be updated to include any additional TCP ports to be used (i.e. for RabbitMQ) +An NGINX ingress chart is provided in the diana Helm repository, +`diana/ingress-common`. A `values.yaml` file may be specified to include any +additional TCP ports to be used (i.e. for RabbitMQ) and then the chart is generally deployed to the `ingress-nginx` namespace. Only one ingress is necessary for a cluster. Deploy the configured ingress with: ``` -helm dependency update /ingress-common -helm install ingress-nginx /ingress-common --namespace ingress-nginx --create-namespace +helm install ingress-nginx diana/ingress-common --namespace ingress-nginx --create-namespace ``` > At this point, check to make sure all expected subdomains resolve to the ingress > IP address (ping each domain and check the resolved address)