From 8a09d414e81c7cdea92ebaf2437649bbd6ffdf9d Mon Sep 17 00:00:00 2001 From: Manish Bansal Date: Sun, 21 Jul 2019 14:22:52 +0530 Subject: [PATCH] Improved PodPreset documentation (#15409) * Adding scroller to the command * Updated * Updated --- content/en/docs/concepts/workloads/pods/podpreset.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/pods/podpreset.md b/content/en/docs/concepts/workloads/pods/podpreset.md index 09fa309f28..876ba995c9 100644 --- a/content/en/docs/concepts/workloads/pods/podpreset.md +++ b/content/en/docs/concepts/workloads/pods/podpreset.md @@ -74,7 +74,11 @@ In order to use Pod Presets in your cluster you must ensure the following: 1. You have enabled the admission controller `PodPreset`. One way to doing this is to include `PodPreset` in the `--enable-admission-plugins` option value specified for the API server. In minikube add this flag - `--extra-config=apiserver.enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,PodPreset` + + ```shell + --extra-config=apiserver.enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,PodPreset + ``` + while starting the cluster. 1. You have defined your Pod Presets by creating `PodPreset` objects in the namespace you will use.