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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: