-
Notifications
You must be signed in to change notification settings - Fork 519
fix: check network from node to k8s api server in CSE #2919
Conversation
💖 Thanks for opening your first pull request! 💖 We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should make sure your first commit and PR title start with a semantic prefix. Examples of commit messages with semantic prefixes: - |
/azp run pr-e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
Run |
/azp run pr-e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
Codecov Report
@@ Coverage Diff @@
## master #2919 +/- ##
==========================================
- Coverage 72.53% 72.49% -0.04%
==========================================
Files 141 141
Lines 25776 25847 +71
==========================================
+ Hits 18696 18739 +43
- Misses 5999 6021 +22
- Partials 1081 1087 +6 |
/lgtm |
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.
/lgtm
Congrats on merging your first pull request! 🎉🎉🎉 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bowang-666, jackfrancis, xuto2 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* fix: check network from node to k8s api server in CSE (#2919) * cherrypick: check network to k8s api server
Reason for Change:
Sometimes agent nodes can not reach k8s api server due to custom network settings. It will cause "nodenotready" failures during create/scale/upgrade. This pr will check the connection from node to k8s api and raise error code if can't connect.
Issue Fixed:
Requirements:
Notes: