From f19bb95c8648da5049ac8d124260e4d56b9ecb85 Mon Sep 17 00:00:00 2001 From: duanhongyi Date: Sun, 25 Nov 2018 00:27:10 +0800 Subject: [PATCH 1/2] feat(workflow): add parameters to determine that s3 enabled SSE --- charts/workflow/values.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/charts/workflow/values.yaml b/charts/workflow/values.yaml index 2bb44afb8..4954dec47 100644 --- a/charts/workflow/values.yaml +++ b/charts/workflow/values.yaml @@ -83,6 +83,8 @@ s3: secretkey: "" # Any S3 region region: "us-west-1" + # Using Server-Side Encryption ? + use_sse: "false" # Your buckets. registry_bucket: "your-registry-bucket-name" database_bucket: "your-database-bucket-name" From 7b0eb0b9a1fd20434bb9913575952250c00a4f16 Mon Sep 17 00:00:00 2001 From: Kingdon Barrett Date: Sat, 24 Nov 2018 11:31:36 -0500 Subject: [PATCH 2/2] specific wording use_sse --- charts/workflow/values.yaml | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/charts/workflow/values.yaml b/charts/workflow/values.yaml index 4954dec47..79d2e53d1 100644 --- a/charts/workflow/values.yaml +++ b/charts/workflow/values.yaml @@ -81,10 +81,15 @@ s3: accesskey: "" # Your AWS secret key. Leave it empty if you want to use IAM credentials. secretkey: "" + # Enable SSE encryption (this must be disabled if you are not using AWS S3), + # since SSE support in boto2 is AWS-specific, it may be necessary to disable it. + # + # Valid values are: + # - true: only the database bucket is encrypted, non-AWS installations will fail + # - false: in database, WALE_S3_SSE will be set to false, SSE is not requested + use_sse: "true" # Any S3 region region: "us-west-1" - # Using Server-Side Encryption ? - use_sse: "false" # Your buckets. registry_bucket: "your-registry-bucket-name" database_bucket: "your-database-bucket-name"