Remove service provider in CLI commands in docs

This commit is contained in:
Nils Hanke 2022-09-07 16:57:22 +02:00 committed by Nils Hanke
parent 46c461c23e
commit c9c954c675
3 changed files with 4 additions and 56 deletions

View file

@ -157,23 +157,10 @@ The following steps will guide you through the process of creating a cluster and
4. Create the cluster with one control-plane node and two worker nodes. `constellation create` uses options set in `constellation-conf.yaml` automatically. 4. Create the cluster with one control-plane node and two worker nodes. `constellation create` uses options set in `constellation-conf.yaml` automatically.
<tabs>
<tabItem value="azure" label="Azure" default>
```bash ```bash
constellation create azure --control-plane-nodes 1 --worker-nodes 2 -y constellation create --control-plane-nodes 1 --worker-nodes 2 -y
``` ```
</tabItem>
<tabItem value="gcp" label="GCP">
```bash
constellation create gcp --control-plane-nodes 1 --worker-nodes 2 -y
```
</tabItem>
</tabs>
This should give the following output: This should give the following output:
```shell-session ```shell-session

View file

@ -56,23 +56,10 @@ For more details, see the [verification section](../workflows/verify.md).
The following command creates a cluster with one control-plane and two worker nodes: The following command creates a cluster with one control-plane and two worker nodes:
<tabs>
<tabItem value="azure" label="Azure" default>
```bash ```bash
constellation create azure --control-plane-nodes 1 --worker-nodes 2 -y constellation create --control-plane-nodes 1 --worker-nodes 2 -y
``` ```
</tabItem>
<tabItem value="gcp" label="GCP" default>
```bash
constellation create gcp --control-plane-nodes 1 --worker-nodes 2 -y
```
</tabItem>
</tabs>
For details on the flags and a list of supported instance types, consult the command help via `constellation create -h`. For details on the flags and a list of supported instance types, consult the command help via `constellation create -h`.
*create* will store your cluster's configuration to a file named [`constellation-state.json`](../architecture/orchestration.md#installation-process) in your current directory. *create* will store your cluster's configuration to a file named [`constellation-state.json`](../architecture/orchestration.md#installation-process) in your current directory.

View file

@ -22,23 +22,10 @@ Once measurements are configured, this command verifies an attestation statement
The following command performs attestation on the Constellation in your current workspace: The following command performs attestation on the Constellation in your current workspace:
<tabs>
<tabItem value="azure" label="Azure" default>
```bash ```bash
constellation verify azure constellation verify
``` ```
</tabItem>
<tabItem value="gcp" label="GCP" default>
```bash
constellation verify gcp
```
</tabItem>
</tabs>
The command makes sure the value passed to `-cluster-id` matches the *clusterID* presented in the attestation statement. The command makes sure the value passed to `-cluster-id` matches the *clusterID* presented in the attestation statement.
This allows you to verify that you are connecting to a specific Constellation instance This allows you to verify that you are connecting to a specific Constellation instance
Additionally, the confidential computing capabilities, as well as the VM image, are verified to match the expected configurations. Additionally, the confidential computing capabilities, as well as the VM image, are verified to match the expected configurations.
@ -50,19 +37,6 @@ You can provide additional arguments for `verify` to verify any Constellation yo
* The IP address of a running Constellation's [VerificationService](../architecture/components.md#verification-service). The *VerificationService* is exposed via a NodePort service using the external IP address of your cluster. Run `kubectl get nodes -o wide` and look for `EXTERNAL-IP`. * The IP address of a running Constellation's [VerificationService](../architecture/components.md#verification-service). The *VerificationService* is exposed via a NodePort service using the external IP address of your cluster. Run `kubectl get nodes -o wide` and look for `EXTERNAL-IP`.
* The Constellation's *clusterID*. See [cluster identity](../architecture/keys.md#cluster-identity) for more details. * The Constellation's *clusterID*. See [cluster identity](../architecture/keys.md#cluster-identity) for more details.
<tabs>
<tabItem value="azure" label="Azure" default>
```bash ```bash
constellation verify azure -e 192.0.2.1 --cluster-id Q29uc3RlbGxhdGlvbkRvY3VtZW50YXRpb25TZWNyZXQ= constellation verify -e 192.0.2.1 --cluster-id Q29uc3RlbGxhdGlvbkRvY3VtZW50YXRpb25TZWNyZXQ=
``` ```
</tabItem>
<tabItem value="gcp" label="GCP" default>
```bash
constellation verify gcp -e 192.0.2.1 --cluster-id Q29uc3RlbGxhdGlvbkRvY3VtZW50YXRpb25TZWNyZXQ=
```
</tabItem>
</tabs>