diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2022-04-03 15:26:09 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-04-03 15:26:09 -0700 |
| commit | 89d1fe2bd23393f0ee5e55d414f1969129a9e52b (patch) | |
| tree | 77c53d8c18feb860ca44fee82e96409a0ec1c045 | |
| parent | aa1391a5e654c7b7d8a2ced7c2ea1a742da74bb9 (diff) | |
| parent | 7ebe82693f17fcd8bdc6ccea97951102b65e5e9d (diff) | |
Merge pull request #6536 from Riaankl/update-conformance-tests.md
update conformance-tests.md
| -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 8da5af86..30b951df 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 operational tools, rather than application-oriented, should not be part of conformance, eg: apiserver logs. Conformance tests are intended to be stable and backwards compatible according to the standard API deprecation policies. Therefore any test that relies on specific |