fix: Fix Traefik TLS verification to front #390
+53
−27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces several changes fixing support for Traefik as an ingress controller and allowing the disabling of TLS verification between Traefik and the backend.
Documentation updates:
mailu/README.md
: Added descriptions for new ingress settings, includingingress.type
andingress.traefik.insecureSkipVerify
. [1] [2]Configuration updates:
mailu/values.yaml
: Introduced new parametersingress.type
andingress.traefik.insecureSkipVerify
to support Traefik and allow disabling TLS verification.Template updates:
mailu/templates/front/ingress.yaml
: Added conditional annotations for Traefik wheningress.traefik.insecureSkipVerify
is enabled.mailu/templates/front/service.yaml
: IncludedserversTransport
configuration for Traefik wheningress.traefik.insecureSkipVerify
is enabled.mailu/templates/front/traefik-serverstransport.yaml
: Added a new template forServersTransport
resource configuration when using Traefik withinsecureSkipVerify
.Fixes #368