Forum Discussion
kunalpuriii
Altocumulus
AltocumulusNGINX(ingress controller)-F5 integration
Hello Team I am working on integrating F5 and NGINX(ingress controller) as per below article https://devcentral.f5.com/s/articles/Better-together-F5-Container-Ingress-Services-and-Nginx-Ingress-...
kunalpuriiiAltocumulus
AltocumulusThanks for your response, It worked.
There are few things i tweaked, username and password i mentioned as absolute value then variables and the called secret.
I removed 8443 from the url of F5.
Also if you can share working example for nodeport, it will be great. I got this working once but after the nodes disappeared and never worked again. I followed couple of links
https://clouddocs.f5.com/training/community/containers/html/class2/module1/lab3.html
but no luck.
what is the best way to troubleshoot it.
Also can you please share data plane forwarding information.
In our setup we have create VIP on F5 which points to the pool which has IP address of worker nodes which is different from this integration, in this integration NGINX POD IP's are getting added.
Normally POD address are not advertised out of kubernetes cluster.
Do we need to setup a routing from F5 to reach to the POD space via worker nodes?
Thanks
Kunal
For NodePort, change 'type: ClusterIP' to 'type: NodePort' in Service definition. - It is a k8s construct
Try to delete the AS3 Tenant on the BIG-IP and recreate the CIS pod and apply ConfigMap again. - The new AS3 will usually apply.
If you are using NodePort, there is nothing else to do be done as there is no CNI. If you are using a CNI, either VXLAN (Flannel) or BGP (Calico), then follow this article ( https://clouddocs.f5.com/containers/v2/ ).