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
We will need to test it to be sure that it will work, but most of the networking in Kubernetes is done at the IP level. It looks like the packet header will identify as TCP with option 30. I suspect that most CNIs will just treat this as TCP traffic.
We will probably need to enable this on all of our servers.
There may be issues with firewalls.
The text was updated successfully, but these errors were encountered:
We will need to test it to be sure that it will work, but most of the networking in Kubernetes is done at the IP level. It looks like the packet header will identify as TCP with option 30. I suspect that most CNIs will just treat this as TCP traffic.
We will probably need to enable this on all of our servers.
There may be issues with firewalls.
The text was updated successfully, but these errors were encountered: