apiVersion: v1
data:
_example: '################################
# #
# EXAMPLE CONFIGURATION #
# #
################################
# This block is not actually functional configuration,
# but serves to illustrate the available configuration
# options and document them in a way that is accessible
# to users that `kubectl edit` this config map.
#
# These sample configuration options may be copied out of
# this example block and unindented to be in the data block
# to actually change the configuration.
# revision-timeout-seconds contains the default number of
# seconds to use for the revision''s per-request timeout, if
# none is specified.
revision-timeout-seconds: "300" # 5 minutes
# 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.
max-revision-timeout-seconds: "600" # 10 minutes
# 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.
revision-cpu-request: "400m" # 0.4 of a CPU (aka 400 milli-CPU)
# 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.
revision-memory-request: "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.
revision-ephemeral-storage-request: "500M" # 500 megabytes of storage
# 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.
revision-cpu-limit: "1000m" # 1 CPU (aka 1000 milli-CPU)
# 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.
revision-memory-limit: "200M" # 200 megabytes of memory
# 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.
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.
container-name-template: "user-container"
# 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.
container-concurrency: "0"
# 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".
container-concurrency-max-limit: "1000"
# allow-container-concurrency-zero controls whether users can
# specify 0 (i.e. unbounded) for containerConcurrency.
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: https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/#accessing-the-service
#
# 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 https://github.com/knative/serving/issues/8498.
enable-service-links: "false"
'
kind: ConfigMap
metadata:
annotations:
knative.dev/example-checksum: cdabec96
kubectl.kubernetes.io/last-applied-configuration: '{"apiVersion":"v1","data":{"_example":"################################\n# #\n# EXAMPLE
CONFIGURATION #\n# #\n################################\n\n#
This block is not actually functional configuration,\n# but serves to illustrate
the available configuration\n# options and document them in a way that is accessible\n#
to users that `kubectl edit` this config map.\n#\n# These sample configuration
options may be copied out of\n# this example block and unindented to be in the
data block\n# to actually change the configuration.\n\n# revision-timeout-seconds
contains the default number of\n# seconds to use for the revision''s per-request
timeout, if\n# none is specified.\nrevision-timeout-seconds: \"300\" # 5 minutes\n\n#
max-revision-timeout-seconds contains the maximum number of\n# seconds that
can be used for revision-timeout-seconds.\n# This value must be greater than
or equal to revision-timeout-seconds.\n# If omitted, the system default is used
(600 seconds).\n#\n# If this value is increased, the activator''s terminationGraceTimeSeconds\n#
should also be increased to prevent in-flight requests being disrupted.\nmax-revision-timeout-seconds:
\"600\" # 10 minutes\n\n# revision-cpu-request contains the cpu allocation
to assign\n# to revisions by default. If omitted, no value is specified\n#
and the system default is used.\n# Below is an example of setting revision-cpu-request.\n#
By default, it is not set by Knative.\nrevision-cpu-request: \"400m\" # 0.4
of a CPU (aka 400 milli-CPU)\n\n# revision-memory-request contains the memory
allocation to assign\n# to revisions by default. If omitted, no value is specified\n#
and the system default is used.\n# Below is an example of setting revision-memory-request.\n#
By default, it is not set by Knative.\nrevision-memory-request: \"100M\" #
100 megabytes of memory\n\n# revision-ephemeral-storage-request contains the
ephemeral storage\n# allocation to assign to revisions by default. If omitted,
no value is\n# specified and the system default is used.\nrevision-ephemeral-storage-request:
\"500M\" # 500 megabytes of storage\n\n# revision-cpu-limit contains the cpu
allocation to limit\n# revisions to by default. If omitted, no value is specified\n#
and the system default is used.\n# Below is an example of setting revision-cpu-limit.\n#
By default, it is not set by Knative.\nrevision-cpu-limit: \"1000m\" # 1 CPU
(aka 1000 milli-CPU)\n\n# revision-memory-limit contains the memory allocation
to limit\n# revisions to by default. If omitted, no value is specified\n# and
the system default is used.\n# Below is an example of setting revision-memory-limit.\n#
By default, it is not set by Knative.\nrevision-memory-limit: \"200M\" # 200
megabytes of memory\n\n# revision-ephemeral-storage-limit contains the ephemeral
storage\n# allocation to limit revisions to by default. If omitted, no value
is\n# specified and the system default is used.\nrevision-ephemeral-storage-limit:
\"750M\" # 750 megabytes of storage\n\n# container-name-template contains a
template for the default\n# container name, if none is specified. This field
supports\n# Go templating and is supplied with the ObjectMeta of the\n# enclosing
Service or Configuration, so values such as\n# {{.Name}} are also valid.\ncontainer-name-template:
\"user-container\"\n\n# container-concurrency specifies the maximum number\n#
of requests the Container can handle at once, and requests\n# above this threshold
are queued. Setting a value of zero\n# disables this throttling and lets through
as many requests as\n# the pod receives.\ncontainer-concurrency: \"0\"\n\n#
The container concurrency max limit is an operator setting ensuring that\n#
the individual revisions cannot have arbitrary large concurrency\n# values,
or autoscaling targets. `container-concurrency` default setting\n# must be at
or below this value.\n#\n# Must be greater than 1.\n#\n# Note: even with this
set, a user can choose a containerConcurrency\n# of 0 (i.e. unbounded) unless
allow-container-concurrency-zero is\n# set to \"false\".\ncontainer-concurrency-max-limit:
\"1000\"\n\n# allow-container-concurrency-zero controls whether users can\n#
specify 0 (i.e. unbounded) for containerConcurrency.\nallow-container-concurrency-zero:
\"true\"\n\n# enable-service-links specifies the default value used for the\n#
enableServiceLinks field of the PodSpec, when it is omitted by the user.\n#
See: https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/#accessing-the-service\n#\n#
This is a tri-state flag with possible values of (true|false|default).\n#\n#
In environments with large number of services it is suggested\n# to set this
value to `false`.\n# See https://github.com/knative/serving/issues/8498.\nenable-service-links:
\"false\"\n"},"kind":"ConfigMap","metadata":{"annotations":{"knative.dev/example-checksum":"cdabec96"},"labels":{"serving.knative.dev/release":"v0.24.0"},"name":"config-defaults","namespace":"knative-serving","ownerReferences":[{"apiVersion":"operator.knative.dev/v1alpha1","blockOwnerDeletion":true,"controller":true,"kind":"KnativeServing","name":"knative-serving","uid":"5162f181-a47b-4465-a388-ee8a99ad290e"}]}}
'
creationTimestamp: '2021-08-30T18:59:53Z'
labels:
serving.knative.dev/release: v0.24.0
managedFields:
- apiVersion: v1
fieldsType: FieldsV1
fieldsV1:
f:data:
.: {}
f:_example: {}
f:metadata:
f:annotations:
.: {}
f:knative.dev/example-checksum: {}
f:kubectl.kubernetes.io/last-applied-configuration: {}
f:labels:
.: {}
f:serving.knative.dev/release: {}
f:ownerReferences:
.: {}
k:{"uid":"5162f181-a47b-4465-a388-ee8a99ad290e"}:
.: {}
f:apiVersion: {}
f:blockOwnerDeletion: {}
f:controller: {}
f:kind: {}
f:name: {}
f:uid: {}
manager: manifestival
operation: Update
time: '2021-08-30T19:00:06Z'
name: config-defaults
namespace: knative-serving
ownerReferences:
- apiVersion: operator.knative.dev/v1alpha1
blockOwnerDeletion: true
controller: true
kind: KnativeServing
name: knative-serving
uid: 5162f181-a47b-4465-a388-ee8a99ad290e
resourceVersion: '6551'
uid: c1b147ff-92c8-497b-ac1c-5780b92c8fc2