Skip to content

feat: global registry support #150

feat: global registry support

feat: global registry support #150

Triggered via pull request April 23, 2026 07:43
Status Cancelled
Total duration 9m 11s
Artifacts 6
Matrix: k8s-e2e-tests-extended / k8s-e2e-tests
k8s-e2e-tests-extended  /  K8s e2e tests
4s
k8s-e2e-tests-extended / K8s e2e tests
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 18 warnings
k8s-e2e-tests-extended / K8s e2e tests apm
Canceling since a higher priority waiting request for test-extended-paths-k8s-feat/global-registry-support exists
k8s-e2e-tests-extended / K8s e2e tests apm
The operation was canceled.
k8s-e2e-tests-extended / K8s e2e tests collector
Canceling since a higher priority waiting request for test-extended-paths-k8s-feat/global-registry-support exists
k8s-e2e-tests-extended / K8s e2e tests collector
The operation was canceled.
k8s-e2e-tests-extended / K8s e2e tests custom-repo
Canceling since a higher priority waiting request for test-extended-paths-k8s-feat/global-registry-support exists
k8s-e2e-tests-extended / K8s e2e tests custom-repo
The operation was canceled.
k8s-e2e-tests-extended / K8s e2e tests dynamic
Canceling since a higher priority waiting request for test-extended-paths-k8s-feat/global-registry-support exists
k8s-e2e-tests-extended / K8s e2e tests dynamic
The operation was canceled.
k8s-e2e-tests-extended / K8s e2e tests proxy
Canceling since a higher priority waiting request for test-extended-paths-k8s-feat/global-registry-support exists
k8s-e2e-tests-extended / K8s e2e tests proxy
The operation was canceled.
k8s-e2e-tests-extended / K8s e2e tests fleet-control
Canceling since a higher priority waiting request for test-extended-paths-k8s-feat/global-registry-support exists
k8s-e2e-tests-extended / K8s e2e tests fleet-control
The operation was canceled.
k8s-e2e-tests-extended / K8s e2e tests
Process completed with exit code 1.
test-extended-paths-k8s
Canceling since a higher priority waiting request for test-extended-paths-k8s-feat/global-registry-support exists
test-extended-paths-k8s
Canceling since a higher priority waiting request for test-extended-paths-k8s-feat/global-registry-support exists
k8s-e2e-tests-extended / K8s e2e tests apm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@96202dee4ae1c2f46a62fe197273aaf22b83f42d, mlugg/setup-zig@d1434d08867e3ee9daa34448df10607b98908d29. 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/
k8s-e2e-tests-extended / K8s e2e tests apm
Adding --force flag to minikube start because Kubernetes version v1.30.14 is not in Minikube's default supported list
k8s-e2e-tests-extended / K8s e2e tests apm
Kubernetes version v1.30.14 is not in Minikube's supported list
k8s-e2e-tests-extended / K8s e2e tests collector
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@96202dee4ae1c2f46a62fe197273aaf22b83f42d, mlugg/setup-zig@d1434d08867e3ee9daa34448df10607b98908d29. 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/
k8s-e2e-tests-extended / K8s e2e tests collector
Adding --force flag to minikube start because Kubernetes version v1.30.14 is not in Minikube's default supported list
k8s-e2e-tests-extended / K8s e2e tests collector
Kubernetes version v1.30.14 is not in Minikube's supported list
k8s-e2e-tests-extended / K8s e2e tests custom-repo
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@96202dee4ae1c2f46a62fe197273aaf22b83f42d, mlugg/setup-zig@d1434d08867e3ee9daa34448df10607b98908d29. 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/
k8s-e2e-tests-extended / K8s e2e tests custom-repo
Adding --force flag to minikube start because Kubernetes version v1.30.14 is not in Minikube's default supported list
k8s-e2e-tests-extended / K8s e2e tests custom-repo
Kubernetes version v1.30.14 is not in Minikube's supported list
k8s-e2e-tests-extended / K8s e2e tests dynamic
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@96202dee4ae1c2f46a62fe197273aaf22b83f42d, mlugg/setup-zig@d1434d08867e3ee9daa34448df10607b98908d29. 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/
k8s-e2e-tests-extended / K8s e2e tests dynamic
Adding --force flag to minikube start because Kubernetes version v1.30.14 is not in Minikube's default supported list
k8s-e2e-tests-extended / K8s e2e tests dynamic
Kubernetes version v1.30.14 is not in Minikube's supported list
k8s-e2e-tests-extended / K8s e2e tests proxy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@96202dee4ae1c2f46a62fe197273aaf22b83f42d, mlugg/setup-zig@d1434d08867e3ee9daa34448df10607b98908d29. 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/
k8s-e2e-tests-extended / K8s e2e tests proxy
Adding --force flag to minikube start because Kubernetes version v1.30.14 is not in Minikube's default supported list
k8s-e2e-tests-extended / K8s e2e tests proxy
Kubernetes version v1.30.14 is not in Minikube's supported list
k8s-e2e-tests-extended / K8s e2e tests fleet-control
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: manusa/actions-setup-minikube@96202dee4ae1c2f46a62fe197273aaf22b83f42d, mlugg/setup-zig@d1434d08867e3ee9daa34448df10607b98908d29. 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/
k8s-e2e-tests-extended / K8s e2e tests fleet-control
Adding --force flag to minikube start because Kubernetes version v1.30.14 is not in Minikube's default supported list
k8s-e2e-tests-extended / K8s e2e tests fleet-control
Kubernetes version v1.30.14 is not in Minikube's supported list

Artifacts

Produced during runtime
Name Size Digest
e2e-result-k8s-apm
240 Bytes
sha256:1c0260000907dd4b7985b13edadcb3585984f06dd45ce70aea1f038e8842bb6e
e2e-result-k8s-collector
258 Bytes
sha256:785ff7d4f7faeae847e341320d25bd395c4b4c6cd420c2c61e13a0c458783f11
e2e-result-k8s-custom-repo
264 Bytes
sha256:565a02e8455ec3b8f389306d744d9c9b6fcfed553fba304b6f6c6c35d4d71c0a
e2e-result-k8s-dynamic
252 Bytes
sha256:a91626c8fef946c30cbb71f11945ad4854aa9aaf6bb32ab5fc4619aca8d57673
e2e-result-k8s-fleet-control
266 Bytes
sha256:4a1272690ab5ba97578eba6339645f704854e307dace1687d3e7373ee3223d61
e2e-result-k8s-proxy
246 Bytes
sha256:a5986644e413d84bfc38c120dba973b3697d6f9d9d2ca16a915986bd607bdf55