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 · 2 comments
Open

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

skhalash opened this issue Oct 25, 2024 · 2 comments
Labels
kind/missing-test Categorizes issue or PR as related to missing automated tests for scenario. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

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
@github-actions GitHub Actions
Copy link

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

@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 Dec 25, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Jan 1, 2025

This issue has been automatically closed due to the lack of recent activity.
/lifecycle rotten

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 1, 2025
@kyma-bot kyma-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 1, 2025
@a-thaler a-thaler added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jan 7, 2025
@a-thaler a-thaler reopened this Jan 7, 2025
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. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@skhalash @a-thaler @kyma-bot