Configuring the Defaults ConfigMap

This ConfigMap is located in the knative-serving namespace.

You can view the current config-defaults ConfigMap by running the following command:

apiVersion:  v1
kind:  ConfigMap
metadata:
  name:  config-defaults
  namespace:  knative-serving
data:
  revision-timeout-seconds: "300"
  max-revision-timeout-seconds: "600"
  revision-cpu-request: "400m"
  revision-memory-request: "100M"
  revision-ephemeral-storage-request: "500M"
  revision-cpu-limit: "1000m"
  revision-memory-limit: "200M"
  revision-ephemeral-storage-limit: "750M"
  container-name-template: "user-container"
  container-concurrency: "0"
  container-concurrency-max-limit: "1000"
  allow-container-concurrency-zero: "true"
  enable-service-links: "false"

See below for a description of each property.

Properties

revision-timeout-seconds contains the default number of seconds to use for the revision’s per-request timeout, if none is specified.

Key: revision-timeout-seconds

Default: "300" (5 minutes)

Example:

apiVersion:  v1
kind:  ConfigMap
  name:  config-defaults
  namespace:  knative-serving
data:
  revision-timeout-seconds: "300" # 5 minutes

Max Revision Timeout Seconds

max-revision-timeout-seconds contains the maximum number of seconds that can be used for revision-timeout-seconds. This value must be greater than or equal to revision-timeout-seconds. If omitted, the system default is used (600 seconds).

If this value is increased, the activator’s terminationGraceTimeSeconds should also be increased to prevent in-flight requests being disrupted.

Key: max-revision-timeout-seconds

Default: "600" (10 minutes)

Example:

apiVersion:  v1
kind:  ConfigMap
metadata:
  name:  config-defaults
  namespace:  knative-serving
data:
  max-revision-timeout-seconds: "600" # 10 minutes

Revision Cpu Request

revision-cpu-request contains the cpu allocation to assign to revisions by default. If omitted, no value is specified and the system default is used. Below is an example of setting revision-cpu-request. By default, it is not set by Knative.

Key: revision-cpu-request

Default: "400m" (0.4 of a CPU (aka 400 milli-CPU))

Example:

kind:  ConfigMap
metadata:
  name:  config-defaults
  namespace:  knative-serving
data:
  revision-cpu-request: "400m" # 0.4 of a CPU (aka 400 milli-CPU)

Revision Memory Request

revision-memory-request contains the memory allocation to assign to revisions by default. If omitted, no value is specified and the system default is used. Below is an example of setting revision-memory-request. By default, it is not set by Knative.

Key: revision-memory-request

Default: "100M" (100 megabytes of memory)

revision-ephemeral-storage-request contains the ephemeral storage allocation to assign to revisions by default. If omitted, no value is specified and the system default is used.

Key: revision-ephemeral-storage-request

Default: "500M" (500 megabytes of storage)

Example:

apiVersion:  v1
kind:  ConfigMap
metadata:
  name:  config-defaults
  namespace:  knative-serving
data:
  revision-ephemeral-storage-request: "500M" # 500 megabytes of storage

Revision Cpu Limit

revision-cpu-limit contains the cpu allocation to limit revisions to by default. If omitted, no value is specified and the system default is used. Below is an example of setting revision-cpu-limit. By default, it is not set by Knative.

Key: revision-cpu-limit

Default: "1000m" (1 CPU (aka 1000 milli-CPU))

Example:

apiVersion:  v1
kind:  ConfigMap
metadata:
  name:  config-defaults
  namespace:  knative-serving
data:
  revision-cpu-limit: "1000m" # 1 CPU (aka 1000 milli-CPU)

Revision Memory Limit

revision-memory-limit contains the memory allocation to limit revisions to by default. If omitted, no value is specified and the system default is used. Below is an example of setting revision-memory-limit. By default, it is not set by Knative.

Key: revision-memory-limit

Default: "200M" (200 megabytes of memory)

Example:

apiVersion:  v1
kind:  ConfigMap
metadata:
  name:  config-defaults
data:
  revision-memory-limit: "200M" # 200 megabytes of memory

Revision Ephemeral Storage Limit

revision-ephemeral-storage-limit contains the ephemeral storage allocation to limit revisions to by default. If omitted, no value is specified and the system default is used.

Key: revision-ephemeral-storage-limit

Default: "750M" (750 megabytes of storage)

Example:

apiVersion:  v1
kind:  ConfigMap
metadata:
  name:  config-defaults
data:
  revision-ephemeral-storage-limit: "750M" # 750 megabytes of storage

container-name-template contains a template for the default container name, if none is specified. This field supports Go templating and is supplied with the ObjectMeta of the enclosing Service or Configuration, so values such as {{.Name}} are also valid.

Key: container-name-template

Default: "user-container"

Container Concurrency

container-concurrency specifies the maximum number of requests the Container can handle at once, and requests above this threshold are queued. Setting a value of zero disables this throttling and lets through as many requests as the pod receives.

Key: container-concurrency

Default: "0"

Example:

apiVersion:  v1
kind:  ConfigMap
metadata:
  name:  config-defaults
  namespace:  knative-serving
data:
  container-concurrency: "0"

Container Concurrency Max Limit

The container concurrency max limit is an operator setting ensuring that the individual revisions cannot have arbitrary large concurrency values, or autoscaling targets. container-concurrency default setting must be at or below this value.

Must be greater than 1.

Note: even with this set, a user can choose a containerConcurrency of 0 (i.e. unbounded) unless allow-container-concurrency-zero is set to “false”.

Key: container-concurrency-max-limit

Default: "1000"

Example:

apiVersion:  v1
kind:  ConfigMap
metadata:
  name:  config-defaults
  namespace:  knative-serving
data:
  container-concurrency-max-limit: "1000"

Allow Container Concurrency Zero

allow-container-concurrency-zero controls whether users can specify 0 (i.e. unbounded) for containerConcurrency.

Key: allow-container-concurrency-zero

Default: "true"

Example:

apiVersion:  v1
kind:  ConfigMap
metadata:
  name:  config-defaults
  namespace:  knative-serving
data:
  allow-container-concurrency-zero: "true"

enable-service-links specifies the default value used for the enableServiceLinks field of the PodSpec, when it is omitted by the user. See the Kubernetes Documentation for the enableServiceLinks Feature.

This is a tri-state flag with possible values of (true|false|default).

In environments with large number of services it is suggested to set this value to false. See .

Key: enable-service-links

Default: "false"

apiVersion:  v1
kind:  ConfigMap
metadata:
  name:  config-defaults
  namespace:  knative-serving
data: