Skip to content
Cluster Run (K3d)

operator: adjust state transition rules to ensure 'running' state always accounted for in db #7445

Sign in to view logs

operator: adjust state transition rules to ensure 'running' state always accounted for in db

operator: adjust state transition rules to ensure 'running' state always accounted for in db #7445

Triggered via pull request August 2, 2024 22:28
@ikreymerikreymer
synchronize #1989
running-relax-state-transition
Status Success
Total duration 20m 34s
Artifacts –

k3d-ci.yaml

on: pull_request
btrix-k3d-test
20m 19s
btrix-k3d-test
Fit to window
Zoom out
Zoom in

Annotations

1 warning
btrix-k3d-test
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, docker/setup-buildx-action@v2, docker/build-push-action@v3, azure/setup-kubectl@v3, azure/setup-helm@v3, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/