cluster, helm: Add new Helm-chart "splice-info" #332
Conversation
giner
force-pushed
the
stas/cluster_helm_add_info
branch
4 times, most recently
from
672b440 to
1d1cf68
Compare
|
Thanks @giner . I haven't yet looked at it closely, but my main concern is that there's no tests for it. At a high level, we need to: deploy this in Pulumi (the Pulumi code is not yet in Splice though 😢 coming soon...), and add some logic to one of the preflight tests in |
|
Whatever gets it merged (or rejected, also works for me :)) faster. If DA folks could add tests let's do that. |
|
Definitely aiming at merge, not reject. Let me see if someone can carve out a bit of time for this then. |
This helm charts runs a simple web-server to provide static deployment and dynamic runtime information as JSON files. - Static deployment configuration is published as JSON under / - Runtime part supports fetching DSO information from Scan and publishes it under /runtime/dso.json Signed-off-by: Stanislav German-Evtushenko <[email protected]>
giner
force-pushed
the
stas/cluster_helm_add_info
branch
from
1d1cf68 to
f90ad05
Compare
| sleep "$((period - (end_time - start_time)))"; | ||
|
|
||
| if [ "$exit_code" -ne 0 ]; then | ||
| exit $exit_code; |
There was a problem hiding this comment.
This exit makes the updater container restart if update fails (which makes the problem easily visible) while the main container keep serving the latest successfully fetched data
This helm charts runs a simple web-server to provide static deployment and dynamic runtime information as JSON files.