Remove client-side rate limiter from Sentry

Remove client-side rate limiter from Sentry

Problem

A cold start of many Dapr deployments would take a long time, and even cause some crash loops.

Impact

A large Dapr deployment would take a non-linear more amount of time that a smaller one to completely roll out.

Root cause

The Sentry Kubernetes client was configured with a rate limiter which would be exhausted when services all new Dapr deployment at once, cause many client to wait significantly.

Solution

Remove the client-side rate limiting from the Sentry Kubernetes client.

Signed-off-by: joshvanl <[email protected]>

Author: JoshVanL

docs/release_notes/v1.15.4.md

@@ -143,4 +143,4 @@ Daprd would not close Scheduler gRPC connections to hosts which no longer exist.
 
 ### Solution
 
-Daprd now closes connections to Scheduler hosts when they are no longer in the list of active hosts.
+Daprd now closes connections to Scheduler hosts when they are no longer in the list of active hosts.

pkg/sentry/server/validator/kubernetes/kubernetes.go

@@ -17,6 +17,7 @@ import (
 	"context"
 	"errors"
 	"fmt"
+	"math"
 	"strings"
 
 	"github.com/lestrrat-go/jwx/v2/jwt"
@@ -88,6 +89,9 @@ func New(opts Options) (validator.Validator, error) {
 		return nil, err
 	}
 
+	opts.RestConfig.RateLimiter = nil
+	opts.RestConfig.QPS = math.MaxFloat32
+	opts.RestConfig.Burst = math.MaxInt
 	cache, err := cache.New(opts.RestConfig, cache.Options{Scheme: scheme})
 	if err != nil {
 		return nil, err