Closed CullenShane closed 2 years ago
Thanks for both this and the PR! :) PR is merged and will be released next week with the weekly patches 👍
Thanks for both this and the PR! :)
PR is merged and will be released next week with the weekly patches 👍
Thanks! There are two PR, one for each bug. https://github.com/truecharts/library-charts/pull/56 and https://github.com/truecharts/apps/pull/2635
@all-contributors please add @CullenShane for bug
@Ornias1993
@CullenShane already contributed before to bug
This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists
App Name
traefik
SCALE Version
22.02.0
App Version
2.6.6_11.3.0
Application Events
Application Logs
Application Configuration
Describe the bug
Traefik does not respect ingressClass when set, all instances of traefik all try to host all the ingresses.
Additionally, all ingress configuration is seen by all Traefik instances, not just from their own namespaces but from all namespaces.
To Reproduce
IngressClass
checkEnabled
Also uncheckisDefaultClass
ingressClass Name
for the appcurl -H "Host: example.com" http://192.168.2.50/
Expected Behavior
The app should not be accessible via the Host header. But instead, the app is accessible.
In fact, the configured Host is now served by all traefi (what is the plural of traefik?) that have been installed.
Screenshots
n/a
Additional Context
As seen below, Traefik is not configured for ingress class with
--providers.kubernetesingress.ingressclass=traefik
Additionally, traefik is not respecting namespace delineations between other copies of traefik as provided by:
When I added these arguments to the deployments, all the traefiks (traefi?) started behaving .
I've read and agree with the following