-
Notifications
You must be signed in to change notification settings - Fork 39.3k
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
endpoints cannot be changed from notReadyAddresses to addresses #125619
Comments
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/sig network |
/assign |
looks like a duplicate of this #117193 |
can we please aggregate all of them in one , having information spreaded across issues is making it more difficult to track, it seems we know the root cause, we have a workaround #117193 (comment) it is missing someone coming with a proposal to fix it |
/close duplicate of #117193 (comment) and #125638 @QuantumEnergyE I want to have only one issue for this, is there any special motivation you want to use #125638 instead of #117193? |
@aojea: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What happened?
I have a k8s clusters that have encountered the following situation:
1、All master nodes are full of memory burst
2、After the memory of all master nodes is restored, the Ready type status of pod is true, but some endpoints in the subsets still remain in notReadyAddresses and do not recover.
service:
enpoints:
pod
3、The issue is resolved only by restarting kube-controller-manager.
/area controller-manager
What did you expect to happen?
When all master node memory is restored, endpoints change from
notReadyAddresses
toaddresses
How can we reproduce it (as minimally and precisely as possible)?
Refer to the description of "What happened?"
Anything else we need to know?
No response
Kubernetes version
Cloud provider
OS version
Install tools
Container runtime (CRI) and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
The text was updated successfully, but these errors were encountered: