From e5973aeff350cc438768ff39f88390309211ea98 Mon Sep 17 00:00:00 2001 From: Nathan Phelps Date: Mon, 20 May 2024 17:26:03 -0400 Subject: [PATCH] Issue 6: Removed Enterprise licensing references out of the chart's value configuration. Signed-off-by: Nathan Phelps --- charts/openbao/values.yaml | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/charts/openbao/values.yaml b/charts/openbao/values.yaml index 2d8ec8f..48a2157 100644 --- a/charts/openbao/values.yaml +++ b/charts/openbao/values.yaml @@ -369,18 +369,6 @@ server: # See vault.mode in _helpers.tpl for implementation details. enabled: "-" - # [Enterprise Only] This value refers to a Kubernetes secret that you have - # created that contains your enterprise license. If you are not using an - # enterprise image or if you plan to introduce the license key via another - # route, then leave secretName blank ("") or set it to null. - # Requires Vault Enterprise 1.8 or later. - enterpriseLicense: - # The name of the Kubernetes secret that holds the enterprise license. The - # secret must be in the same namespace that Vault is installed into. - secretName: "" - # The key within the Kubernetes secret that holds the enterprise license. - secretKey: "license" - # Resource requests, limits, etc. for the server cluster placement. This # should map directly to the value of the resources field for a PodSpec. # By default no direct resource request is made.