Open
Description
Hello,
I have the same setup running in multiple clusters.
HelmRepository pointing to private registry
When updating from 1.4.0 to 1.5.0 the HelmRepository in one of our clusters was not able to become ready.
When switching back to 1.4.0 it became ready and could be used.
The log in debug mode showed the following
{
"level": "debug",
"ts": "2025-03-21T12:36:18.846Z",
"logger": "events",
"msg": "failed to fetch Helm repository index: failed to cache index to temporary file: Get \"https://<redacted>/index.yaml\": net/http: TLS handshake timeout",
"type": "Warning",
"object": {
"kind": "HelmRepository",
"namespace": "k6-system",
"name": "nexus",
"uid": "<redacted>",
"apiVersion": "source.toolkit.fluxcd.io/v1",
"resourceVersion": "<redacted>"
},
"reason": "Failed"
}
{
"level": "error",
"ts": "2025-03-21T12:36:18.861Z",
"msg": "Reconciler error",
"controller": "helmrepository",
"controllerGroup": "source.toolkit.fluxcd.io",
"controllerKind": "HelmRepository",
"HelmRepository": {
"name": "nexus",
"namespace": "k6-system"
},
"namespace": "k6-system",
"name": "nexus",
"reconcileID": "<redacted>",
"error": "failed to fetch Helm repository index: failed to cache index to temporary file: Get \"https://<redacted>/index.yaml\": net/http: TLS handshake timeout",
"stacktrace": "sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler\n\tsigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:341\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem\n\tsigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:288\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.2\n\tsigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:249"
}
As mentioned, it works in other clusters, it works when switching back to 1.4.0.
Please let me know if you need anything more
Metadata
Metadata
Assignees
Labels
No labels