Skip to content

Commit 186ffeb

Browse files
authored
docs: clarify botstopper kubernetes instructions (#1404)
This makes it clear that when generating a kubernetes secret to pull the bot stopper image that: - no email is required - a user is required but the actual value of the username is not checked - the GH token needs to be pasted in Signed-off-by: Thomas Arrow <tarrow@users.noreply.github.com>
1 parent ff87aac commit 186ffeb

1 file changed

Lines changed: 2 additions & 3 deletions

File tree

docs/docs/admin/botstopper.mdx

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -51,9 +51,8 @@ If you are using Kubernetes, you will need to create an image pull secret:
5151
kubectl create secret docker-registry \
5252
techarohq-botstopper \
5353
--docker-server ghcr.io \
54-
--docker-username your-username \
55-
--docker-password your-access-token \
56-
--docker-email your@email.address
54+
--docker-username any-username \
55+
--docker-password <your-access-token> \
5756
```
5857

5958
Then attach it to your Deployment:

0 commit comments

Comments
 (0)