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

E2E Cluster API Tests #88

Closed
rsdcastro opened this issue Apr 12, 2018 · 7 comments
Closed

E2E Cluster API Tests #88

rsdcastro opened this issue Apr 12, 2018 · 7 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v0.1.x

Comments

@rsdcastro
Copy link

From @jessicaochen on January 3, 2018 19:26

Setup E2E tests that use Cluster API for in kubernetes/test-infra

Copied from original issue: kubernetes-retired/kube-deploy#472
@rsdcastro
Copy link
Author

From @medinatiger on January 8, 2018 19:14

@jessicaochen, do you mean create E2E test to test cluster API especially machine controller or convert existing test-infra to use cluster API?

@rsdcastro
Copy link
Author

From @jessicaochen on January 8, 2018 19:45

I mean convert existing test-infra to use the cluster API for this issue. I think both ultimately are good.

@rsdcastro
Copy link
Author

From @medinatiger on January 8, 2018 19:48

OK. I opened kubernetes-retired/kube-deploy#476 to track the work for writing integration test for machine controller. It could be a great starter project for anyone want to start contributing.

@roberthbailey roberthbailey transferred this issue from kubernetes-sigs/cluster-api Jan 10, 2019
@roberthbailey roberthbailey added this to the v1alpha1 milestone Jan 11, 2019
@roberthbailey roberthbailey added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jan 11, 2019
@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 Apr 28, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

@k8s-ci-robot k8s-ci-robot 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 May 28, 2019
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v0.1.x
Development

No branches or pull requests
4 participants
@rsdcastro @roberthbailey @k8s-ci-robot @fejta-bot