Open bsmerja opened 1 year ago
Hi @bsmerja! Welcome to the project! 🎉
Thanks for opening this issue! Be sure to check out our Contributing Guidelines and the Issue Lifecycle while you wait for someone on the team to take a look at this.
Hi @bsmerja
I'm trying to reproduce this but creating pods doesn't affect the Autoscaling group for me. Are you still seeing this behavior? If so can you share the logs from nginx-asg-sync as well?
Describe the bug When there are multiple pods running in the EKS environment EKS node members have multiple Private IP addresses based on number of pods running on specific node, nginx-asg-sync fetches any one Private IP address and populates NGINX config, which cause 502 bad gateway.
To Reproduce
Will cause wrong IP addresses in upstream
Provide the following files as part of the bug report
nginx -T
outcomeactual IP addresses of EKS Nodes -
kubectl get nodes -o wide
Also, aws cli command gives Private IP address with filter and query as applied:
config.yaml:
Steps to reproduce the behaviour, such as:
/var/log/nginx-asg-sync/nginx-asg-sync.log
Expected behavior A clear and concise description of what you expected to happen.
Your environment nginx-asg-sync version 0.5.0 nginx version: nginx/1.23.2 (nginx-plus-r28) Amazon Linux 2
Additional context Is it possible to add an additional query inside of config.yaml which I used to find exact Private address in following command:
aws ec2 describe-instances --filters "Name=tag:aws:autoscaling:groupName,Values=eks-Node-instances<1234>" --profile Users-1234 --query 'Reservations[].Instances[].[PrivateIpAddress]' --output text