Skip to content

Commit 64a9256

Browse files
authored
Update example KES config in helm chart (#2008)
Update example KES config * Starting KES version `2023-11-10T10-44-28Z` the `keys` was renamed to `keystore`. * Using default entity as `admin` instead of apply a policy, as a best-practice recommended. * `root` field no longer exists Signed-off-by: pjuarezd <pjuarezd@users.noreply.github.com>
1 parent 9cf58b8 commit 64a9256

File tree

1 file changed

+3
-10
lines changed

1 file changed

+3
-10
lines changed

helm/tenant/values.yaml

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -348,30 +348,23 @@ tenant:
348348
# replicas: 2
349349
# configuration: |-
350350
# address: :7373
351-
# root: _ # Effectively disabled since no root identity necessary.
352351
# tls:
353352
# key: /tmp/kes/server.key # Path to the TLS private key
354353
# cert: /tmp/kes/server.crt # Path to the TLS certificate
355354
# proxy:
356355
# identities: []
357356
# header:
358357
# cert: X-Tls-Client-Cert
359-
# policy:
360-
# my-policy:
361-
# paths:
362-
# - /v1/key/create/*
363-
# - /v1/key/generate/*
364-
# - /v1/key/decrypt/*
365-
# identities:
366-
# - ${MINIO_KES_IDENTITY}
358+
# admin:
359+
# identity: ${MINIO_KES_IDENTITY}
367360
# cache:
368361
# expiry:
369362
# any: 5m0s
370363
# unused: 20s
371364
# log:
372365
# error: on
373366
# audit: off
374-
# keys:
367+
# keystore:
375368
# # KES configured with fs (File System mode) doesn't work in Kubernetes environments and is not recommended
376369
# # use a real KMS
377370
# # fs:

0 commit comments

Comments
 (0)