Forum Discussion
MVPF5 Kubernetes CNF/BNK GSLB functionality ?
Hello everyone is there F5 CNF/BNK GSLB functionality ?
I see the containers gslb-engine (probably the main GTM/DNS module) and gslb-probe-agent (probably the big3d in a container/pod ) but no CR/CRD definitions about it and and can this data be shared between F5 TMM in different clusters (something like DNS sync groups) or probing normal F5 BIG-IP devices (not in kubernetes).
https://clouddocs.f5.com/cnfs/robin/latest/cnf-software-install.html
https://clouddocs.f5.com/cnfs/robin/latest/intro.html
4 Replies
- Melissa_C
Moderator
Hi Nikoolayy1,
Noticed there wasn't an answer on here yet, were you able to locate an answer outside of here or would you like me to find someone who can help?
-Melissa
- Nikoolayy1
Hey Melissa_C thanks for the suggestion and if it is not an issue can you check if someone can answer this.
- Melissa_C
No issue at all! Reaching out to someone right now.
- Nikoolayy1
I think that this feature may not be currently in CNF as probably the containers are from the F5 NEXT that was cancelled https://my.f5.com/manage/s/article/K000152956 as there are no CRD for Data Center, Server, Link, Virtual Server or Server objects.
I still think that the GSLB feature will be great addition even if limited like to be able to do only static load balancing like Topology records. The sync between the different openshift/kubernetes clusters that will have TMM and the GSLB pods. For this the probe agent pod will probably be needed and some volumes to be added to the gslb as to save the data when new cluster is added to the GTM sync group maybe with CRD that does what the "gtm_add" script does for BIG-IP.
F5 NEXT had GSLB as that was the only DNS feature in it so porting this to k8s seems possible as BIND pods/containers or outside of the k8s external DNS servers (hardware/vm) do not offer intelligent DNS services. About the option to connect to normal LTM devices well that is maybe going overboard from my part 😀 Still adding k8s clusters that do not have the gslb pod but just normal TMM pods like LTM devices like the "big3d add" script will make sense as only the prober pod could be installed on those clusters that shared the Security Context IP address (like LTM Virtual Servers) to the gslb pods on the k8s clusters that will act like DNS/GTM devices .
