From 491249fea6ba712a387df20f494956cf5223a7ca Mon Sep 17 00:00:00 2001 From: Nils Hanke Date: Thu, 8 Sep 2022 15:46:08 +0200 Subject: [PATCH] Sync Azure/GCP tab choice --- docs/docs/architecture/attestation.md | 2 +- docs/docs/getting-started/first-steps.md | 8 ++++---- docs/docs/getting-started/install.md | 4 ++-- docs/docs/workflows/create.md | 2 +- docs/docs/workflows/recovery.md | 2 +- docs/docs/workflows/scale.md | 4 ++-- docs/docs/workflows/storage.md | 6 +++--- docs/docs/workflows/troubleshooting.md | 2 +- 8 files changed, 15 insertions(+), 15 deletions(-) diff --git a/docs/docs/architecture/attestation.md b/docs/docs/architecture/attestation.md index 56d006b25..abd9d3691 100644 --- a/docs/docs/architecture/attestation.md +++ b/docs/docs/architecture/attestation.md @@ -124,7 +124,7 @@ Constellation allows to specify in the [config](../reference/config.md) which me Enforcing non-reproducible measurements controlled by the cloud provider means that changes in these values require manual updates to the cluster's config. By default, Constellation only enforces measurements that are stable values produced by the infrastructure or by Constellation directly. - + Constellation leverages the [vTPM](https://docs.microsoft.com/en-us/azure/virtual-machines/trusted-launch#vtpm) feature of Azure CVMs for runtime measurements. diff --git a/docs/docs/getting-started/first-steps.md b/docs/docs/getting-started/first-steps.md index 361b0ceec..e28c380ad 100644 --- a/docs/docs/getting-started/first-steps.md +++ b/docs/docs/getting-started/first-steps.md @@ -6,7 +6,7 @@ The following steps will guide you through the process of creating a cluster and 1. Create the configuration file for your selected cloud provider. - + ```bash @@ -27,8 +27,8 @@ The following steps will guide you through the process of creating a cluster and 2. Fill in your cloud provider specific information: - - + + For a quick start it's recommended to use our `az` script to automatically create all required resources: @@ -114,7 +114,7 @@ The following steps will guide you through the process of creating a cluster and Set the configuration value to the secret value. - + For a quick start it's recommended to use our `gcloud` script to automatically create all required resources: diff --git a/docs/docs/getting-started/install.md b/docs/docs/getting-started/install.md index 052bbc986..055cf2030 100644 --- a/docs/docs/getting-started/install.md +++ b/docs/docs/getting-started/install.md @@ -62,7 +62,7 @@ Don't use the testing methods for setting up a production-grade Constellation cl ::: - + **Testing** @@ -116,7 +116,7 @@ For production clusters, use one of the following options on a trusted machine: ### Authorization - + Your user account needs the following permissions to set up a Constellation cluster: diff --git a/docs/docs/workflows/create.md b/docs/docs/workflows/create.md index 73c4f245d..2cb1459ab 100644 --- a/docs/docs/workflows/create.md +++ b/docs/docs/workflows/create.md @@ -25,7 +25,7 @@ You can find the currently supported machine types for your cloud environment in Constellation can generate a configuration file for your cloud provider: - + ```bash diff --git a/docs/docs/workflows/recovery.md b/docs/docs/workflows/recovery.md index 318516bbe..e6b54991a 100644 --- a/docs/docs/workflows/recovery.md +++ b/docs/docs/workflows/recovery.md @@ -28,7 +28,7 @@ Constellation provides logging information on the boot process and status via [c In the following, you'll find detailed descriptions for identifying clusters stuck in recovery for each cloud environment. Once you've identified that your cluster is in an unhealthy state you can use the [recovery](recovery.md#recover-your-cluster) command of the Constellation CLI to restore it. - + In the Azure cloud portal find the cluster's resource group `-` diff --git a/docs/docs/workflows/scale.md b/docs/docs/workflows/scale.md index 37f93fa60..81e3902fb 100644 --- a/docs/docs/workflows/scale.md +++ b/docs/docs/workflows/scale.md @@ -8,7 +8,7 @@ Constellation provides all features of a Kubernetes cluster including scaling an Alternatively, you can choose to manually scale your cluster: - + 1. Find your Constellation resource group. @@ -34,7 +34,7 @@ Control-plane nodes can **only be scaled manually and only scaled up**! To increase the number of control-plane nodes, follow these steps: - + diff --git a/docs/docs/workflows/storage.md b/docs/docs/workflows/storage.md index 995c58fcf..66a229b84 100644 --- a/docs/docs/workflows/storage.md +++ b/docs/docs/workflows/storage.md @@ -22,7 +22,7 @@ For more details see [encrypted persistent storage](../architecture/encrypted-st Constellation can use the following drivers which offer node level encryption and optional integrity protection. - + 1. [Azure Disk Storage](https://github.com/edgelesssys/constellation-azuredisk-csi-driver) @@ -48,7 +48,7 @@ Note that in case the options above aren't a suitable solution for you, Constell The following installation guide gives a brief overview of using CSI-based confidential cloud storage for persistent volumes in Constellation. - + 1. Install the CSI driver: @@ -184,7 +184,7 @@ By default, integrity protection is disabled for performance reasons. If you wan ### Set the default storage class The examples above are defined to be automatically set as the default storage class. The default storage class is responsible for all persistent volume claims that don't explicitly request `storageClassName`. In case you need to change the default, follow the steps below: - + 1. List the storage classes in your cluster: diff --git a/docs/docs/workflows/troubleshooting.md b/docs/docs/workflows/troubleshooting.md index fbdc6940c..0238d70ee 100644 --- a/docs/docs/workflows/troubleshooting.md +++ b/docs/docs/workflows/troubleshooting.md @@ -8,7 +8,7 @@ To provide information during early stages of the node's boot process, Constella You can view these information in the follow places: - + 1. In your Azure subscription find the Constellation resource group.