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
This would solve one of the important use-cases - a self-updating image through livenessProbe.
With the livenessProbe pointed to query the releases link comparing against the current version would allow it to fail once there is a new image available, causing the pod restart allowing it to self-update. This requires imagePullPolicy: Always set for this specific deployment.
Add client-managed healthchecks (livenessProbe, readinessProbe and their parameters) and setting imagePullPolicy to Always.
potentially but first we need to clean up the local dev env set up (readme on the github repo) for node and provider repos, so that others can get set up (we did this for console before engaging OSS dev community)
This would solve one of the important use-cases - a self-updating image through
livenessProbe
.With the
livenessProbe
pointed to query the releases link comparing against the current version would allow it to fail once there is a new image available, causing the pod restart allowing it to self-update. This requiresimagePullPolicy: Always
set for this specific deployment.Add client-managed healthchecks (
livenessProbe
,readinessProbe
and their parameters) and settingimagePullPolicy
toAlways
.Refs
https://discord.com/channels/747885925232672829/1090670585555730563/1091261402729156608
akash-network/provider#54
#50
https://github.com/arno01/self-update
PoC
The text was updated successfully, but these errors were encountered: