Open Arnold1 opened 4 years ago
I had the same problem, but with apiservice connecting to port 8443 (default service.internalPort) at pod, fixed with creating a firewall rule to allow master to connect via port 8443 (on private cluster, only traffic via 443/10250 is allowed by default, ref https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters#add_firewall_rules).
There was a similar issue https://github.com/banzaicloud/banzai-charts/issues/1060, where enabling host network solved the problem, which is available in version 0.1.3. @Arnold1 is this problem still occurring? In case it still occurs, could you pease describe k8s version , cloud provider, network plugin?
Describe the bug
hi, I have some issue with kube-metrics-adapter and FailedDiscoveryCheck. how to fix it?
Steps to reproduce the issue:
Expected behavior
no error
Screenshots
no
Additional context