-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Experimental limited support for cluster-api #15522
Conversation
0a391f2
to
8e98296
Compare
999bed2
to
1ee9dae
Compare
@justinsb: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
This only barely works, but we can start to boot machines and make incremental progress.
This lets us use some of the shared schema helpers, without taking a full dependency on the cluster-api (and all the versions that would entail).
Generate CRDs and deepcopy.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Very limited experimental support for cluster-api; we are able to launch GCE VMs into an existing cluster (with some carefully constructed yaml), they can't currently join the cluster or really do anything useful.