Skip to content

Support for tenancy=host with 1 instance - 1 host relation #5599

@enxebre

Description

@enxebre

/kind feature

Describe the solution you'd like
As a Service Consumer I want to be able to leverage dedicated hosts for BYOL scenarios.
As a Service Consumer I want to express intent for 1 - 1 relation between instance and host with matching capacity so I don’t need to carry the burden of reservations out of band.
As capi/capa API consumer I want capa to expose a knob so I can express intent for this use case. It would discover the most efficient reservation out of my instance type, create the reservation and pin the instance to it at run time

Anything else you would like to add:

Similar to #5548 but covering a different use case. Both complementary.

Environment:

  • Cluster-api-provider-aws version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.needs-priorityneeds-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions