The route names we generate in the knative-openshift-ingress component are based on a numeric index that's determined by walking through all targets that a Knative Ingress has. If these targets change, there is no guarantee that the order of things stays the same. If only one target changes its visibility, all following targets will get a different index.

This can cause unnecessary churn on creating and deleting routes and most importantly this has an impact on the user's workloads.

Instead of adding a numeric index, we should append a hash based on the current target's host. That guarantees that we will have exactly one route per ingress and host and update that route if necessary.