Skip to content
E2E CI

fix controller setting for privatesNodes and virtualscheduler and resourceClaimstatuses translation in pod #6969

Sign in to view logs

fix controller setting for privatesNodes and virtualscheduler and resourceClaimstatuses translation in pod

fix controller setting for privatesNodes and virtualscheduler and resourceClaimstatuses translation in pod #6969

Triggered via pull request February 10, 2026 18:17
@flomedjaflomedja
synchronize #3573
flomedja:ENGTEN-57-Fix-bug-in-resource-claim-template-configuration-in-controller
Status Success
Total duration 24m 39s
Artifacts 3

e2e.yaml

on: pull_request
detect_changes  /  changes
13s
detect_changes / changes
build
2m 4s
build
get-testsuites-dir
11s
get-testsuites-dir
Download the latest vCluster cli
19s
Download the latest vCluster cli
Install and delete virtual cluster
2m 14s
Install and delete virtual cluster
Matrix: Execute test suites
Matrix: test if we can upgrade from older version
Fit to window
Zoom out
Zoom in

Annotations

1 warning
build
You are using 'latest' as default version. Will lock to '~> v2'.

Artifacts

Produced during runtime
Name Size Digest
vcluster Expired
25.9 MB
sha256:33e1378dcfbdf7552239e3d52968e17f0196cb0c1ae757ae8cf3b8594744e08a
vcluster-current Expired
26.4 MB
sha256:fb693605336fd5ef0d44f60ee436b73299b73dc921856e19186bea06788ed1a2
vcluster_syncer Expired
65.1 MB
sha256:75050d83bcb7cf1cbe73984007635fcdf8750a4c6a927439e64469e9db58e5a2