(I am starting with the assumption that KBase article is intended for the releases in which GC support is tech preview)

I propose that we:

• remove the KB link from the 4.21 docs when it goes GA in 4.21.z
• update the KB article to make it clear which versions it is about (and confirm version relevance for all procedures in the KB article)
• add the pre-4.21 workaround details to the KB (https://docs.google.com/document/d/1dAs2tNJot4V-lRRoj5RLzGAbVmnK7am0w_Rw6gSYdM0/edit?tab=t.0#heading=h.mvu307pxe8pj)
• include the shorter workaround details for the 4.21.z GA in the official docs as either a RN or directly in the cloud platform compatibility section (tracked separately in CNV-78430 subtask)

Alternate plan:

• do not remove KB link from 4.21 docs when 4.21.z GAs
• include all workaround details in the KB article, ensuring that the sections are clearly marked with the relevant version numbers

rhn-support-jsaucier , agilboa@redhat.com , rh-ee-nassouli - any thoughts or plans for the KB article on your end?

I/the docs team will handle the official doc updates for 4.21.z. I am unsure of who owns or should own the KB updates.

Thanks!