Repository navigation
docs(deploy): add sandbox deploy runbook and recreate-relay script - #768
Conversation
🦋 Changeset detectedLatest commit: e781c91 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
da7ac54 to
df40b32
Compare
Document post-image update steps for single-relay and HAProxy stacks; link deploy README to the runbook without duplicating health/HAProxy setup.
df40b32 to
4baf9b9
Compare
|
Capture the running relay image before deploy, document script install path, use compose exit-code-from for migrate, and add SKIP_MIGRATE for rollback.
| cp "$REPO/deploy/docker-compose.haproxy.yml" "$REPO/deploy/rolling-relay-recreate.sh" /opt/nostream/ | ||
| cp -r "$REPO/deploy/haproxy" /opt/nostream/ | ||
| chmod +x /opt/nostream/rolling-relay-recreate.sh |
There was a problem hiding this comment.
The refresh commands copy the new haproxy.cfg, but nothing reloads or recreates haproxy. The later commands replace only the relay backends. If a release changes proxy settings, operators following this runbook keep serving traffic with the old settings.
Add a config check and an explicit reload or recreate step, noting any downtime.
Description
Document the manual post-pull migrate and recreate flow, rollback steps, and /readyz verification. Closes the gap where the webhook pull stack loads images but does not restart the relay.
Related Issue
closes:- #767
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: