You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users want a way to expose the k8s api via an ngrok endpoint. Sometimes this would be via a whitelabeled reserved domain, some users would probably be fine with an ngrok.app or other ngrok domain.
Ideally this would be done via some parameters set at helm install time, to be able to configure what domain name to use for the ngrok edge, and any relevant authentication information (mtls etc) to layer on top of the edge.
I wonder also if it makes sense to create a new CRD for accomplishing this directly in a manifest file too?
Below is a manifest file that works but is a bit complicated for users to implement.
Description
Users want a way to expose the k8s api via an ngrok endpoint. Sometimes this would be via a whitelabeled reserved domain, some users would probably be fine with an ngrok.app or other ngrok domain.
Ideally this would be done via some parameters set at helm install time, to be able to configure what domain name to use for the ngrok edge, and any relevant authentication information (mtls etc) to layer on top of the edge.
I wonder also if it makes sense to create a new CRD for accomplishing this directly in a manifest file too?
Below is a manifest file that works but is a bit complicated for users to implement.
Use Case
No response
Related issues
No response
The text was updated successfully, but these errors were encountered: