Skip to content

Commit

Permalink
Switch to production image (#5)
Browse files Browse the repository at this point in the history
Switched to the production image, and updated the README to reference the Helm chart repo now that it's available.
  • Loading branch information
adamconnelly authored Nov 18, 2021
1 parent b91c256 commit 96dfa0e
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 2 deletions.
15 changes: 14 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,18 @@ on Kubernetes. The chart deploys the worker pool as a StatefulSet containing two
Follow the instructions [here](https://docs.spacelift.io/concepts/worker-pools) to create a
new worker pool, generating a private key and token.

Next, add our Helm chart repo and update your local chart cache:

```shell
helm repo add spacelift https://downloads.spacelift.io/helm
helm repo update
```

Assuming your key and token are stored in the `SPACELIFT_PK` and `SPACELIFT_TOKEN` environment
variables, you can install the chart using the following command:

```shell
helm upgrade spacelift-worker . --install --set "credentials.token=$SPACELIFT_TOKEN,credentials.privateKey=$SPACELIFT_PK"
helm upgrade spacelift-worker spacelift/spacelift-worker --install --set "credentials.token=$SPACELIFT_TOKEN,credentials.privateKey=$SPACELIFT_PK"
```

Read the rest of this page to find out how to configure various other options.
Expand All @@ -27,6 +34,12 @@ This chart uses [Docker in Docker](https://hub.docker.com/_/docker) to provide a
for the launcher. The `dind` container needs a privileged [security context](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/)
to work. Please make sure this is acceptable to you before deploying it to your own clusters.

## Image Version

The `launcher.image.tag` is set to `latest` by default in this chart. We rely on this behavior
to automatically roll out new versions of the launcher. Pinning this to a specific version
may eventually cause your private launchers to stop working.

## Authentication

To authenticate with Spacelift, you need to set the `SPACELIFT_TOKEN` and `SPACELIFT_POOL_PRIVATE_KEY`
Expand Down
2 changes: 1 addition & 1 deletion values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ podSecurityContext: {}
launcher:
image:
# repository contains the docker repository containing the launcher image.
repository: public.ecr.aws/spacelift-dev/launcher
repository: public.ecr.aws/spacelift/launcher
# pullPolicy defines the pull policy for the image.
pullPolicy: Always
# tag specifies the image tag to use.
Expand Down

0 comments on commit 96dfa0e

Please sign in to comment.