Cilium: Hubble fails when cilium_cluster_name is customized.

[kolovo]

Environment:

• Cloud provider or hardware configuration:
  Not Relevant

• OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):
  Not Relevant

• Version of Ansible (ansible --version):
  Not Relevant

• Version of Python (python --version):
  Not Relevant

Kubespray version (commit) (git rev-parse --short HEAD):
a1521dc

Network plugin used:
cilium

Full inventory with variables (ansible -i inventory/sample/inventory.ini all -m debug -a "var=hostvars[inventory_hostname]"):
Not Relevant

Command used to invoke ansible:
Not Relevant

Output of ansible run:
Not Relevant

Anything else do we need to know:
When not using the default cluster-name in cilium (cluster.local) hubble fails to start with the following error:
level=warning msg="Failed to create peer client for peers synchronization; will try again after the timeout has expired" error="context deadline exceeded" subsys=hubble-relay target="hubble-peer.kube-system.svc.cluster.local:443"

cilium cluster-name parameter is not set in hubble template(roles/network_plugin/cilium/templates/hubble/config.yml.j2) and therefore fails to start as it is unable to peer the right cluster.
To resolve the issue cluster-name parameter should be added in the template file like below:
cat roles/network_plugin/cilium/templates/hubble/config.yml.j2
apiVersion: v1
kind: ConfigMap
metadata:
name: hubble-relay-config
namespace: kube-system
data:
config.yaml: |
cluster-name: "{{ cilium_cluster_name }}" >> missing parameter
listen-address: :4245
metrics-listen-address: ":9966"
dial-timeout:
...
...

[MrFreezeex]

Hi @kolovo we would be very happy if you could send a PR for this 🙏

[eugene-eeo]

hey @MrFreezeex we're running into this issue on our deployment, so I've made a PR that should fix it: #10614.