2 provider-network can't share same bond about kube-ovn

[zhangzujian]

provider-networks cannot share the same nic.

[zhangzujian]

If you want to use different VLANs on the same nic, you can refer the provider-network in multiple vlans:

apiVersion: kubeovn.io/v1
kind: Vlan
metadata:
  name: vlan1
spec:
  id: 1
  provider: external
---
apiVersion: kubeovn.io/v1
kind: Vlan
metadata:
  name: vlan2
spec:
  id: 2
  provider: external

[Smithx10]

K, I was trying to separate out a different name for use with. ovn-external-gw-config It requires you to have the name be the same as your provider device which in my case is "external" I was hoping to use something like "default-eip"

https://kubeovn.github.io/docs/v1.13.x/en/advance/ovn-eip-fip-snat/#2-ovn-eip

[zcq98]

K, I was trying to separate out a different name for use with. ovn-external-gw-config It requires you to have the name be the same as your provider device which in my case is "external" I was hoping to use something like "default-eip"

https://kubeovn.github.io/docs/v1.13.x/en/advance/ovn-eip-fip-snat/#2-ovn-eip

like this?

apiVersion: kubeovn.io/v1
kind: ProviderNetwork
metadata:
  name: default-eip
spec:
  defaultInterface: external

[Smithx10]

@zcq98,

When deploying the default vpc external gateway, it requires the gateway-switch name match the subnet name etc.

"external" is a generic subnet name, and I was hoping to be able to name it something a bit more detailed like "eip" or "default-eip".

We use the name "External" to describe our top of rack bond that is external, we have another bond that is "admin" and in some cases another bond that is for "storage" 3 different pieces of fabric.

I declared the following in our kube-ovn-controller:
- --external-gateway-vlanid=1998
- --external-gateway-switch=external

[bobz965]

• --external-gateway-vlanid=1998
• --external-gateway-switch=eip|default-eip

you can use this as you said, but the subnet name eip|default-eip should be created.

[github-actions]

Issues go stale after 60d of inactivity. Please comment or re-open the issue if you are still interested in getting this issue fixed.