It manages sometimes to sync the ad-groups, not sure if that is still expected or not
{"level":"error","ts":1730378101.6257863,"caller":"proxy/handlers.go:61","msg":"Ready check failed","error":"Unauthorized","stacktrace":"github.com/xenitab/azad-kube-proxy/internal/proxy.(*handler).readiness.func1\n\t/workspace/internal/proxy/handlers.go:61\nnet/http.HandlerFunc.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2122\ngithub.com/gorilla/mux.(*Router).ServeHTTP\n\t/go/pkg/mod/github.com/gorilla/mux@v1.8.0/mux.go:210\nnet/http.serverHandler.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2936\nnet/http.(*conn).serve\n\t/usr/local/go/src/net/http/server.go:1995"}
{"level":"info","ts":1730378105.4999404,"caller":"proxy/azure_groups.go:60","msg":"Synchronized Azure AD groups to cache","groupCount":12,"syncReason":"ticker"}
{"level":"error","ts":1730378111.6246645,"caller":"proxy/handlers.go:61","msg":"Ready check failed","error":"Unauthorized","stacktrace":"github.com/xenitab/azad-kube-proxy/internal/proxy.(*handler).readiness.func1\n\t/workspace/internal/proxy/handlers.go:61\nnet/http.HandlerFunc.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2122\ngithub.com/gorilla/mux.(*Router).ServeHTTP\n\t/go/pkg/mod/github.com/gorilla/mux@v1.8.0/mux.go:210\nnet/http.serverHandler.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2936\nnet/http.(*conn).serve\n\t/usr/local/go/src/net/http/server.go:1995"}
After upgrading some clusters to 1.30.5 issues appear in the proxy.
Starts fine and runs OK for ~20-30min, then errors are thrown.
It manages sometimes to sync the ad-groups, not sure if that is still expected or not