You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Here is a README which goes through a setup of Kubernetes cluster with kops and Flannel and Weave for networks.
It takes about 10-15min to go over it and have a working cluster.
There are a few known issues that would be good to have a second pair of eyes on, in case I am doing something stupid. I have tried to dynamically attach/detach network interfaces with weave to pods, but they are not accessible. I believe this must be possible because Kubernetes / CNI-Genie / Weave CNI must be setting up those interfaces somehow correctly when the annotations are present.
Here is a demo of this setup in case you find this useful:
Known issues have been addressed by disabling the weave-npc as the weave network policy controller is picking up the PodIP when adding rules to ipset (used by iptables), and this is not OK when the PodIP is set to an IP within the flannel network.
Merging this as this is pretty much the setup we used with @Stebalien to try sidecar with k8s.
The current known issues are:
When using the host network, for some reason there is a missing ip route to the Kubernetes Services CIDR. I opened an issue/question for this one at ClusterIP services not accessible when using flannel CNI from host machines in Kubernetes flannel-io/flannel#1243 - not sure if this is a bug within kops or flannel, or we are misconfiguring something on our side. For now we add these routes manually (or via an init container after Flannel is installed).
We can't allocate IPs because the Weave CNI doesn't support that. We have to submit a PR or fork it, or use the weave cmdline utility. Technically it is possible to allocate a specific IP with Weave, but not through the current version of the Weave CNI.
Will follow up with additional PR, where we improve docs, and add code to support sidecar k8s runner.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Here is a README which goes through a setup of Kubernetes cluster with
kopsand Flannel and Weave for networks.It takes about 10-15min to go over it and have a working cluster.
There are a few known issues that would be good to have a second pair of eyes on, in case I am doing something stupid.
I have tried to dynamically attach/detach network interfaces withI believe this must be possible because Kubernetes / CNI-Genie / Weave CNI must be setting up those interfaces somehow correctly when the annotations are present.weaveto pods, but they are not accessible.Here is a demo of this setup in case you find this useful:
asciinema play -s 3 ./demo2.cast