CNCF Kubernetes conformance

Introduction

Interoperability, consistency, and traceability play a crucial role in the deployment and use of a Kubernetes environment. Testing ensures this conformance across different Kubernetes environments.

The SCS project always intends to reuse existing standards whenever possible. For this reason, the upstream test suite of the Certified Kubernetes Conformance Program is used for conformance testing.

Motivation

As an operator as well as an user, I want to check the conformance of a Kubernetes environment in order to ensure the interoperability, consistency, and traceability of it.

Regulations

The conformance testing is performed as part of the SCS compliance check suite executing the standard set of conformance tests defined by the [Conformance] tag in the Kubernetes e2e suite. All conformance tests MUST be passed successfully.

We allow exceptions from the Kubernetes e2e tests if it is reasonable, e.g. bugs in certain tests. Please note that exceptions may be added and/or removed in such reasonable cases and thereby allowing the standard to be updated without the need for a new version of it. If the reason for an exception goes away, so does the exception and it will therefore be removed.

The exceptions are listed under the key okToFail in Tests/kaas/scs-sonobuoy-config-v1.yaml.