Jean-Philippe Evrard a02ae67559 Accelerate CI jobs ...

Without this, some CI jobs are flaky or slow due to the following
issues:
- Triggering a reboot cause an unrecoverable boot loop.
  This fixes it by restarting the containers that are incorrectly
  exited.
- API server is down while operations happen.
  This fixes it by ensuring at least one API server is up. In this
  case, we don't add a reboot marker on the unique api server.
- The amount of nodes in a test environment is larger than
  necessary.
  This fixes it by ensuring two nodes are required to reboot.
  This is enough for concurrency, and for the e2e testing.
- The wait time between operations is high, and can cause
  a heartbeat to be missed in the check script.
  This fixes it by checking more often, at the expense of
  more logging. This is compensated by increasing the amount
  of tries.

Signed-off-by: Jean-Philippe Evrard <open-source@a.spamming.party>

2024-10-02 23:30:41 +02:00

..

create-reboot-sentinels.sh

Accelerate CI jobs

2024-10-02 23:30:41 +02:00

follow-coordinated-reboot.sh

Accelerate CI jobs

2024-10-02 23:30:41 +02:00

test-metrics.sh

Add prometheus export metrics functional testing

2021-04-13 16:17:42 +02:00