You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<aname="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
The text was updated successfully, but these errors were encountered:
k8s-ci-robot
added
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
sig/scalability
Categorizes an issue or PR as relevant to SIG Scalability.
and removed
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
labels
Oct 2, 2024
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
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
The text was updated successfully, but these errors were encountered: