From 4e7bed357762e813900f1ed5a402675711c530f9 Mon Sep 17 00:00:00 2001 From: Daniel Pawlik Date: Thu, 12 Nov 2020 09:15:52 +0100 Subject: [PATCH] Changed informations provided in openshiftpods driver Some informations that were in openshiftpods driver was confusing how to use the driver correctly. Change-Id: I55461b445407111c358bf02131c8fb7bf2d46c56 --- doc/source/openshift-pods.rst | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/doc/source/openshift-pods.rst b/doc/source/openshift-pods.rst index 4fbf5c72d..c65e31fee 100644 --- a/doc/source/openshift-pods.rst +++ b/doc/source/openshift-pods.rst @@ -12,9 +12,8 @@ Selecting the openshift pods driver adds the following options to the :type: list The Openshift Pods driver is similar to the Openshift driver, but it - only support pod label to be created in a single project. This enable - using an unprivileged service account that doesn't requires the - self-provisioner role. + only supports pod label. This enables using an unprivileged service account + that doesn't require the self-provisioner role. Example: @@ -36,8 +35,7 @@ Selecting the openshift pods driver adds the following options to the Name of the context configured in ``kube/config``. Before using the driver, Nodepool services need a ``kube/config`` file - manually installed with self-provisioner (the service account needs to - be able to create projects) context. + manually installed. Make sure the context is present in ``oc config get-contexts`` command output. @@ -61,7 +59,7 @@ Selecting the openshift pods driver adds the following options to the .. attr:: name :required: - The project's name that will be used to create the pods. + The project's (namespace) name that will be used to create the pods. .. attr:: node-attributes :type: dict