Bug 1776226 - KubeAPI server doesn't accept patch requests > 1MB
Summary: KubeAPI server doesn't accept patch requests > 1MB
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.11.z
Assignee: Stefan Schimanski
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On: 1775757
Blocks: 1776259
TreeView+ depends on / blocked
 
Reported: 2019-11-25 10:06 UTC by Lukasz Szaszkiewicz
Modified: 2019-12-16 11:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-16 11:57:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 24196 0 'None' 'closed' 'Bug 1776226: KubeAPI server doesn''t accept large patch requests' 2019-12-06 19:43:23 UTC
Red Hat Product Errata RHBA-2019:4050 0 None None None 2019-12-16 11:57:28 UTC

Description Lukasz Szaszkiewicz 2019-11-25 10:06:24 UTC 
The following PR[1] fixes bounds checking of large JSON patches in KubeAPI server. Before that sending/applying large (1 MB) patches were not possible[2]. The PR has been already backported to the master branch [3]

[1]https://github.com/kubernetes/kubernetes/pull/84963/files
[2]https://github.com/kubernetes/kubernetes/issues/84908
[3]https://github.com/openshift/origin/pull/24183
Comment 2 Xingxing Xia 2019-12-05 06:57:59 UTC 
Verified in v3.11.157 env with verification steps of bug 1775736.
Comment 4 errata-xmlrpc 2019-12-16 11:57:11 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:4050
Note You need to log in before you can comment on or make changes to this bug.