Skip to content

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

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

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

Triggered via pull request May 22, 2026 21:16
Status Success
Total duration 6m 46s
Artifacts 3

e2e.yaml

on: pull_request
detect_changes  /  changes
12s
detect_changes / changes
Download the latest vCluster cli
7s
Download the latest vCluster cli
get-testsuites-dir
9s
get-testsuites-dir
Install and delete virtual cluster
2m 13s
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:fdb501d6c46c77c0c870988e58bf02873e1f26431c2292e216c9f145684f8271
vcluster-current Expired
26.8 MB
sha256:4031f79067a9897d2a17cd291010dae11cd7d505831fd74c44a848e0be7ebc4a
vcluster_syncer Expired
36.9 MB
sha256:1d75c326fad76cf5a94132fc05e946e9eaabb6da2e400c34175ce372094fb6c6