Configurable ports when service type is NodePort

[Jhoyola]

For a simple and static way to connect to the node RPCs from host machine, the service type can be set to "NodePort". This PR makes it possible to fix static ports for each node to preconfigure a development environment based on warnet.

[pinheadmz]

I think mechanically this is the right choice to get remote access to each pod individually. It seems more correct and kubernetes-y than #686 which addresses the same goal.

Questions:

• How does the local user get the IP:port of the pod they want to connect to?
• How does this work in a large scale cluster with multiple kubernetes nodes, multiple pods on each node?

[Jhoyola]

• How does the local user get the IP:port of the pod they want to connect to?

User would add the below to the node on their network configuration. Then it's accessible at localhost:30443. I added documentation about this. Also added a small section about kubectl port-forward similar to #686 but without a warnet command.

    service:
      type: NodePort
      rpcNodePort: 30443

• How does this work in a large scale cluster with multiple kubernetes nodes, multiple pods on each node?

Haven't tested it, but according to Kubernetes docs it works just as: <kubernetes-node-ip>:<exposed-port>

[Jhoyola]

Rebased

[Copilot]

Copilot was unable to review this pull request because the user who requested the review is ineligible. To be eligible to request a review, you need a paid Copilot license, or your organization must enable Copilot code review.

[pinheadmz]

Sorry about the long delay. Rebased on main mainly to refresh CI. WIll review today.

[pinheadmz]

fixed a nit in the doc and added a test

[pinheadmz]

adding new command warnet host which can be used to get the cluster node IP or hostname (including minikube) for use with NodePort

[pinheadmz]

Tested locally with macos using Docker Desktop and Minikube backends. Ran a remote cluster on digital ocean and tested that setup from debian. Along with the CI which runs ubuntu and Minikube, I think this is working as well as expected.

The tricky part was warnet host -- determining where to connect to those NodePorts on all platforms. Especially on macos, where kubernetes is run inside a VM with IP addresses normally inaccessible to the host.

Unfortunately there is no good way to test the feature on Macos using minkube backend, so I programmed the test to just skip if that is the condition

[pinheadmz]

@Jhoyola I think this is ready to merge, do you wanna take one last look and make sure I didn't break anything you need?

[Jhoyola]

Looks good to me. Thanks!