Este contenido no está disponible en el idioma seleccionado.
Chapter 16. Tuning serving configuration
16.1. Overriding Knative Serving system deployment configurations
				You can override the default configurations for some specific deployments by modifying the workloads spec in the KnativeServing custom resources (CRs).
			
16.1.1. Overriding system deployment configurations
					Currently, overriding default configuration settings is supported for the resources, replicas, labels, annotations, and nodeSelector fields, as well as for the readiness and liveness fields for probes.
				
					In the following example, a KnativeServing CR overrides the webhook deployment so that:
				
- 
							The readinessprobe timeout fornet-kourier-controlleris set to be 10 seconds.
- The deployment has specified CPU and memory resource limits.
- The deployment has 3 replicas.
- 
							The example-label: labellabel is added.
- 
							The example-annotation: annotationannotation is added.
- 
							The nodeSelectorfield is set to select nodes with thedisktype: hddlabel.
						The KnativeServing CR label and annotation settings override the deployment’s labels and annotations for both the deployment itself and the resulting pods.
					
KnativeServing CR example
- 1
- You can use thereadinessandlivenessprobe overrides to override all fields of a probe in a container of a deployment as specified in the Kubernetes API except for the fields related to the probe handler:exec,grpc,httpGet, andtcpSocket.