-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Annotating ingress rules with non-default entryPoints #1898
Comments
+1 The best way if all frontend/backend options configurable by metadata.annotations in Ingress.
|
|
what there a resolution to this? I also only see http being wired. even though I have traefik.frontend.entryPoints: "https" also tried
|
|
I confirmed it's a bug. |
Closed by #2594. |
Do you want to request a feature or report a bug?
Feature (maybe)
What did you do?
I'm using traefik as a kubernetes ingress controller. Most of my websites require HTTPS and the encryption perfectly works together with the Letsencrypt certs.
However, I have a couple of websites for which I cannot turn HTTPS on for various reasons and I would like to annotate some of my ingress rules so that traefik served only HTTP.
I've been trying a few variations of the following, but with no luck:
No matter what I do, the traefik dashboard keeps showing
http
+https
badges next to the rule and the website gets served fromhttps://...
.If configuring entrypoints is not yet supported in the k8s environment, what do you guys think about adding it? If it's just a matter of a missing note in the docs, what annotation should be mentioned there?
The text was updated successfully, but these errors were encountered: