Skip to content

Investigate why quay client IP address is always 10.130.0.2 #244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
DanielFroehlich opened this issue Feb 10, 2025 · 0 comments
Open

Investigate why quay client IP address is always 10.130.0.2 #244

DanielFroehlich opened this issue Feb 10, 2025 · 0 comments
Labels

Comments

@DanielFroehlich
Copy link

When looking at quay registry access logs, it suprises a bit that the IP address of the client is alway 10.130.0.2
See e.g. here: https://quay.coe.muc.redhat.com/repository/shared/microshift/microshift-4.17-bootc?tab=logs
Or any other image repo.
10.130.0.2 is in the CIDR of the pod network. So e.g. the router or keepalived pods (which sit in front of the quay app pod) could be suspected.
But looking at the pod IPs, there is none with that address (oc get pods -o=wide -A | grep 10.130.0.2 ).
The router pods run with host network IPs (see oc get pods -n openshift-kni-infra -o wide).

It remains a mystery for me, please investigate and advise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant