From 3d24393f2a6bb656daebe41e23bd590ba5419886 Mon Sep 17 00:00:00 2001 From: Karthik Gaekwad Date: Tue, 19 Mar 2019 12:26:23 -0500 Subject: [PATCH] Removed conformance from column definition (#13139) The conformance column doesn't exist anymore... --- content/en/docs/setup/pick-right-solution.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/en/docs/setup/pick-right-solution.md b/content/en/docs/setup/pick-right-solution.md index 26ebb67853..06a67661e6 100644 --- a/content/en/docs/setup/pick-right-solution.md +++ b/content/en/docs/setup/pick-right-solution.md @@ -291,8 +291,6 @@ The above table is ordered by version test/used in nodes, followed by support le nodes. * **Networking** is what implements the [networking model](/docs/concepts/cluster-administration/networking/). Those with networking type _none_ may not support more than a single node, or may support multiple VM nodes in a single physical node. -* **Conformance** indicates whether a cluster created with this configuration has passed the project's conformance - tests for supporting the API and base features of Kubernetes v1.0.0. * **Support Levels** * **Project**: Kubernetes committers regularly use this configuration, so it usually works with the latest release of Kubernetes.