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
A small remark: It does not have to be as simple as in the UI - using Terraform, I am comfortable to create agency, KMS key, etc by hand. I guess I just need a Terraform way to configure the CCE Node data disk to utilize the encryption id.
[CCE] Add possibility to encrypt data volumes
What this PR does / why we need it
Add possibility to set data volume metadata for encryption with KMS
Which issue this PR fixes
Refers to: opentelekomcloud/terraform-provider-opentelekomcloud#1109
=== RUN TestNodes
--- PASS: TestNodes (731.13s)
=== RUN TestNodes/TestNodeLifecycle
--- PASS: TestNodes/TestNodeLifecycle (341.20s)
PASS
Process finished with the exit code 0
Reviewed-by: None <None>
Reviewed-by: Anton Sidelnikov <None>
Reviewed-by: Anton Kachurin <katchuring@gmail.com>
[CCE] Add possibility to encrypt data volumes
Summary of the Pull Request
Add new field kms_id in data_volumes spec to perform encryption with KMS
Resolves: #1109
PR Checklist
Refers to: #1109
Tests added/passed.
Documentation updated.
Schema updated.
Acceptance Steps Performed
=== RUN TestAccCCENodesV3Basic
--- PASS: TestAccCCENodesV3Basic (734.55s)
=== RUN TestAccCCENodesV3EncryptedVolume
--- PASS: TestAccCCENodesV3EncryptedVolume (1686.42s)
PASS
Process finished with the exit code 0
Reviewed-by: Anton Sidelnikov <None>
Reviewed-by: None <None>
Reviewed-by: Anton Kachurin <katchuring@gmail.com>
Reviewed-by: Rodion Gyrbu <fpsoff@outlook.com>
One of the features of CCE 1.19 is the disk encryption of worker nodes: https://open-telekom-cloud.com/de/support/release-notes/cloud-container-engine/release-kubernetes-1-19
However, I cannot find a way to activate this cool new feature in Terraform when creating a CCE node: https://registry.terraform.io/providers/opentelekomcloud/opentelekomcloud/latest/docs/resources/cce_node_v3
The text was updated successfully, but these errors were encountered: