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

[CILIUM] CiliumNetworkingSpec should be able to set all configs like API Rate Limit gathering lots of TooManyRequests #16571

Open
dannyeuu opened this issue May 14, 2024 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@dannyeuu
Copy link
Contributor

dannyeuu commented May 14, 2024

/kind feature

In some hours of the day, we started to have issues with new pods created together, our workload is spark jobs, so hourly create lots of spark executors pods gathering Error on Pods with TooManyRequests.

There is another way to config this? https://docs.cilium.io/en/stable/configuration/api-rate-limiting/#configuration-parameters

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label May 14, 2024
@dannyeuu
Copy link
Contributor Author

dannyeuu commented May 21, 2024

@sayboras and @aanm as CIlium, can you help here?

@dannyeuu dannyeuu changed the title [CILIUM] CiliumNetworkingSpec should be able to set all configs like API Rate Limit [CILIUM] CiliumNetworkingSpec should be able to set all configs like API Rate Limit gathering lots of TooManyRequests Jun 3, 2024
@sayboras
Copy link

sayboras commented Jun 7, 2024

👋 thanks for the ping, I am not familar with kops and how it's configured with Cilium, so can't comment.

Cilium helm chart is having extraArgs in values.yaml, which can be used to pass --api-rate-limit.

@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 Sep 5, 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 Oct 5, 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/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants