Webmail 27.1-rc.11 (now in inbuxa-charts release/suite.yaml, charts #43) drains its connections before it stops (K-W5), so an upgrade under open tabs should lose no request. Until now gitops-test.sh only reported failed requests, since rc.10 lost one to three on a restart.
Tracker: inbuxa-charts#14
Webmail 27.1-rc.11 (now in inbuxa-charts release/suite.yaml, charts #43) drains its connections before it stops (K-W5), so an upgrade under open tabs should lose no request. Until now gitops-test.sh only reported failed requests, since rc.10 lost one to three on a restart.
Tracker: inbuxa-charts#14
Webmail 27.1-rc.11 drains its connections before it stops (K-W5), so an
upgrade under open tabs should lose no request at all. Until now the test
only reported failed requests, because rc.10 lost one to three on a
restart.
The setup pod's port-forward started as soon as the bootstrap pod's was
killed, on the same port. When the old one hadn't let go of 18080 yet, the
new one exited and nothing answered for 60 s, though the pod was up: the
crossing failed that way under Argo CD on amd64. stop_forward now waits for
the port-forward to exit, and forward() starts it again if it has.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Webmail 27.1-rc.11 (now in inbuxa-charts release/suite.yaml, charts #43) drains its connections before it stops (K-W5), so an upgrade under open tabs should lose no request. Until now gitops-test.sh only reported failed requests, since rc.10 lost one to three on a restart.
Tracker: inbuxa-charts#14