Hide Forgot
Description of problem: When using the command 'oc describe X', the output given is not shown in the same order every time, which could cause confusion for users expecting to see items in the same place for every output Version-Release number of selected component (if applicable): oc v3.3.1.3 How reproducible: Every time Steps to Reproduce: 1. oc describe sa default 2. oc describe sa default Actual results: Name: default Namespace: wgordon Labels: <none> Image pull secrets: default-dockercfg-llqsl my-pull-secret Mountable secrets: default-token-xe2u5 default-dockercfg-llqsl Tokens: default-token-i0dd6 default-token-xe2u5 **** Name: default Namespace: wgordon Labels: <none> Mountable secrets: default-token-xe2u5 default-dockercfg-llqsl Tokens: default-token-i0dd6 default-token-xe2u5 Image pull secrets: default-dockercfg-llqsl my-pull-secret Expected results: Name: default Namespace: wgordon Labels: <none> Image pull secrets: default-dockercfg-llqsl my-pull-secret Mountable secrets: default-token-xe2u5 default-dockercfg-llqsl Tokens: default-token-i0dd6 default-token-xe2u5 **** Name: default Namespace: wgordon Labels: <none> Image pull secrets: default-dockercfg-llqsl my-pull-secret Mountable secrets: default-token-xe2u5 default-dockercfg-llqsl Tokens: default-token-i0dd6 default-token-xe2u5 Additional info:
`oc describe` is meant to be a human-readable output and is not meant to be consumed by machines, etc. I don't think it is in the domain space for `oc describe` to have deterministic sorting/ordering in the output.
I would agree that it's intended to be human readable, but it's very likely that a user would not read the labels, and assume something was lost. I also noticed this to be the case for `oc describe limits`...and likely other outputs. So perhaps not a bug, per se, but I think it's jarring for the user when trying to compare outputs from `oc describe`