Originally posted on Github: https://github.com/k-orc/openstack-resource-controller/issues/577

What would you like to see implemented?
In order to use ORC controllers in CAPO, we need to match feature parity with what CAPO currently exposes. This issue is a top-level issue to track needed changes.
New controllers:

KeyPair (#136)
Trunk (#364)

Additions to the Server controller:

Metadata
ConfigDrive
RootVolume
SchedulerHints

Additions to the Volume controller:

AvailabilityZone

Additions to the Port controller:

AdminStateUp
MACAddress
Binding Profile
Binding HostID
PropagateUplinkStatus
ValueSpecs

Additional information
The tracking issue in CAPO: kubernetes-sigs/cluster-api-provider-openstack#2814