Open API v3 requirement for `PATCH` verb support (introduced PR #115119)
aaron-kasten opened this issue · comments
What happened?
Aggregated API backend: Call to CREATE endpoint consults PATCH field validation properties, even if the resource does not support the PATCH verb..
What did you expect to happen?
Expected CREATE to be called with CREATE field validation without looking at the PATCH endpoint.
How can we reproduce it (as minimally and precisely as possible)?
Create Open API v3 specification with a field validator. Storage for API server (aggregated API server) advertises support only for CREATE, GET, DELETE
Anything else we need to know?
No response
Kubernetes version
$ kubectl version
Client Version: v1.28.9
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.9-gke.1000000Cloud provider
OS version
architecture: amd64
bootID: f993a6ef-ee9e-457b-856e-bfd51f9cdd22
containerRuntimeVersion: containerd://1.7.13
kernelVersion: 5.15.0-1054-gke
kubeProxyVersion: v1.27.12-gke.1190000
kubeletVersion: v1.27.12-gke.1190000
machineID: 4da31cf9d84cf8d82e680abcb09130ae
operatingSystem: linux
osImage: Ubuntu 22.04.4 LTS
systemUUID: 4da31cf9-d84c-f8d8-2e68-0abcb09130ae
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output hereInstall tools
Container runtime (CRI) and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
This issue is currently awaiting triage.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
/sig cli
In response to this:
/meow
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.