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

Add Broker/Trigger tests to KEDA test job #3814

Open
Cali0707 opened this issue Apr 4, 2024 · 1 comment · May be fixed by #3819
Open

Add Broker/Trigger tests to KEDA test job #3814

Cali0707 opened this issue Apr 4, 2024 · 1 comment · May be fixed by #3819
Labels
area/test kind/feature-request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@Cali0707
Copy link
Member

Cali0707 commented Apr 4, 2024

Problem
Currently the KEDA tests only test KafkaSource tests. However, with Broker/Triggers now supporting KEDA scaling as well we should run those tests in the same environment to make sure everything works performantly with KEDA and autoscaling enabled

Persona:
Which persona is this feature for?

Exit Criteria
All Broker/Trigger reconciler tests run in the KEDA test job

Time Estimate (optional):
How many developer-days do you think this may take to resolve? 1

Additional context (optional)
Add any other context about the feature request here.

Copy link
Contributor

github-actions bot commented Jul 4, 2024

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test kind/feature-request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
Development

Successfully merging a pull request may close this issue.

1 participant