Moritz Sanft 402a8834ca
ci: add e2e test for self-managed infrastructure (#2472)
* add self-managed infra e2e test

* self-managed terminatio

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* fix upgrade test

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* fix indentation

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* use -r when copying dir

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* add terraform variable parsing

* copy constellation conf

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* remove unnecessary line breaks

* add missing value

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* add image fetching for CSP

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* fix quoting

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* add missing input to internal lb test

* normalize Azure URLs.. Of course

* tidy

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* fix expressions

* initsecret to hex

* update hexdump cmd

* add build test

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* add node / pod cidr outputs

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* explicitly delete the state file

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* add missing license header

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* always write all outputs

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* fix list output

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* remove state-file and admin-conf on destroy

* dont use test payload

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* [remove] use self managed infra in manual e2e for testing

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* init: always skip infrastructure phase

* patch maa in workflow

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>

* default to Constellation-created infra in e2e test

---------

Signed-off-by: Moritz Sanft <58110325+msanft@users.noreply.github.com>
2023-10-27 09:37:26 +02:00
2023-10-19 16:28:07 +02:00
2023-09-27 17:58:19 +02:00
2023-10-22 10:10:48 +02:00
2023-09-27 17:58:19 +02:00
2023-10-12 14:42:24 +02:00
2023-09-27 17:58:19 +02:00
2023-03-23 14:57:38 +01:00
2023-03-10 11:13:05 +01:00
2022-11-11 13:40:13 +01:00
2022-09-02 11:52:42 +02:00
2022-08-19 14:54:11 +02:00
2023-10-20 17:17:59 +02:00
2023-10-20 17:17:59 +02:00
2023-10-12 16:11:02 +02:00
2022-09-05 09:17:25 +02:00
2022-09-02 11:52:42 +02:00
2023-10-24 10:20:16 +02:00
2023-10-10 18:33:04 +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

🔍 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

Learn more: "Getting started with Constellation" videos series.

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

Description
Constellation is the first Confidential Kubernetes. Constellation shields entire Kubernetes clusters from the (cloud) infrastructure using confidential computing.
Readme AGPL-3.0 96 MiB
Languages
Go 83%
Starlark 8.4%
HCL 4.3%
Shell 2.4%
Smarty 1.2%
Other 0.6%