The kubernetes API timeout value is too short.

[mimuret]

What happend:
After updating multus to v4.2.2, creating a Pod resulted in a timeout when accessing the GetPod API in the k8s API.

[error] Multus: [monitoring-system/alloy-9pktd/2cff1f1d-983b-4455-9afc-06df7ab68088]: error waiting for pod: Get "https://MASK:6443/api/v1/namespaces/monitoring-system/pods/alloy-9pktd?timeout=1m0s%22: context deadline exceeded
[debug] GetPod for [monitoring-system/alloy-9pktd] took 500.936629m

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Our cluster has nodes distributed worldwide, so the hard-coded timeout value is too short.
On our network, processing a request from London to Tokyo takes about 700 ms.

Environment:

• Multus version 4.2.2
  image path and image ID (from 'docker images')
• Kubernetes version (use kubectl version): 1.33
• Primary CNI for Kubernetes cluster:
• OS (e.g. from /etc/os-release):
• File of '/etc/cni/net.d/'
• File of '/etc/cni/multus/net.d'
• NetworkAttachment info (use kubectl get net-attach-def -o yaml)
• Target pod yaml info (with annotation, use kubectl get pod <podname> -o yaml)
• Other log outputs (if you use multus logging)