-
Notifications
You must be signed in to change notification settings - Fork 21
feat: use uwsgi with http only #520
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
feat: use uwsgi with http only #520
Conversation
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 a lot for the PR! I think it makes total sense.
Is it possible to also change nautobot-deployment.yaml
template so we don't expose unnecessary ports?
Co-authored-by: Gerasimos Tzakis <[email protected]>
Happy to contribute :-) Thanks for your proposals. I think so ;-) I'll try to take a look at it how it is connected there... |
Put condition around exposing 8443 port. Please, take a look if it meet your standards and approach. |
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.
LGTM
Fixes: #519
To have an option to disable HTTPS communication within uWSGi.
Security of HTTPS can be handled by ingress which terminates TLS traffic and I find this useful / actually necessary when running in Kubernetes with only read-only filesystem that disallow processes to touch nautobot.crt and nautobot.key files defined within uwsgi.ini and cause an error during deployment (current state).
Of course other option is to enable nginx sidecar with nautobot but I think this could be useful for some scenarios.
Tried to update also docs and validation scheme which impacted quite many other lines...