-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Added document for labeling AWS resources on existing clusters #6237
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
Conversation
+ | ||
[source,bash] | ||
---- | ||
# ssystemctl restart atomic-openshift-master-api atomic-openshift-master-controller atomic-openshift-node |
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.
typo here, systemctl
@sdodson, @ahardin-rh, I'd imagine we'd want the labeling documentation. I think we should alert operators of this requirement for dedicated. Just my .02. |
I'd assumed we (Red Hat) were the operators of those environments and dedicated admins needed to take no action of their own? |
@sdodson, Maybe I am misunderstanding the dedicated docs. Is the operations team the only consumers of those? Do we have external consumers running dedicated? If not, then that's fine. I know that we've been deploying dedicated clusters since before these tags were mandated. I'm fine if we do not want to doc it for dedicated. I know there is work to do and we need to go and apply these tags to clusters. |
96f6c44
to
f55a661
Compare
f55a661
to
8fb2222
Compare
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.
LGTM
8fb2222
to
6f690c1
Compare
[rev_history] |
Continues the work in #5732
Preview Build: http://file.rdu.redhat.com/~ahardin/11082017/rrati-fork/admin_guide/aws_cluster_labeling.html