KEDA with Calico CNI: Working without hostNetwork:true?

[rashid-gh]

Hi everyone,

I'm running KEDA v2.16.0 on an EKS cluster with Calico as the CNI provider, and I'm encountering the following error:

failing or missing response from https://10.131.47.93:6443/apis/external.metrics.k8s.io/v1beta1: Get "https://10.131.47.93:6443/apis/external.metrics.k8s.io/v1beta1": Address is not allowed

According to the KEDA troubleshooting documentation (https://keda.sh/troubleshooting/keda-external-metrics-issue), one solution is to set hostNetwork: true in the metrics-apiserver deployment. However, our cluster enforces Pod Security Policies that prohibit using hostNetwork.

My question:
Does KEDA support Calico CNI without requiring hostNetwork: true? If so, what's the recommended configuration to make the metrics-apiserver accessible to the Kubernetes API server?

I've tried:

• Creating NetworkPolicies to allow traffic

But I'm still getting the "Address is not allowed" error.

Has anyone successfully run KEDA with Calico without using hostNetwork? Any configuration examples or workarounds would be greatly appreciated.

[LionHuntDiG]

If your using Calico CNI on EKS,
you have to make hostNetwork: true for metrics apiserver,
and also dnspolicy policy should be ClusterFirstWithHostNet
and make sure to open SG Rules for 6443