feat: automatically enable Cilium kube-proxy replacement feature #4565
GitHub Actions / e2e test report
failed
Sep 4, 2025 in 0s
18 tests run, 6 passed, 10 skipped, 2 failed.
Annotations
Check failure on line 1 in caren-e2e
github-actions / e2e test report
caren-e2e.[It] Self-hosted Docker Cilium ClusterResourceSet topology-cilium-crs Should pivot the bootstrap cluster to a self-hosted cluster [Serial, provider:Docker, cni:Cilium, addonStrategy:ClusterResourceSet]
Timed out after 600.000s.
{
"metadata": {
"creationTimestamp": null
},
"spec": {
"version": "",
"machineTemplate": {
"metadata": {},
"infrastructureRef": {}
},
"kubeadmConfigSpec": {}
},
"status": {
"replicas": 0,
"updatedReplicas": 0,
"readyReplicas": 0,
"unavailableReplicas": 0,
"initialized": false,
"ready": false
}
}
Expected
<bool>: false
to be true
Raw output
[FAILED] Timed out after 600.000s.
{
"metadata": {
"creationTimestamp": null
},
"spec": {
"version": "",
"machineTemplate": {
"metadata": {},
"infrastructureRef": {}
},
"kubeadmConfigSpec": {}
},
"status": {
"replicas": 0,
"updatedReplicas": 0,
"readyReplicas": 0,
"unavailableReplicas": 0,
"initialized": false,
"ready": false
}
}
Expected
<bool>: false
to be true
In [It] at: /home/runner/go/pkg/mod/sigs.k8s.io/cluster-api/[email protected]/framework/controlplane_helpers.go:193 @ 09/04/25 00:24:17.866
Check failure on line 1 in caren-e2e
github-actions / e2e test report
caren-e2e.[It] Self-hosted Docker Cilium HelmAddon topology-cilium-helm-addon Should pivot the bootstrap cluster to a self-hosted cluster [Serial, provider:Docker, cni:Cilium, addonStrategy:HelmAddon]
failed to run clusterctl init
Unexpected error:
<context.deadlineExceededError>:
context deadline exceeded
{}
occurred
Raw output
[FAILED] failed to run clusterctl init
Unexpected error:
<context.deadlineExceededError>:
context deadline exceeded
{}
occurred
In [It] at: /home/runner/go/pkg/mod/sigs.k8s.io/cluster-api/[email protected]/framework/clusterctl/client.go:90 @ 09/04/25 00:42:38.732
There were additional failures detected after the initial failure. These are visible in the timeline
Loading