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
What happened:
In my SNO cluster, there is only one physical interface (eno1) attached, and a bridge network (br-ex) has already been created using it. I would like to create an additional Linux bridge network without impacting the existing br-ex configuration.
What you expected to happen:
Create Linux Bridge How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
Openshift 4.16
NodeNetworkState on affected nodes (use kubectl get nodenetworkstate <node_name> -o yaml):
What happened:
In my SNO cluster, there is only one physical interface (eno1) attached, and a bridge network (br-ex) has already been created using it. I would like to create an additional Linux bridge network without impacting the existing br-ex configuration.
What you expected to happen:
Create Linux Bridge
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
Openshift 4.16
NodeNetworkState
on affected nodes (usekubectl get nodenetworkstate <node_name> -o yaml
):NodeNetworkConfigurationPolicy
:kubectl get pods --all-namespaces -l app=kubernetes-nmstate -o jsonpath='{.items[0].spec.containers[0].image}'
):nmcli --version
)kubectl version
):Sorry, I am new to this and I have limited knowledge in this area. Please help.
The text was updated successfully, but these errors were encountered: