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.
# ingress.class specifies the default ingress class
# to use when not dictated by Route annotation.
#
# If not specified, will use the Istio ingress.
#
# Note that changing the Ingress class of an existing Route
# will result in undefined behavior. Therefore it is best to only
# update this value during the setup of Knative, to avoid getting
# undefined behavior.
ingress.class: "istio.ingress.networking.knative.dev"
# certificate.class specifies the default Certificate class
# to use when not dictated by Route annotation.
#
# If not specified, will use the Cert-Manager Certificate.
#
# Note that changing the Certificate class of an existing Route
# will result in undefined behavior. Therefore it is best to only
# update this value during the setup of Knative, to avoid getting
# undefined behavior.
certificate.class: "cert-manager.certificate.networking.knative.dev"
# domainTemplate specifies the golang text template string to use
# when constructing the Knative service''s DNS name. The default
# value is "{{.Name}}.{{.Namespace}}.{{.Domain}}".
#
# Valid variables defined in the template include Name, Namespace, Domain,
# Labels, and Annotations. Name will be the result of the tagTemplate
# below, if a tag is specified for the route.
#
# Changing this value might be necessary when the extra levels in
# the domain name generated is problematic for wildcard certificates
# that only support a single level of domain name added to the
# certificate''s domain. In those cases you might consider using a value
# of "{{.Name}}-{{.Namespace}}.{{.Domain}}", or removing the Namespace
# entirely from the template. When choosing a new value be thoughtful
# of the potential for conflicts - for example, when users choose to use
# characters such as `-` in their service, or namespace, names.
# {{.Annotations}} or {{.Labels}} can be used for any customization in the
# go template if needed.
# We strongly recommend keeping namespace part of the template to avoid
# domain name clashes:
# eg. ''{{.Name}}-{{.Namespace}}.{{ index .Annotations "sub"}}.{{.Domain}}''
# and you have an annotation {"sub":"foo"}, then the generated template
# would be {Name}-{Namespace}.foo.{Domain}
domainTemplate: "{{.Name}}.{{.Namespace}}.{{.Domain}}"
# tagTemplate specifies the golang text template string to use
# when constructing the DNS name for "tags" within the traffic blocks
# of Routes and Configuration. This is used in conjunction with the
# domainTemplate above to determine the full URL for the tag.
tagTemplate: "{{.Tag}}-{{.Name}}"
# Controls whether TLS certificates are automatically provisioned and
# installed in the Knative ingress to terminate external TLS connection.
# 1. Enabled: enabling auto-TLS feature.
# 2. Disabled: disabling auto-TLS feature.
autoTLS: "Disabled"
# Controls the behavior of the HTTP endpoint for the Knative ingress.
# It requires autoTLS to be enabled.
# 1. Enabled: The Knative ingress will be able to serve HTTP connection.
# 2. Disabled: The Knative ingress will reject HTTP traffic.
# 3. Redirected: The Knative ingress will send a 301 redirect for all
# http connections, asking the clients to use HTTPS.
httpProtocol: "Enabled"
# rolloutDuration contains the minimal duration in seconds over which the
# Configuration traffic targets are rolled out to the newest revision.
rolloutDuration: "0"
# autocreateClusterDomainClaims controls whether ClusterDomainClaims should
# be automatically created (and deleted) as needed when DomainMappings are
# reconciled.
#
# If this is "false" (the default), the cluster administrator is
# responsible for creating ClusterDomainClaims and delegating them to
# namespaces via their spec.Namespace field. This setting should be used in
# multitenant environments which need to control which namespace can use a
# particular domain name in a domain mapping.
#
# If this is "true", users are able to associate arbitrary names with their
# services via the DomainMapping feature.
autocreateClusterDomainClaims: "false"
# If true, networking plugins can add additional information to deployed
# applications to make their pods directly accessible via their IPs even if mesh
is
# enabled and thus direct-addressability is usually not possible.
# Consumers like Knative Serving can use this setting to adjust their behavior
# accordingly, i.e. to drop fallback solutions for non-pod-addressable systems.
#
# NOTE: This flag is in an alpha state and is mostly here to enable internal testing
# for now. Use with caution.
enable-mesh-pod-addressability: "false"
# Defines the scheme used for external URLs if autoTLS is not enabled.
# This can be used for making Knative report all URLs as "HTTPS" for example,
if you''re
# fronting Knative with an external loadbalancer that deals with TLS termination
and
# Knative doesn''t know about that otherwise.
defaultExternalScheme: "http"
'
ingress.class: kourier.ingress.networking.knative.dev
kind: ConfigMap
metadata:
annotations:
knative.dev/example-checksum: d38faef1
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# ingress.class specifies
the default ingress class\n# to use when not dictated by Route annotation.\n#\n#
If not specified, will use the Istio ingress.\n#\n# Note that changing the Ingress
class of an existing Route\n# will result in undefined behavior. Therefore
it is best to only\n# update this value during the setup of Knative, to avoid
getting\n# undefined behavior.\ningress.class: \"istio.ingress.networking.knative.dev\"\n\n#
certificate.class specifies the default Certificate class\n# to use when not
dictated by Route annotation.\n#\n# If not specified, will use the Cert-Manager
Certificate.\n#\n# Note that changing the Certificate class of an existing Route\n#
will result in undefined behavior. Therefore it is best to only\n# update this
value during the setup of Knative, to avoid getting\n# undefined behavior.\ncertificate.class:
\"cert-manager.certificate.networking.knative.dev\"\n\n# domainTemplate specifies
the golang text template string to use\n# when constructing the Knative service''s
DNS name. The default\n# value is \"{{.Name}}.{{.Namespace}}.{{.Domain}}\".\n#\n#
Valid variables defined in the template include Name, Namespace, Domain,\n#
Labels, and Annotations. Name will be the result of the tagTemplate\n# below,
if a tag is specified for the route.\n#\n# Changing this value might be necessary
when the extra levels in\n# the domain name generated is problematic for wildcard
certificates\n# that only support a single level of domain name added to the\n#
certificate''s domain. In those cases you might consider using a value\n# of
\"{{.Name}}-{{.Namespace}}.{{.Domain}}\", or removing the Namespace\n# entirely
from the template. When choosing a new value be thoughtful\n# of the potential
for conflicts - for example, when users choose to use\n# characters such as
`-` in their service, or namespace, names.\n# {{.Annotations}} or {{.Labels}}
can be used for any customization in the\n# go template if needed.\n# We strongly
recommend keeping namespace part of the template to avoid\n# domain name clashes:\n#
eg. ''{{.Name}}-{{.Namespace}}.{{ index .Annotations \"sub\"}}.{{.Domain}}''\n#
and you have an annotation {\"sub\":\"foo\"}, then the generated template\n#
would be {Name}-{Namespace}.foo.{Domain}\ndomainTemplate: \"{{.Name}}.{{.Namespace}}.{{.Domain}}\"\n\n#
tagTemplate specifies the golang text template string to use\n# when constructing
the DNS name for \"tags\" within the traffic blocks\n# of Routes and Configuration. This
is used in conjunction with the\n# domainTemplate above to determine the full
URL for the tag.\ntagTemplate: \"{{.Tag}}-{{.Name}}\"\n\n# Controls whether
TLS certificates are automatically provisioned and\n# installed in the Knative
ingress to terminate external TLS connection.\n# 1. Enabled: enabling auto-TLS
feature.\n# 2. Disabled: disabling auto-TLS feature.\nautoTLS: \"Disabled\"\n\n#
Controls the behavior of the HTTP endpoint for the Knative ingress.\n# It requires
autoTLS to be enabled.\n# 1. Enabled: The Knative ingress will be able to serve
HTTP connection.\n# 2. Disabled: The Knative ingress will reject HTTP traffic.\n#
3. Redirected: The Knative ingress will send a 301 redirect for all\n# http
connections, asking the clients to use HTTPS.\nhttpProtocol: \"Enabled\"\n\n#
rolloutDuration contains the minimal duration in seconds over which the\n# Configuration
traffic targets are rolled out to the newest revision.\nrolloutDuration: \"0\"\n\n#
autocreateClusterDomainClaims controls whether ClusterDomainClaims should\n#
be automatically created (and deleted) as needed when DomainMappings are\n#
reconciled.\n#\n# If this is \"false\" (the default), the cluster administrator
is\n# responsible for creating ClusterDomainClaims and delegating them to\n#
namespaces via their spec.Namespace field. This setting should be used in\n#
multitenant environments which need to control which namespace can use a\n#
particular domain name in a domain mapping.\n#\n# If this is \"true\", users
are able to associate arbitrary names with their\n# services via the DomainMapping
feature.\nautocreateClusterDomainClaims: \"false\"\n\n# If true, networking
plugins can add additional information to deployed\n# applications to make their
pods directly accessible via their IPs even if mesh is\n# enabled and thus direct-addressability
is usually not possible.\n# Consumers like Knative Serving can use this setting
to adjust their behavior\n# accordingly, i.e. to drop fallback solutions for
non-pod-addressable systems.\n#\n# NOTE: This flag is in an alpha state and
is mostly here to enable internal testing\n# for now. Use with caution.\nenable-mesh-pod-addressability:
\"false\"\n\n# Defines the scheme used for external URLs if autoTLS is not enabled.\n#
This can be used for making Knative report all URLs as \"HTTPS\" for example,
if you''re\n# fronting Knative with an external loadbalancer that deals with
TLS termination and\n# Knative doesn''t know about that otherwise.\ndefaultExternalScheme:
\"http\"\n","ingress.class":"kourier.ingress.networking.knative.dev"},"kind":"ConfigMap","metadata":{"annotations":{"knative.dev/example-checksum":"d38faef1"},"labels":{"serving.knative.dev/release":"v0.24.0"},"name":"config-network","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:ingress.class: {}
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:07Z'
name: config-network
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: '6597'
uid: 7f9911fb-2a08-484d-93f6-1fdb7354cea5