OpenStack Floating IP Associate

Associates an existing OpenStack Neutron floating IP with a port, providing external connectivity to whatever is attached to the port (typically a compute instance). This is a join resource that connects two independently managed resources -- a floating IP allocated via OpenStackFloatingIp and a port created via OpenStackNetworkPort -- making the association relationship explicit as a visible DAG node in InfraCharts.

What Gets Created

When you deploy an OpenStackFloatingIpAssociate resource, OpenMCF provisions:

• Floating IP Association — an openstack_networking_floatingip_associate_v2 resource that binds the specified floating IP address to the target port

Prerequisites

• OpenStack credentials configured via environment variables or OpenMCF provider config
• An allocated floating IP — either the IP address or UUID of an existing floating IP (typically from an OpenStackFloatingIp resource)
• A port with at least one fixed IP — the target port must exist and have at least one fixed IP address (typically from an OpenStackNetworkPort resource)

Quick Start

Create a file fip-associate.yaml:

apiVersion: openstack.openmcf.org/v1
kind: OpenStackFloatingIpAssociate
metadata:
  name: my-fip-associate
  labels:
    openmcf.org/provisioner: pulumi
    openmcf.org/stack.jobId: dev.OpenstackFloatingIpAssociate.my-fip-associate
    openmcf.org/stack.module.source: github.com/plantonhq/openmcf//apis/org/openmcf/provider/openstack/openstackfloatingipassociate/v1/iac/pulumi/module
spec:
  floatingIp:
    value: "203.0.113.42"
  portId:
    value: "a1b2c3d4-e5f6-7890-abcd-ef1234567890"

Deploy:

openmcf apply -f fip-associate.yaml

This associates the floating IP 203.0.113.42 with the specified port, enabling external connectivity through that floating IP.

Configuration Reference

Required Fields

Optional Fields

Examples

Basic Association with Literal Values

Associates a floating IP with a port using literal IP address and port UUID values. Suitable when both resources are managed outside of OpenMCF or when you already know the values:

apiVersion: openstack.openmcf.org/v1
kind: OpenStackFloatingIpAssociate
metadata:
  name: web-fip-associate
  labels:
    openmcf.org/provisioner: pulumi
    openmcf.org/stack.jobId: dev.OpenstackFloatingIpAssociate.web-fip-associate
    openmcf.org/stack.module.source: github.com/plantonhq/openmcf//apis/org/openmcf/provider/openstack/openstackfloatingipassociate/v1/iac/pulumi/module
spec:
  floatingIp:
    value: "203.0.113.42"
  portId:
    value: "a1b2c3d4-e5f6-7890-abcd-ef1234567890"

Association with Foreign Key References

Uses valueFrom to reference an OpenStackFloatingIp and an OpenStackNetworkPort managed in the same InfraChart. The FK resolver automatically retrieves the floating IP address and port UUID at deploy time. Since kind and fieldPath default to the annotated values, only name is required in each reference:

apiVersion: openstack.openmcf.org/v1
kind: OpenStackFloatingIpAssociate
metadata:
  name: app-fip-associate
  labels:
    openmcf.org/provisioner: pulumi
    openmcf.org/stack.jobId: staging.OpenstackFloatingIpAssociate.app-fip-associate
    openmcf.org/stack.module.source: github.com/plantonhq/openmcf//apis/org/openmcf/provider/openstack/openstackfloatingipassociate/v1/iac/pulumi/module
spec:
  floatingIp:
    valueFrom:
      name: app-floating-ip
  portId:
    valueFrom:
      name: app-port

Association with Fixed IP on a Multi-IP Port

When the target port has multiple fixed IP addresses, use fixedIp to specify which one the floating IP should map to. Without this field, OpenStack picks the first fixed IP on the port:

apiVersion: openstack.openmcf.org/v1
kind: OpenStackFloatingIpAssociate
metadata:
  name: multi-ip-fip-associate
  labels:
    openmcf.org/provisioner: pulumi
    openmcf.org/stack.jobId: prod.OpenstackFloatingIpAssociate.multi-ip-fip-associate
    openmcf.org/stack.module.source: github.com/plantonhq/openmcf//apis/org/openmcf/provider/openstack/openstackfloatingipassociate/v1/iac/pulumi/module
spec:
  floatingIp:
    valueFrom:
      name: prod-floating-ip
  portId:
    valueFrom:
      name: prod-multi-ip-port
  fixedIp: "10.0.1.100"

Association in a Specific Region

Overrides the provider-level region for deployments that span multiple OpenStack regions:

apiVersion: openstack.openmcf.org/v1
kind: OpenStackFloatingIpAssociate
metadata:
  name: region2-fip-associate
  labels:
    openmcf.org/provisioner: pulumi
    openmcf.org/stack.jobId: prod.OpenstackFloatingIpAssociate.region2-fip-associate
    openmcf.org/stack.module.source: github.com/plantonhq/openmcf//apis/org/openmcf/provider/openstack/openstackfloatingipassociate/v1/iac/pulumi/module
spec:
  floatingIp:
    value: "198.51.100.10"
  portId:
    valueFrom:
      name: region2-app-port
  region: RegionTwo

Stack Outputs

After deployment, the following outputs are available in status.outputs:

Related Components

• OpenStackFloatingIp — allocates floating IPs from external networks; use its built-in portId field for simple allocation-and-association in a single manifest
• OpenStackNetworkPort — creates ports with specific IPs and security groups that floating IPs can be associated with
• OpenStackNetwork — provides the Layer 2 network on which ports are created
• OpenStackSubnet — defines IP address ranges and DHCP settings that determine the fixed IPs available on ports
• OpenStackRouter — provides routing between internal networks and external connectivity