diff options
| author | Riaan Kleinhans <61125752+Riaankl@users.noreply.github.com> | 2022-03-31 06:35:46 +1300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-03-31 06:35:46 +1300 |
| commit | 7ebe82693f17fcd8bdc6ccea97951102b65e5e9d (patch) | |
| tree | 9fcde301c196155609d23e46f84a1032e1ec9bb0 | |
| parent | 41e37715de8f8f379eae6136696c80c8c093b26f (diff) | |
Update conformance-tests.md
| -rw-r--r-- | contributors/devel/sig-architecture/conformance-tests.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/devel/sig-architecture/conformance-tests.md b/contributors/devel/sig-architecture/conformance-tests.md index cb9a7dcd..685ce539 100644 --- a/contributors/devel/sig-architecture/conformance-tests.md +++ b/contributors/devel/sig-architecture/conformance-tests.md @@ -67,7 +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. +- 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 |