Reference

Everything on these pages is generated. The field tables come from the schema artefacts the control plane validates against, the mutability column is measured by running the hash function that decides it, and the rejection catalogue is walked out of the constructors that build the messages. None of it is transcribed, so none of it can disagree with the code.

• Deployment manifest — every field of a long-running deployment, section by section.
• Job manifest — work that runs to completion.
• CronJob manifest — work that runs on a schedule.
• Deployment, REST API surface — the same resource as the API accepts it, including the keys that surface takes and a YAML manifest refuses.
• Rejections and alterations — every machine-readable code, the field it names, the accepted form, and the changes the server makes that you did not send.

Two columns are worth reading before the rest. Mutability says whether changing a field replaces the container: there are two answers and no third, and being wrong about it costs an outage. Since says which release first carried the field, so a reader on an older one does not act on newer behaviour.