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
{{ message }}
Repository navigation
Use Secret for st2.docker.conf instead of ConfigMap #408
This is supported via st2.existingConfigSecret. You create a secret with your st2.conf contents, and then pass that secret name to the chart. It then gets mounted like this:
I'm using the existingConfig and now I have a secret called st2-secrets-conf that contains the DB / LDAP / RabbitMQ connection info and also a configMap called -st2-config that contains both st2.docker.conf that contains redis and rabbitMQ connection info in clear text.
And I think that the only reason I don't have Mongo connection info there as well is that I'm not using the mongo chart.
imo there should be a way to force the installation to only accept credentials from secrets.
Activity
cognifloyd commentedon Apr 11, 2024
This is supported via
st2.existingConfigSecret. You create a secret with yourst2.confcontents, and then pass that secret name to the chart. It then gets mounted like this:stackstorm-k8s/templates/_helpers.tpl
Lines 167 to 171 in fabbea9
stackstorm-k8s/templates/_helpers.tpl
Lines 177 to 181 in fabbea9
The value is described here:
stackstorm-k8s/values.yaml
Lines 112 to 116 in fabbea9
Does that resolve your concerns?
akshat-rubrik commentedon Aug 14, 2024
Can we add this to docs please?
fdrab commentedon Aug 15, 2024
I'm using the existingConfig and now I have a secret called st2-secrets-conf that contains the DB / LDAP / RabbitMQ connection info and also a configMap called -st2-config that contains both st2.docker.conf that contains redis and rabbitMQ connection info in clear text.
And I think that the only reason I don't have Mongo connection info there as well is that I'm not using the mongo chart.
imo there should be a way to force the installation to only accept credentials from secrets.