kubectl app url is not able to correctly parse the Port number

[devdattakulkarni]

When application instances are created with Service type as "LoadBalancer" or "NodePort", the 'kubectl app url' outputs URLs like the following:
http://192.168.49.2:-1

[devdattakulkarni]

@rahulkumar-choudhary
You can take a look at this issue as part of looking into kubectl app url plugin.

[devdattakulkarni]

First, we can get rid of "connections" parameter, similar to applogs.
Second, currently we are running get_resources_connections to first get all the resources and then we use that resources list to find out ingresses and services
(check: https://github.com/cloud-ark/kubeplus/blob/master/plugins/appurl.py#L137)
We can simplify this by implementing two separate methods (get_ingresses(custom_resource_instance)) and (get_services(custom_resource_instance)). These methods will take name of the custom_resource_instance as input and query for ingresses/services in the namespace corresponding to that cr_instance.
This change will also improve performance of the kubectl appurl plugin.