Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

Enable modifying EC2 Instance Metadata Options on Day 2 for ROSA/OSD clusters via Hive

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

Hive customers, i.e. ROSA and OSD, want the ability to modify – on day 2 – the EC2 Instance Metadata options.  Currently, only day 1 changes are supported via Hive.

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

Motivation for customers to use EC2 IMDS is to increase security posture provided by IMDS v2 endpoint and use AWS governance tools like IAM Policy, SCPs, AWS Configs etc to track compliance. Today, Hive and Hive customers can set this value at the time of cluster creation however, if they need to move between IMDSv2 optional and IMDSv2 required, they can not change this. They'd like to change it on all cluster's EC2 instances - including control plane, infra nodes, and compute nodes. In the Service Delivery, this also includes any temporary instances used for bootstrapping, supporting etc. 

Today the alternative available are 1) Delete and recreate the cluster 2) SRE do white-glove process to modify this upon customer request. Given OCP documentation has steps to modify this, it is confusing for customers to understand why the managed service does not give a self-service way to have this configuration changed.

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

<your text here>

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

Slack Discussion in #forum-ocp-hive : https://redhat-internal.slack.com/archives/CE3ETN3J8/p1691596437419779 

 [1] https://docs.openshift.com/container-platform/4.13/machine_management/control_plane_machine_management/cpmso-using.html#machineset-imds-options_cpmso-using 

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>