You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it is required to BYO the gossip encryption key, and this is documented in the values.yaml file:
# gossipEncryption configures which Kubernetes secret to retrieve Consul's
# gossip encryption key from (see https://www.consul.io/docs/agent/options.html#_encrypt).
# If secretName or secretKey are not set, gossip encryption will not be enabled.
# The secret must be in the same namespace that Consul is installed into.
#
# The secret can be created by running:
# kubectl create secret generic consul-gossip-encryption-key \
# --from-literal=key=$(consul keygen).
#
It would be helpful to have the option to have helm auto-generate the gossip encryption key and install the secret at install time.
The text was updated successfully, but these errors were encountered:
t-eckert
changed the title
add support for auto-generating gossip encryption secret
helm:add support for auto-generating gossip encryption secret
Aug 24, 2021
Currently it is required to BYO the gossip encryption key, and this is documented in the values.yaml file:
It would be helpful to have the option to have helm auto-generate the gossip encryption key and install the secret at install time.
The text was updated successfully, but these errors were encountered: