Skip to content

Feature parity with CAPO #577

Description

@mandre

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:

Additions to the Server controller:

  • Metadata
  • ConfigDrive
  • RootVolume
  • SchedulerHints

Additions to the Volume controller:

  • AvailabilityZone

Additions to the Port controller:

  • AdminStateUp
  • MACAddress
  • TrustedVIF
  • Binding HostID
  • PropagateUplinkStatus
  • ValueSpecs

Additional information

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions