-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLSEdge support #312
TLSEdge support #312
Conversation
9a89538
to
f0338f2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! 🥳
return err | ||
} | ||
|
||
if err := r.updateIPRestrictionModule(ctx, edge, remoteEdge); err != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: We could just return r.updateIPRestrictionMoudle(ctx, edge, remoteEdge)
here right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could, but I kinda like having the symmetry among the things-to-update 🤷
Resolves ngrok-private/ngrok#22654
What
Add support for TLS Edges. No support as an ingress yet, but direct use of the tlsedge crd is functional.
How
Mostly copy-paste the TCP types/controller. Slight variations around hostport assignment, but otherwise identical currently.
Breaking Changes
Should be none, also fixing a couple of bugs along the way.