Git-Mirrors/constellation
1
0
Fork 0
mirror of https://github.com/edgelesssys/constellation.git synced 2024-10-01 01:36:09 -04:00
Code Issues Packages Projects Releases Wiki Activity

docs: publish

Browse Source
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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/versioned_docs/version-2.0/architecture/orchestration.md
View File

@ -78,7 +78,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.

2
docs/versioned_docs/version-2.1/architecture/orchestration.md
View File

@ -78,7 +78,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.

2
docs/versioned_docs/version-2.2/architecture/orchestration.md
View File

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

2
docs/versioned_docs/version-2.2/getting-started/install.md
View File

@ -111,7 +111,7 @@ If you don't have a cloud subscription, you can try [MiniConstellation](first-st
<tabs groupId="csp">
<tabItem value="azure" label="Azure">
The following resource providers need to be need to be [registered](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider) in your subscription:
The following [resource providers need to be need to be registered](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider) in your subscription:
* `Microsoft.Compute`
* `Microsoft.ManagedIdentity`
* `Microsoft.Network`

4
docs/versioned_docs/version-2.3/architecture/orchestration.md
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.

2
docs/versioned_docs/version-2.3/getting-started/install.md
View File

@ -111,7 +111,7 @@ If you don't have a cloud subscription, you can try [MiniConstellation](first-st
<tabs groupId="csp">
<tabItem value="azure" label="Azure">
The following resource providers need to be need to be [registered](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider) in your subscription:
The following [resource providers need to be registered](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider) in your subscription:
* `Microsoft.Compute`
* `Microsoft.ManagedIdentity`
* `Microsoft.Network`

2
docs/versioned_docs/version-2.3/workflows/config.md
View File

@ -32,7 +32,7 @@ constellation config generate aws
This creates the file `constellation-conf.yaml` in the current directory.
## Choosing VM types
## Choosing a VM type
Constellation supports the following VM types:
<tabs groupId="csp">

4
docs/versioned_docs/version-2.4/architecture/orchestration.md
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.

2
docs/versioned_docs/version-2.4/getting-started/install.md
View File

@ -111,7 +111,7 @@ If you don't have a cloud subscription, you can try [MiniConstellation](first-st
<tabs groupId="csp">
<tabItem value="azure" label="Azure">
The following resource providers need to be need to be [registered](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider) in your subscription:
The following [resource providers need to be registered](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider) in your subscription:
* `Microsoft.Compute`
* `Microsoft.ManagedIdentity`
* `Microsoft.Network`

2
docs/versioned_docs/version-2.4/workflows/config.md
View File

@ -32,7 +32,7 @@ constellation config generate aws
This creates the file `constellation-conf.yaml` in the current directory.
## Choosing VM types
## Choosing a VM type
Constellation supports the following VM types:
<tabs groupId="csp">

4
docs/versioned_docs/version-2.5/architecture/orchestration.md
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.

2
docs/versioned_docs/version-2.5/getting-started/install.md
View File

@ -111,7 +111,7 @@ If you don't have a cloud subscription, you can try [MiniConstellation](first-st
<tabs groupId="csp">
<tabItem value="azure" label="Azure">
The following resource providers need to be need to be [registered](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider) in your subscription:
The following [resource providers need to be registered](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider) in your subscription:
* `Microsoft.Compute`
* `Microsoft.ManagedIdentity`
* `Microsoft.Network`

2
docs/versioned_docs/version-2.5/workflows/config.md
View File

@ -36,7 +36,7 @@ This creates the file `constellation-conf.yaml` in the current directory.
You can also automatically generate a configuration file by adding the `--generate-config` flag to the `constellation iam create` command when [creating an IAM configuration](#creating-an-iam-configuration).
:::
## Choosing VM types
## Choosing a VM type
Constellation supports the following VM types:
<tabs groupId="csp">