Thanks for the response, though I don’t think this is what we were looking for unfortunately.
We’re more wondering if we can, after the install, change the port that kotsadm is exposing for the NodePort service. By default I believe it’s 8800 if you do not change it in kots configuration file.
A customer is wondering if we can change it after the fact, as they have a requirement that port not be open on the node and it needs to be blocked from outside of the node.
To re-configure the kotsadm NodePort to another port after installation, customer can generate a new installer script with new kotsadm.uiBindPort and run it on any primary in the cluster.