CipherTrust Transparent Encryption for Kubernetes Support
CTE for Kubernetes is an implementation of the CipherTrust Transparent Encryption with native support for Kubernetes through the implementation of a CSI (Container Storage Interface) driver. Unlike traditional CTE, product installation and GuardPoint management is done through Kubernetes. This means that as the cluster scales up with more nodes, CTE for Kubernetes scales with it. CTE for Kubernetes is designed to protect Kubernetes Persistent Storage Claims that are backed by storage with filesystem semantics.
Thales qualifies only Active Kubernetes releases when releasing a CTE-K8s feature release.
CTE for Kubernetes release types
| CTE Release | Major | Service Pack | Cumulative Patch |
|---|---|---|---|
| Numbering | 1.0.0 | 1.1.0 | 1.1.1 |
| Cadence | 3+ Years | 4+ Months | As needed |
| Contents | Major change in functionality | New features, fixes | New minor features, fixes |
Support Phase Definitions
| Support Phase | Definition | Timeframe |
|---|---|---|
| Active | Period during which Thales customer support will assist customers with issues. A maintenance agreement will make the customer eligible for patches, and service packs. | From GA to the start of Continued Support |
| Continued Support | Customer support can be engaged mainly for troubleshooting and work-arounds. Thales engineering will provide bugs and security fixes on an as-needed basis. No additional investment will be made by development and engineering departments. | Begins with the release of the next Service Pack; Ends after six months. |
| Extended Support | Support provided on an as-needed basis. An extended maintenance agreement must be in place. Thales will provide bug fixes only. | Only applies to the last Service pack before a Major release. Support timeframe begins after Continued Support ends and lasts six months |