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

Remove dependency on kubeadm, kubelet, and kubeproxy #11

Open
dlipovetsky opened this issue Jul 9, 2018 · 1 comment
Open

Remove dependency on kubeadm, kubelet, and kubeproxy #11

dlipovetsky opened this issue Jul 9, 2018 · 1 comment
Assignees
@dlipovetsky

Comments

@dlipovetsky
Copy link
Contributor

The provider imports the kubeadm, kubelet and kubeproxy configuration types. The provider imports Cluster API types, too. The latter is locked to release-1.9, but the provider targets kubeadm release-1.10. Due to an API change, kubeadm types are not compatible across release-1.9 and release-1.10.
@dlipovetsky dlipovetsky self-assigned this Jul 9, 2018
@dlipovetsky
Copy link
Contributor Author

The workaround to the problems of configuration types is to have the provider define its own types for now. These types must marshal into valid kubeadm MasterConfigurations and NodeConfigurations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dlipovetsky dlipovetsky

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dlipovetsky