Join us from October 8-10 in New York City to learn the latest tips, trends, and news about GraphQL Federation and API platform engineering.Join us for GraphQL Summit 2024 in NYC
Docs
Start for Free

Managing GraphOS Router Resources in Kubernetes

Recommendations and considerations for application pods

routerkubernetes

Self-hosting the is limited to GraphOS Enterprise plans. Other plan types use managed cloud routing with GraphOS. Check out the pricing page to learn more.

Determining the correct resource requests and limits for your application pods in a Kubernetes system is not an exact science. Your specific needs depend on many factors, including:

  • The cardinality of unique shapes
  • The latency of underlying and s
  • The size of responses
  • The complexity of s

Our general recommendation for Kubernetes is to start with these requests and limits:

resources:
requests:
memory: '1G'
cpu: '1000m'
limits:
memory: '2G'
# no CPU limit to avoid throttling

💡 TIP

The router resource estimator is a helpful tool for getting a starting baseline for what resources you may need in production based on your expected traffic.

When using Horizontal pod autoscaling, we recommend targeting 90% utilization:

metrics:
- type: Resource
resource:
name: cpu
target:
type: Utilization
averageUtilization: 90
- type: Resource
resource:
name: memory
target:
type: Utilization
averageUtilization: 90

The GraphOS Router starts up quickly, but when using Managed Federation, the has to fetch the from Apollo Uplink before it can start serving traffic. We recommend measuring your router's startup time and lowering the averageUtilization if your startup time is longer due to Uplink latency or the size of your supergraph schema.

Next
Home
Rate articleRateEdit on GitHubEditForumsDiscord

© 2024 Apollo Graph Inc., d/b/a Apollo GraphQL.

Privacy Policy

Company