Open yellowhat opened 1 year ago
/assign @swetharepakula
I get the same behaviour even if the MultiClusterService
is created from scratch with the networking.gke.io/max-rate-per-endpoint: "1"
annotation
Also I have noticed that if you create an Ingress (not MultiClusterIngress) the default is Max RPS: 1 (per endpoint)
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/kind feature
/lifecycle frozen
Hi, I would like to manage the
max-rate-per-endpoint
via theMultiClusterService
orBackendConfig
k8s manifest. Currently even if I change the "Max RPS" value for an endpoint via the console, after few minutes gets reset to the default value (100000000).I have tried to add:
or
or modifying the service created by
MultiClusterService
But the console always shows:
Max RPS: 100000000 (per endpoint)
Thanks