Skip to content

Update gMSA docs for WS2016 troubleshooting #1383

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.

Sign up for GitHub

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

Open
rpsqrd wants to merge 8 commits into
base: main
Choose a base branch
from
Open

Update gMSA docs for WS2016 troubleshooting #1383

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
ac92321
Merge pull request #1347 from MicrosoftDocs/master
Mar 6, 2020
009bdaf
Update common-problems.md
daschott Mar 6, 2020
8eedfdc
Merge pull request #497 from MicrosoftDocs/master
eross-msft Mar 10, 2020
6f21640
Merge pull request #499 from MicrosoftDocs/master
eross-msft Mar 21, 2020
b140ac1
Merge pull request #1376 from MicrosoftDocs/master
thecloudtaylor Apr 8, 2020
420cfc7
Merge pull request #1378 from MicrosoftDocs/master
alvinmorales1 Apr 9, 2020
16ebc4f
Merge pull request #505 from MicrosoftDocs/master
mamezgeb Apr 15, 2020
fb07cfa
Adding note about WS2016 containers and krbtgt
rpsqrd Apr 16, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update common-problems.md
  • Loading branch information
@daschott
daschott authored Mar 6, 2020
commit 009bdaf44124f42fd5a90b019eb3b7e7084b670f
5 changes: 4 additions & 1 deletion virtualization/windowscontainers/kubernetes/common-problems.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,10 @@ One of the Kubernetes networking requirements (see [Kubernetes model](https://ku
```

### My Windows node cannot access a NodePort service ###
Local NodePort access from the node itself will fail. This is a known limitation. NodePort access will work from other nodes or external clients.
Local NodePort access from the node itself will fail due to a design limitation on Windows Server 2019. NodePort access will work from other nodes or external clients.

### My Windows node stops routing thourgh NodePorts after I scaled down my pods ###
Due to a design limitation, there needs to be at least one pod running on the Windows node for NodePort forwarding to work.

### After some time, vNICs and HNS endpoints of containers are being deleted ###
This issue can be caused when the `hostname-override` parameter is not passed to [kube-proxy](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/). To resolve it, users need to pass the hostname to kube-proxy as follows:
Expand Down