Skip to content

feat(pods): add sync.toHost.pods.dns.nameservers #8024

feat(pods): add sync.toHost.pods.dns.nameservers

feat(pods): add sync.toHost.pods.dns.nameservers #8024

Triggered via pull request May 22, 2026 14:00
Status Success
Total duration 6m 49s
Artifacts 3

e2e.yaml

on: pull_request
detect_changes  /  changes
16s
detect_changes / changes
Download the latest vCluster cli
9s
Download the latest vCluster cli
get-testsuites-dir
17s
get-testsuites-dir
Install and delete virtual cluster
2m 26s
Install and delete virtual cluster
Matrix: test if we can upgrade from older version
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: goreleaser/goreleaser-action@v6. 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/
build
You are using 'latest' as default version. Will lock to '~> v2'.
Install and delete virtual cluster
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@v4, loft-sh/setup-vind@v1. 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/
test if we can upgrade from older version (k8s)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@v4, loft-sh/setup-vind@v1. 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/

Artifacts

Produced during runtime
Name Size Digest
vcluster Expired
27.4 MB
sha256:a2ff8d5107f1bce9403721b8e38b807d9bbf7432effcc93b80e12e02580b5c5e
vcluster-current Expired
26.8 MB
sha256:932e750d527450062bc01ed23e6463967cbb6e8ae029d34f5ecbc20513b2baed
vcluster_syncer Expired
36.9 MB
sha256:5be538d9a3f0d707a3b62f375cb8cc1222e7c37bb359c1c8d731de624dd6131f