Edgelesssys Constellation Versions Save

Constellation is the first Confidential Kubernetes. Constellation shields entire Kubernetes clusters from the (cloud) infrastructure using confidential computing.

v2.7.0

1 year ago

What's Changed

🛠 Breaking changes

🎁 New features

🐛 Bug fixes

🔧 Other changes

Full Changelog: https://github.com/edgelesssys/constellation/compare/v2.6.0...v2.7.0

v2.6.0

1 year ago

What's Changed

🛡 Security improvements

  • Fix a vulnerability where an attacker with access to the victim's cloud subscription could gain code execution on a booting node through the initramfs emergency shell. See the accompanying security advisory for more information.

🎁 New features

🐛 Bug fixes

🔧 Other changes

New Contributors

Full Changelog: https://github.com/edgelesssys/constellation/compare/v2.5.0...v2.6.0

v2.5.3

1 year ago

What's Changed

🐛 Bug fixes

Full Changelog: https://github.com/edgelesssys/constellation/compare/v2.5.2...v2.5.3

v2.5.2

1 year ago

What's Changed

:lock: Security

  • aTLS: a bug was fixed where a malicious CSP insider could have used a MITM attack to gain control over the cluster during initialization. See the accompanying security advisory for more information.

Full Changelog: https://github.com/edgelesssys/constellation/compare/v2.5.1...v2.5.2

v2.5.1

1 year ago

What's Changed

🐛 Bug fixes

🔧 Other changes

Full Changelog: https://github.com/edgelesssys/constellation/compare/v2.5.0...v2.5.1

v2.5.0

1 year ago

Hints

  • Azure is currently rolling out a new ID key on Azure CVMs. Therefore constellation-init may report an invalid idkeydigest. To circumvent the problem, add under the key idKeyDigest in your constellation-conf.yaml an additional value:
    934f68bd8ba01938eec21475c872e3a942b60c59fafc6df9e9a76ee66bc47f2d09c676f61c0315c578da26085fb13a71
    We're working on a permanent solution for this.

What's Changed

🎁 New features

🐛 Bug fixes

🔧 Other changes

Full Changelog: https://github.com/edgelesssys/constellation/compare/v2.4.0...v2.5.0

v2.4.0

1 year ago

Hints

  • Azure is currently rolling out a new ID key on Azure CVMs. Therefore constellation-init may report an invalid idkeydigest. To circumvent the problem change the key idKeyDigest in your constellation-conf.yaml to the new value: 0356215882a825279a85b300b0b742931d113bf7e32dde2e50ffde7ec743ca491ecdd7f336dc28a6e0b2bb57af7a44a3
  • The original SBOM for the CLI uploaded with this release is invalid. The SBOMs for container images in the registry are unaffected by this issue. We uploaded a corrected for the CLI SBOM with the extension .fixed. below. We keep the original ones uploaded with .original. to keep the provenance valid. In doubt, you can independently generate a SBOM of all components using Syft.

What's Changed

🎁 New features

🐛 Bug fixes

🔧 Other changes

New Contributors

Full Changelog: https://github.com/edgelesssys/constellation/compare/v2.3.0...v2.4.0

v2.3.0

1 year ago

Changes

Added

  • constellation iam create can be used to automatically create service accounts and set permissions for Constellation
  • Automatic CSI driver deployment for Azure and GCP during Constellation init
  • Release CLI with SLSA Level 3 requirements.
  • Improve reproducibility by pinning the Kubernetes components.
  • Client verification during constellation init
  • Environment variable CONSTELL_AZURE_CLIENT_SECRET_VALUE as an alternative way to provide the configuration value provider.azure.clientSecretValue.

Changed

  • Constellation operators are now deployed using Helm.
  • Updated the config version to v2. Check how to migrate your config.
  • OS images are now configured globally in the images field of the configuration file.
  • The measurements entry in the CLI now uses an updated format, merging enforcedMeasurements and old measurements into one
  • Expected measurements in the config and Constellation's Cluster-ID are now hex encoded by default. Base64 is still supported.

Removed

  • access-manager was removed from code base. K8s native way to SSH into nodes documented.
  • SSHUsers has been removed from the user configuration following the removal of access-manager.
  • Azure Trusted Launch support. May come back in the future.

Fixed

  • constellation create on GCP now always uses the local default credentials.

v2.2.2

1 year ago

Fixed

  • constellation create on GCP now always uses the local default credentials.
  • A release process error encountered in v2.2.1. This led to a broken QEMU-based Constellation deployment, where PCR[8] didn't match.

Hint

  • The original SBOM uploaded with this release lists more packages than shipped in the built version of the CLI. This may create false positives with vulnerability scanners. Please consider using the .new. SBOM file uploaded. In doubt, you can independently generate a SBOM of all components using Syft.

v2.2.1

1 year ago

:warning: The default config for QEMU-based cluster creation is broken in this release. Please upgrade to v2.2.2.

Changed

  • Increase timeout for constellation config fetch-measurements from 3 seconds to 60 seconds.
  • Consistently log CLI warnings and errors to stderr.

Security

Vulnerabilities in kube-apiserver fixed by upgrading to v1.23.14, v1.24.8 and v1.25.4: