Update README and solo node start to provide commands to setup kubectl port forward for network nodes

[jeromy-cannon]

requested by Simi for uses to be able to leverage to setup a connection against the network.

[JeffreyDallas]

Need more elaboration on this, is ths about to adding new flags to enable port forwarding for
haproxy--svc ?

[jeromy-cannon]

Need more elaboration on this, is ths about to adding new flags to enable port forwarding for haproxy--svc ?

Just write up the kubectl commands that they can execute that will setup the port forwards and add them into a section of the README.md. I think that something like that got dumped to sysout in some of our dev scripts in the FST helm chart tests. Yes, I think point them at the haproxy service, as that is what we connect to to build our SDK connections as well.

[jeromy-cannon]

This is from our FST deployment notes.txt:

Get the name of the envoy gateway system:
  export ENVOY_SERVICE=$(kubectl get svc -n envoy-gateway-system --selector=gateway.envoyproxy.io/owning-gateway-namespace="${NAMESPACE}",gateway.envoyproxy.io/owning-gateway-name=fst -o jsonpath="{.items[0].metadata.name}")

Forward a port on the gateway to a local port:
  kubectl port-forward "svc/${ENVOY_SERVICE}" -n envoy-gateway-system "${LOCAL_PORT}":"${GATEWAY_PORT}" &

Some examples, that for convenience, use the same local port as that on the gateway:

To access the Hedera Mirror Node Explorer locally (port 8888 on the gateway):
  kubectl port-forward "svc/${ENVOY_SERVICE}" -n envoy-gateway-system 8888:8888 &
  open http://127.0.0.1:8888

To access the GRPC port of node 2 (starting port 52000 for node 0 on the gateway):
  kubectl port-forward "svc/${ENVOY_SERVICE}" -n envoy-gateway-system 52002:52002 &

To access the GRPC secure (TLS) port of node 1 (starting port 53000 for node 0 on the gateway):
  kubectl port-forward "svc/${ENVOY_SERVICE}" -n envoy-gateway-system 53001:53001 &

To access the gossip port of node 0 (starting port 51000 for node 0 on the gateway):
  kubectl port-forward "svc/${ENVOY_SERVICE}" -n envoy-gateway-system 51000:51000 &

To access the GRPC web port of node 5 (starting port 18000 for node 0 on the gateway):
  kubectl port-forward "svc/${ENVOY_SERVICE}" -n envoy-gateway-system 18005:18005 &

So, something like this, except use our haproxy grpc port. test the commands to make sure they are good, then add them to a section in the README.md to help those less familiar with Kubernetes and kubectl expose the ports locally so they can use their network nodes to run tests against.

The envoy-gateway is gone, so ignore that. this is just an example.

[swirlds-automation]

🎉 This issue has been resolved in version 0.31.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀