Re: Not able to route to services

Hi TIm, Did you try to curl directly on the docker-registry POD? If it works maybe the docker-registry endpoint is missing. You can also try to recreate the docker-registry service. Best, Rodrigo Bersa Cloud Consultant, RHCVA, RHCE Red Hat Brasil rbe...@redhat.com

Re: Not able to route to services

A little more on this. I have two systems, installed in an identical manner as is possible. One works fine, on the other I can't connect to services. For instance, from the master node I try to connect the docker-registry service on the infrastructure node. If I try: curl -I https://:5000/heal

Re: Not able to route to services

Sorry, I am using port 5000. I wrote that bit incorrectly. I did do some more digging based on what's here (https://docs.openshift.org/latest/admin_guide/sdn_troubleshooting.html) and it looks like there's something wrong with the node to node communications. From the master I try to contact t

Re: Not able to route to services

Isn't the default port for your Registry 5000? Try `curl -kv https://docker-registry.default.svc:5000/healthz` [0][1]. [0] https://access.redhat.com/solutions/1616953#health [1] https://docs.openshift.com/container-platform/3.7/install_config/registry/ac

Not able to route to services

Something strange has happened in my environment which has resulted in not being able to route to any of the services. Earlier this was all working fine. The install was done using the ansible installer and this is happening with 3.6.1 and 3.7.1. The services are all there are running fine, and D