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

after ccm reboot, rollingupdate service delay 2 minutes to watch endpoint change #412

Open
monkeydzhao opened this issue Aug 23, 2024 · 1 comment · May be fixed by #413
Open

after ccm reboot, rollingupdate service delay 2 minutes to watch endpoint change #412

monkeydzhao opened this issue Aug 23, 2024 · 1 comment · May be fixed by #413
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@monkeydzhao
Copy link

What happened: reboot ccm pod, and rollingupdate a service, endpoint change in 10 sec,but ccm watch endpoint change after 2 min and cause traffic fail

What you expected to happen: ccm instantly watch endpoint change

How to reproduce it (as minimally and precisely as possible):

  1. create a clb on alicloud console
  2. create a service on k8s and change to loadbalancer type and set the clb id to service
  3. reboot ccm daemonsets
  4. rollingupdate service
  5. service endpoint changes but clb doesn't update backend server
  6. after 2 minutes the ccm watch endpoint change and update clb backend server

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version): 1.24
  • Cloud provider or hardware configuration: alicloud
  • OS (e.g: cat /etc/os-release): Alma 8.8
  • Kernel (e.g. uname -a): 4.18.0-477
  • Install tools: yaml
  • Network plugin and version (if this is a network-related bug): terway
  • Others:
@monkeydzhao monkeydzhao added the kind/bug Categorizes issue or PR as related to a bug. label Aug 23, 2024
@kaiiyvwu kaiiyvwu linked a pull request Aug 29, 2024 that will close this issue
Open
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

modify method to get service in endpoint related event kaiiyvwu/cloud-provider-alibaba-cloud
3 participants
@k8s-ci-robot @monkeydzhao @k8s-triage-robot