apiVersion: operator.knative.dev/v1beta1
kind: KnativeServing
metadata:
name: knative-serving
namespace: knative-serving
spec:
workloads:
- name: net-kourier-controller
env:
- container: controller
envVars:
- name: KUBE_API_BURST
value: "200" (1)
- name: KUBE_API_QPS
value: "200" (2)- Documentation
- Red Hat OpenShift Serverless
- Serving
- Configuring burst and QPS for net-kourier history bug_report picture_as_pdf
- About Serverless
- Installing Serverless
- Preparing to install OpenShift Serverless
- Installing the Serverless Operator
- Installing the Knative CLI
- Installing Knative Serving
- Installing Knative Eventing
- Configuring Knative for Apache Kafka
- Configuring kube-rbac-proxy resources for Knative for Apache Kafka
- Configuring Serverless Functions
- Serverless upgrades
- Functions
- Getting started with functions
- Creating functions
- Running functions locally
- Deploying functions
- Building functions
- Listing existing functions
- Invoking functions
- Deleting functions
- Building and deploying functions on the cluster
- Connecting an event source to a function
- Subscribing functions to CloudEvents
- Functions development reference guide
- Configuring functions
- Serving
- Getting started with Knative Serving
- Autoscaling
- Configuring Serverless applications
- Debugging Serverless applications
- Kourier and Istio ingresses
- Traffic splitting
- External and Ingress routing
- Routing overview
- Customizing labels and annotations
- Configuring routes for Knative services
- Global HTTPS redirection
- URL scheme for external routes
- HTTPS redirection per service
- Cluster local availability
- Kourier Gateway service type
- Using HTTP2 and gRPC
- Using Serving with OpenShift ingress sharding
- Configuring access to Knative services
- Configuring kube-rbac-proxy resources for Serving
- Configuring burst and QPS for net-kourier
- Configuring custom domains for Knative services
- High availability configuration for Knative Serving
- Tuning serving configuration
- Configuring Queue Proxy resources
- Eventing
- Knative CLI
- Observability
- Integrations
- Removing Serverless
×
Configuring burst and QPS for net-kourier
The queries per second (QPS) and burst values determine the frequency of requests or API calls to the API server.
Configuring burst and QPS values for net-kourier
The queries per second (QPS) value determines the number of client requests or API calls that are sent to the API server.
The burst value determines how many requests from the client can be stored for processing. Requests exceeding this buffer will be dropped. This is helpful for controllers that are bursty and do not spread their requests uniformly in time.
When the net-kourier-controller restarts, it parses all ingress resources deployed on the cluster, which leads to a significant number of API calls. Due to this, the net-kourier-controller can take a long time to start.
You can adjust the QPS and burst values for the net-kourier-controller in the KnativeServing CR:
KnativeServing CR example
| 1 | The QPS rate of communication between controller and the API Server. The default value is 200. |
| 2 | The burst capacity of communication between Kubelet and the API Server. The default value is 200. |