Add general guideline for control plane node scaling #344
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DebakelOrakel
force-pushed
the
control-plane-scaling-guide
branch
4 times, most recently
from
77380c2 to
95115f0
Compare
Relates: OCP-840
DebakelOrakel
force-pushed
the
control-plane-scaling-guide
branch
from
95115f0 to
1e5305e
Compare
simu
reviewed
Jul 26, 2024
Comment on lines
+28
to
+30
| | 4 CPU | ||
|
|
||
| 24Gi Memory |
There was a problem hiding this comment.
This size doesn't really make sense on any provider except vSphere where we can do whatever we want. Neither cloudscale nor Exoscale have a 4 CPU / 24Gi VM size.
There was a problem hiding this comment.
vSphere has 😁
Co-authored-by: Simon Gerber <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relates: OCP-840