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
* ci(mlflow): speed up k3s CI jobs
- Use 1-node k3s clusters instead of 3-node; GKE keeps 3 nodes
- Remove invalid skip-preflights and debug inputs from kots-install action
- Replace 5-minute service poll loop with kubectl wait --for=condition=Available
* ci(mlflow): apply Copilot review suggestions
- Poll for deployment existence before kubectl wait (avoids immediate
failure if KOTS hasn't created the Deployment yet)
- Add || true to kubectl diagnostics in error handler (prevents bash -e
from swallowing the original error when describe returns non-zero)
- Fail port-forward step explicitly if MLflow never becomes reachable,
with pod logs and port-forward log printed before exiting non-zero
* ci(mlflow): fix KOTS port-forward race and reduce postgres instances
kubectl wait --for=condition=Available returns immediately for a
Deployment with maxUnavailable=1 and replicas=1 because 0 ready pods
satisfies the condition (0 >= 1-1). The pod was still Init:0/2 when
port-forward ran.
Replace with kubectl rollout status which correctly waits until all
desired replicas are Running and Ready, with a 10m timeout to cover
the CNPG bootstrap + pip init containers.
Also set postgres.embedded.instances=1 in the CI test values; the
default 3-instance cluster is unnecessary for smoke testing and adds
significant startup latency on single-node k3s clusters.
* ci(mlflow): increase port-forward readiness poll to cover DB migrations
MLflow runs alembic DB migrations on first start before binding to
port 5000. With no readiness probe, kubectl rollout status completes
as soon as the container process starts, not when the server is
actually listening. The 30s curl loop (10x3s) was too short to cover
the full migration sequence on GKE.
Increase to 10s initial wait + 30 attempts x 5s = up to 160s total,
which comfortably covers the migration runtime.
0 commit comments