Skip to content
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

Jump to bottom

Create trouble_shooting.md #509

Merged
merged 5 commits into from
Jul 6, 2018
Merged

Create trouble_shooting.md #509

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5c52e20
Create trouble_shooting.md
weinong Jul 6, 2018
78d8395
Update trouble_shooting.md
weinong Jul 6, 2018
bb3011b
Rename trouble_shooting.md to troubleshooting.md
weinong Jul 6, 2018
9a6be89
Update troubleshooting.md
weinong Jul 6, 2018
8750777
Update troubleshooting.md
weinong Jul 6, 2018
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
12 changes: 12 additions & 0 deletions troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# AKS Troubleshooting guide

## Problems

### Exposed service is not reachable from Internet

When the exposed service is not reachable, the first thing to verify is whether the NSG rules are modified from the stock configurations maintained by Kubernetes.

If the NSG rules are OK, you can check if your service is reachable using the service cluster IP from another pod.
If that's not reachable, it's likely that iptables is out of sync.
Try to delete the kube-proxy pod under `kube-system` namespace.