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

Capture resource requirements #239

Closed
maleck13 opened this issue Sep 19, 2024 · 2 comments
Closed

Capture resource requirements #239

maleck13 opened this issue Sep 19, 2024 · 2 comments

Comments

@maleck13
Copy link
Collaborator

maleck13 commented Sep 19, 2024

Blocked by: #141

What

Capture resource requirements for the DNS-Operator (Mem and CPU) for setting limits via k8s

  • minimum:
    • 1 gateway,
    • 1 listener,
    • 1 DNSPolicy (with health check)
  • baseline:
    • 1 gateway,
    • 64 listeners,
    • 1 DNSPolicy (with health check)
  • baseline +1:
    • 2 gateways with:
      • 64 listeners,
      • 1 DNSPolicy (with health check)

Can just use DNSRecords but might be easier with DNSPolicy.

Increase limits based on diff between baseline and baseline +1

Make use of Grafana and Prometheus to take measurements.

Could be useful as a pipeline that can output suggested limits, which we can reuse on every release.

@maleck13
Copy link
Collaborator Author

@philbrookes @mikenairn above make sense as a method for coming up with some baseline numbers?

@maleck13
Copy link
Collaborator Author

maleck13 commented Oct 2, 2024

closing as putting more focus on Kuadrant as a whole

@maleck13 maleck13 closed this as completed Oct 2, 2024
@maleck13 maleck13 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

1 participant