Red Hat Bugzilla – Bug 1466593
[paid][pro-us-east-1] two registry pods running on the same node
Last modified: 2017-08-16 04:17:34 EDT
Description of problem:
Is it intentional to have two registry pods running on the same node (online Pro V3 production):
docker-registry-4-bd4xv 1/1 Running 1 6d 10.131.0.89 ip-172-31-52-61.ec2.internal
docker-registry-4-cfmnm 1/1 Running 2 6d 10.129.4.115 ip-172-31-51-115.ec2.internal
docker-registry-4-s1m4h 1/1 Running 1 6d 10.131.0.90 ip-172-31-52-61.ec2.internal
I am not aware of any requirements for registry that would require it to be on different nodes. Router pods are the only ones that have this.
No requirement, it just seemed odd and I wanted to make sure it was intended.
Pushing this out of the blocker list for now. Holding off on closing this as not a bug to better understand if we need to do something about this or if this is something that can be ignored and left to the scheduler.