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 e2e testing of cloud provider via Cluster API Clusterctl framework or Cluster API kubetest2 deployer #130

Open
randomvariable opened this issue Sep 25, 2020 · 6 comments
Open

Add e2e testing of cloud provider via Cluster API Clusterctl framework or Cluster API kubetest2 deployer #130

randomvariable opened this issue Sep 25, 2020 · 6 comments
Assignees
@randomvariable
Labels
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.

Comments

@randomvariable
Copy link
Member

What would you like to be added:
Add e2e conformance testing to this repo

Why is this needed:
Discussed a while ago about testing requirements for this repo, and had demo'd launching kubetest via Cluster API's clusterctl framework. Inclusion of conformance testing is almost complete (see kubernetes-sigs/cluster-api#3652), and am considering adding a Cluster API deployer to kubetest2 ( kubernetes-sigs/kubetest2#48 ).

This could be used to then set up e2e testing on this repo.

/kind feature
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 25, 2020
@randomvariable
Copy link
Member Author

/assign

@randomvariable
Copy link
Member Author

randomvariable commented Oct 1, 2020 •
edited
Loading

kubernetes-sigs/cluster-api#3652 is in, and kubernetes-sigs/cluster-api-provider-aws#1991 serves as an example to consume, so can probably start adding similar here.

Will probably naively try spinning up Cluster API AWS cluster with external CPI, pass the kubeconfig to a new goroutine to run the CPI and then run the relevant kubetest bits.

@randomvariable
Copy link
Member Author

/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 Oct 14, 2020
@randomvariable
Copy link
Member Author

Hah, I started playing around with a kubetest2 deployer, but @benmoss is already ahead in kubernetes-sigs/kubetest2#48 (comment)

@randomvariable randomvariable mentioned this issue Nov 3, 2020
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 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 Jan 12, 2021
@randomvariable
Copy link
Member Author

/lifecycle frozen

Will be getting round to this next week,.

@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 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@randomvariable randomvariable

Labels
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.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@randomvariable @k8s-ci-robot @fejta-bot