Update for 0.2.0 release (#102)
This commit is contained in:
parent
ea0e66760f
commit
a5331f5b38
3 changed files with 5 additions and 7 deletions
|
@ -1,4 +1,4 @@
|
|||
## 0.2.0 (Unreleased)
|
||||
## 0.2.0 (October 29th, 2019)
|
||||
|
||||
Features:
|
||||
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
apiVersion: v1
|
||||
name: vault
|
||||
version: 0.1.2
|
||||
version: 0.2.0
|
||||
description: Install and configure Vault on Kubernetes.
|
||||
home: https://www.vaultproject.io
|
||||
icon: https://github.com/hashicorp/vault/raw/f22d202cde2018f9455dec755118a9b84586e082/Vault_PrimaryLogo_Black.png
|
||||
|
|
|
@ -6,7 +6,7 @@ global:
|
|||
enabled: true
|
||||
|
||||
# Image is the name (and tag) of the Vault Docker image.
|
||||
image: "vault:1.2.2"
|
||||
image: "vault:1.2.4"
|
||||
# Overrides the default Image Pull Policy
|
||||
imagePullPolicy: IfNotPresent
|
||||
# Image pull secret to use for registry authentication.
|
||||
|
@ -33,9 +33,8 @@ server:
|
|||
# memory: 256Mi
|
||||
# cpu: 250m
|
||||
|
||||
# Ingress settings
|
||||
# Enabling it a ingress will be created which will manage external access to the
|
||||
# cluster, very useful if you want to expose the Vault UI
|
||||
# Ingress allows ingress services to be created to allow external access
|
||||
# from Kubernetes to access Vault pods.
|
||||
ingress:
|
||||
enabled: false
|
||||
labels: {}
|
||||
|
@ -79,7 +78,6 @@ server:
|
|||
extraVolumes: []
|
||||
# - type: secret (or "configMap")
|
||||
# name: my-secret
|
||||
# load: false # if true, will add to `-config` to load by Vault
|
||||
# path: null # default is `/vault/userconfig`
|
||||
|
||||
# Affinity Settings
|
||||
|
|
Loading…
Reference in a new issue