2020-06-10 02:47:10 +03:00
|
|
|
### Which issue this PR addresses:
|
|
|
|
|
|
|
|
|
|
<!--
|
Ssh docs/examples , PR template update (#1446)
* Fix -> remove the dash, valid names are master0,master1,master2, but not master-0,master-1,master-2
* Add more information, show example with nodes, show multiple ways to ssh to a worker node
* Change VSTS to ADO because that is the tool we use now
* Add an additional example of connecting to a worker
* respected->respective, english is hard
2021-04-19 13:36:36 +03:00
|
|
|
Please include a link to the ADO work item as well as any GitHub issues.
|
2020-06-10 02:47:10 +03:00
|
|
|
|
|
|
|
|
Usage: `Fixes #<GitHub issue number>`, or `Fixes (paste link of issue)`.
|
|
|
|
|
-->
|
|
|
|
|
Fixes
|
|
|
|
|
|
|
|
|
|
### What this PR does / why we need it:
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
Include a brief summary of what the PR is intended to accomplish and how the PR
|
|
|
|
|
does it. (2-3 sentences)
|
|
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
### Test plan for issue:
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
How did you test that this PR works?
|
|
|
|
|
|
|
|
|
|
- Are there unit tests?
|
|
|
|
|
- Are there integration/e2e tests?
|
|
|
|
|
- If it is not possible to write automated tests, explain why and document how
|
|
|
|
|
to manually test and verify the feature.
|
|
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
### Is there any documentation that needs to be updated for this PR?
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
- If yes and the docs are in GitHub, include doc updates in the PR.
|
Ssh docs/examples , PR template update (#1446)
* Fix -> remove the dash, valid names are master0,master1,master2, but not master-0,master-1,master-2
* Add more information, show example with nodes, show multiple ways to ssh to a worker node
* Change VSTS to ADO because that is the tool we use now
* Add an additional example of connecting to a worker
* respected->respective, english is hard
2021-04-19 13:36:36 +03:00
|
|
|
- If yes and the docs are not in GitHub (i.e. ADO wiki), include a link to the
|
2020-06-10 02:47:10 +03:00
|
|
|
docs.
|
|
|
|
|
- If no, explain why (e.g. "tech debt cleanup, N/A").
|
|
|
|
|
-->
|
2024-03-07 00:51:22 +03:00
|
|
|
|
|
|
|
|
### How do you know this will function as expected in production?
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
- Does adequate telemetry, monitoring and documentation exist to effectively operate your change?
|
|
|
|
|
- Have failure modes been identified and mitigated?
|
|
|
|
|
-->
|
