Pack defaults do not get overridden when a pack is reinstalled about stackstorm-k8s HOT 2 OPEN

I agree that the override feature should also be included in other services besides st2client ( i.e. st2actionrunner)
the documentation says that

Upon a pack install or reload resource state is managed as follows:
State is read from the pack’s resource metadata files that reside in /opt/stackstorm/packs/. These are downloaded from the relevant repository of the pack, e.g. GIT, StackStorm-Exchange.

If /opt/stackstorm/overrides/_global.yaml is present, then any global overrides are applied. The _global.yaml allows you to specify the default state of a particular resource types, e.g. disable all sensors. The format of the _global.yaml is as follows (set to disable everything):

However, this does not work when running packs.install or packs.load action from the UI. So docs are misleading...

from stackstorm-k8s.

How are you defining your overrides? Via the st2.overrides value?
https://github.com/StackStorm/stackstorm-k8s/blob/master/values.yaml#L96-L109

Or are you trying to create files in the st2client pod? If you put files in the st2client pod, they will only be visible to processes (like st2ctl) that you run in that pod. They will not be visible in the st2actionrunner pods which handle the packs.install action (the st2api pods might also read the files).

Also, are you trying to use st2.packs.volumes? https://github.com/StackStorm/stackstorm-k8s/blob/master/values.yaml#L170-L171
Supporting this with st2.packs.volumes probably requires adding another volume at st2.packs.volumes.overrides similar to st2.packs.volumes.virtualenvs so that the files can be appropriately shared across the st2actionrunner and st2api pods.

from stackstorm-k8s.