api-conventions.md should explain patchStrategy

[MikeSpreitzer]

The API conventions doc should explain, or point to an explanation of, the patchStrategy stuff that appears in golang. The reader should be told how to understand the existing golang, and how to use patchStrategy when writing new golang. This should include a pointer to the definitions of what each patchStrategy means.

[MikeSpreitzer]

@kubernetes/sig-api-machinery-misc

[nikhita]

Adding sig-arch as well because they own the doc
/sig architecture
/kind documentation

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[MikeSpreitzer]

/remove-lifecycle rotten