Rakshith R 4f0bb2315b rbd: add aws-sts-metdata encryption type ... With Amazon STS and kubernetes cluster is configured with OIDC identity provider, credentials to access Amazon KMS can be fetched using oidc-token(serviceaccount token). Each tenant/namespace needs to create a secret with aws region, role and CMK ARN. Ceph-CSI will assume the given role with oidc token and access aws KMS, with given CMK to encrypt/decrypt DEK which will stored in the image metdata. Refer: https://docs.aws.amazon.com/STS/latest/APIReference/welcome.html Resolves: #2879 Signed-off-by: Rakshith R <rar@redhat.com>		2022-03-16 07:29:56 +00:00
..
doc.go	rbd: add aws-sts-metdata encryption type	2022-03-16 07:29:56 +00:00
logging.go	rbd: add aws-sts-metdata encryption type	2022-03-16 07:29:56 +00:00
metadata.go	rbd: add aws-sts-metdata encryption type	2022-03-16 07:29:56 +00:00
middleware.go	rbd: add aws-sts-metdata encryption type	2022-03-16 07:29:56 +00:00
ordered_group.go	rbd: add aws-sts-metdata encryption type	2022-03-16 07:29:56 +00:00
stack_values.go	rbd: add aws-sts-metdata encryption type	2022-03-16 07:29:56 +00:00
stack.go	rbd: add aws-sts-metdata encryption type	2022-03-16 07:29:56 +00:00
step_build.go	rbd: add aws-sts-metdata encryption type	2022-03-16 07:29:56 +00:00
step_deserialize.go	rbd: add aws-sts-metdata encryption type	2022-03-16 07:29:56 +00:00
step_finalize.go	rbd: add aws-sts-metdata encryption type	2022-03-16 07:29:56 +00:00
step_initialize.go	rbd: add aws-sts-metdata encryption type	2022-03-16 07:29:56 +00:00
step_serialize.go	rbd: add aws-sts-metdata encryption type	2022-03-16 07:29:56 +00:00