Your support team recommended I open an inprovement request in response to ticket #157457.
Regarding a Kubernetes deployment of Artifactory, one thing we recently noticed is the Apache reverse proxy configuration generated by the Artifactory UI (Admininstration -> Services/Artifactory -> HTTP Settings) results in BalancerMember stanzas which reference the exposed IP addresses of the pods, which then breaks if those ever change due to node migration, etc.
We altered those statements to reference the service, and that worked, so we no longer need to worry about the dependency.
from BalancerMember http://**10.131.2.68**:8082 route=openshiftartifactoryha-artifactory-ha-primary-0
to BalancerMember http://**openshiftartifactoryha-artifactory-ha-primary**:8082 route=openshiftartifactoryha-artifactory-ha-primary-0