What would you like to be added:
Add hostnameLabel and assignPrivateDnsRecord fields to the VnicAttachment spec, and pass them through to
CreateVnicDetails when attaching secondary VNICs during instance launch.
Why is this needed:
Secondary VNICs on bare metal instances always have a null FQDN after launch. OCI constructs the FQDN as
...oraclevcn.com — without hostnameLabel, OCI has nothing to build it
from; without assignPrivateDnsRecord, OCI won't register the private IP in DNS at all.
Both fields are supported by the OCI SDK's CreateVnicDetails and are already available on the primary VNIC via
NetworkDetails. There is currently no equivalent path for secondary VNICs.
This breaks DNS-dependent workloads on secondary VNICs. A concrete case: OCP node registration on bare metal shapes
where the OCP subnet is attached as a secondary VNIC — nodes cannot be reached by hostname because the secondary
VNIC has no DNS record.
The only current workaround is a post-launch UpdateVnic call outside CAPOCI's lifecycle, which introduces a race
condition and operational complexity.
Both fields should be optional with omitempty so existing VnicAttachment configs are unaffected — OCI defaults apply
when the fields are omitted.
What would you like to be added:
Add hostnameLabel and assignPrivateDnsRecord fields to the VnicAttachment spec, and pass them through to
CreateVnicDetails when attaching secondary VNICs during instance launch.
Why is this needed:
Secondary VNICs on bare metal instances always have a null FQDN after launch. OCI constructs the FQDN as
...oraclevcn.com — without hostnameLabel, OCI has nothing to build it
from; without assignPrivateDnsRecord, OCI won't register the private IP in DNS at all.
Both fields are supported by the OCI SDK's CreateVnicDetails and are already available on the primary VNIC via
NetworkDetails. There is currently no equivalent path for secondary VNICs.
This breaks DNS-dependent workloads on secondary VNICs. A concrete case: OCP node registration on bare metal shapes
where the OCP subnet is attached as a secondary VNIC — nodes cannot be reached by hostname because the secondary
VNIC has no DNS record.
The only current workaround is a post-launch UpdateVnic call outside CAPOCI's lifecycle, which introduces a race
condition and operational complexity.
Both fields should be optional with omitempty so existing VnicAttachment configs are unaffected — OCI defaults apply
when the fields are omitted.