Skip to content

merge queue: embarking main (24980cb) and #900 together#905

Closed
mergify[bot] wants to merge 6 commits intomainfrom
mergify/merge-queue/edb7660df7
Closed

merge queue: embarking main (24980cb) and #900 together#905
mergify[bot] wants to merge 6 commits intomainfrom
mergify/merge-queue/edb7660df7

Conversation

@mergify
Copy link

@mergify mergify bot commented Mar 12, 2026

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (24980cb) and #900 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #900.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: 24980cb241a0ddea2a8c786c4b423c5e92309c56
previous_failed_batches: []
pull_requests:
  - number: 900
...

ktdreyer and others added 6 commits March 12, 2026 15:05
Kind is the recommended local development tool and matches CI.
CRC remains available for OpenShift-specific testing.

The CI workflow now uses kind instead of minikube. The Makefile
"local-up", "local-down", "local-clean", and "local-rebuild"
targets are now aliases for their kind equivalents, so existing
muscle memory still works.

Fixes #898

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Kind requires cluster names to match "^[a-z0-9.-]+$". In CI,
"git rev-parse --abbrev-ref HEAD" returns "HEAD" (detached),
producing "ambient-HEAD" which kind rejects.

Pipe through "tr A-Z a-z" before sanitizing so the slug is
always lowercase.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The "kubectl wait --for=condition=ready" step already validates
the backend pod's readiness probe (which hits /health). The
explicit "wget" check fails in ubi-minimal containers that lack
wget, and is redundant with the readiness gate.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The comprehensive test script assumed minikube-specific behavior
(DISABLE_AUTH, local-dev-user, ingress-nginx, local-reload-*
targets). Update all tests to match the kind overlay setup:

- Check pod readiness instead of curling via minikube IP
- Accept missing ingress-nginx (kind uses NodePort mapping)
- Check for NAMESPACE/PORT/BACKEND_URL env vars instead of
  DISABLE_AUTH
- Validate test-user SA instead of local-dev-user
- Test kind-rebuild instead of removed local-reload-* targets
- Pass CONTAINER_ENGINE to make local-status in CI

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Bump KIND_VERSION from v0.27.0 to v0.31.0 so the CI workflow
matches the "kindest/node:v1.35.0" image used in setup-kind.sh.
Node images are only officially supported with the kind version
they shipped with.

Rename the "MK" Mermaid node identifier to "KIND" in the
deployment-stack diagram, since the node now represents Kind
rather than Minikube.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@mergify mergify bot closed this Mar 12, 2026
@mergify mergify bot deleted the mergify/merge-queue/edb7660df7 branch March 12, 2026 21:00
@mergify mergify bot mentioned this pull request Mar 12, 2026
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant