-
Notifications
You must be signed in to change notification settings - Fork 98
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
update nginx template for TLS passthrough #2166
update nginx template for TLS passthrough #2166
Conversation
I didn't add anything to data plane for upstreams yet, I was thinking of reusing the existing type BackendGroup and just adding an IsStream boolean |
d76b1c4
to
d48dba2
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.
@sarthyparty nice work! Please see my review
eb22a09
to
fa2812f
Compare
Parameters: []http.MapParameter{ | ||
{ | ||
Value: t.Hostname, | ||
Result: "unix:/var/lib/nginx/" + t.Hostname + fmt.Sprint(t.Port) + ".sock", |
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.
Hostnames can have * which are not valid characters for file names.
- are fine :)
server {
listen unix:/var/run/*.server.sock;
access_log off;
return 200 "hello\n";
}
ls /var/run/*.sock
'/var/run/*.server.sock'
a5e35b7
to
af649df
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.
Can we rebase the feature branch feature/tls-passthrough
on main to reduce the diff in this PR? Some extra stuff in there from other unrelated commits.
internal/mode/static/handler.go
Outdated
@@ -170,7 +170,7 @@ func newEventHandlerImpl(cfg eventHandlerConfig) *eventHandlerImpl { | |||
|
|||
func (h *eventHandlerImpl) HandleEventBatch(ctx context.Context, logger logr.Logger, batch events.EventBatch) { | |||
start := time.Now() | |||
logger.V(1).Info("Started processing event batch") | |||
logger.V(1).Info("Started processing event batch hello", "name", "sarthak") |
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.
Debugging log can be removed.
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.
ok will do
23f8b38
to
47ba96e
Compare
would it make sense to enable GitHub pipeline including linting for the branch feature/tls-passthrough ? |
Yes, definitely, good catch. @lucacome what's the best way to do that? Should I just add the feature branch name to the |
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.
Leaving a partial review. I'm about half-way through, but want to give you something to work on while I finish.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## feature/tls-passthrough #2166 +/- ##
===========================================================
+ Coverage 87.59% 87.79% +0.20%
===========================================================
Files 96 98 +2
Lines 6698 6810 +112
Branches 50 50
===========================================================
+ Hits 5867 5979 +112
Misses 774 774
Partials 57 57 ☔ View full report in Codecov by Sentry. |
Problem: nginx configuration templates didn't support TLS passthrough Solution: I added a template setup fro stream servers
Co-authored-by: Kate Osborn <50597707+kate-osborn@users.noreply.github.com>
1bc8be4
into
nginxinc:feature/tls-passthrough
Update nginx template for TLS passthrough Problem: nginx configuration templates didn't support TLS passthrough Solution: I added a template setup fro stream servers
Update nginx template for TLS passthrough Problem: nginx configuration templates didn't support TLS passthrough Solution: I added a template setup fro stream servers
Update nginx template for TLS passthrough Problem: nginx configuration templates didn't support TLS passthrough Solution: I added a template setup fro stream servers
Update nginx template for TLS passthrough Problem: nginx configuration templates didn't support TLS passthrough Solution: I added a template setup fro stream servers
Update nginx template for TLS passthrough Problem: nginx configuration templates didn't support TLS passthrough Solution: I added a template setup fro stream servers
Update nginx template for TLS passthrough Problem: nginx configuration templates didn't support TLS passthrough Solution: I added a template setup fro stream servers
Update nginx template for TLS passthrough Problem: nginx configuration templates didn't support TLS passthrough Solution: I added a template setup fro stream servers
Update nginx template for TLS passthrough Problem: nginx configuration templates didn't support TLS passthrough Solution: I added a template setup fro stream servers
Proposed changes
Problem: Nginx templates didn't support TLS passthrough inside stream block
Solution: I added nginx template for stream servers and also added a Layer4Server type to data plane
Testing: Tested the conversion from data plane type to nginx template
Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.
Closes #ISSUE
Checklist
Before creating a PR, run through this checklist and mark each as complete.
Release notes
If this PR introduces a change that affects users and needs to be mentioned in the release notes,
please add a brief note that summarizes the change.