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
It would be useful if the kubestack/framework image had a location where arbitrary scripts could be placed, which would then be executed at runtime by the default entrypoint.
This would facilitate running some extra tasks at runtime without needing to override the default entrypoint (and fixing it when that entrypoint changes).
It would enable some nice and lazy thing like, say, authenticating to a cluster in CI (just to illustrate):
I think this is a valid idea to explore. Hooks seem a common approach to this. We could define points in the entrypoint and have pre- and post- hooks where it makes sense.
Hi, really liking Kubestack so far! 🙏
It would be useful if the
kubestack/framework
image had a location where arbitrary scripts could be placed, which would then be executed at runtime by the default entrypoint.This would facilitate running some extra tasks at runtime without needing to override the default entrypoint (and fixing it when that entrypoint changes).
It would enable some nice and lazy thing like, say, authenticating to a cluster in CI (just to illustrate):
Example of other images using this pattern
postgres
uses/docker-entrypoint-initdb.d/
as described herenginx
uses/docker-entrypoint.d/
as shown hereThe text was updated successfully, but these errors were encountered: