concept spec and status section in category kubernetes
appears as: spec d status sections, spec and status sections

This is an excerpt from Manning's book Kubernetes in Action, Second Edition MEAP V05.
In contrast, the earlier YAML manifest of the Node object was relatively easy to read, because the order of the top-level fields is what one would expect: apiVersion, kind, metadata, spec, and status. You’ll notice that this is simply because the alphabetical order of the five fields just happens to make sense. But the fields under those fields suffer from the same problem, as they are also sorted alphabetically.