From 23cb8e7501373498b152b66e9b1b8517aca9229f Mon Sep 17 00:00:00 2001 From: "Kumar, Rajesh (XINBM1A)" Date: Tue, 25 Jun 2024 17:47:24 +0530 Subject: [PATCH] updated vault helm chart doc with usecase of nlb Signed-off-by: Kumar, Rajesh (XINBM1A) --- website/content/docs/platform/k8s/helm/index.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/content/docs/platform/k8s/helm/index.mdx b/website/content/docs/platform/k8s/helm/index.mdx index 53f410103b93..b06ee230afb5 100644 --- a/website/content/docs/platform/k8s/helm/index.mdx +++ b/website/content/docs/platform/k8s/helm/index.mdx @@ -59,6 +59,8 @@ cluster](https://kubernetes.io/docs/tasks/administer-cluster/securing-a-cluster/ options](/vault/docs/platform/k8s/helm/configuration), and read the [production deployment checklist](/vault/docs/platform/k8s/helm/run#architecture). +-> **Important:** This helm chart always provisions Application Load Balancer(ALB) at the AWS side, if you have the requirements of running vault with Network Load Balancer(NLB) then you need to provision NLB in front of your ALB. This special kind of requirement can arise where you need to use AWS PrivateLink with your vault and PrivateLink only works with NLB. + ## Tutorial Refer to the [Kubernetes](/vault/tutorials/kubernetes)