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

kinder: create test jobs for node add and removal #1661

Open
neolit123 opened this issue Jul 10, 2019 · 6 comments
Open

kinder: create test jobs for node add and removal #1661

neolit123 opened this issue Jul 10, 2019 · 6 comments
Assignees
@neolit123
Labels
area/kinder Issues to track work in the kinder tool area/test kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Milestone
Next

Comments

@neolit123
Copy link
Member

neolit123 commented Jul 10, 2019 •
edited
Loading

as discussed with @fabriziopandini we should add jobs that test changing cluster topology
e.g. single CP -> HA and removing CP nodes.

possibly also:

  • concurrent join of CP/non-CP nodes
  • joining version skewed CP nodes
@neolit123 neolit123 added area/test kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Jul 10, 2019
@neolit123 neolit123 added this to the v1.16 milestone Jul 10, 2019
@fabriziopandini
Copy link
Member

when #1660 this should become much more easy to achieve with kinder

@neolit123 neolit123 modified the milestones: v1.16, Next Jul 18, 2019
@fabriziopandini
Copy link
Member

As for kubeadm office hour discussion, we should consider also if to add E2E tests for joining nodes using a discovery file instead of tokens

@neolit123
Copy link
Member Author

merging #1633 here.
#1633 is about concurrent join.

@neolit123 neolit123 mentioned this issue Oct 13, 2019
Closed
2 tasks
@fabriziopandini
Copy link
Member

add E2E tests for joining nodes using a discovery file instead of tokens

Done

@neolit123 neolit123 mentioned this issue Nov 7, 2019
Closed
@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-testing, kubernetes/test-infra and/or fejta.
/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 Jan 11, 2020
@neolit123
Copy link
Member Author

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 11, 2020
@neolit123 neolit123 mentioned this issue Mar 24, 2020
Merged
@neolit123 neolit123 mentioned this issue Sep 1, 2020
Merged
@neolit123 neolit123 added the area/kinder Issues to track work in the kinder tool label Sep 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@neolit123 neolit123

Labels
area/kinder Issues to track work in the kinder tool area/test kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
Next
Development

No branches or pull requests
4 participants
@neolit123 @fabriziopandini @k8s-ci-robot @fejta-bot