Constellation is the first Confidential Kubernetes. Constellation shields entire Kubernetes clusters from the (cloud) infrastructure using confidential computing.
Go to file
Daniel Weiße d7a2ddd939
config: add separate option for handling attestation parameters (#1623)
* Add attestation options to config

* Add join-config migration path for clusters with old measurement format

* Always create MAA provider for Azure SNP clusters

* Remove confidential VM option from provider in favor of attestation options

* cli: add config migrate command to handle config migration (#1678)

---------

Signed-off-by: Daniel Weiße <dw@edgeless.systems>
2023-05-03 11:11:53 +02:00
.github ci: only add tf-log flag if the binary supports it 2023-05-02 11:08:40 +02:00
3rdparty deps: update go to 1.20.3 (#1622) 2023-04-06 16:36:07 +02:00
bazel deps: update golang.org/x/exp digest to 47ecfdc (#1690) 2023-04-27 17:51:46 +02:00
bootstrapper image: OpenStack vTPM (#1616) 2023-04-05 16:49:03 +02:00
cli config: add separate option for handling attestation parameters (#1623) 2023-05-03 11:11:53 +02:00
csi go: remove redefinitions of builtins 2023-03-20 08:41:01 -04:00
debugd deps: update fedora:37 Docker digest to e734322 (#1689) 2023-04-27 17:51:14 +02:00
dev-docs docs: remove second build documentation 2023-04-27 13:04:40 +02:00
disk-mapper bazel: add protoc codegen to //:generate target (#1554) 2023-03-30 14:47:29 +02:00
docs config: add separate option for handling attestation parameters (#1623) 2023-05-03 11:11:53 +02:00
e2e config: add separate option for handling attestation parameters (#1623) 2023-05-03 11:11:53 +02:00
hack Revert "misc: replace sha256sum with shasum -a 256 (#1681)" 2023-05-02 11:07:05 +02:00
image image: fix pcr 12 calculation (#1706) 2023-05-02 12:01:30 +02:00
internal config: add separate option for handling attestation parameters (#1623) 2023-05-03 11:11:53 +02:00
joinservice config: add separate option for handling attestation parameters (#1623) 2023-05-03 11:11:53 +02:00
keyservice bazel: remove apko and Dockerfile where Bazel is used to build container images 2023-04-18 15:35:15 +02:00
measurement-reader internal: refactor oid package to variant package (#1538) 2023-03-29 09:30:13 +02:00
operators/constellation-node-operator bazel: remove apko and Dockerfile where Bazel is used to build container images 2023-04-18 15:35:15 +02:00
rfc rfc: attestation config options (#1436) 2023-03-29 14:58:57 +02:00
rpm upgrade rpms 2023-04-18 15:35:15 +02:00
tools bazel: don't exit early in workspace_status.sh (#1713) 2023-05-02 16:57:08 +02:00
upgrade-agent bazel: add protoc codegen to //:generate target (#1554) 2023-03-30 14:47:29 +02:00
verify bazel: remove apko and Dockerfile where Bazel is used to build container images 2023-04-18 15:35:15 +02:00
.bazelrc bazel: allow custom container_prefix (#1693) 2023-04-27 11:52:02 +02:00
.bazelversion deps: update bazel to v6.1.0 2023-03-23 12:20:36 -04:00
.dockerignore ci: run versionsapi as docker action 2023-01-13 10:23:43 +01:00
.gitignore cli: add Terraform log support (#1620) 2023-04-14 14:15:07 +02:00
.golangci.yml ci: add e2e-upgrade test 2023-03-23 14:57:38 +01:00
.grype.yaml ci: ignore replaced ghsa (#1392) 2023-03-10 11:13:05 +01:00
.lycheeignore Fix links and clean lycheeignore (#1219) 2023-02-19 21:45:20 +01:00
.shellcheckrc Fix shellcheck warnings 2022-11-11 13:40:13 +01:00
.vale.ini Add docs to repo (#38) 2022-09-02 11:52:42 +02:00
BUILD.bazel bazel: allow custom container_prefix (#1693) 2023-04-27 11:52:02 +02:00
CMakeLists.txt bazel: use host platform by default (#1434) 2023-03-16 16:13:48 +01:00
CODE_OF_CONDUCT.md Ref/readme (#375) 2022-08-19 14:54:11 +02:00
CODEOWNERS bazel: remove apko and Dockerfile where Bazel is used to build container images 2023-04-18 15:35:15 +02:00
CONTRIBUTING.md dev-docs: move into top-level dir (#924) 2023-01-10 14:18:41 +01:00
go.mod deps: update module golang.org/x/tools to v0.8.0 (#1642) 2023-04-12 17:31:48 +02:00
go.sum deps: update module golang.org/x/tools to v0.8.0 (#1642) 2023-04-12 17:31:48 +02:00
go.work go: clean work file (#1537) 2023-03-28 18:15:42 +02:00
LICENSE add license 2022-09-05 09:17:25 +02:00
netlify.toml Add docs to repo (#38) 2022-09-02 11:52:42 +02:00
README.md docs: update govulncheck badge to new workflow (#1531) 2023-03-29 10:26:45 +02:00
renovate.json ci: fix grouping of renovate groups (#1585) 2023-04-03 13:37:56 +02:00
SECURITY.md promote new github security reporting feature 2022-11-10 16:31:13 +01:00
shell.nix bazel: add build files for go (#1186) 2023-03-09 15:23:42 +01:00
version.txt chore: bump version.txt 2023-04-06 18:20:50 +02:00
WORKSPACE.bazel deps: rename bazel-zig-cc to hermetic_cc_toolchain (#1695) 2023-04-27 10:27:43 +02:00

Constellation

Always Encrypted Kubernetes

Constellation License Govulncheck Go Report Discord Twitter

Constellation is a Kubernetes engine that aims to provide the best possible data security. It wraps your K8s cluster into a single confidential context that is shielded from the underlying cloud infrastructure. Everything inside is always encrypted, including at runtime in memory. For this, Constellation leverages confidential computing (see the whitepaper) and more specifically Confidential VMs.

Concept

Goals

From a security perspective, Constellation is designed to keep all data always encrypted and to prevent access from the infrastructure layer (i.e., remove the infrastructure from the TCB). This includes access from datacenter employees, privileged cloud admins, and attackers coming through the infrastructure (e.g., malicious co-tenants escalating their privileges).

From a DevOps perspective, Constellation is designed to work just like what you would expect from a modern K8s engine.

Use cases

Encrypting your K8s is good for:

  • Increasing the overall security of your clusters
  • Increasing the trustworthiness of your SaaS offerings
  • Moving sensitive workloads from on-prem to the cloud
  • Meeting regulatory requirements

Features

🔒 Everything always encrypted

  • Runtime encryption: All nodes run inside AMD SEV-based Confidential VMs (CVMs). Support for Intel TDX will be added in the future.
  • Transparent encryption of network and storage: All pod-to-pod traffic and all writes to persistent storage are automatically encrypted
  • Transparent key management: All cryptographic keys are managed within the confidential context

🔍 Everything verifiable

🚀 Performance and scale

  • High availability with multi-master architecture and stacked etcd topology
  • Dynamic cluster autoscaling with verification and secure bootstrapping of new nodes
  • Competitive performance (see K-Bench comparison with AKS and GKE)

🧩 Easy to use and integrate

Getting started

If you're already familiar with Kubernetes, it's easy to get started with Constellation:

  1. 📦 Install the CLI
  2. ⌨️ Create a Constellation cluster in the cloud or locally
  3. 🏎️ Run your app

Constellation Shell

Live demos

We're running public instances of popular software on Constellation:

These instances run on CVMs in Azure and Constellation keeps them end-to-end confidential.

Documentation

To learn more, see the documentation. You may want to start with one of the following sections.

Support

  • If something doesn't work, make sure to use the latest release and check out the known issues.
  • Please file an issue to get help or report a bug.
  • Join the Discord to have a chat on confidential computing and Constellation.
  • Visit our blog for technical deep-dives and tutorials and follow us on Twitter for news.
  • Edgeless Systems also offers Enterprise Support.

Contributing

Refer to CONTRIBUTING.md on how to contribute. The most important points:

Warning

Please report any security issue via a private GitHub vulnerability report or write to security@edgeless.systems.

License

The Constellation source code is licensed under the GNU Affero General Public License v3.0. Edgeless Systems provides pre-built and signed binaries and images for Constellation. You may use these free of charge to create and run services for internal consumption, evaluation purposes, or non-commercial use. You can find more information in the license section of the docs.