Constellation is the first Confidential Kubernetes. Constellation shields entire Kubernetes clusters from the (cloud) infrastructure using confidential computing.
Go to file
Daniel Weiße c29107f5be
init: create kubeconfig file with unique user/cluster name (#1133)
* Generate kubeconfig with unique name

* Move create name flag to config

* Add name validation to config

* Move name flag in e2e tests to config generation

* Remove name flag from create

* Update ascii cinema flow

---------

Signed-off-by: Daniel Weiße <dw@edgeless.systems>
2023-02-10 13:27:22 +01:00
.github init: create kubeconfig file with unique user/cluster name (#1133) 2023-02-10 13:27:22 +01:00
3rdparty/gcp-guest-agent deps: update ubuntu:22.04 Docker digest to c985bc3 (#1142) 2023-02-03 18:07:34 +01:00
apko deps: update apk package hashes (#1153) 2023-02-08 05:03:02 -05:00
bootstrapper init: create kubeconfig file with unique user/cluster name (#1133) 2023-02-10 13:27:22 +01:00
cli init: create kubeconfig file with unique user/cluster name (#1133) 2023-02-10 13:27:22 +01:00
csi Enable cryptsetup read/write workqueue bypass (#1150) 2023-02-08 12:01:14 +01:00
debugd cli: add version validation and force flag 2023-02-08 12:30:01 +01:00
dev-docs dev-docs: Go package docs (#958) 2023-01-19 15:57:50 +01:00
disk-mapper internal: use go-kms-wrapping for KMS backends (#1012) 2023-02-08 12:03:54 +01:00
docs init: create kubeconfig file with unique user/cluster name (#1133) 2023-02-10 13:27:22 +01:00
e2e dev-docs: Go package docs (#958) 2023-01-19 15:57:50 +01:00
hack cli: change upgrade-plan to upgrade-check 2023-02-08 12:30:01 +01:00
image fix path for qemu/image.raw in S3/CDN (#1106) 2023-01-31 10:44:19 +01:00
internal init: create kubeconfig file with unique user/cluster name (#1133) 2023-02-10 13:27:22 +01:00
joinservice deps: update gcr.io/distroless/static Docker digest to 390b7a3 (#1139) 2023-02-03 18:06:21 +01:00
keyservice internal: use go-kms-wrapping for KMS backends (#1012) 2023-02-08 12:03:54 +01:00
operators/constellation-node-operator internal: use go-kms-wrapping for KMS backends (#1012) 2023-02-08 12:03:54 +01:00
proto deps: update ubuntu:22.04 Docker digest to c985bc3 (#1142) 2023-02-03 18:07:34 +01:00
rfc ci: refactor image measurement generation (#1152) 2023-02-09 13:33:17 +01:00
rpm build: add Bazel workspace and toolchains 2023-01-31 17:55:09 +01:00
toolchains deps: update dependency io_bazel_rules_go to v0.38.1 (#1147) 2023-02-06 13:18:25 +01:00
tools build: add Bazel workspace and toolchains 2023-01-31 17:55:09 +01:00
upgrade-agent dev-docs: Go package docs (#958) 2023-01-19 15:57:50 +01:00
verify ci: add workflow for proto code generation check 2023-01-23 12:20:37 +01:00
.bazelrc deps: update dependency io_bazel_rules_go to v0.38.1 (#1147) 2023-02-06 13:18:25 +01:00
.bazelversion build: pin bazel version 2023-01-31 17:55:09 +01:00
.dockerignore ci: run versionsapi as docker action 2023-01-13 10:23:43 +01:00
.gitignore build: add shell.nix 2023-01-31 17:55:09 +01:00
.golangci.yml Revert "warn about function argument count over 5 (#558)" (#620) 2022-11-22 14:20:11 +01:00
.ko.yaml ko: fix typo 2023-01-19 15:28:00 +01:00
.lycheeignore ci: ignore ntia.gov and twitter checking links 2023-01-04 15:12:39 +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 build: set test timeout 2023-01-31 17:55:09 +01:00
CMakeLists.txt cli: add version validation and force flag 2023-02-08 12:30:01 +01:00
CODE_OF_CONDUCT.md Ref/readme (#375) 2022-08-19 14:54:11 +02:00
CODEOWNERS codeowners: own apko 2023-01-30 16:05:00 +01:00
CONTRIBUTING.md dev-docs: move into top-level dir (#924) 2023-01-10 14:18:41 +01:00
Dockerfile.build deps: update Go to v1.19.5 (#949) 2023-01-12 13:36:17 +01:00
go.mod cli: change upgrade-plan to upgrade-check 2023-02-08 12:30:01 +01:00
go.sum cli: change upgrade-plan to upgrade-check 2023-02-08 12:30:01 +01:00
go.work Upgrade Go version to 1.19 2022-10-28 16:06:53 +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 security issue warning to use Github warning banner (#1050) 2023-01-20 16:17:39 +01:00
renovate.json ci: update renovate pr title 2023-01-19 18:47:49 +01:00
SECURITY.md promote new github security reporting feature 2022-11-10 16:31:13 +01:00
shell.nix build: add shell.nix 2023-01-31 17:55:09 +01:00
WORKSPACE.bazel build: specify C toolchains correctly (#1128) 2023-02-01 12:48:19 +01: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

  • 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.