-
Notifications
You must be signed in to change notification settings - Fork 19
Description
Summary
I have successfully integrated the F5 IPAM Controller with the F5 BIG-IP Controller using CRDs and the VirtualServer kind in a Tanzu Kubernetes environment. The integration works as expected, and the IPAM reservation in Infoblox (in DHCP mode) is correctly handled.
However, I noticed that no DNS entries (A records or host records) are created in Infoblox, even though the DNS zone is already configured for this IPAM network.
Steps to Reproduce
- Deploy F5 IPAM Controller and F5 BIG-IP Controller in a Tanzu environment.
- Configure CRDs using the
VirtualServerkind. - Create a VirtualServer type with ipam enabled
- Observe that IP reservations are made correctly.
- Check Infoblox for corresponding DNS A/host records.
Expected Behavior
An A record or host record should be automatically created in Infoblox when an IP is assigned, assuming the DNS zone is correctly associated with the IPAM network.
Actual Behavior
The IP is reserved successfully, but no DNS records (A or host) are created in Infoblox.
Question
Are A records or host records still supported with the F5 IPAM Controller when integrated with Infoblox in DHCP mode? If so, is there any additional configuration required to enable DNS record creation?
Environment
- F5 IPAM & BIG-IP Controller installed with helm:
- F5 IPAM Controller version: 0.1.11
- F5 BIG-IP Controller version: 2.19.0
- Kubernetes platform: Tanzu
- Infoblox version: 9.0.3-50212-ee11d5834df9
- CRD type used:
VirtualServer
Thanks in advance for your support!