Today, administrators who need to change an OpenShift node’s hostname after it has joined the cluster must follow an unsanctioned, multi‑step workaround (outlined in https://access.redhat.com/solutions/7073526 ). Because this procedure is not part of the supported product lifecycle, any failures or side‑effects fall outside of official SLAs, and users cannot turn to Red Hat Support when issues arise.

Requested Enhancement

Provide formal product support for the manual hostname update workflow described in https://access.redhat.com/solutions/7073526 , including:

1. Documentation in the OpenShift Administration Guide of the exact steps and caveats.
2. Supportability matrix clarifying which OpenShift versions and node configurations are covered.
3. Validation tests in the release pipeline to ensure the procedure remains valid across future Releases.
4. Support escalation path so that customers can open tickets against this procedure if they encounter problems.

Benefits

Customer confidence: Users gain assurance that they can rely on this procedure under Red Hat’s support umbrella.

Reduced risk: Official testing and documentation minimize the chance of missteps or unsupported edge cases.

Consistency: Aligns this common operational need with other first‑class cluster‑lifecycle operations.