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 v1alpha3 to v1alpha4 upgrade e2e test #2388

Closed
sedefsavas opened this issue May 6, 2021 · 8 comments · Fixed by #2770
Closed

Add v1alpha3 to v1alpha4 upgrade e2e test #2388

sedefsavas opened this issue May 6, 2021 · 8 comments · Fixed by #2770
Assignees
@yuzhang17
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@sedefsavas
Copy link
Contributor

Add an e2e test for v1alpha3 to v1alpha4 upgrade similar to what core cluster-api is adding here and run a basic scale test to make sure it is functional.

kubernetes-sigs/cluster-api#3708

/help
/good-first-issue
/milestone v0.7.x
@k8s-ci-robot
Copy link
Contributor

@sedefsavas:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

Add an e2e test for v1alpha3 to v1alpha4 upgrade similar to what core cluster-api is adding here and run a basic scale test to make sure it is functional.

kubernetes-sigs/cluster-api#3708

/help
/good-first-issue
/milestone v0.7.x

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added this to the v0.7.x milestone May 6, 2021
@k8s-ci-robot k8s-ci-robot added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels May 6, 2021
@yuzhang17
Copy link

Could I work on this issue？ It may take more time because I'm a newcomer

@sedefsavas
Copy link
Contributor Author

sedefsavas commented May 17, 2021 •
edited
Loading

@yuzhang17 yes!

/assign @yuzhang17

You can reach out to us in #cluster-api channel for help because this will be probably done by calling ClusterctlUpgradeSpec.

@yuzhang17
Copy link

/lifecycle active

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label May 17, 2021
@yuzhang17
Copy link

Learning Ginkgo and Reading E2E code. Working in progress.

@sedefsavas
Copy link
Contributor Author

Thanks for the heads up @yuzhang17 , no rush we are still at least a month from a v1alpha4 release.

@sedefsavas
Copy link
Contributor Author

sedefsavas commented May 26, 2021 •
edited
Loading

/hold
until #2429 is merged for new cluster-api version.

@yuzhang17 yuzhang17 mentioned this issue May 31, 2021
Closed
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. labels Aug 24, 2021
@Ankitasw Ankitasw mentioned this issue Sep 15, 2021
Merged
4 tasks
@randomvariable randomvariable mentioned this issue Oct 6, 2021
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yuzhang17 yuzhang17

Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
4 participants
@yuzhang17 @k8s-ci-robot @k8s-triage-robot @sedefsavas