Skip to content

charts,salt: Bump prometheus-adapter chart to 5.3.0 #4811

charts,salt: Bump prometheus-adapter chart to 5.3.0

charts,salt: Bump prometheus-adapter chart to 5.3.0 #4811

Triggered via push March 17, 2026 15:03
Status Cancelled
Total duration 2m 2s
Artifacts 1

pre-merge.yaml

on: push
changed-files
11s
changed-files
build-devcontainer  /  build-and-publish-devcontainer
22s
build-devcontainer / build-and-publish-devcontainer
build_integration_container_nginx
0s
build_integration_container_nginx
unit_tests_ui
0s
unit_tests_ui
unit_tests_shell_ui
0s
unit_tests_shell_ui
unit_tests_crd_client_generator
0s
unit_tests_crd_client_generator
build-shell-ui  /  shell-ui
build-shell-ui / shell-ui
build  /  ...  /  build-and-publish-devcontainer
14s
build / build-devcontainer / build-and-publish-devcontainer
build-docs  /  ...  /  build-and-publish-devcontainer
build-docs / build-devcontainer / build-and-publish-devcontainer
build  /  ...  /  shell-ui
57s
build / build-shell-ui / shell-ui
unit_tests_metalk8s_operator
0s
unit_tests_metalk8s_operator
unit_tests_storage_operator
0s
unit_tests_storage_operator
unit_tests_salt
23s
unit_tests_salt
unit_tests_lib_alert_tree
0s
unit_tests_lib_alert_tree
integration_tests_ui
0s
integration_tests_ui
build  /  ...  /  build-and-publish-devcontainer
6s
build / build-docs / build-devcontainer / build-and-publish-devcontainer
build-docs  /  docs
build-docs / docs
build  /  ...  /  docs
build / build-docs / docs
build  /  write-final-status
9s
build / write-final-status
e2e-tests  /  ...  /  multi-node
e2e-tests / multi-node-e2e / multi-node
e2e-tests  /  ...  /  single-node
e2e-tests / single-node-e2e / single-node
e2e-tests  /  ...  /  destroy-multi-node-cluster
e2e-tests / multi-node-e2e / destroy-multi-node-cluster
e2e-tests  /  ...  /  destroy-single-node-cluster
e2e-tests / single-node-e2e / destroy-single-node-cluster
write-final-status
13s
write-final-status
Fit to window
Zoom out
Zoom in

Annotations

13 errors, 5 warnings, and 2 notices
build / build
Canceling since a higher priority waiting request for tests-improvement/bump-prometheus-adapter-5.3.0-true exists
unit_tests_salt
Canceling since a higher priority waiting request for tests-improvement/bump-prometheus-adapter-5.3.0-true exists
unit_tests_salt
The operation was canceled.
lint
Canceling since a higher priority waiting request for tests-improvement/bump-prometheus-adapter-5.3.0-true exists
lint
The operation was canceled.
build / build-docs / build-devcontainer / build-and-publish-devcontainer
Canceling since a higher priority waiting request for tests-improvement/bump-prometheus-adapter-5.3.0-true exists
build / build-shell-ui / shell-ui
Canceling since a higher priority waiting request for tests-improvement/bump-prometheus-adapter-5.3.0-true exists
build / build-shell-ui / shell-ui
The operation was canceled.
Pre merge
Canceling since a higher priority waiting request for tests-improvement/bump-prometheus-adapter-5.3.0-true exists
Pre merge
Canceling since a higher priority waiting request for tests-improvement/bump-prometheus-adapter-5.3.0-true exists
Pre merge
Canceling since a higher priority waiting request for tests-improvement/bump-prometheus-adapter-5.3.0-true exists
Pre merge
Canceling since a higher priority waiting request for tests-improvement/bump-prometheus-adapter-5.3.0-true exists
Pre merge
Canceling since a higher priority waiting request for tests-improvement/bump-prometheus-adapter-5.3.0-true exists
build-devcontainer / build-and-publish-devcontainer
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build / build-devcontainer / build-and-publish-devcontainer
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build / build-shell-ui / shell-ui
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build / write-final-status
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: scality/action-artifacts@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
write-final-status
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: scality/action-artifacts@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build / write-final-status
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-67915839a8.Pre-merge.4811
write-final-status
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-67915839a8.Pre-merge.4811

Artifacts

Produced during runtime
Name Size Digest
scality~metalk8s~XTDP86.dockerbuild
44.3 KB
sha256:9648d858dc941a562b82fe34e9830569721da26266412b51ebac7bbbf38cbcda