From fa92f23eb92eb4afafa69964b3d084f1b5ddd04a Mon Sep 17 00:00:00 2001 From: Mateusz Gozdek Date: Mon, 4 Oct 2021 14:54:14 +0200 Subject: [PATCH] k8s.io/apiserver/pkg/server: fix name in APIServerHandler description In 18177e2bdeafbddeb3d66fec0b8cb88794cd69ff, PostGoRestful field has been renamed to NonGoRestfulMux, but the documentation change did not follow. This commit fixes that to avoid potential confusion. Signed-off-by: Mateusz Gozdek Kubernetes-commit: 36ede8de945adcc06bde21c49dc157e9c741e0d2 --- pkg/server/handler.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pkg/server/handler.go b/pkg/server/handler.go index 85d8af1ce..23b72a3ac 100644 --- a/pkg/server/handler.go +++ b/pkg/server/handler.go @@ -59,7 +59,7 @@ type APIServerHandler struct { // which we don't fit into and it still muddies up swagger. Trying to switch the webservices into a route doesn't work because the // containing webservice faces all the same problems listed above. // This leads to the crazy thing done here. Our mux does what we need, so we'll place it in front of gorestful. It will introspect to - // decide if the route is likely to be handled by goresful and route there if needed. Otherwise, it goes to PostGoRestful mux in + // decide if the route is likely to be handled by goresful and route there if needed. Otherwise, it goes to NonGoRestfulMux mux in // order to handle "normal" paths and delegation. Hopefully no API consumers will ever have to deal with this level of detail. I think // we should consider completely removing gorestful. // Other servers should only use this opaquely to delegate to an API server.