aks tunnel check failure on konnectivity

[chmill-zz]

Describe the bug
We default to using port 9000 for the aks tunnel url. This port isn't applicable for konnectivity clusters. So the assessment gets a connection refused which is misleading.

To Reproduce
Steps to reproduce the behavior: (for example)
1 - run on konnectivity cluster
2 - check aks tunnel results

Expected behavior
We should be using port 443. For konnectivity checks. Same as the apiserver check.

Additional context
I think the only way to check if we're on a konnectivity cluster is if the konnectivity-agent pod(s) exist within the kubeobjects we're grabbing.

[Tatsinnit]

Thanks for this @chmill-zz - I notice that for 9000 it will always show refused connection, cool, I will change this to 443 , thank you.