Camel K API

camel.apache.org/v1

Build

Refer to the Kubernetes API documentation for the fields of the metadata field.

camel.apache.org/v1

CamelCatalog

Refer to the Kubernetes API documentation for the fields of the metadata field.

the actual state of the catalog

the desired state of the catalog

camel.apache.org/v1

Integration

Refer to the Kubernetes API documentation for the fields of the metadata field.

the desired Integration specification

the status of the Integration

camel.apache.org/v1

IntegrationKit

Refer to the Kubernetes API documentation for the fields of the metadata field.

the desired configuration

the actual status

camel.apache.org/v1

IntegrationPlatform

Refer to the Kubernetes API documentation for the fields of the metadata field.

(Members of RawMessage are embedded into this type.)

Generic raw message, typically a map containing the keys (trait parameters) and the values (either single text or array)

the identification (GAV for maven dependencies or file name for other file types)

where it is located in the builder Pod

the expected location in the runtime

a checksum (SHA1) of the content

name of the task

Type of integration condition.

Status of the condition, one of True, False, Unknown.

The last time this condition was updated.

Last time the condition transitioned from one status to another.

The reason for the condition’s last transition.

A human-readable message indicating details about the transition.

The sequence of Build tasks to be performed as part of the Build execution.

The strategy that should be used to perform the Build.

Timeout defines the Build maximum execution duration. The Build deadline is set to the Build start time plus the Timeout duration. If the Build deadline is exceeded, the Build context is canceled, and its phase set to BuildPhaseFailed.

ObservedGeneration is the most recent generation observed for this Build.

describes the phase

the image name built

the digest from image

the base image used for this build

a list of artifacts contained in the build

the error description (if any)

the reason of the failure (if any)

the time when it started

a list of conditions occurred during the build

how long it took for the build Change to Duration / ISO 8601 when CRD uses OpenAPI spec v3 https://github.com/OAI/OpenAPI-Specification/issues/845

(Members of BaseTask are embedded into this type.)

(Members of PublishTask are embedded into this type.)

The platform of build image

log more information

docker image to use

(Members of BaseTask are embedded into this type.)

the base image layer

the configuration required for the runtime application

the list of dependencies to use for this build

the list of steps to execute (see pkg/builder/)

the configuration required by Maven for the application build phase

workspace directory to use

(Members of CamelArtifactDependency are embedded into this type.)

Base Camel Artifact dependency

accepted URI schemes

accepted languages

accepted data formats

required dependencies

the Java types used by the artifact feature (ie, component, data format, …​)

(Members of MavenArtifact are embedded into this type.)

the maven dependency

provide a list of artifacts to exclude for this dependency

Maven Group

Maven Artifact

the runtime targeted for the catalog

artifacts required by this catalog

loaders required by this catalog

(Members of MavenArtifact are embedded into this type.)

the base Maven artifact required

a list of DSLs supported

a list of additional dependencies required beside the base one

the ID (ie, timer in a timer:xyz URI)

is a passive scheme

is a HTTP based scheme

required scope for consumer

required scope for producers

list of dependencies needed for this scope

represents the type of configuration, ie: property, configmap, secret, …​

the value to assign to the configuration (syntax may vary depending on the Type)

the name of the specification

the path where the file is stored

the source code (plain text)

the source code (binary)

the confimap reference holding the source content

the confimap key holding the source content

the content type (tipically text or binary)

if the content is compressed (base64 encrypted)

a short text specifying the reason

the time when the failure has happened

the recovery attempted for this failure

attempt number

maximum number of attempts

(Optional)

time of the attempt execution

(Members of RawMessage are embedded into this type.)

Type of integration condition.

Status of the condition, one of True, False, Unknown.

The last time this condition was updated.

Last time the condition transitioned from one status to another.

First time the condition status transitioned to True.

The reason for the condition’s last transition.

A human-readable message indicating details about the transition.

Type of integration condition.

Status of the condition, one of True, False, Unknown.

The last time this condition was updated.

Last time the condition transitioned from one status to another.

The reason for the condition’s last transition.

A human-readable message indicating details about the transition.

the container image as identified in the container registry

a list of Camel dependecies used by this kit

the profile which is expected by this kit

traits that the kit will execute

Deprecated: Use camel trait (camel.properties) to manage properties Use mount trait (mount.configs) to manage configs Use mount trait (mount.resources) to manage resources Use mount trait (mount.volumes) to manage volumes configuration used by the kit

Maven repositories that can be used by the kit

ObservedGeneration is the most recent generation observed for this IntegrationKit.

phase of the kit

base image used by the kit

actual image name of the kit

actual image digest of the kit

list of artifacts used by the kit

failure reason (if any)

the runtime version for which this kit was configured

the runtime provider for which this kit was configured

the platform for which this kit was configured

the Camel K operator version for which this kit was configured

a list of conditions which happened for the events related the kit

The builder trait is internally used to determine the best strategy to build and configure IntegrationKits.

The Camel trait sets up Camel configuration.

The Quarkus trait configures the Quarkus runtime. It’s enabled by default. NOTE: Compiling to a native executable, i.e. when using package-type=native, is only supported for kamelets, as well as YAML and XML integrations. It also requires at least 4GiB of memory, so the Pod running the native build, that is either the operator Pod, or the build Pod (depending on the build strategy configured for the platform), must have enough memory available.

The Registry trait sets up Maven to use the Image registry as a Maven repository.

The collection of addon trait configurations

the strategy to adopt for building an Integration base image

the strategy to adopt for publishing an Integration base image

the Camel K Runtime dependency version

the runtime used. Likely Camel Quarkus (we used to have main runtime which has been discontinued since version 1.5)

a base image that can be used as base layer for all images. It can be useful if you want to provide some custom base image with further utility softwares

the image registry used to push/pull Integration images

how much time to wait before time out the build process

Maven configuration used to build the Camel/Camel-Quarkus applications

Generic options that can used by each publish strategy

Type of integration condition.

Status of the condition, one of True, False, Unknown.

The last time this condition was updated.

Last time the condition transitioned from one status to another.

The reason for the condition’s last transition.

A human-readable message indicating details about the transition.

the remote repository in the format github:ORG/REPO/PATH_TO_KAMELETS_FOLDER

remote repository used to retrieve Kamelet catalog

what kind of cluster you’re running (ie, plain Kubernetes or OpenShift)

the profile you wish to use. It will apply certain traits which are required by the specific profile chosen. It usually relates the Cluster with the optional definition of special profiles (ie, Knative)

specify how to build the Integration/IntegrationKits

list of traits to be executed for all the Integration/IntegrationKits built from this IntegrationPlatform

Deprecated: Use camel trait (camel.properties) to manage properties Use mount trait (mount.configs) to manage configs Use mount trait (mount.resources) to manage resources Use mount trait (mount.volumes) to manage volumes list of configuration properties to be attached to all the Integration/IntegrationKits built from this IntegrationPlatform

configuration to be executed to all Kamelets controlled by this IntegrationPlatform

(Members of IntegrationPlatformSpec are embedded into this type.)

ObservedGeneration is the most recent generation observed for this IntegrationPlatform.

defines in what phase the IntegrationPlatform is found

which are the conditions met (particularly useful when in ERROR phase)

the Camel K operator version controlling this IntegrationPlatform

generic information related to the build of Camel K operator software

the number of Pods needed for the running Integration

the sources which contain the Camel routes to run

a source in YAML DSL language which contain the routes to run

the reference of the IntegrationKit which is used for this Integration

the list of Camel or Maven dependencies required by the Integration

the profile needed to run this Integration

the traits needed to run this Integration

Pod template customization

Deprecated: Use camel trait (camel.properties) to manage properties Use mount trait (mount.configs) to manage configs Use mount trait (mount.resources) to manage resources Use mount trait (mount.volumes) to manage volumes

additional Maven repositories to be used

custom SA to use for the Integration

ObservedGeneration is the most recent generation observed for this Integration.

the actual phase

the digest calculated for this Integration

the container image used

a list of dependencies needed by the application

the profile needed to run this Integration

the reference of the IntegrationKit which is used for this Integration

The IntegrationPlatform watching this Integration

a list of sources generated for this Integration

the runtime version targeted for this Integration

the runtime provider targeted for this Integration

Deprecated: a list of configuration specification

a list of events happened for the Integration

the operator version

the number of replicas

label selector

features offered by the Integration

the timestamp representing the last time when this integration was initialized.

(Members of BaseTask are embedded into this type.)

(Members of PublishTask are embedded into this type.)

log more information

use a cache

docker image to use

true if a cache is enabled

the PVC used to store the cache

Maven Group

Maven Artifact

Maven Version

(Members of MavenSpec are embedded into this type.)

base Maven specification

additional repositories

Servers (auth)

The path of the local Maven repository.

The Maven properties.

A reference to the ConfigMap or Secret key that contains the Maven settings.

A reference to the ConfigMap or Secret key that contains the security of the Maven settings.

The Secrets name and key, containing the CA certificate(s) used to connect to remote Maven repositories. It can contain X.509 certificates, and PKCS#7 formatted certificate chains. A JKS formatted keystore is automatically created to store the CA certificate(s), and configured to be used as a trusted certificate(s) by the Maven commands. Note that the root CA certificates are also imported into the created keystore.

The Maven build extensions. See https://maven.apache.org/guides/mini/guide-using-extensions.html.

The CLI options that are appended to the list of arguments for Maven commands, e.g., -V,--no-transfer-progress,-Dstyle.color=never. See https://maven.apache.org/ref/3.8.4/maven-embedder/cli.html.

Volumes

InitContainers

Containers

EphemeralContainers

RestartPolicy

TerminationGracePeriodSeconds

ActiveDeadlineSeconds

DNSPolicy

NodeSelector

TopologySpreadConstraints

PodSecurityContext

the specification

can be useful to share info with other tasks

base image layer

final image name

where to publish the final image

if the container registry is insecure (ie, http only)

the URI to access

the secret where credentials are stored

the configmap which stores the Certificate Authority

the registry organization

identifies the repository

name of the repository

location of the repository

can use snapshot

can use stable releases

is the policy activated or not

This element specifies how often updates should attempt to occur. Maven will compare the local POM’s timestamp (stored in a repository’s maven-metadata file) to the remote. The choices are: always, daily (default), interval:X (where X is an integer in minutes) or never

When Maven deploys files to the repository, it also deploys corresponding checksum files. Your options are to ignore, fail, or warn on missing or incorrect checksums.

(Members of DataSpec are embedded into this type.)

the content of the resource

the kind of data to expect

the mount path on destination Pod

Camel K Runtime version

Camel main application provider, ie, Camel Quarkus

application entry point (main) to be executed

list of dependencies needed to run the application

set of metadata

features offered by this runtime

(Members of BaseTask are embedded into this type.)

can be useful to share info with other tasks

used by the ImageStream

(Members of DataSpec are embedded into this type.)

contains configuration related to the source code

specify which is the language (Camel DSL) used to interpret this source code

Loader is an optional id of the org.apache.camel.k.RoutesLoader that will interpret this source at runtime

Interceptors are optional identifiers the org.apache.camel.k.RoutesLoader uses to pre/post process sources

Type defines the kind of source described by this object

List of property names defined in the source (e.g. if type is "template")

(Members of BaseTask are embedded into this type.)

(Members of PublishTask are embedded into this type.)

a BuilderTask (base task)

a BuildahTask, for Buildah strategy

a KanikoTask, for Kaniko strategy

a SpectrumTask, for Spectrum strategy

a S2iTask, for S2I strategy

(Members of RawMessage are embedded into this type.)

generic raw message, typically a map containing the keys (trait parameters) and the values (either single text or array)

TraitConfiguration parameters configuration

The configuration of Affinity trait

The configuration of Builder trait

The configuration of Camel trait

The configuration of Container trait

The configuration of Cron trait

The configuration of Dependencies trait

The configuration of Deployer trait

The configuration of Deployment trait

The configuration of Environment trait

The configuration of Error Handler trait

The configuration of GC trait

The configuration of Health trait

The configuration of Ingress trait

The configuration of Istio trait

The configuration of Jolokia trait

The configuration of JVM trait

The configuration of Kamelets trait

The configuration of Knative trait

The configuration of Knative Service trait

The configuration of Logging trait

The configuration of Mount trait

The configuration of OpenAPI trait

The configuration of Owner trait

The configuration of PDB trait

The configuration of Platform trait

The configuration of Pod trait

The configuration of Prometheus trait

The configuration of Pull Secret trait

The configuration of Quarkus trait

The configuration of Registry trait

The configuration of Route trait

The configuration of Service trait

The configuration of Service Binding trait

The configuration of Toleration trait

The extension point with addon traits

Deprecated: for backward compatibility.

Deprecated: for backward compatibility.

Deprecated: for backward compatibility.

Deprecated: for backward compatibility.

Deprecated: for backward compatibility.

Selects a key of a ConfigMap.

Selects a key of a secret.

(Members of Trait are embedded into this type.)

Always co-locates multiple replicas of the integration in the same node (default false).

Never co-locates multiple replicas of the integration in the same node (default false).

Defines a set of nodes the integration pod(s) are eligible to be scheduled on, based on labels on the node.

Defines a set of pods (namely those matching the label selector, relative to the given namespace) that the integration pod(s) should be co-located with.

Defines a set of pods (namely those matching the label selector, relative to the given namespace) that the integration pod(s) should not be co-located with.

(Members of Trait are embedded into this type.)

Enable verbose logging on build components that support it (e.g. Kaniko build pod).

A list of properties to be provided to the build task

(Members of Trait are embedded into this type.)

The camel-k-runtime version to use for the integration. It overrides the default version set in the Integration Platform.

A list of properties to be provided to the Integration runtime

(Members of RawMessage are embedded into this type.)

(Members of Trait are embedded into this type.)

To automatically enable the trait

The minimum amount of CPU required.

The minimum amount of memory required.

The maximum amount of CPU required.

The maximum amount of memory required.

Can be used to enable/disable exposure via kubernetes Service.

To configure a different port exposed by the container (default 8080).

To configure a different port name for the port exposed by the container. It defaults to http only when the expose parameter is true.

To configure under which service port the container port is to be exposed (default 80).

To configure under which service port name the container port is to be exposed (default http).

The main container name. It’s named integration by default.

The main container image

The pull policy: Always|Never|IfNotPresent

(Members of Trait are embedded into this type.)

The CronJob schedule for the whole integration. If multiple routes are declared, they must have the same schedule for this mechanism to work correctly.

A comma separated list of the Camel components that need to be customized in order for them to work when the schedule is triggered externally by Kubernetes. A specific customizer is activated for each specified component. E.g. for the timer component, the cron-timer customizer is activated (it’s present in the org.apache.camel.k:camel-k-cron library).

Supported components are currently: cron, timer and quartz.

Use the default Camel implementation of the cron endpoint (quartz) instead of trying to materialize the integration as Kubernetes CronJob.

Specifies how to treat concurrent executions of a Job. Valid values are: - "Allow": allows CronJobs to run concurrently; - "Forbid" (default): forbids concurrent runs, skipping next run if previous run hasn’t finished yet; - "Replace": cancels currently running job and replaces it with a new one

Automatically deploy the integration as CronJob when all routes are either starting from a periodic consumer (only cron, timer and quartz are supported) or a passive consumer (e.g. direct is a passive consumer).

It’s required that all periodic consumers have the same period, and it can be expressed as cron schedule (e.g. 1m can be expressed as 0/1 * * * *, while 35m or 50s cannot).

Optional deadline in seconds for starting the job if it misses scheduled time for any reason. Missed jobs executions will be counted as failed ones.

Specifies the duration in seconds, relative to the start time, that the job may be continuously active before it is considered to be failed. It defaults to 60s.

Specifies the number of retries before marking the job failed. It defaults to 2.

(Members of Trait are embedded into this type.)

(Members of Trait are embedded into this type.)

Allows to explicitly select the desired deployment kind between deployment, cron-job or knative-service when creating the resources for running the integration.

Use server-side apply to update the owned resources (default true). Note that it automatically falls back to client-side patching, if SSA is not available, e.g., on old Kubernetes clusters.

(Members of Trait are embedded into this type.)

The maximum time in seconds for the deployment to make progress before it is considered to be failed. It defaults to 60s.

The deployment strategy to use to replace existing pods with new ones.

The maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). Absolute number is calculated from percentage by rounding down. This can not be 0 if MaxSurge is 0. Defaults to 25%.

The maximum number of pods that can be scheduled above the desired number of pods. Value can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. Defaults to 25%.

(Members of Trait are embedded into this type.)

Enables injection of NAMESPACE and POD_NAME environment variables (default true)

Propagates the HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment variables (default true)

A list of environment variables to be added to the integration container. The syntax is KEY=VALUE, e.g., MY_VAR="my value". These take precedence over the previously defined environment variables.

(Members of Trait are embedded into this type.)

The error handler ref name provided or found in application properties

(Members of Trait are embedded into this type.)

Discovery client cache to be used, either disabled, disk or memory (default memory). Deprecated: to be removed from trait configuration.

(Members of Trait are embedded into this type.)

Configures the liveness probe for the integration container (default false).

Scheme to use when connecting to the liveness probe (default HTTP).

Number of seconds after the container has started before the liveness probe is initiated.

Number of seconds after which the liveness probe times out.

How often to perform the liveness probe.

Minimum consecutive successes for the liveness probe to be considered successful after having failed.

Minimum consecutive failures for the liveness probe to be considered failed after having succeeded.

Configures the readiness probe for the integration container (default true).

Scheme to use when connecting to the readiness probe (default HTTP).

Number of seconds after the container has started before the readiness probe is initiated.

Number of seconds after which the readiness probe times out.

How often to perform the readiness probe.

Minimum consecutive successes for the readiness probe to be considered successful after having failed.

Minimum consecutive failures for the readiness probe to be considered failed after having succeeded.

(Members of Trait are embedded into this type.)

To configure the host exposed by the ingress.

To automatically add an ingress whenever the integration uses an HTTP endpoint consumer.

(Members of Trait are embedded into this type.)

Configures a (comma-separated) list of CIDR subnets that should not be intercepted by the Istio proxy (10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 by default).

Forces the value for labels sidecar.istio.io/inject. By default the label is set to true on deployment and not set on Knative Service.

(Members of Trait are embedded into this type.)

Activates remote debugging, so that a debugger can be attached to the JVM, e.g., using port-forwarding

Suspends the target JVM immediately before the main class is loaded

Prints the command used the start the JVM in the container logs (default true)

Transport address at which to listen for the newly launched JVM (default *:5005)

A list of JVM options

Additional JVM classpath (use Linux classpath separator)

(Members of Trait are embedded into this type.)

The PEM encoded CA certification file path, used to verify client certificates, applicable when protocol is https and use-ssl-client-authentication is true (default /var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt for OpenShift).

The principal(s) which must be given in a client certificate to allow access to the Jolokia endpoint, applicable when protocol is https and use-ssl-client-authentication is true (default clientPrincipal=cn=system:master-proxy, cn=hawtio-online.hawtio.svc and cn=fuse-console.fuse.svc for OpenShift).

Listen for multicast requests (default false)

Mandate the client certificate contains a client flag in the extended key usage section, applicable when protocol is https and use-ssl-client-authentication is true (default true for OpenShift).

The Host address to which the Jolokia agent should bind to. If "*" or "0.0.0.0" is given, the servers binds to every network interface (default "*").

The password used for authentication, applicable when the user option is set.

The Jolokia endpoint port (default 8778).

The protocol to use, either http or https (default https for OpenShift)

The user to be used for authentication

Whether client certificates should be used for authentication (default true for OpenShift).

A list of additional Jolokia options as defined in JVM agent configuration options

(Members of Trait are embedded into this type.)

Automatically inject all referenced Kamelets and their default configuration (enabled by default)

Comma separated list of Kamelet names to load into the current integration

(Members of Trait are embedded into this type.)

Configures the Knative autoscaling class property (e.g. to set hpa.autoscaling.knative.dev or kpa.autoscaling.knative.dev autoscaling).

Refer to the Knative documentation for more information.

Configures the Knative autoscaling metric property (e.g. to set concurrency based or cpu based autoscaling).

Refer to the Knative documentation for more information.

Sets the allowed concurrency level or CPU percentage (depending on the autoscaling metric) for each Pod.

Refer to the Knative documentation for more information.

The minimum number of Pods that should be running at any time for the integration. It’s zero by default, meaning that the integration is scaled down to zero when not used for a configured amount of time.

Refer to the Knative documentation for more information.

An upper bound for the number of Pods that can be running in parallel for the integration. Knative has its own cap value that depends on the installation.

Refer to the Knative documentation for more information.

Enables to gradually shift traffic to the latest Revision and sets the rollout duration. It’s disabled by default and must be expressed as a Golang time.Duration string representation, rounded to a second precision.

Setting cluster-local, Knative service becomes a private service. Specifically, this option applies the networking.knative.dev/visibility label to Knative service.

Refer to the Knative documentation for more information.

Automatically deploy the integration as Knative service when all conditions hold:

(Members of Trait are embedded into this type.)

Can be used to inject a Knative complete configuration in JSON format.

List of channels used as source of integration routes. Can contain simple channel names or full Camel URIs.

List of channels used as destination of integration routes. Can contain simple channel names or full Camel URIs.

List of channels used as source of integration routes.

List of endpoints used as destination of integration routes. Can contain simple endpoint names or full Camel URIs.

List of event types that the integration will be subscribed to. Can contain simple event types or full Camel URIs (to use a specific broker different from "default").

List of event types that the integration will produce. Can contain simple event types or full Camel URIs (to use a specific broker).

Enables filtering on events based on the header "ce-knativehistory". Since this header has been removed in newer versions of Knative, filtering is disabled by default.

Allows binding the integration to a sink via a Knative SinkBinding resource. This can be used when the integration targets a single sink. It’s enabled by default when the integration targets a single sink (except when the integration is owned by a Knative source).

Enable automatic discovery of all trait properties.

(Members of Trait are embedded into this type.)

Colorize the log output

Logs message format

Adjust the logging level (defaults to INFO)

Output the logs in JSON

Enable "pretty printing" of the JSON logs

(Members of Trait are embedded into this type.)

A list of configuration pointing to configmap/secret. The configuration are expected to be UTF-8 resources as they are processed by runtime Camel Context and tried to be parsed as property files. They are also made available on the classpath in order to ease their usage directly from the Route. Syntax: [configmap|secret]:name[/key], where name represents the resource name and key optionally represents the resource key to be filtered

A list of resources (text or binary content) pointing to configmap/secret. The resources are expected to be any resource type (text or binary content). The destination path can be either a default location or any path specified by the user. Syntax: [configmap|secret]:name[/key][@path], where name represents the resource name, key optionally represents the resource key to be filtered and path represents the destination path

A list of Persistent Volume Claims to be mounted. Syntax: [pvcname:/container/path]

(Members of Trait are embedded into this type.)

The configmaps holding the spec of the OpenAPI

(Members of Trait are embedded into this type.)

The set of annotations to be transferred

The set of labels to be transferred

(Members of Trait are embedded into this type.)

The number of pods for the Integration that must still be available after an eviction. It can be either an absolute number or a percentage. Only one of min-available and max-unavailable can be specified.

The number of pods for the Integration that can be unavailable after an eviction. It can be either an absolute number or a percentage (default 1 if min-available is also not set). Only one of max-unavailable and min-available can be specified.

(Members of Trait are embedded into this type.)

To create a default (empty) platform when the platform is missing.

Indicates if the platform should be created globally in the case of global operator (default true).

To automatically detect from the environment if a default platform can be created (it will be created on OpenShift only).

(Members of Trait are embedded into this type.)

(Members of Trait are embedded into this type.)

Whether a PodMonitor resource is created (default true).

The PodMonitor resource labels, applicable when pod-monitor is true.

(Members of Trait are embedded into this type.)

The pull secret name to set on the Pod. If left empty this is automatically taken from the IntegrationPlatform registry configuration.

When using a global operator with a shared platform, this enables delegation of the system:image-puller cluster role on the operator namespace to the integration service account.

Automatically configures the platform registry secret on the pod if it is of type kubernetes.io/dockerconfigjson.

(Members of Trait are embedded into this type.)

The Quarkus package types, either fast-jar or native (default fast-jar). In case both fast-jar and native are specified, two IntegrationKit resources are created, with the native kit having precedence over the fast-jar one once ready. The order influences the resolution of the current kit for the integration. The kit corresponding to the first package type will be assigned to the integration in case no existing kit that matches the integration exists.

(Members of Trait are embedded into this type.)

(Members of Trait are embedded into this type.)

To configure the host exposed by the route.

The TLS termination type, like edge, passthrough or reencrypt.

Refer to the OpenShift route documentation for additional information.

The TLS certificate contents.

Refer to the OpenShift route documentation for additional information.

The secret name and key reference to the TLS certificate. The format is "secret-name[/key-name]", the value represents the secret name, if there is only one key in the secret it will be read, otherwise you can set a key name separated with a "/".

Refer to the OpenShift route documentation for additional information.

The TLS certificate key contents.

Refer to the OpenShift route documentation for additional information.

The secret name and key reference to the TLS certificate key. The format is "secret-name[/key-name]", the value represents the secret name, if there is only one key in the secret it will be read, otherwise you can set a key name separated with a "/".

Refer to the OpenShift route documentation for additional information.

The TLS CA certificate contents.

Refer to the OpenShift route documentation for additional information.

The secret name and key reference to the TLS CA certificate. The format is "secret-name[/key-name]", the value represents the secret name, if there is only one key in the secret it will be read, otherwise you can set a key name separated with a "/".

Refer to the OpenShift route documentation for additional information.

The destination CA certificate provides the contents of the ca certificate of the final destination. When using reencrypt termination this file should be provided in order to have routers use it for health checks on the secure connection. If this field is not specified, the router may provide its own destination CA and perform hostname validation using the short service name (service.namespace.svc), which allows infrastructure generated certificates to automatically verify.

Refer to the OpenShift route documentation for additional information.

The secret name and key reference to the destination CA certificate. The format is "secret-name[/key-name]", the value represents the secret name, if there is only one key in the secret it will be read, otherwise you can set a key name separated with a "/".

Refer to the OpenShift route documentation for additional information.

To configure how to deal with insecure traffic, e.g. Allow, Disable or Redirect traffic.

Refer to the OpenShift route documentation for additional information.

(Members of Trait are embedded into this type.)

List of Services in the form [[apigroup/]version:]kind:[namespace/]name

(Members of Trait are embedded into this type.)

To automatically detect from the code if a Service needs to be created.

Enable Service to be exposed as NodePort (default false). Deprecated: Use service type instead.

The type of service to be used, either 'ClusterIP', 'NodePort' or 'LoadBalancer'.

(Members of Trait are embedded into this type.)

The list of taints to tolerate, in the form Key[=Value]:Effect[:Seconds]

Can be used to enable or disable a trait. All traits share this common property.

Legacy trait configuration parameters. Deprecated: for backward compatibility.