Operator configuration field map

This is an entry reference to the documented KnativeServing and KnativeEventing configuration fields, not a complete generated API schema. Operator v1.24.0's Serving CRD and Eventing CRD are namespaced and serve/store only operator.knative.dev/v1beta1; the Helm CRD templates agree. Examples in the linked collections use this API. Check the CRD installed by your Operator release for the complete schema, for example with kubectl explain knativeserving.spec or kubectl explain knativeeventing.spec.

ConfigMap mapping

The Operator propagates spec.config values from the custom resource to system ConfigMaps. Manual updates to those managed ConfigMaps are overwritten by reconciliation.

For a ConfigMap named config-<name>, Operator v1.24 accepts either the full ConfigMap name (config-<name>) or the shortened name (<name>) under spec.config. It checks the full-name entry first, then the shortened entry only if the full entry is absent. If both are present, it selects the full entry; it does not merge their data. Prefer one naming form per ConfigMap to avoid conflicting configuration. The nested values become ConfigMap data. UpdateConfigMap writes the selected entry's supplied keys over the existing manifest data, retaining manifest keys not supplied by that entry; this does not merge the full and shortened CR entries. This lookup and update are implemented by the v1.24 ConfigMap transforms.

For example, domain and config-domain both address config-domain. Eventing's Broker Channel example uses the full name config-br-default-channel; br-default-channel is its shortened form. For names without a config- prefix, use the full name, such as Eventing's default-ch-webhook.

To change the Serving autoscaler's soft concurrency default, use the bounded cluster-default concurrency procedure; the Serving concurrency reference defines the setting and its precedence. Consult the component's configuration documentation for the keys, valid values, defaults, and interactions; the Operator does not define those settings independently.

In a local-cluster installation, the ConfigMaps are in the custom resource's namespace. For example, a KnativeServing resource in knative-serving manages Serving ConfigMaps in that namespace. Remote-cluster deployment has additional prerequisites and scope; see multi-cluster deployment.

The following example supplies values for two ConfigMaps:

apiVersion: operator.knative.dev/v1beta1
kind: KnativeServing
metadata:
  name: knative-serving
  namespace: knative-serving
spec:
  config:
    domain:
      example.org: |
        selector:
          app: prod
      example.com: ""
    autoscaler:
      stable-window: "60s"

Here, domain maps to config-domain, and autoscaler maps to config-autoscaler. The values illustrate configuration, not a recommendation for every installation. To apply a change, use Configure Knative by using the Operator.

Component field destinations

Field or section	Scope and lookup destination
spec.version	Component release selection. See Serving version configuration, Eventing version configuration, and supported component versions. For an existing installation, follow Operator upgrades.
spec.manifests, spec.additionalManifests	Replacement or additional installation manifests. See Serving custom manifests and Eventing custom manifests.
spec.registry	System image templates, overrides, and pull secrets. See Serving registry settings and Eventing container identifiers. These are not application image settings.
spec.controller-custom-certs	Serving controller registry certificate selection: name identifies the ConfigMap or Secret; type is ConfigMap or Secret. See controller certificates.
spec.ingress	Serving networking implementation settings. See Serving networking configuration.
spec.defaultBrokerClass	Eventing default Broker class. See default Broker class configuration.
spec.high-availability	Replica configuration for managed component workloads and related HPA interactions. See Serving or Eventing.
spec.workloads	Named system workload overrides, including resources and scheduling. See Serving or Eventing.
spec.services	Named system Service labels, annotations, and selectors. See Serving or Eventing.
spec.podDisruptionBudgets	Named PDB minAvailable override. See Serving or Eventing.
spec.clusterProfileRef	Remote-cluster target, available starting with Operator v1.22; immutable after creation. See multi-cluster deployment.

The linked collections retain the detailed examples and constraints. Do not treat a partial example as a complete replacement for your existing custom resource.