You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-49Lines changed: 16 additions & 49 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -191,62 +191,20 @@ StackStorm employs etcd as a distributed coordination backend, required for st2
191
191
`3` node Raft cluster is deployed via external official Helm chart dependency [etcd-operator](https://github.com/helm/charts/tree/master/stable/etcd-operator).
192
192
As any other Helm dependency, it's possible to further configure it for specific scaling needs via `values.yaml`.
193
193
194
-
### Docker registry
195
-
If you do not already have an appropriate docker registry for storing custom st2 packs images, we made it
196
-
very easy to deploy one in your k8s cluster. You can optionally enable in-cluster Docker registry via
197
-
`values.yaml` by setting `docker-registry.enabled: true` and additional 3rd party charts [docker-registry](https://github.com/helm/charts/tree/master/stable/docker-registry)
198
-
and [kube-registry-proxy](https://github.com/helm/charts/tree/master/incubator/kube-registry-proxy) will be configured.
199
-
200
194
## Install custom st2 packs in the cluster
201
-
In the kubernetes cluster, the `st2 pack install` command will not work. Instead, you need to bake the packs into a custom
202
-
docker image, and push it to a private or public docker registry. The image will provide `/opt/stackstorm/{packs,virtualenvs}`
203
-
via a sidecar container in pods which need access to the packs.
204
-
205
-
If you do not already have an appropriate docker registry, we made it very easy to deploy one in your k8s cluster.
206
-
See below for details.
207
-
208
-
### Build st2packs image
209
-
To build the st2packs image which contains your required packs installed in `/opt/stackstorm/packs` and
210
-
`/opt/stackstorm/virtualenvs`, define the `PACKS` build argument using a space separated list of pack names.
211
-
Set DOCKER_REGISTRY to the docker registry URL. If using the private docker registry in the k8s cluster,
212
-
set `DOCKER_REGISTRY`to `localhost:5000`.
213
-
214
-
Please see https://hub.docker.com/r/stackstorm/st2packs/ for details on how to build your custom `st2packs` image.
215
-
216
-
### Push st2packs image to a docker registry
217
-
If you're pushing to a private docker registry in the k8s cluster, you will need to port forward from your local host to the registry. You can use:
218
-
```
219
-
kubectl port-forward $(kubectl get pod -l app=docker-registry -o jsonpath="{.items[0].metadata.name}") 5000:5000
220
-
```
221
-
222
-
NOTE: If running on MacOS, before deploying the image, open another terminal and execute:
The source for the `stackstorm/socat` image is found at https://github.com/StackStorm/docker-socat.
228
-
229
-
To deploy the image to the registry, execute:
230
-
```
231
-
docker push ${DOCKER_REGISTRY}/st2packs:latest
232
-
```
195
+
In distributed environment of the Kubernetes cluster `st2 pack install` won’t work.
196
+
Instead, you need to bake the packs into a custom docker image, push it to a private or public docker registry and reference that image in Helm values.
197
+
Helm chart will take it from there, sharing `/opt/stackstorm/{packs,virtualenvs}` via a sidecar container in pods which require access to the packs.
233
198
234
-
### Pull st2packs from a private Docker registry
235
-
If you need to pull your packs Docker image from a private registry, you need to create a Kubernetes Docker registry secret and pass it to helm.
236
-
See [K8s documentation](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) for more info.
237
-
```
238
-
# Create a Docker registry secret called 'st2packs-auth'
Once secret created, you pass its name to helm value: `st2.packs.image.pullSecret`.
199
+
### Building st2packs image
200
+
For your convenience, we created a new `st2-pack-install <pack1> <pack2> <pack3>` utility and included it in a container that will help to install custom packs during the Docker build process without relying on live DB and MQ connection.
201
+
Please see https://github.com/StackStorm/st2packs-dockerfiles/ for instructions on how to build your custom `st2packs` image.
243
202
244
203
### How to provide custom pack configs
245
-
Update the `pack.configs` section of `stackstorm-ha/values.yaml`:
204
+
Update the `st2.packs.configs` section of Helm values:
246
205
247
206
For example:
248
207
```
249
-
pack
250
208
configs:
251
209
email.yaml: |
252
210
---
@@ -258,6 +216,15 @@ pack
258
216
```
259
217
Don't forget running Helm upgrade to apply new changes.
260
218
219
+
### Pull st2packs from a private Docker registry
220
+
If you need to pull your custom packs Docker image from a private repository, create a Kubernetes Docker registry secret and pass it to Helm values.
221
+
See [K8s documentation](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) for more info.
222
+
```
223
+
# Create a Docker registry secret called 'st2packs-auth'
0 commit comments