You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of the problem:
In AWS we are using EKS with AWS CNI. The current AWS architecture pre-provisions IPs on VM. For instance and m4.xlarge VM may have 20 IPs reserved for POD. In this case, they are not using bridge or overlay.
In EKS current Registrator code is not able to get POD IP consul is getting service entry with consul-client IP.
How reproducible: very reproducible
Steps to Reproduce:
Run consul using default consul-helm chart.
Dockerfile
for application that is having issues.Docker inspect of service pod:
Description of the problem:
In AWS we are using EKS with AWS CNI. The current AWS architecture pre-provisions IPs on VM. For instance and m4.xlarge VM may have 20 IPs reserved for POD. In this case, they are not using bridge or overlay.
In EKS current Registrator code is not able to get POD IP consul is getting service entry with consul-client IP.
How reproducible: very reproducible
Steps to Reproduce:
Run consul using default consul-helm chart.
Start registrator like
Run nginx pod
Actual Results:
Service entry of nginx with consul-client ip.
Expected Results:
Service entry of nginx should be there with pod_ip
Additional info:
Submitted pull request to solve this issue: #674
The text was updated successfully, but these errors were encountered: