Skip to content

Limits to protect the client memory #5062

@shawkins

Description

@shawkins

Is your task related to a problem? Please describe

If there is a precise need to control the memory of the kubernetes-client, or the need to limit the scope of a potential negative effects from an attack, there could be limits introduced on the size of various response from the api-server. This includes the websocket frames and messages, and regular http response chunks and total response size.

Describe the solution you'd like

While ideally implemented at the standardhttpclient layer, that may be too high for some of the enforcement - individual websocket frames or http response chunks may not be proactively checked at that level and may not have enforcement mechanisms at a lower level.

Jetty and Vertx of course have mechanisms to enforce ws limits - #5036

Describe alternatives you've considered

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions