Skip to content
This repository was archived by the owner on Apr 25, 2023. It is now read-only.

Add e2e upgrade tests #1313

Closed
makkes opened this issue Oct 31, 2020 · 6 comments
Closed

Add e2e upgrade tests #1313

makkes opened this issue Oct 31, 2020 · 6 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@makkes
Copy link
Contributor

makkes commented Oct 31, 2020

What would you like to be added: End-to-end test verifying upgrade behaviour between two different kubefed versions.

Why is this needed:

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 31, 2020
@hectorj2f
Copy link
Contributor

I might take care of this test ;).

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 13, 2021
@hectorj2f
Copy link
Contributor

@makkes We added a test to upgrade from a previous image to the latest in master.

@makkes
Copy link
Contributor Author

makkes commented Apr 13, 2021

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 13, 2021
@makkes
Copy link
Contributor Author

makkes commented Apr 13, 2021

@hectorj2f would you mind linking it here and closing the issue then, please? Thanks!

@hectorj2f
Copy link
Contributor

@makkes it was added here 8a435bc.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants