AVI: Difference between revisions
→Replace kube-proxy with Avi
Line 140:
== Replace kube-proxy with Avi ==
*If kube-proxy is enabled, it uses the service subnet (default is 172.30.0.0/16) to allocate east-west VIPs to services.
*In this case, east-west VIPs handled by Vantage have to be configured to use other subnets.
*Kube-proxy will be running, but unused, since services use Avi-allocated VIPs for east-west traffic, instead of OpenShift-allocated VIPs from the service network.
*If a user wishes to use the service subnet to load balance traffic using Avi, kube-proxy must be disabled.
*This mode offers operational advantages, since OpenShift’s API and CLI are in sync with the VIP used for the service.
*That is to say, if someone does a “oc get service,” the VIPs shown in the output are the same VIPs on which Avi provides the service.
;Disable kube-proxy
1) OpenShift Master node delete all user-created services:
| |||