-
Notifications
You must be signed in to change notification settings - Fork 146
Closed as not planned
Labels
StaleIssues or pull requests that have not been updated for a whileIssues or pull requests that have not been updated for a whilebacklogIssues that are in the backlogIssues that are in the backlogbugIssues that are confirmed to be bugsIssues that are confirmed to be bugs
Description
Describe the bug
The ingress template has changed since version 1.5.0 to use https instead of http. This results in Traefik responding with error 500 because the certificate of mailu-front is not valid for the host mailu-front.[namespace].svc.[cluster_domain].
Environment
- Kubernetes Platform:
kubeadmcluster
Additional context
There are two possible solutions for this:
- Revert the ingress back to using
httpinstead ofhttps - Add a Traefik
ServersTransportformailu-frontwithinsecureSkipVerify: true, and reference it in the ingress template to bypass TLS verification for that host.
Option two will require some way of conditionally applying if Traefik is in use, of course.
EDIT to add: Option 3: make the http/https behavior an option in values.yaml (defaulting to https), this would be an easy solution.
zeschko and ArnComigs35323, ArnCo and ekozan
Metadata
Metadata
Assignees
Labels
StaleIssues or pull requests that have not been updated for a whileIssues or pull requests that have not been updated for a whilebacklogIssues that are in the backlogIssues that are in the backlogbugIssues that are confirmed to be bugsIssues that are confirmed to be bugs