Nits on the VPA documentation#91921
Conversation
|
🤖 Thu Apr 10 09:31:13 - Prow CI generated the docs preview: https://91921--ocpdocs-pr.netlify.app/openshift-enterprise/latest/machine_management/creating-infrastructure-machinesets.html |
| <3> Set the mode to `Auto`, `Recreate`, or `Off`. The `Recreate` mode should be used rarely, only if you need to ensure that the pods are restarted whenever the resource request changes. | ||
| <4> Specify the containers you want to opt-out and set `mode` to `Off`. | ||
| <3> Set the mode to `Auto`, `Recreate`, `Initial`, or `Off`. The `Recreate` mode should be used rarely, only if you need to ensure that the pods are restarted whenever the resource request changes. | ||
| <4> Specify the containers you want to opt-out of and set `mode` to `Off`. |
There was a problem hiding this comment.
Specify the containers you want to opt-out of
This means I want to opt out of the container, where we want to opt the container out of the VPA. How about:
Specify the containers that you do not want updated by the VPA and set the
modetoOff.
There was a problem hiding this comment.
Yes, I think that's best.
Co-authored-by: Michael Burke <mburke@redhat.com>
c78a096 to
c03872d
Compare
|
Awesome @mburke5678 , I've rebased and committed your suggestions. |
|
@prozehna: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
|
/cherrypick enterprise-4.12 |
|
/cherrypick enterprise-4.13 |
|
/cherrypick enterprise-4.14 |
|
/cherrypick enterprise-4.15 |
|
/cherrypick enterprise-4.16 |
|
/cherrypick enterprise-4.17 |
|
/cherrypick enterprise-4.18 |
|
/cherrypick enterprise-4.19 |
|
@mburke5678: #91921 failed to apply on top of branch "enterprise-4.12": DetailsIn 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-sigs/prow repository. |
|
@mburke5678: #91921 failed to apply on top of branch "enterprise-4.13": DetailsIn 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-sigs/prow repository. |
|
@mburke5678: #91921 failed to apply on top of branch "enterprise-4.14": DetailsIn 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-sigs/prow repository. |
|
@mburke5678: #91921 failed to apply on top of branch "enterprise-4.15": DetailsIn 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-sigs/prow repository. |
|
@mburke5678: new pull request created: #91991 DetailsIn 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-sigs/prow repository. |
|
@mburke5678: new pull request created: #91992 DetailsIn 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-sigs/prow repository. |
|
@mburke5678: new pull request created: #91993 DetailsIn 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-sigs/prow repository. |
|
@mburke5678: new pull request created: #91994 DetailsIn 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-sigs/prow repository. |
|
/cherrypick enterprise-4.15 |
|
@mburke5678: #91921 failed to apply on top of branch "enterprise-4.15": DetailsIn 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-sigs/prow repository. |
Attempt #2.
While investigation PR ##91896
I found some nits that'd I'd like to correct.
All but one are punctuation/grammar, the other being a small clarification (node being used changing from master to infra.)
Version(s): 4.12 to 4.19
Issue:
N/A, just nits I found
Link to docs preview:
I don't know how to this
@mburke5678 Since I am QE, I'm not sure who else would run through these suggestions other than the two of us. Would you take a look?