next-version/graph: Adapt config so ingress comm' is functional
Ingress is for cluster external communication (the "internet") to internal cluster services. We use it in a specific way though so we can benefit from the metrics we already have set for ingress.
But ingress internal "dns" resolution (within the cluster) is not a defacto standard. Contrary to the integrated service resolution, we actually need to declare service with externalName so the communication can occur appropriately.
Tested locally and finally ok.. I've adapted the the next-version cluster so it's reflecting this. Tests are concluant (added as comment below).
Edited by Antoine R. Dumont