1. Proposed title of this feature request:

We need the timeout flag for unified node addition method across all the installation types
i.e `oc adm node-image create` as per the requirement in case of customer having lower b/w environment.

2. What is the nature and description of the request?

Currently, when using oc adm node-image create for node addition, there is no configurable timeout parameter to handle environments with lower bandwidth or slower image downloads. This limitation can cause failures or retries during image creation, especially in constrained customer networks.

The request is to introduce a --timeout flag (or similar configurable parameter) to oc adm node-image create. This would allow administrators to explicitly define the maximum wait time for image creation and pulling operations, ensuring consistent behavior across different OpenShift installation types (Agent-based, Assisted Installer, IPI/UPI, and SNO).

3. Why does the customer need this? (List the business requirements here)

Support for low-bandwidth environments: Customers with limited or high-latency network connectivity require extended timeouts to successfully generate node images without failure.

Operational efficiency: Avoids repeated failures, manual retries, or custom scripting for node addition, reducing administrative overhead in production environments.

Improved customer experience: Provides flexibility to adapt the node addition process to diverse customer network conditions, ensuring smoother adoption of OpenShift. And also to troubleshoot.

4. List any affected packages or components.

openShift CLI (oc) — specifically the oc adm node-image create subcommand