Skip to content

[PR #756/b07fbd62 backport][stable-5] Fix waiting for daemonset when desired number of pods is 0 #382

[PR #756/b07fbd62 backport][stable-5] Fix waiting for daemonset when desired number of pods is 0

[PR #756/b07fbd62 backport][stable-5] Fix waiting for daemonset when desired number of pods is 0 #382

Triggered via pull request July 10, 2024 14:20
Status Success
Total duration 15m 22s
Artifacts

integration-tests.yaml

on: pull_request
splitter
7s
splitter
Matrix: integration
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
splitter
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration-py3.12-milestone-kubernetes.core-1
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.8.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration-py3.12-milestone-kubernetes.core-1
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, helm/kind-action@v1.8.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/