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

Add an E2E testing ensuring that rolling upgrade does not make pipelines unhealthy #1566

Open
skhalash opened this issue Oct 25, 2024 · 0 comments
Open

Add an E2E testing ensuring that rolling upgrade does not make pipelines unhealthy #1566

skhalash opened this issue Oct 25, 2024 · 0 comments
Labels
kind/missing-test Categorizes issue or PR as related to missing automated tests for scenario.

Comments

@skhalash
Copy link
Collaborator

Description

A successful rolling upgrade should not degrade Log/Metric/Trace Pipeline status to unhealthy. In the status check we rely on internal details of Pod controller (by checking different fields of PodStatus), which might change in future versions of Kubernetes. We need an E2E test to ensure no regression will happen.

Related Issues

#1545
#1236
@skhalash skhalash added the kind/missing-test Categorizes issue or PR as related to missing automated tests for scenario. label Oct 25, 2024
@skhalash skhalash mentioned this issue Oct 25, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/missing-test Categorizes issue or PR as related to missing automated tests for scenario.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@skhalash