Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MultiClusterService: max-rate #2282

Open
yellowhat opened this issue Oct 3, 2023 · 7 comments
Open

MultiClusterService: max-rate #2282

yellowhat opened this issue Oct 3, 2023 · 7 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@yellowhat
Copy link

Hi,
I would like to manage the max-rate-per-endpoint via the MultiClusterService or BackendConfig 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:

apiVersion: cloud.google.com/v1
kind: BackendConfig
metadata:
  name: name
  annotations:
    networking.gke.io/max-rate-per-endpoint: "1"

or

apiVersion: networking.gke.io/v1
kind: MultiClusterService
metadata:
  name: name
  annotations:
    cloud.google.com/backend-config: '{"default": "{{ .Release.Name }}"}'
    networking.gke.io/max-rate-per-endpoint: "1"

or modifying the service created by MultiClusterService

apiVersion: v1
kind: Service
metadata:
 annotations:
   cloud.google.com/neg: '{"exposed_ports":{"8080":{}}}'
   cloud.google.com/neg-status: '{"network_endpoint_groups":{"5000":"..."},"zones":["us-central1-a","us-central1-c","us-central1-f"]}'
   networking.gke.io/max-rate-per-endpoint: "1"

But the console always shows: Max RPS: 100000000 (per endpoint)

Thanks

@gauravkghildiyal
Copy link
Member

/assign @swetharepakula

@yellowhat
Copy link
Author

I get the same behaviour even if the MultiClusterService is created from scratch with the networking.gke.io/max-rate-per-endpoint: "1" annotation

@yellowhat
Copy link
Author

Also I have noticed that if you create an Ingress (not MultiClusterIngress) the default is Max RPS: 1 (per endpoint)

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 29, 2024
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 28, 2024
@swetharepakula
Copy link
Member

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 7, 2024
@swetharepakula
Copy link
Member

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

5 participants