Skip to content

MK8S-197 - Add PrometheusAuthProvider #4844

MK8S-197 - Add PrometheusAuthProvider

MK8S-197 - Add PrometheusAuthProvider #4844

Triggered via push March 18, 2026 16:42
Status Cancelled
Total duration 25m 14s
Artifacts 2

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
2m 28s
build_integration_container_nginx
unit_tests_ui
1m 40s
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
17s
build / build-devcontainer / build-and-publish-devcontainer
build-docs  /  ...  /  build-and-publish-devcontainer
build-docs / build-devcontainer / build-and-publish-devcontainer
build  /  ...  /  shell-ui
1m 4s
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
2m 1s
unit_tests_salt
unit_tests_lib_alert_tree
0s
unit_tests_lib_alert_tree
integration_tests_ui
5m 7s
integration_tests_ui
build  /  ...  /  build-and-publish-devcontainer
30s
build / build-docs / build-devcontainer / build-and-publish-devcontainer
build-docs  /  docs
build-docs / docs
build  /  ...  /  docs
2m 6s
build / build-docs / docs
build  /  write-final-status
17s
build / write-final-status
e2e-tests  /  ...  /  multi-node
0s
e2e-tests / multi-node-e2e / multi-node
e2e-tests  /  ...  /  single-node
1m 31s
e2e-tests / single-node-e2e / single-node
e2e-tests  /  ...  /  destroy-multi-node-cluster
34s
e2e-tests / multi-node-e2e / destroy-multi-node-cluster
e2e-tests  /  ...  /  destroy-single-node-cluster
38s
e2e-tests / single-node-e2e / destroy-single-node-cluster
write-final-status
11s
write-final-status
Fit to window
Zoom out
Zoom in

Annotations

8 errors, 13 warnings, and 7 notices
e2e-tests / single-node-e2e / single-node
Canceling since a higher priority waiting request for tests-feature/MK8S-197-UI-update-to-include-auth-token-true exists
e2e-tests / multi-node-e2e / multi-node
Canceling since a higher priority waiting request for tests-feature/MK8S-197-UI-update-to-include-auth-token-true exists
e2e-tests / single-node-e2e / destroy-single-node-cluster
Process completed with exit code 22.
e2e-tests / multi-node-e2e / destroy-multi-node-cluster
Process completed with exit code 22.
Pre merge
Canceling since a higher priority waiting request for tests-feature/MK8S-197-UI-update-to-include-auth-token-true exists
Pre merge
Canceling since a higher priority waiting request for tests-feature/MK8S-197-UI-update-to-include-auth-token-true exists
Pre merge
Canceling since a higher priority waiting request for tests-feature/MK8S-197-UI-update-to-include-auth-token-true exists
Pre merge
Canceling since a higher priority waiting request for tests-feature/MK8S-197-UI-update-to-include-auth-token-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-docs / 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, 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/
unit_tests_ui
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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_integration_container_nginx
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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-docs / docs
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/
integration_tests_ui
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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 / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v2, 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
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/
e2e-tests / single-node-e2e / destroy-single-node-cluster
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3, hashicorp/setup-terraform@v2, 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/
e2e-tests / multi-node-e2e / destroy-multi-node-cluster
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3, hashicorp/setup-terraform@v2, 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 / build-shell-ui / shell-ui
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-bed75df66f.Pre-merge.4844
unit_tests_ui
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-bed75df66f.Pre-merge.4844
build / build-docs / docs
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-bed75df66f.Pre-merge.4844
integration_tests_ui
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-bed75df66f.Pre-merge.4844
build / build
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-bed75df66f.Pre-merge.4844
build / write-final-status
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-bed75df66f.Pre-merge.4844
write-final-status
Your artifacts has been uploaded here: https://artifacts.scality.net/builds/github:scality:metalk8s:staging-bed75df66f.Pre-merge.4844

Artifacts

Produced during runtime
Name Size Digest
scality~metalk8s~UA3EBO.dockerbuild
37.3 KB
sha256:56f337ded1659b892765532533cc18f56af6380c66ef8288338a75575cc7e91d
scality~metalk8s~X32AEX.dockerbuild
45.2 KB
sha256:c1cfbdaf0857207b755c5d106303905eb606134d04e68327613813a34818375d