Skip to content

Always use dedicated service account in device-plugin helm chart #659

Always use dedicated service account in device-plugin helm chart

Always use dedicated service account in device-plugin helm chart #659

Triggered via push May 22, 2026 20:06
Status Success
Total duration 24m 52s
Artifacts

ci.yaml

on: push
basic  /  ...  /  variables
7s
basic / variables / variables
basic  /  ...  /  check
2m 24s
basic / golang / check
basic  /  ...  /  Unit test
1m 45s
basic / golang / Unit test
basic  /  ...  /  Build
1m 20s
basic / golang / Build
basic  /  ...  /  Test
1m 16s
basic / helm / Test
basic  /  ...  /  Analyze Go code with CodeQL
2m 46s
basic / code-scanning / Analyze Go code with CodeQL
Matrix: image / build
image  /  create-manifest
10s
image / create-manifest
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
basic / golang / Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
image / build (arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
image / build (amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog/setup-jfrog-cli@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
e2e-test / e2e-tests
No files were found with the provided path: ginkgo.json. No artifacts will be uploaded.