Skip to content

Websockets are disconnected after ResponseStartTimeoutSeconds #16169

@mbaynton

Description

@mbaynton

What version of Knative?

0.11.x

Output of git describe --dirty
knative-v1.19.1-1-g3d65c06cb-dirty

Expected Behavior

Websocket connections are not interrupted.

Actual Behavior

  1. Websocket is established through queueproxy
  2. After the number of seconds configured as revision-response-start-timeout-seconds, the websocket is closed.

Steps to Reproduce the Problem

Here's a minimal knative service producing an app that will initiate a websocket connection if you visit it in a browser. You can watch the websocket in the browser's network tab and see that it gets disconnected at 5 minutes. (Note that a new websocket will be created as a result, with the javascript in this image.)

apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name: hello
spec:
  template:
    spec:
      containers:
        - image: mbaynton/streamlit-example:latest
          command: ["streamlit", "run", "app/main.py", "--server.port", "8080"]
          ports:
            - containerPort: 8080

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions