Xingxing Xia

/label cherry-pick-approved

/label cherry-pick-approved

/label cherry-pick-approved

/label cherry-pick-approved

Right, the display of kubectl/oc's subcommands like `get -o yaml`, `edit`, `explain` et al print the fields alphabetically. So, while following our documents, if user runs `edit` to **edit existing**...

But by default, these customization fields are not existent in a fresh env, so user only **adds new** fields rather than edits the existing fields at the beginning. In terms...

Anyway, ordering as per the original issue's request is fine. Other problems come as below, though. Need they be updated too? `oc edit ingress.config.openshift.io cluster` will show: ``` apiVersion: config.openshift.io/v1...

@yuwang-RH @xueli181114, in addition, for other ROSA/OSD parts changed within the `ifndef::openshift-rosa[]` or `ifdef::openshift-rosa[]`, they are not OCP common scope so I have no more background, need you to double...

/label qe-approved

@lunarwhite @geliu2016 would you like to also help review when available?