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

We may need debounce mechanism to collapse Kubernetes events #60

Closed
tokers opened this issue Dec 8, 2020 · 6 comments
Closed

We may need debounce mechanism to collapse Kubernetes events #60

tokers opened this issue Dec 8, 2020 · 6 comments
Labels
discuss question Further information is requested
Milestone
1.0.0

Comments

@tokers
Copy link
Contributor

tokers commented Dec 8, 2020

No description provided.

@tokers tokers added question Further information is requested discuss labels Dec 8, 2020
@gxthrj
Copy link
Contributor

gxthrj commented Dec 21, 2020

Is it related to #59 ?

@gxthrj gxthrj added this to the 0.1.1 milestone Dec 21, 2020
@tokers
Copy link
Contributor Author

tokers commented Dec 21, 2020

Is it related to #59 ?

No.

@gxthrj
Copy link
Contributor

gxthrj commented Dec 21, 2020

Or Is this issue meaning : Need a mechanism to ensure that the resources in k8s and apisix are consistent ?

@tokers
Copy link
Contributor Author

tokers commented Dec 21, 2020

@gxthrj The debounce mechanism is used to prevent ingress-apisix/apisix overwhelming from too many resource change events arriving in.

@gxthrj
Copy link
Contributor

gxthrj commented Dec 26, 2020

This will be an extreme scenario, we can simulate and test the current limiting capability of workqueue.

@gxthrj gxthrj modified the milestones: 0.2.0, 0.1.0, 1.0.0 Dec 26, 2020
@gxthrj
Copy link
Contributor

gxthrj commented Jun 19, 2021

stale issue, feel free to reopen .

@gxthrj gxthrj closed this as completed Jun 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discuss question Further information is requested
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
2 participants
@gxthrj @tokers