-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
-
Support and expose Tenancy through AWSNodePoolPlatform
-
BU Product Work
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-1530 - Support and expose Tenancy through AWSNodePoolPlatform | Part I
-
OCPSTRAT-1530Support and expose Tenancy through AWSNodePoolPlatform | Part I
-
0% To Do, 0% In Progress, 100% Done
-
0
-
0
-
0
User Story:
As a (user persona), I want to be able to:
- Set Tenancy options through the NodePool API.
so that I can achieve
- machines backed by a Dedicated Instance
- machines backed by a Dedicated Host
Acceptance Criteria:
Description of criteria:
- Upstream documentation
- Point 1
- Point 2
- Point 3
(optional) Out of Scope:
Detail about what is specifically not being delivered in the story
Engineering Details:
- We need to expose the following CAPA field in the NodePool API under .spec.platform.aws https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/api/v1beta2/awsmachine_types.go#L191
This does not require a design proposal.
This requires a feature gate.
- blocks
-
OCPSTRAT-1530 Support and expose Tenancy through AWSNodePoolPlatform | Part I
- Release Pending
- is related to
-
HIVE-2589 Support AWS Dedicated Hosts for AWS MachinePools
- To Do