aws / aws/aws-eks-best-practices
Windows Networking
- Dominant language
- Python
- Stars
- 2.2k
- Forks
- 567
- Avg merge
- 6d 6h
- Merged PRs (30d)
- 3
Description
**Describe the problem**
Windows Networking page references a link to eks workshops that doesnt exist.
>DSR enablement can be verified following the instructions in the [Microsoft Networking blog](https://techcommunity.microsoft.com/t5/networking-blog/direct-server-return-dsr-in-a-nutshell/ba-p/693710) and the [Windows Containers on AWS Lab](https://catalog.us-east-1.prod.workshops.aws/v2/workshops/1de8014a-d598-4cb5-a119-801576492564/en-US/lab3-add-win-worker-node/lab3-5-check-dsr-status).
Should probably also mention: https://kubernetes.io/docs/concepts/services-networking/windows-networking/
The link to https://techcommunity.microsoft.com/t5/networking-blog/direct-server-return-dsr-in-a-nutshell/ba-p/693710 is valid but the instructions aren't policy.txt is now a json array by default and contains the following
```json
{
"ID": "43dbc27c-7b3a-4136-b3f1-57a4f2148f7a",
"Version": 1234566,
"SchemaVersion": {
"Major": 2,
"Minor": 0
},
"HostComputeEndpoints": [
"b0967432-f0f2-4fa1-a1ab-9891df132931"
],
"FrontendVIPs": [
"172.20.178.147"
],
"PortMappings": [
{
"Protocol": 6,
"InternalPort": 8085,
"ExternalPort": 80
}
],
"Flags": 1
},
```
https://github.com/microsoft/SDN/blob/master/Kubernetes/windows/debug/Debug.md may be a slightly better link. But the instructions no longer match the function.
hcsdiag.txt contains references to DSR per endpoint but its not the most useful output.
**References**
Link References
`https://aws.github.io/aws-eks-best-practices/windows/docs/networking/`
`https://catalog.us-east-1.prod.workshops.aws/workshops/1de8014a-d598-4cb5-a119-801576492564/en-US/lab3-add-win-worker-node/lab3-5-check-dsr-status`
Contributor guide
Research direction
Start with the Windows Networking page and inspect the referenced AWS EKS workshop link. Compare its DSR instructions with the Microsoft Networking blog, Kubernetes Windows networking documentation, and the mentioned SDN Debug.md, policy.txt, and hcsdiag.txt outputs; done means replacing the broken link and documenting instructions that match the current diagnostics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- documentation, networking
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100