|
|
||
|---|---|---|
| .github | ||
| 3rdparty | ||
| access_manager | ||
| bootstrapper | ||
| cli | ||
| conformance | ||
| csi | ||
| debugd | ||
| docs | ||
| hack | ||
| image | ||
| internal | ||
| joinservice | ||
| kms | ||
| operators/constellation-node-operator | ||
| proto | ||
| rfc | ||
| state | ||
| terraform/libvirt | ||
| verify | ||
| .dockerignore | ||
| .gitignore | ||
| .golangci.yml | ||
| .lycheeignore | ||
| .vale.ini | ||
| CHANGELOG.md | ||
| CMakeLists.txt | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Dockerfile.build | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| netlify.toml | ||
| README.md | ||
| SECURITY.md | ||
Always Encrypted K8s
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 our whitepaper) and more specifically Confidential VMs.
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 (more)
- Transparent key management: All cryptographic keys are managed within the confidential context (more)
🔍 Everything verifiable
- "Whole cluster" attestation based on the remote-attestation feature of CVMs (more)
- Confidential computing-optimized node images based on Fedora CoreOS; fully measured and integrity-protected (more)
- Supply chain protection with Sigstore (more)
🚀 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
- Constellation is a CNCF-certified Kubernetes. It's aligned to Kubernetes' version support policy and will likely work with your existing workloads and tools.
- ☁️ Support for Azure and GCP, more to come.
Getting started
If you're already familiar with Kubernetes, it's easy to get started with Constellation:
Documentation
To learn more, see the official documentation. You may want to start with one of the following sections.
- Confidential Kubernetes (Constellation vs. AKS/GKE + CVMs)
- Security benefits
- Architecture
Support
- Please ask questions via Discord or file an issue.
- If you experience errors, please create a bug report.
- 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:
- Pull requests are welcome! You need to agree to our Contributor License Agreement.
- Please follow the Code of Conduct.
- ⚠️ To report a security issue, please 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. You can find more information in the license section of the docs.