K8s Clustering Leader Receives Context Deadline Error on Target about gnmic HOT 5 CLOSED

This might be a bug, gNMIc is trying to list all leases with a context that already reached its deadline. The 0.1 seconds is an internal retry timer, changing it won't solve this problem.
Can you share which version of gNMI you are running ?

from gnmic.

Seeing this on 0.36.2, This also could be a misconfiguration due to the limited documentation around the k8s locker. We configured the k8s locker based on a comment in karimra/gnmic#560 (comment)

from gnmic.

We are on version 0.36.2

version : 0.36.2
 commit : a7844a6d
   date : 2024-03-05T20:10:26Z
 gitURL : https://github.com/openconfig/gnmic
   docs : https://gnmic.openconfig.net

from gnmic.

The solution was to make sure the ENV variables were configured correctly. These were removed originally because they were not documented or explained in any way.

            - name: GNMIC_CLUSTERING_INSTANCE_NAME
              valueFrom:
                fieldRef:
                  fieldPath: metadata.name
            - name: GNMIC_CLUSTERING_SERVICE_ADDRESS
              value: "$(GNMIC_CLUSTERING_INSTANCE_NAME).gnmic-svc.gnmic.svc.cluster.local"

from gnmic.

The ENV variables follow a naming pattern explained here: https://gnmic.openconfig.net/user_guide/configuration_env/#configuration-file-to-environment-variables-mapping

GNMIC_CLUSTERING_INSTANCE_NAME=XXX and GNMIC_CLUSTERING_SERVICE_ADDRESS=YYY are equivalent to:

clustering:
  instance-name: XXX
  service-address: YYY

from gnmic.