We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
To me it looks like the Bunkerweb Scheduler with Autoconf is always using HTTP for REVERSE_PROXY_HOST.
Is it possible to change that behavior to a defined backend protocol (HTTPS)?
What I'm looking for is an equivalent to "nginx.ingress.kubernetes.io/backend-protocol".
No response
The text was updated successfully, but these errors were encountered:
Hi @abargst, this is a great idea! We will implement it in the next 1.6.X minor/major 😄
Sorry, something went wrong.
[#1766] feat: enhance IngressController to support configurable servi…
b97257c
…ce protocol
No branches or pull requests
What's needed and why?
To me it looks like the Bunkerweb Scheduler with Autoconf is always using HTTP for REVERSE_PROXY_HOST.
Is it possible to change that behavior to a defined backend protocol (HTTPS)?
What I'm looking for is an equivalent to "nginx.ingress.kubernetes.io/backend-protocol".
Implementations ideas (optional)
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: