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

clusterctl: correctly handle cluster networking and CNI when bootstrapping a cluster #34

Closed
xmudrii opened this issue Sep 5, 2018 · 0 comments · Fixed by #56
Closed

clusterctl: correctly handle cluster networking and CNI when bootstrapping a cluster #34

xmudrii opened this issue Sep 5, 2018 · 0 comments · Fixed by #56

Comments

@xmudrii
Copy link
Member

xmudrii commented Sep 5, 2018

The clusterctl successfully bootstrap the cluster and cluster is ready, but the networking is not handled correctly.

Tasks to be done:

  • Handle CNI plugins. Currently no CNI plugin is installed,
  • Decide between Kubenet and CNI,
  • Set correct pods and services CIDR depending on the CNI plugin chosen.
@xmudrii xmudrii mentioned this issue Sep 5, 2018
Closed
@xmudrii xmudrii changed the title clusterctl: correctly handle cluster networking when bootstrapping a cluster clusterctl: correctly handle cluster networking and CNI when bootstrapping a cluster Sep 5, 2018
@xmudrii xmudrii mentioned this issue Sep 12, 2018
Merged
@xmudrii xmudrii mentioned this issue Oct 10, 2018
Closed
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

clusterctl: deploy Flannel CNI plugin kubernetes-sigs/cluster-api-provider-digitalocean
1 participant
@xmudrii