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
Use case: When values in a mounted configmap/secret is changed (e.g. a password to a service), would like a way to reload at runtime without needing to restart the integration (pod)
The text was updated successfully, but these errors were encountered:
Considering that Camel K rebuilds are fast, would it be safer to trigger a rebuild & redeploy of the integration, rather than reloading the runtime? From the outset (i.e. user changing creds) it would appear similar (the runtime uses the new credentials), but internally, we would move through regular kubernetes lifecycle steps (rebuild, redeploy, rollover, readiness checks). Reloading at runtime doesn't sounds right to me.
This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!
Opening this request to capture discussion here: https://camel.zulipchat.com/#narrow/stream/257299-camel-k/topic/watching.20mounted.20configmap.2Fsecret
Use case: When values in a mounted configmap/secret is changed (e.g. a password to a service), would like a way to reload at runtime without needing to restart the integration (pod)
The text was updated successfully, but these errors were encountered: