[wip] Private Service doesn't need a cluster IP

[dprotaso]

This brings back "change private K8s service to be a headless service (#15170)" with some additional changes.

When we set 'ClusterIP: None' on the private service the activator
can't perform the fallback service probing. This is needed
while in mesh mode.

This change tweaks the fallback probing to use the hostname
of the private service instead of using a cluster IP.

On caveat is that when using a headless service Istio/K8s doesn't
perform any port translation 80 (http)->8012 (queue-proxy http).

Thus we perform this lookup ourselves.

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dprotaso]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dprotaso]

/test istio-latest-mesh
/test istio-latest-mesh-short
/test istio-latest-mesh-tls

[dprotaso]

/test istio-latest-mesh
/test istio-latest-mesh-short
/test istio-latest-mesh-tls

[github-actions]

This Pull Request is stale because it has been open for 90 days with
no activity. It will automatically close after 30 more days of
inactivity. Reopen with /reopen. Mark as fresh by adding the
comment /remove-lifecycle stale.

[skonto]

@dprotaso what is the status of the PR, is this something you still want to pursue?

[skonto]

@dprotaso should we revive this one?

[knative-prow]

@dprotaso: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
istio-latest-mesh_serving_main	a76d104	link	false	/test istio-latest-mesh
istio-latest-mesh-short_serving_main	a76d104	link	false	/test istio-latest-mesh-short
unit-tests_serving_main	e8c6655	link	true	/test unit-tests

Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.