From b4709af96b193beabf4b5106ad25c03e29dd4b1d Mon Sep 17 00:00:00 2001 From: Michele Baldessari Date: Wed, 6 May 2026 13:48:26 +0200 Subject: [PATCH] Version 0.1.8 --- Chart.yaml | 2 +- README.md | 6 ++++-- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/Chart.yaml b/Chart.yaml index fe9cc1e..a0a7799 100644 --- a/Chart.yaml +++ b/Chart.yaml @@ -3,7 +3,7 @@ description: A Helm chart to configure Hashicorp's vault. keywords: - pattern name: hashicorp-vault -version: 0.1.7 +version: 0.1.8 home: https://github.com/validatedpatterns/hashicorp-vault-chart dependencies: - name: vault diff --git a/README.md b/README.md index 8925b17..3a118cf 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # hashicorp-vault -![Version: 0.1.7](https://img.shields.io/badge/Version-0.1.7-informational?style=flat-square) +![Version: 0.1.8](https://img.shields.io/badge/Version-0.1.8-informational?style=flat-square) A Helm chart to configure Hashicorp's vault. @@ -24,6 +24,7 @@ This chart is used by the Validated Patterns installation script that can be fou | Key | Type | Default | Description | |-----|------|---------|-------------| +| defaultDenyNetworkPolicy | object | false | Default-deny NetworkPolicy for the vault namespace When enabled, deploys a namespace-wide NetworkPolicy that blocks all ingress and egress for pods without an explicit allow policy. Patterns that need zero-trust network isolation should enable this and provide per-pod allow rules via vault.server.networkPolicy. | | global | object | depends on the individual settings | The global namespace contains some globally used variables used in patterns | | global.localClusterDomain | string | `"apps.foo.cluster.com"` | The DNS entry for the cluster the chart is being rendered on with the apps. prefix | | global.openshift | bool | `true` | Setting the enforces openshift templates for the vault chart | @@ -82,4 +83,5 @@ This is why we set the following in the values files: Make sure to run "./update-helm-dependency.sh" after you updated the subchart (by calling helm dependency update .) -We can drop this local patch once upstream merges +We can drop this local patch once upstream fixes the bug (which would need reopining, discuss +and fixing)