Eugen

I believe there are 2 possible ways to improve this story: handle properly st2actionrunner failures/re-schedules in st2 core or re-architect stackstorm-ha. This could be a future enhancement.

`st2ctl status` reports pids of the currently running st2 processes in the local environment. It's not expected for `st2ctl` to report the correct status in HA environment as you control...

Slightest part of `CI` story is done via adding Helm & K8s lint checks: https://github.com/StackStorm/stackstorm-enterprise-ha/pull/25

TODO: Automate the Helm chart deployment for every release release to Github pages via https://github.com/jupyterhub/chartpress This is currently done manually. Example: https://github.com/opsdroid/helm-chart/blob/25ffce4a0125823b92eca7f3e3415106d1d808c2/ci/deploy.sh#L17

This might be helpful too for further integration: * https://github.com/helm/chart-releaser * https://circleci.com/blog/deploying-documentation-to-github-pages-with-continuous-integration/ * https://circleci.com/developer/orbs/orb/pennlabs/helm-tools

This belongs to https://github.com/stackStorm/stackstorm-ha project and repository. Transferred there from stackstorm/st2.

Yes, that's caused by the fact that hooks are not managed by Helm and there is no garbage collector for them yet: https://helm.sh/docs/topics/charts_hooks/#hook-resources-are-not-managed-with-corresponding-releases The only workaround is adding `"helm.sh/hook-delete-policy": hook-succeeded`...

Alternative per Helm doc advice is trying `ttlSecondsAfterFinished` (https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/#clean-up-finished-jobs-automatically) and `TTLController` https://kubernetes.io/docs/concepts/workloads/controllers/ttlafterfinished/ to clean-up the job automatically after some reasonable delay. However this feature looks like still in `alpha` state.

@cflanny See https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork how to create a PR from a fork.

``` mongodb: architecture: standalone ``` That's probably the reason here as the default for the Helm chart is a `replicaset` architecture and so probably other templating and naming is used...