-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
Tracking issue for e2e testing framework and implementation #1732
Comments
Some ideas that came out of #1742 reduce boilerplate
consistency
cc @detiber @wfernandes, thanks for the feedback |
What does this mean Since MachineDeployments do not support control-plane nodes yet, does this mean presently the three control-plane nodes will be created individually using just "kind: Machine" and not MachineDeployments ? |
"Creating a control plane machine and a MachineDeployment with two replicas will create a three node cluster with one control plane node and two worker nodes."
root@capd:~# kubectl --kubeconfig=./capi-quickstart.kubeconfig get pods -n mynamespace -o wide Can I do something more to help this one please ? |
@sb1975 I updated the issue to link to the actual tests in the framework as examples to get folks started. Take a look at the existing tests and try to follow the existing patterns or if you find something that needs improving, improve it. |
I'm planning on working on this framework test: Deleting a cluster deletes all resources associated with that cluster including Machines, BootstrapConfigs, InfraMachines, InfraCluster, and generated secrets. I'm hoping to pair that work as I accomplish this story #1775. |
Closing this in favor of #2141 Other cases are not important right now and will be added in future as importance rises. /close |
@chuckha: Closing this issue. In response to this:
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. |
Testing framework
Based on the testing proposal we have a lot of work to do! This issue tracks the work to be done
Initial work to set patterns
Parallel work after patterns are in place (in order of priority)
Tests to write in the framework that can be reused
/milestone v0.3.0
/priority important-soon
/assign
The text was updated successfully, but these errors were encountered: