docs: publish

This commit is contained in:
Thomas Tendyck 2023-03-06 10:41:56 +01:00 committed by Thomas Tendyck
parent c7f0cf1e79
commit 3471d73c6c
13 changed files with 16 additions and 16 deletions

View file

@ -16,7 +16,7 @@ Note that every operation on a cluster always has to be performed from the direc
## Cluster creation process
To allow for fine-grained configuration of your cluster and cloud environment, Constellation supports an extensive configuration file with strong defaults. [Generating the configuration file](../workflows/create.md#configuration) is typically the first thing you do in the workspace.
To allow for fine-grained configuration of your cluster and cloud environment, Constellation supports an extensive configuration file with strong defaults. [Generating the configuration file](../workflows/config.md) is typically the first thing you do in the workspace.
Altogether, the following files are generated during the creation of a Constellation cluster and stored in the current workspace:
@ -76,7 +76,7 @@ For step-by-step instructions on how to do this, refer to [Upgrade your cluster]
### Attestation of upgrades
With every new image, corresponding measurements are released.
During an update procedure, the CLI provides the new measurements to the [JoinService](components.md#joinservice) securely.
During an update procedure, the CLI provides new measurements to the [JoinService](components.md#joinservice) securely.
New measurements for an updated image are automatically pulled and verified by the CLI following the [supply chain security concept](attestation.md#chain-of-trust) of Constellation.
The [attestation section](attestation.md#cluster-facing-attestation) describes in detail how these measurements are then used by the JoinService for the attestation of nodes.