mirror of
https://github.com/edgelesssys/constellation.git
synced 2024-10-01 01:36:09 -04:00
Rewording in "Getting started" (#193)
* Small changes * Update docs/docs/getting-started/first-steps.md Co-authored-by: Nils Hanke <Nirusu@users.noreply.github.com> * Update docs/docs/getting-started/first-steps.md Co-authored-by: Nils Hanke <Nirusu@users.noreply.github.com> * Update docs/versioned_docs/version-2.0/getting-started/first-steps.md Co-authored-by: Nils Hanke <Nirusu@users.noreply.github.com> Co-authored-by: Nils Hanke <Nirusu@users.noreply.github.com>
This commit is contained in:
parent
9f0a18cbe2
commit
2b32b79026
@ -180,7 +180,7 @@ The following steps guide you through the process of creating a cluster and depl
|
||||
|
||||
:::tip
|
||||
|
||||
On Azure, after creating a user-assigned managed identity and app registration, Azure AD needs time to propagate permissions to different regions due to replication lag. To avoid permission errors, it's recommended to wait at least 15 minutes after role assignments before creating the cluster.
|
||||
On Azure, you may need to wait 15+ minutes at this point for role assignments to propagate.
|
||||
|
||||
:::
|
||||
|
||||
@ -220,6 +220,12 @@ The following steps guide you through the process of creating a cluster and depl
|
||||
Keep `constellation-mastersecret.json` somewhere safe.
|
||||
This will allow you to [recover your cluster](../workflows/recovery.md) in case of a disaster.
|
||||
|
||||
:::info
|
||||
|
||||
Depending on your CSP and region, `constellation init` may take 10+ minutes to complete.
|
||||
|
||||
:::
|
||||
|
||||
6. Configure kubectl
|
||||
|
||||
```bash
|
||||
|
@ -135,7 +135,7 @@ Follow Google's guide on [understanding](https://cloud.google.com/iam/docs/under
|
||||
|
||||
You need to authenticate with your CSP. The following lists the required steps for *testing* and *production* environments.
|
||||
|
||||
:::danger
|
||||
:::note
|
||||
The steps for a *testing* environment are simpler. However, they may expose secrets to the CSP. If in doubt, follow the *production* steps.
|
||||
:::
|
||||
|
||||
|
@ -180,7 +180,7 @@ The following steps guide you through the process of creating a cluster and depl
|
||||
|
||||
:::tip
|
||||
|
||||
On Azure, after creating a user-assigned managed identity and app registration, Azure AD needs time to propagate permissions to different regions due to replication lag. To avoid permission errors, it's recommended to wait at least 15 minutes after role assignments before creating the cluster.
|
||||
On Azure, you may need to wait 15+ min. at this point for role assignments to propagate.
|
||||
|
||||
:::
|
||||
|
||||
@ -220,6 +220,12 @@ The following steps guide you through the process of creating a cluster and depl
|
||||
Keep `constellation-mastersecret.json` somewhere safe.
|
||||
This will allow you to [recover your cluster](../workflows/recovery.md) in case of a disaster.
|
||||
|
||||
:::info
|
||||
|
||||
Depending on your CSP and region, `constellation init` may take 10+ minutes to complete.
|
||||
|
||||
:::
|
||||
|
||||
6. Configure kubectl
|
||||
|
||||
```bash
|
||||
|
@ -135,7 +135,7 @@ Follow Google's guide on [understanding](https://cloud.google.com/iam/docs/under
|
||||
|
||||
You need to authenticate with your CSP. The following lists the required steps for *testing* and *production* environments.
|
||||
|
||||
:::danger
|
||||
:::note
|
||||
The steps for a *testing* environment are simpler. However, they may expose secrets to the CSP. If in doubt, follow the *production* steps.
|
||||
:::
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user