-
Notifications
You must be signed in to change notification settings - Fork 1.9k
BZ2053605: Add instructions on how to scale up AWS nodes #44431
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
✅ Deploy Preview for osdocs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
07139ec to
df6f9ef
Compare
|
@gpei hi, could you help check if your team can review this? |
|
@sunilcio hi, this should be scaling up via machineset, @sunzhaohua2 could you help to check this? |
|
This is about master instancetype change, we didn't test this before, I can have a try tomorrow and let etcd team help to check, I feel this is not supported. |
|
@xenolinux I added a comment in https://bugzilla.redhat.com/show_bug.cgi?id=2053605#c7, tested with worker machine and master machine, this couldn't change instance type. |
|
@sunzhaohua2 Does t
@sunzhaohua2 Does this mean that this change is unsupported? I am in doubt about whether we can add these steps to our documentation? |
|
@xenolinux sorry for the late reply. Yes, I think this is not supported, at least only this change in the doc is unsupported. We will support this feature in 4.12, this is epic https://issues.redhat.com/browse/OCPCLOUD-1372, this is enhancements doc pr openshift/enhancements#1008 |
|
#44431 (comment) closing this PR since this change is unsupported in the docs. |
Bug
Preview
OCP version: 4.6+
QE contact @sunilcio