Release Note for CTE for Kubernetes
| Release Note Version | Date |
|---|---|
| 1.2.0.56 | 2023-09-22 |
Container Image Digest
Verify that the Container Image Digest matches the version that you are installing.
| Release Date | Tag | Container Image Digest (Fingerprint) |
|---|---|---|
| 2023-09-22 | 1.2.0.56 | sha256:07cfc0ee0b0e91203581a52b9f80763c542b06711f48777017c8eccaa673726a |
Minimum System Requirements
| Pod Type | Memory | CPU |
|---|---|---|
| CTE CSI Controller | 512Mb | 1 |
| CTE CSI Node Server | 512Mb + 100Mb per GuardPoint | 2 |
| CTE CSI Staging pod | 5Mb | 0.1 |
Note
-
Encryption CPU requirements on the node server are highly dependent on the workload that is accessing the CTE for Kubernetes encrypted volume. Additional CPU resources may be required depending on the expected number of IOPS for the application.
-
Applying hard memory limits on the CTE for Kubernetes node server pods can result in the pod being evicted. This will cause a service interruption to the CTE for Kubernetes volume. Hard memory limits are not recommended for the CTE node server.
-
Staging pods do not consume any CPU resources after starting and very minimal memory resources after starting.
Resolved Issues
-
AGT-46880 [CS1431227]: CTE Policy Process not available
An application that was running on CTE for Kubernetes, in Pods which used multiple threads, and performed writes from a thread that was not the original thread to open the file handle after the opening thread was exited, may not have been properly authenticated. Additionally, if using user-based or process-based security rules, they may have been incorrectly denied access. This problem has been fixed.
