Trying to understand how to enable the breno1 after reboot. #5064
Unanswered
jasvinder1107
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Team i have installed the ovn-kubernetes via helm chart on k0s distribution(currently single controller). Everything works with installation. But after reboot my breno1 (default gateway bridge) doesn't get the IP at all. I am not understanding why because during installation eno1 (which is port with default gw) gets taken over by breno1. After manually plumbing the IP and default gateway for breno1 everything works. But i have to do this from console. Can you please help me if this is a bug in ovn-node ?
I have two port on the system.
netplan is configured to have default gw on eno1. There is no known config for breno1 created after the OVN deployment in netplan by me.
My question is if this works first time and breno1 takes over eno1, why it fails to come up after the reboot. The CNI should handle it on reboot as well.
Upon plumbing the ip on brdige and pushing default gw everything works after the reboot as well.
Can you help me with a way to solve this problem so i don't have to manually plumb the IP on breno1
my netplan looks like below.
I can confirm the eno1 gets taken over by ovs-system after the reboot, but ip remains plumbed on eno1 , since that is only default GW. And breno1 doesn't take over the IP.
I have updated these values chart to deploy it .
Alpine pod is confirming that CNI is working after reboot and manual plumb of breno1
Beta Was this translation helpful? Give feedback.
All reactions