fix: use explicit k3d API port to avoid connection refused in CI
--api-port 0 means no host mapping, breaking kubectl wait. Use port 16443 for k3d API host access during cluster setup. Made-with: Cursor
This commit is contained in:
parent
9450101a68
commit
75250b47ee
2 changed files with 2 additions and 2 deletions
2
.github/workflows/pr-test.yml
vendored
2
.github/workflows/pr-test.yml
vendored
|
|
@ -1662,7 +1662,7 @@ jobs:
|
|||
|
||||
- name: Create k3d cluster
|
||||
run: |
|
||||
k3d cluster create tai-test --no-lb --wait --api-port 0
|
||||
k3d cluster create tai-test --no-lb --wait --api-port 16443
|
||||
kubectl wait --for=condition=Ready node --all --timeout=60s
|
||||
k3d image import alpine:latest -c tai-test
|
||||
|
||||
|
|
|
|||
2
.github/workflows/unit-test.yml
vendored
2
.github/workflows/unit-test.yml
vendored
|
|
@ -1216,7 +1216,7 @@ jobs:
|
|||
|
||||
- name: Create k3d cluster
|
||||
run: |
|
||||
k3d cluster create tai-test --no-lb --wait --api-port 0
|
||||
k3d cluster create tai-test --no-lb --wait --api-port 16443
|
||||
kubectl wait --for=condition=Ready node --all --timeout=60s
|
||||
k3d image import alpine:latest -c tai-test
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue