RATATOSK
← All releases

Confidential Containersv0.17.0

Security 1Breaking changes 3Enhancements 6Dependency updates 1Other changes 4

Get Confidential Containers alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Check before upgrading

Prerequisites2
Host platform compatibility with CoCo-provisioned hypervisor and guest kernel
Make sure your host platform is compatible with the hypervisor and guest kernel
provisioned by CoCo.
github.com/confidential-containers/confidential-containers/blob/main/releases/v0.17.0.md
Host SELinux requires permissive mode
* SELinux is not supported on the host and must be set to permissive if in use.
github.com/confidential-containers/confidential-containers/blob/main/releases/v0.17.0.md
Known issues10
Attestation tested on Intel TDX, AMD SEV-SNP, and IBM SEL

Features based on attestation are expected to work on these platforms, although not all features have been tested on each one.

Attestation is supported and tested on three platforms: Intel TDX, AMD SEV-SNP, and IBM SEL.
Not all features have been tested on every platform, but those based on attestation
are expected to work on the platforms above.
github.com/confidential-containers/confidential-containers/blob/main/releases/v0.17.0.md
Authenticated registry credentials exposed to the host
* Credentials for authenticated registries are exposed to the host.
github.com/confidential-containers/confidential-containers/blob/main/releases/v0.17.0.md
Not all features are tested on all platforms
Nydus snapshotter support remains immature

It sometimes fails to pull images, host pulling is not enabled, and it is unsupported with enclave-cc. An experimental option forces image pulls in the guest without a snapshotter, but it is also immature and must be configured manually.

* Nydus snapshotter support is not mature.
  * Nydus snapshotter sometimes fails to pull an image.
  * Host pulling with Nydus snapshotter is not yet enabled.
  * Nydus snapshotter is not supported with enclave-cc.
  * There is an experimental option to force guest image pull without a snapshotter.
    This is also not mature and must be manually configured.
github.com/confidential-containers/confidential-containers/blob/main/releases/v0.17.0.md
Guest image pulls may increase resource usage

These pulls may slow startup.

* Pulling container images inside guest may have negative performance implications including greater resource usage and slower startup.
github.com/confidential-containers/confidential-containers/blob/main/releases/v0.17.0.md
crio support is still evolving
Platform support is changing rapidly
Kubernetes integration still in progress
* Complete integration with Kubernetes is still in progress.
github.com/confidential-containers/confidential-containers/blob/main/releases/v0.17.0.md
Existing APIs do not fully support the CoCo security and threat model
  * Existing APIs do not fully support the CoCo security and threat model. [More info](https://github.com/confidential-containers/confidential-containers/issues/53)
github.com/confidential-containers/confidential-containers/blob/main/releases/v0.17.0.md
Confidential-data access commands may fail or expose information to the host
  * Some commands accessing confidential data, such as `kubectl exec`, may either fail to work, or incorrectly expose information to the host
github.com/confidential-containers/confidential-containers/blob/main/releases/v0.17.0.md

Security1

Breaking changes3

Enhancements6

Dependency updates1

    1 more, none mentioning security
    • This release is based on [3.23.0](https://github.com/kata-containers/kata-containers/releases/tag/3.23.0) of Kata Containers and [v0.11.0](https://github.com/confidential-containers/enclave-cc/releases/tag/v0.11.0) of enclave-cc.
    Other changes4

    Summaries are produced by AI, so they can be wrong, and they are provided without warranty.