diff options
| author | Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com> | 2022-03-14 14:26:37 +1300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-03-14 14:26:37 +1300 |
| commit | 41e37715de8f8f379eae6136696c80c8c093b26f (patch) | |
| tree | 7c83316a57db6abcef05f153443ee00e2ba70bd0 /contributors | |
| parent | 09fa4f3113db8b5832e221bf40af348c256e4b3c (diff) | |
update conformance-tests.md
Diffstat (limited to 'contributors')
| -rw-r--r-- | contributors/devel/sig-architecture/conformance-tests.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/contributors/devel/sig-architecture/conformance-tests.md b/contributors/devel/sig-architecture/conformance-tests.md index 8546f649..cb9a7dcd 100644 --- a/contributors/devel/sig-architecture/conformance-tests.md +++ b/contributors/devel/sig-architecture/conformance-tests.md @@ -67,6 +67,7 @@ Examples of features which are not currently eligible for conformance tests: - cloud-provider-specific features, eg: GCE monitoring, S3 Bucketing, etc. - anything that requires a non-default admission plugin - features that are pending deprecation, eg: componentstatus +- any endpoints that are used as tools for operation like apiserver logs should not be part of conformance. Conformance tests are intended to be stable and backwards compatible according to the standard API deprecation policies. Therefore any test that relies on specific |