
* Quick pass over create.md * pass over verify.md * Re-arrange workflows * Quick polish of scale.md and upgrade.md * Quick polish of terminate.md * Cut recovery.md down * Brush over ssh * storage * Brush over trusted launch VMs * Update docs/docs/workflows/verify-cluster.md Co-authored-by: Thomas Tendyck <51411342+thomasten@users.noreply.github.com> * Update docs/docs/workflows/verify-cluster.md Co-authored-by: Thomas Tendyck <51411342+thomasten@users.noreply.github.com> * Update docs/docs/workflows/verify-cluster.md Co-authored-by: Thomas Tendyck <51411342+thomasten@users.noreply.github.com> * Add Azure back to title * Update docs/docs/workflows/verify-cluster.md Co-authored-by: Thomas Tendyck <51411342+thomasten@users.noreply.github.com> * fix lint errors * publish to 2.0 Co-authored-by: Thomas Tendyck <51411342+thomasten@users.noreply.github.com> Co-authored-by: Thomas Tendyck <tt@edgeless.systems>
2.4 KiB
Manually verify your cluster
Constellation's attestation feature allows you, or a third party, to explicitly verify the integrity and confidentiality of your Constellation cluster.
:::note
The steps below are purely optional. They're automatically executed by constellation init
when you initialize your cluster. The constellation verify
command mostly has an illustrative purpose.
:::
Fetch measurements
To verify the integrity of Constellation you need trusted measurements to verify against. For each node image released by Edgeless Systems, there are signed measurements, which you can download using the CLI:
constellation config fetch-measurements
This command performs the following steps:
- Download the signed measurements for the configured image. By default, this will use Edgeless Systems' public measurement registry.
- Verify the signed images. This will use Edgeless Systems' public key.
- Write measurements into configuration file.
The verify command
The verify
command obtains and verifies an attestation statement from a running Constellation cluster.
constellation verify [--cluster-id ...]
From the attestation statement, the command verifies the following properties:
- The cluster is using the correct Confidential VM (CVM) type.
- Inside the CVMs, the correct node images are running. The node images are identified through the measurements obtained in the previous step.
- The unique ID of the cluster matches the one passed in via
--cluster-id
.
Once the above properties are verified, you know that you are talking to the right Constellation cluster and it's in a good and trustworthy shape.
Custom arguments
The verify
command also allows you to verify any Constellation deployment that you have network access to. For this you need to following:
- The IP address of a running Constellation cluster's VerificationService. The
VerificationService
is exposed via aNodePort
service using the external IP address of your cluster. Runkubectl get nodes -o wide
and look forEXTERNAL-IP
. - The cluster's clusterID. See cluster identity for more details.
For example:
constellation verify -e 192.0.2.1 --cluster-id Q29uc3RlbGxhdGlvbkRvY3VtZW50YXRpb25TZWNyZXQ=