-
Notifications
You must be signed in to change notification settings - Fork 305
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
Create trouble_shooting.md #509
Conversation
trouble_shooting.md
Outdated
|
||
### Exposed service is not reachable from Internet | ||
|
||
When the exposed service is not reacheable, the first thing to verify is whether the NSG rules are modified outs |
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.
typo - reachable
trouble_shooting.md
Outdated
|
||
### Exposed service is not reachable from Internet | ||
|
||
When the exposed service is not reacheable, the first thing to verify is whether the NSG rules are modified outs |
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.
I would mention that there are three components. You would want to check the LB,NSG and potentially kube-proxy. I would also put a reference to the describe commands via kubectl so that you can confirm the sync loops on the cloud-controller code isn't throwing errors before checking the Azure side of things
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.
Pinging this again
trouble_shooting.md
Outdated
@@ -0,0 +1,12 @@ | |||
# AKS Troubleshooting guide |
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.
change filename to troubleshooting.md
troubleshooting.md
Outdated
|
||
### 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 outs |
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.
What does "modified outs" mean?
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.
sometimes customers apply their own rules...
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.
Perhaps say instead, "first verify whether NSG rules have been modified from their stock configuration."
troubleshooting.md
Outdated
When the exposed service is not reachable, the first thing to verify is whether the NSG rules are modified outs | ||
|
||
If the NSG rules are OK, you can check if your service is reachable using service's cluster IP from another pod. | ||
If that's not reachable, it's likely that the iptable is out of sync. |
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.
s/the iptable/iptables
troubleshooting.md
Outdated
|
||
When the exposed service is not reachable, the first thing to verify is whether the NSG rules are modified outs | ||
|
||
If the NSG rules are OK, you can check if your service is reachable using service's cluster IP from another pod. |
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.
Should be: "using the service cluster IP"
No description provided.