Miles Monteleone
Miles Monteleone
EDIT: Discovered the `ignore_migration_failures` config value, which let us proceed with our upgrade. Has there been any movement on this? We're facing a similar issue while upgrading 4.2.x -> 4.3.x....
Default containerPort is wrong in the latest release - https://github.com/kubernetes-sigs/metrics-server/issues/1236. Try overriding that to `10250`.
Are you using any CNI plugin (calico, weave, vpc-cni, etc.)? If so, setting `hostnetwork: true` in your deployment might help.
@MahiraTechnology Let me know how it goes - we're on EKS and noticed in newer versions of the vpc-cni plugin, there was a communication breakdown somewhere between the pod VPC...
you probably have to change the port to something else, 10250 will clash with the kubelet API port. try setting `containerPort: 4443`
check your security group and firewall rules. ensure tcp 10250 is open between nodes
that could mean one of many things. try running through this article: https://repost.aws/knowledge-center/eks-cni-plugin-troubleshooting
Heads up, Istio 1.24 now supports 1.31