Multi host #5

Merged
merged 2 commits into from Oct 28, 2015

Conversation

Projects
None yet
2 participants
Collaborator

chuckbutler commented Oct 28, 2015

This is the core modification to K8's to support flannel networking. The overall implementation has been abstracted enough to be generic to most deployments.

There are a few things going on here we should be cognizant of:

  • Networking CIDR applies to both the K8s services, and the flannel network configuration
  • Any other layer implementation will need to follow the same guidelines, pass a cidr between both
  • we're pulling containers from quay.io and gcr.io - both of which will not make it past the firewall test
  • Once libnetwork takes over, this layer is likely to go away all together in favor of a unified libnetwork layer to configure the different providers

The flannel layer can be found here

@@ -0,0 +1 @@
+includes: ['layer:docker', 'layer:flannel', 'interface:etcd']
@mbruzek

mbruzek Oct 28, 2015

Owner

Glad to have the new name of the file, charm-tools 1.8.0 allowed this, right?

@chuckbutler

chuckbutler Oct 28, 2015

Collaborator

Correct. as of 1.8.0 this is fully supported.

@@ -75,7 +75,7 @@ def download_kubectl():
cmd = 'chmod +x /usr/local/bin/kubectl'
check_call(split(cmd))
set_state('kubectl.downloaded')
- status_set('maintenance', 'Kubernetes installed')
+ status_set('active', 'Kubernetes installed')
Owner

mbruzek commented Oct 28, 2015

Regarding

"we're pulling containers from quay.io and gcr.io - both of which will not make it past the firewall test"

We have to balance the firewall test with how the industry is recommending the distribution of the releases. At the moment this seems to be the way it is going, perhaps we will have to pull the images from another location at some point in the future

mbruzek added a commit that referenced this pull request Oct 28, 2015

@mbruzek mbruzek merged commit 47bb688 into mbruzek:master Oct 28, 2015

Collaborator

chuckbutler commented Oct 28, 2015

+1 on that comment. I just felt it was prudent to leave somewhere that we should be cognizant of it :)

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