TCP+TLS connection kill in 3.0.0-rc5 about traefik HOT 14 OPEN

Hello @kamikaze @jur3,

Depending on the routing configuration you have, this behavior could have been fixed by PR #10615.
This fix has not been released yet, but can you please try the experimental images traefik/traefik:experimental-v3.0 in the mean time?

from traefik.

Hello,

it's because we have the default timeout: https://doc.traefik.io/traefik/migration/v2/#entrypointtransportrespondingtimeoutsreadtimeout

You can find community suggestions about the value to use in your context: https://github.com/traefik/traefik/wiki/respondingTimeouts-for-applications

from traefik.

Hello,

it's because we have the default timeout: https://doc.traefik.io/traefik/migration/v2/#entrypointtransportrespondingtimeoutsreadtimeout

You can find community suggestions about the value to use in your context: https://github.com/traefik/traefik/wiki/respondingTimeouts-for-applications

nope, it still fails in the same ~1min with

SSL connection has been closed unexpectedly
The connection to the server was lost. Attempting reset: Succeeded.
SSL connection (protocol: TLSv1.3, cipher: TLS_AES_128_GCM_SHA256, compression: off)

even with:

    entryPoints:
      psql:
        address: ":5432"
        transport:
          respondingTimeouts:
            readTimeout: "0"

from traefik.

This timeout issue is present already in v3.0.0-rc4 version.

from traefik.

Unable to install it via Helm chart:

Helm install failed for release traefik-v3/traefik with chart [email protected]: template: traefik/templates/rbac/clusterrole.yaml:59:13: executing "traefik/templates/rbac/clusterrole.yaml" at <semverCompare "<3.0.0-0" (include "imageVersion" $)>: error calling semverCompare: Invalid Semantic Version

from traefik.

Hello @mloiseleur,

Unable to install it via Helm chart:

It looks like a limitation, WDYT of adding support for our experimental images to the Helm chart?

from traefik.

@rtribotte Sure. Would you please let me know what you think of traefik/traefik-helm-chart#1045 ?

BTW, wdyt of following semver for this experimental version ? It would mean produce an image with tag v3.0-experimental.

from traefik.

@mloiseleur I agree, if there are no blockers, adopting Semver would allow supporting any experimental tag by default.

from traefik.

But v3.0-experimental it's not a semver version: the 3 numbers (vX.Y.Z-xxx) are required with semver.

The experimental-v3.0 is a floating tag, like latest or v3.0, there is no relation with a specific version or semver.

from traefik.

I think we should not change the tag from experimental-v3.0 to v3.0-experimental.

from traefik.

@ldez I agree with you: it's not a complete semver version. Nevertheless, it's good enough to be supported by semverCompare, see traefik/traefik-helm-chart#1046

from traefik.

it's not a complete semver version

It's semver or it's not, there is no partial semver.

semverCompare uses a specific syntax ~ (from npm) to check only minor and major, but this doesn't mean that we should abuse this behavior to allow non-semver versions.

experimental-v3.0 is a floating tag, so there is no need for comparison or being semver-ish.

from traefik.

Yes, there is no partial semver.

Wondering why it's supported, I am discovering that this question has been heavily discussed : semver/semver#237
They ended by not accepting version without patch as a valid semver and allows compare parsing, see semver/semver#237 (comment)

Anyway, it's up to Traefik maintainers to decide how this tag should be managed.

What I can say is that, from the Chart perspective, the v28 does not support anymore Traefik Proxy v2 specifics. This semverCompare call is useful to warn users who missed this major requirement.

from traefik.