-
Notifications
You must be signed in to change notification settings - Fork 8
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
Pod networking #25
Comments
I think I've got this all wrong. Don't mind this for now, let me wrap my head around this a bit more. |
Yes, you would need to change |
Added |
I have some struggle setting the cluster CIDR alltogether. I've set it to
But when creating deployments, Pods still get IP addresses in the "old" CIDR, like I'll get the latest changes from master and see if it works better. |
@anton-johansson
|
Ah, that is probably it. Should the subnet of the bridge be the same as the Flannel one? I think that'll happen with your latest changes, which I did not do. Let me give it a go. |
Actually, I'm gonna wait until #23 is done. :) |
It does not seem to like it when both Flannel and the Bridge use the same subnet, which makes sense. Maybe the idea is to remove the Bridge in favor of Flannel? |
Are you trying on a fresh install or have you changed the CIDR afterwards? Apparently that causes issues. |
I'm doing fresh installations now, to make sure I get things right. Here's my Flannel configuration: ---
kind: ConfigMap
apiVersion: v1
metadata:
name: kube-flannel-cfg
namespace: kube-system
labels:
tier: node
app: flannel
data:
cni-conf.json: |
{
"name": "cbr0",
"plugins": [
{
"type": "flannel",
"delegate": {
"hairpinMode": true,
"isDefaultGateway": true
}
},
{
"type": "portmap",
"capabilities": {
"portMappings": true
}
}
]
}
net-conf.json: |
{
"Network": "10.244.0.0/16",
"Backend": {
"Type": "vxlan"
}
} ... where I think I'm missing something regarding how the bridge plays together with Flannel (or other overlay networks). |
You are right. The |
I think one of either:
I think the first one is better. But maybe with need examples instead, so people can get started more easily. The bridge configuration is a good example for single nodes. Maybe examples for DNS and Ingress is a good idea too? They wouldn't "ruin" the purpose of the repository. About my issue: Is it enough to just remove the CNI configuration (
I must be doing something wrong, though, I'm not sure where |
Okay, some progress.
The old bridge, But should we re-open this issue so we can fix the CNI configuration? |
Ah, nice find! Yes, go ahead |
I can't 😂 |
Do you think that |
I don't have an opinion on that really. For me, personally, it does not matter. I don't mind having Is there any kind of standard or common CIDR that most people use that would be wise to default to? |
I know pod networking isn't something that should be handled by this repository, but I have a minor question. I've just gotten into pod networking, I've previously worked with a single worker node, meaning that the bridge supplied by this repository has worked wonders.
This repository supplies a bridge using the subnet
10.19.0.0/16
.This repository installs
kube-controller-manager
with the argument--cluster-cidr=10.19.0.0/16
, which I believe is in charge of appointing IP addresses to each new pod.I've now installed Flannel that should be used as an overlay network for proper pod networking. The configuration for it uses the subnet
10.244.0.0/16
(from the default in the flannel repository).My question: How am I supposed to tell my cluster to use the Flannel subnet instead? One idea would be to have an Ansible parameter for this, but I'm kind of clueless here. Is that the right way to go? Or am I missing something? :)
The text was updated successfully, but these errors were encountered: