Should APPLY requests be counted in MUTATE SLO?

[m-messiah]

The current API Call latency SLO doc does not include APPLY requests:

community/sig-scalability/slos/api_call_latency.md

Lines 15 to 16 in 4950116

	<a name="footnote2">\[2\]</a> By mutating API calls we mean POST, PUT, DELETE
	and PATCH.

And it looks like the doc was not updated since the APPLY was introduced.

Being the main part of updates the call is definitely of MUTATE nature and seems that should not be less important than PATCH or UPDATE.

Any strong objections or side-talks why it should not be included in MUTATE group and advised for SLO?

/sig scalability
/sig docs

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale