-
Notifications
You must be signed in to change notification settings - Fork 122
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
Ingress HTTPS support #726
Comments
PR - gh-726 Initial support for basic ingress support
Currently, base functionality is implemented and tested minimally : How to create rules (standalone)
How to test:curl -H "Application/json" -H "Content-type: application/json" -H "HOST: loxilb.io" --insecure https://10.10.10.254:2020 Need to be integrated and tested with loxilb-ingress next. |
gh-726 Better support for http2
Initial support is in. More details here |
gh-726 Added a proxy only mode
gh-726 For proxyonly mode, do not use privileged ops
PR - Support for https2https proxy #726
gh-726 fixed issue with longer hostnames
gh-726 Use default system certs if availabe for https probe
gh-726 Fixes for hanging connections in proxy mode
gh-726 Handling of race conditions in proxy mode
gh-726 Overall fixes for Ingress Support
gh-726 Fixes related to fd reuse
gh-726 updated ca-certificates for loxilb container
The support is now available and basic features have been verified. The CICD runs look good. Closing this.!! |
gh-726 Fixes to https handling
Is your feature request related to a problem? Please describe.
Currently Loxi supports HTTP. Adding HTTPS enhances security, e-2-e encryption.
Describe the solution you'd like
HTTPS support
The text was updated successfully, but these errors were encountered: