-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update nginx image
- Loading branch information
Showing
4 changed files
with
7 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3f29e43
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.
@aledbf can I ask why you had to add cap_net_bind_service for this nginx version bump?
I understand the constraints around binding to ports < 1024 but we (for example) have tended just to use command-line args to get nginx to bind to 8080, 8443 etc so that the process doesn't need that capability.
There's also a load of
authbind
stuff in this image which I don't fully understand but appears to be intended to solve the same problem.3f29e43
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.
@michaelbannister because go binaries do not work with authbind and without
cap_net_bind
we break ssl-passthrough.3f29e43
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.
Thanks, I understand. But if I’m not using ssl-passthrough or intend to change the ssl port by setting
--https-port
and--ssl-passthrough-proxy-port
to ports higher than 1024, I won’t need this. It’d be nicer if this could be done at runtime only if required. Not sure if that’s possible.My use case is that I have a fairly restrictive pod security policy by default, disallowing all capabilities (I just use higher ports), so this has forced me to create a special PSP just for the ingress controller. Fine, but would be simpler if I didn’t have to. 🙂 Might put this in a new issue after discussing with my team.
3f29e43
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.
That's not possible running as user. We tried that in the past but that approach just introduces complexity and edge cases where it does not work.
You can fork the repo, changing just the dockerfile and use that image, you just need docker installed to build 😉