What content on scaleway.com/en/docs is affected?
tutorials/deploying-hubble-add-on-scaleway-kubernetes-clusters/index.mdx
What part(s) of the content would you like to see updated?
I try to deploy the helm chart with default value for scaleway-cilium-hubble. After the deployement of the hubble resources (deployment, config-map, ...), and before performing a roll-out restart of cilium agent, i get an error. The pod hubble-relay is in crash loop-back because the startup probe failed. The pod report a connection refused error:
time="2026-04-23T09:29:44.562563869Z" level=info msg="Failed to create peer notify client for peers change notification; will try again after the timeout has expired" connection timeout=30s error="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp 10.32.15.118:443: connect: connection refused\"" subsys=hubble-relay
Due to the fact that cilium.agent is set to false, the cilium config maps is not modify. The currently deployed config map cilium-config in the kube-system namespace, still shows:
enable-hubble: "false"
And this could cause the connection error.
So, I think there is something missing in the doc.
If the pod error is normal, then it should be mentionned after the helm update command.
Additional context
No response
Related PR(s)
No response
What content on scaleway.com/en/docs is affected?
tutorials/deploying-hubble-add-on-scaleway-kubernetes-clusters/index.mdx
What part(s) of the content would you like to see updated?
I try to deploy the helm chart with default value for scaleway-cilium-hubble. After the deployement of the hubble resources (deployment, config-map, ...), and before performing a roll-out restart of cilium agent, i get an error. The pod hubble-relay is in crash loop-back because the startup probe failed. The pod report a connection refused error:
time="2026-04-23T09:29:44.562563869Z" level=info msg="Failed to create peer notify client for peers change notification; will try again after the timeout has expired" connection timeout=30s error="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp 10.32.15.118:443: connect: connection refused\"" subsys=hubble-relayDue to the fact that
cilium.agentis set to false, the cilium config maps is not modify. The currently deployed config mapcilium-configin the kube-system namespace, still shows:enable-hubble: "false"And this could cause the connection error.
So, I think there is something missing in the doc.
If the pod error is normal, then it should be mentionned after the helm update command.
Additional context
No response
Related PR(s)
No response