Description
For clarity, this is for dynamic listening TCP process and ingresses that occur after the workspace is provisioned.
Currently if coded is running, it looks for open ports and can suggest them via the workspace forward webui.
The name of the subdomain / wildcard is static right now for dynamic forwards in coder.
@ii has a similar feature, but default to name of process.WILDCARDDOMAIN.pair.sharing.io.
For example, if we run netcat -l 8080 on one of our clusters, within moments there will be a working TLS ingress at https://nc.hh.pair.sharing.io that is publicly accessible.
If we want to specify the ingress name, we run SHARINGIO_PAIR_EXPOSER_HOSTNAME=foo nc -l 8080 resulting in https://foo.hh.pair.sharing.io being accessible.
pair.sharing.io environment exporter and exposer:
- https://github.com/sharingio/environment#variables
- https://github.com/sharingio/environment/tree/master/cmd/environment-exporter
- https://github.com/sharingio/environment/tree/master/cmd/environment-exposer
This may be two separate ideas / features:
CODER_APP_HOSTNAME=foo nc -l 8080dynamically creatingfoo-WORKSPACE.WILDCARDDOMAINcoder_app workspace forward- Support for
564D
coderd to look for k8s ingresses, dynamically creating
ingressname-WORKSPACE.WILDCARDDOMAINcoder_app workspace forward