Open feloy opened 2 weeks ago
cc @deboer-tim @cdrage
š Would really help improvement. I'm assuming this works fine with OpenShift too?
š Would really help improvement. I'm assuming this works fine with OpenShift too?
Yes, I have made a quick PoC, and we have access to the information on OpenShift Sandbox
kubernetes client used groups to deal with resource manipulations but noticed we were processing Routes even on non OpenShift clusters so how do this relates ? Does it includes non standard CRDs ?
Is your enhancement related to a problem? Please describe
The current implementation for checking the connectivity to Kubernetes contexts uses informers. This solution has some drawbacks:
Describe the solution you'd like
I propose to query the
SelfSubjectRulesReview
resource in the cluster to check the connectivity to the cluster, before to start informers. The advantages are:SelfSubjectRulesReview
are expected to be accessible for all userslist
permission, to have a degraded implementation usinglist
operation and notwatch
(informers), if the user haslist
but notwatch
permissions.Describe alternatives you've considered
No response
Additional context
No response