-
Notifications
You must be signed in to change notification settings - Fork 1.6k
fix: Virtual Machine Installation WorkloadGroup yaml sample typo #16872
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
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: 王然 <[email protected]>
|
😊 Welcome! This is either your first contribution to the Istio documentation repo, or
Thanks for contributing! Courtesy of your friendly welcome wagon. |
|
Hi @chinaran. Thanks for your PR. I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
/ok-to-test |
|
@chinaran, you will have to run |
Signed-off-by: 王然 <[email protected]>
|
@sridhargaddam Thanks for your reminder, it has been updated. |
sridhargaddam
left a comment
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, thanks.
|
@sridhargaddam Is this PR ready to be merged, please? |
I do not have merge permissions. @istio/wg-docs-maintainers-english can you PTAL? |
|
I am wondering how the docs test was passing before, without this change. Can you make sure to update the test to cover this? |
@kfaseela I'm not familiar with document testing. Which test are you referring to? |
@sridhargaddam could you please help point to the respective test files? I am a bit busy for the next two weeks. |
The VM tests actually largely do not test the installation as it is slightly different due to the "virtual machines" actually being nothing more than a docker container running inside of a VM, and the cluster being kind as docker containers next to it. The changed code is actually not tested. |
Reviewers