Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add note about current AWS CVM issues #2418

Merged
merged 1 commit into from
Oct 10, 2023
Merged

Conversation

thomasten
Copy link
Member

What do you think of this kind of note? Is it at the right place?

@thomasten thomasten added the no changelog Change won't be listed in release changelog label Oct 6, 2023
@thomasten thomasten requested review from m1ghtym0 and derpsteb October 6, 2023 12:58
@netlify
Copy link

netlify bot commented Oct 6, 2023

Deploy Preview for constellation-docs ready!

Name Link
🔨 Latest commit 552bed9
🔍 Latest deploy log https://app.netlify.com/sites/constellation-docs/deploys/652517ab323e460007c55329
😎 Deploy Preview https://deploy-preview-2418--constellation-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -170,6 +170,16 @@ If you encounter any problem with the following steps, make sure to use the [lat

:::

:::note

**AWS**: Currently, confidential VMs may temporarily fail to boot. If creating or initializing a cluster fails, terminate the cluster and try again later. Alternatively, you can use non-confidential Nitro VMs for evaluation purposes. To do so, generate a new configuration with the `aws-nitro-tpm` attestation variant:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**AWS**: Currently, confidential VMs may temporarily fail to boot. If creating or initializing a cluster fails, terminate the cluster and try again later. Alternatively, you can use non-confidential Nitro VMs for evaluation purposes. To do so, generate a new configuration with the `aws-nitro-tpm` attestation variant:
**AWS**: Currently, confidential VMs may temporarily fail to boot. AWS is actively working on a solution. If creating or initializing a cluster fails, terminate the cluster and try again later. Alternatively, you can use non-confidential Nitro VMs for evaluation purposes. To do so, generate a new configuration with the `aws-nitro-tpm` attestation variant:

Mention that this is out of our control? Could also be sth like We are actively working with AWS to remediate the issue.

@thomasten thomasten force-pushed the feat/docs/aws-cvm-issues branch from 836753d to 552bed9 Compare October 10, 2023 09:21
@thomasten thomasten merged commit 7141586 into main Oct 10, 2023
@thomasten thomasten deleted the feat/docs/aws-cvm-issues branch October 10, 2023 10:11
@malt3 malt3 mentioned this pull request Oct 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no changelog Change won't be listed in release changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants