Spike: Expose catalogd service off cluster

[ankitathomas]

epic: #1424

Investigate methods for exposing catalogd service off cluster for querying for kubectl-operator. Potential options include:

• kubectl port-forward : requires permissions to set up the port-forward connection (Enhance RBAC model to separate pod creation and port-forwarding kubernetes/kubernetes#110999 (comment), bind local port),
• proxy : access the service at http://<kubernetes_master_address>/api/v1/namespaces/<namespace_name>/services/<service_name>/proxy - requires service/proxy permissions, no client authentication for external access to catalogd
• Expose service with a nodeport : Create the catalogd service with a nodeport, requires local port reservation by default with catalogd, and for the kubectl plugin to discover the local port assignment (present on service as externalIPs, ports.nodePort).
• kubernetes Gateway or Ingress : requires either the Gateway API addon or a third party ingress controller, OLM cannot make assumptions that a gateway/ingress controller will be running on every cluster.

If choosing a hybrid approach, follow-on work is required to also add ability to toggle on or off different methods, and also to automatically choose a method depending on the information provided by the currently running catalogd controller

[github-actions]

Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.

[ankitathomas]

See https://hackmd.io/uupzJCqGTny24Ngjvb9JaA.