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.

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

Implement e2e test that kills KEDA Operator & Metrics Server pods #3927

Closed
zroubalik opened this issue Nov 29, 2022 · 0 comments · Fixed by #3935
Closed

Implement e2e test that kills KEDA Operator & Metrics Server pods #3927

zroubalik opened this issue Nov 29, 2022 · 0 comments · Fixed by #3935
Assignees
Labels
feature-request All issues for new features that have not been committed to help wanted Looking for support from community needs-discussion testing

Comments

@zroubalik
Copy link
Member

Proposal

Implement e2e test that kills KEDA Operator & Metrics Server pods while scaling is happening, the test should check that KEDA is able to continue in the scaling after errors on both.

Scenarios:

  1. kill operator pod
  2. kill ms pod
  3. kill both opeator & ms pods

We should run all these scenarios while having 1 replica of Operator and MS and also when we have mutliple replicas of these.

Use-Case

No response

Anything else?

No response

@zroubalik zroubalik added needs-discussion feature-request All issues for new features that have not been committed to help wanted Looking for support from community testing labels Nov 29, 2022
@tomkerkhove tomkerkhove moved this to Proposed in Roadmap - KEDA Core Nov 29, 2022
@JorTurFer JorTurFer self-assigned this Nov 29, 2022
Repository owner moved this from Proposed to Ready To Ship in Roadmap - KEDA Core Dec 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request All issues for new features that have not been committed to help wanted Looking for support from community needs-discussion testing
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants