From c43105d0dc9eeb2240d077f178fa79dba5054f8c Mon Sep 17 00:00:00 2001 From: Alexander Zielenski Date: Thu, 10 Nov 2022 15:28:37 -0800 Subject: [PATCH] fix apiregistration priority v1 discovery always has apiregistration first. this rigs the priority to be greater than maximum so it is guaranteed to be first in the list --- .../kube-aggregator/pkg/apiserver/handler_discovery.go | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/staging/src/k8s.io/kube-aggregator/pkg/apiserver/handler_discovery.go b/staging/src/k8s.io/kube-aggregator/pkg/apiserver/handler_discovery.go index a4ac10ffcee..401c42c3aad 100644 --- a/staging/src/k8s.io/kube-aggregator/pkg/apiserver/handler_discovery.go +++ b/staging/src/k8s.io/kube-aggregator/pkg/apiserver/handler_discovery.go @@ -39,7 +39,10 @@ import ( ) var APIRegistrationGroupVersion metav1.GroupVersion = metav1.GroupVersion{Group: "apiregistration.k8s.io", Version: "v1"} -var APIRegistrationGroupPriority int = 18000 + +// Maximum is 20000. Set to higher than that so apiregistration always is listed +// first (mirrors v1 discovery behavior) +var APIRegistrationGroupPriority int = 20001 // Given a list of APIServices and proxyHandlers for contacting them, // DiscoveryManager caches a list of discovery documents for each server