Feature Overview (aka. Goal Summary)  

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

vSphere 8 now allows 255 volumes per VM (i.e OCP workers) and we use the default value of 59 which is safe for vsphere 7 but vsphere 8 customers want to be able to leverage the new improved limit.

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.

Keep maxAllowedBlockVolumesPerNode default to 59 but allow customers to configure the value themselves.

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.

New API to configure maxAllowedBlockVolumesPerNode

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.

As an OCP admin on top of vsphere 8 i want to increase the maximum number of volumes that can be attached to OCP workers.

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.

Autoconfigure based on vsphere version

Background

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

The limit was safe in the past but the new vsphere 8 limit requires us to make this option configurable

Customer Considerations

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

Make sure we document the limit of 255 which is applicable to vsphere 8+ only

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.

Document how to override maxAllowedBlockVolumesPerNode + current limit (255).
Mention that vsphere 7 is still limited to 59

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.

Non