From 5635c33aa263080fe84e29a11a52f86fee583ca2 Mon Sep 17 00:00:00 2001 From: Stephen Steiner Date: Sun, 16 Jun 2019 22:31:17 -0400 Subject: [PATCH] Update demo.md (#1396) Step 2 instructs the user to create the namespace `argo`, and the coin-flip (at least) uses the service account `argo`, so it makes sense to provide `--serviceaccount=argo:argo` so that the initial experience works, "out of the box". --- demo.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/demo.md b/demo.md index 014a615dd274..5f7f321ebd2b 100644 --- a/demo.md +++ b/demo.md @@ -32,9 +32,9 @@ kubectl create clusterrolebinding YOURNAME-cluster-admin-binding --clusterrole=c To run all of the examples in this guide, the 'default' service account is too limited to support features such as artifacts, outputs, access to secrets, etc... For demo purposes, run the following -command to grant admin privileges to the 'default' service account in the namespace 'default': +command to grant admin privileges to the 'argo' service account in the namespace 'argo': ``` -kubectl create rolebinding default-admin --clusterrole=admin --serviceaccount=default:default +kubectl create rolebinding default-admin --clusterrole=admin --serviceaccount=argo:argo ``` For the bare minimum set of privileges which a workflow needs to function, see [Workflow RBAC](docs/workflow-rbac.md). You can also submit workflows which run with a different