# The default 300s is not enough here, and the three parts that fill the budget
# are worth naming so the number can be lowered again if one of them changes:
#
#   1. TWO INIT CONTAINERS PER POD. The build one runs a full Quarkus
#      augmentation - upstream's own issue reports measure "Quarkus
#      augmentation completed in" at roughly 13-23 seconds, and a CI runner is
#      not a fast machine.
#   2. THE FIRST START CREATES THE WHOLE SCHEMA through Liquibase, and with two
#      replicas the second pod waits on the first's migration lock. So the two
#      pods do not become Ready in parallel.
#   3. The rollout is only complete when BOTH pods are Ready, which is
#      deliberate (it is what makes cluster formation part of the assertion)
#      and which means the slow parts add up rather than overlap.
#
# The chart's own startupProbe budget is 600s (10s x 60); this timeout has to
# be at least that, or the test gives up before the probe would have.
INSTALL_TIMEOUT=900