Epic Goal

• Tasks shipped by ecosystem shouldn't have multiple steps as it leads to requests/limit ranges doubled when LimitRange is used

Why is this important?

• Resource utilization is a critical part so this change is important to avoid unnecessary usage of resources

Scenarios

Details : https://redhat-internal.slack.com/archives/C050H792L2Y/p1723101488638219

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment