-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
OSDOCS-2922: Added a warning for deleting clusters. #41128
OSDOCS-2922: Added a warning for deleting clusters. #41128
Conversation
✔️ Deploy Preview for osdocs ready! 🔨 Explore the source changes: 798f749 🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/61fc40afb785f4000783142e 😎 Browse the preview: https://deploy-preview-41128--osdocs.netlify.app |
8347e18
to
a283d9d
Compare
modules/rosa-deleting-cluster.adoc
Outdated
|
||
[IMPORTANT] | ||
==== | ||
You must remove any network configurations, such as VPN configurations and VPC peering, before you delete a cluster. If these configurations remain, then the cluster will not delete properly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You must remove any network configurations, such as VPN configurations and VPC peering, before you delete a cluster. If these configurations remain, then the cluster will not delete properly. | |
You must remove any network configurations, such as VPN configurations and VPC peering, before you delete a cluster. If these configurations remain, then the cluster will not delete properly. | |
+ | |
ifdef:sts[] | |
Account-wide IAM roles and policies might be used by other ROSA clusters in the same AWS account. You must only remove the resources if they are not required by other clusters. | |
endif::sts[] |
@okashi18, so I served this section three different ways. @mjpytlak made some good suggestions on how to show this correctly. Currently, it will display two important notes on the STS side. This isn't really bad per se, since we want the user two note both important comments. These are separate warnings that can result in issues if ignored. Another option that Mike documented in the ticket is to combine the two notes based on context. The first image shows the notes combined on STS: Finally, here's what it looks like if I change that second important note into a scarily worded paragraph: I am flexible with the way we should document this, though I think the second option is a bit too disrupting. I would prefer the third option, first option, then second. Mike can weigh in on this as well. |
@EricPonvelle As we discussed, I find that doc sets (not just Red Hat) overuse note and important admonitions. To take your 3rd option a step further (which I happen to like best), why not list removing network configurations (1st important) as a prerequisite? Prerequisites
And to take this even a step further for STS: Prerequisites
Note that I avoided the scary language all-together. :) |
@mjpytlak - I like that idea of putting the removal of network configurations in the prereqs. Though I would keep the note about the account roles. |
a283d9d
to
d681e67
Compare
973ad96
to
2e16024
Compare
5f671a4
to
fa19c0d
Compare
fa19c0d
to
571aa3a
Compare
lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some nits and feedback. Nothing major.
55539b0
to
cde9b3d
Compare
== Prerequisites | ||
|
||
* If {product-title} created a VPC, you must remove the following before you delete your cluster: | ||
* network configurations, such as VPN configurations and VPC peering |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should "VPC peering" be something like "VPC peering connections" or "VPC peering configurations"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@0kashi - which one should it be?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
VPC peering connections is fine
[id="prerequisites_rosa-deleting-cluster"] | ||
== Prerequisites | ||
|
||
* If {product-title} created a VPC, you must remove the following before you delete your cluster: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* If {product-title} created a VPC, you must remove the following before you delete your cluster: | |
* If {product-title} created a VPC, you must remove the following [$PLURAL_NOUN] before you delete your cluster: |
Better for translation, but nothing in particular is coming to mind. :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maxwelldb This work?
- If {product-title} created a VPC, you must remove the following items from your cluster before you can successfully delete your cluster:
c5fa592
to
269af2d
Compare
269af2d
to
798f749
Compare
/cherry-pick enterprise-4.9 |
/cherry-pick enterprise-4.10 |
@EricPonvelle: new pull request created: #41389 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@EricPonvelle: new pull request created: #41390 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This PR adds a note to a few topics to warn users that they should remove all network configurations before they delete a cluster.
JIRA: https://issues.redhat.com/browse/OSDOCS-2922
PREVIEWS:
1. Revoking access to ROSA (STS) - https://deploy-preview-41128--osdocs.netlify.app/openshift-rosa/latest/rosa_getting_started_sts/rosa-sts-deleting-access-cluster.html2. Deleting a cluster - https://deploy-preview-41128--osdocs.netlify.app/openshift-rosa/latest/rosa_getting_started/rosa-deleting-cluster.html
3. Deleting cluster (STS) - https://deploy-preview-41128--osdocs.netlify.app/openshift-rosa/latest/rosa_getting_started_sts/rosa-sts-deleting-cluster.html