-
Notifications
You must be signed in to change notification settings - Fork 600
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
failed (add): failed to create macvlan: cannot assign requested address #1378
Comments
Hey Daniel! Ummm, so... alright, another reference config, here's the example I use for testing setting a static ip/mac at run time (e.g. via annotation) https://gist.github.com/dougbtv/a1f2b40bb3e57429ab0dcd8ad4d96c42 I think you might need to add tuning into the CNI chain, my example:
and then your config...
Kinda just wildly pasted in an run through a json lint. I think that might be the piece that's missing is the tuning plugin. Worth a shot at least. |
Cool homelab setup, like, it's rad that it looks like you're doing some kind of isolation to handle the IoT network or something? So like you isolate that traffic on the pod to the IoT segment or something? Just curious what you're doing if you don't mind sharing, mostly I think it's neat. |
@dougbtv Thanks! I mostly am following the k8s-at-home generated projects. There are 5 nodes in my cluster: 3 control-plane and 2 workers. My main use case is this. I want to expose Home Assistant running in my homelab vlan (30) to my iot vlan (50) so that it can discover the devices and services running over there. This used to work, but for some reason, the last couple of months, it stopped and I was getting that message that it couldn't assign addresses. I have a test pod I've been playing with, but just sits there in a pending state with the message I posted. There are other services I'd like to expose to that vlan as well, like ESPHome, etc. as well Is there anything specific you'd like to know about it? |
I updated the network definition, but I'm still getting the same error:
Is there something potentially with |
I'm not able to assign addresses to my pod.
Multus is deployed with FluxCD, here is the HelmRelease:
https://github.com/dmfrey/home-gitops/blob/main/kubernetes/homelab-k8s-001/apps/network/multus/app/helmrelease.yaml
And my networks are configured with the following
NetworkAttachmentDefinition
:https://github.com/dmfrey/home-gitops/blob/main/kubernetes/homelab-k8s-001/apps/network/multus/config/networkattachment-iot.yaml
My Talos cluster exposes the
eth0.50
vlanI'm applying a pod annotation to the pod in the HelmRelease:
When the pod starts its fire the following events.
Is there some way to get around this issue?
Environment:
If there is anything else I can provide, please let me know. Thanks for any assistance.
The text was updated successfully, but these errors were encountered: