Skip to content

Commit

Permalink
More Explicit Text to Not Run SA Permissions Commands, Edit Max Numbe…
Browse files Browse the repository at this point in the history
…r of Sessions Instructions, Tag Image as 2.0 #61
  • Loading branch information
danielhelfand committed Sep 19, 2019
2 parents f37c639 + 829c163 commit 3132ea4
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 6 deletions.
3 changes: 2 additions & 1 deletion .workshop/settings.sh
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
WORKSHOP_NAME=lab-tekton-pipelines
WORKSHOP_IMAGE=quay.io/openshiftlabs/lab-tekton-pipelines:latest
WORKSHOP_IMAGE=quay.io/openshiftlabs/lab-tekton-pipelines:2.0
CONSOLE_IMAGE=quay.io/openshift/origin-console:4.2
RESOURCE_BUDGET=custom
MAX_SESSION_AGE=7200
IDLE_TIMEOUT=300
SERVER_LIMIT=50
9 changes: 5 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,12 +30,13 @@ Next create a project in OpenShift into which the workshop is to be deployed.
oc new-project workshops
```

From within the top level of the Git repository, now run the command below. **NOTE:** You
will want to set the `n` as part of `--override SERVER_LIMIT=n` to the number of users
you will expect as part of your workshop.
**NOTE:** The default max number of sessions (i.e. users who can access the workshop at the same time) defaults to 50. The number for the max number
of sessions can be set in [settings.sh](./.workshop/settings.sh) using the `SERVER_LIMIT` property. If 50 is not enough sessions or too many, the amount can be increased or decreased by changing the property from 50 to the expected number of users. It's also important to make sure your OpenShift cluster can support as many users that the workshop needs.

From within the top level of the Git repository, now run the command below.

```
./.workshop/scripts/deploy-spawner.sh --override SERVER_LIMIT=n
./.workshop/scripts/deploy-spawner.sh
```

The name of the deployment will be `lab-tekton-pipelines`.
Expand Down
3 changes: 2 additions & 1 deletion workshop/content/exercises/serviceaccount.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,8 @@ later in this workshop. This is how you will connect the `pipeline` service acco
to the pipeline run.

For reference, you can add the permissions used by `pipeline` to a service account
using the `oc` commands below:
using the `oc` commands below. However, you do not need to run these commands now as
`pipeline` has been set up for you with the appropriate permissions.

[source,bash]
----
Expand Down

0 comments on commit 3132ea4

Please sign in to comment.