diff --git a/CHANGELOG.md b/CHANGELOG.md index e1e646ec..c13f33ac 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,7 +1,7 @@ # Changelog ## In Development - +* Add option for st2packs-PersistentVolumes to allow for seamless custom pack-updates without job-impact (#160) (by @moonrail) ## v0.40.0 * Switch st2 version to `v3.4dev` as a new latest development version (#157) diff --git a/README.md b/README.md index d35d9ddb..47194656 100644 --- a/README.md +++ b/README.md @@ -182,7 +182,7 @@ As any other Helm dependency, it's possible to further configure it for specific ## Install custom st2 packs in the cluster In distributed environment of the Kubernetes cluster `st2 pack install` won’t work. 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. -Helm chart will take it from there, sharing `/opt/stackstorm/{packs,virtualenvs}` via a sidecar container in pods which require access to the packs. +Helm chart will take it from there, sharing `/opt/stackstorm/{packs,virtualenvs}` via a sidecar container or alternatively shared PersistentVolume in pods which require access to the packs. ### Building st2packs image For your convenience, we created a new `st2-pack-install ` 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. @@ -213,6 +213,34 @@ kubectl create secret docker-registry st2packs-auth --docker-server=