package
1.12.1
Repository: https://github.com/apache/camel-k.git
Documentation: pkg.go.dev

# Constants

No description provided by the author
No description provided by the author
Quarkus package type representing "fast jar" packaging.
No description provided by the author
Quarkus package type representing "native" packaging.
ServiceTypeClusterIP means a service will only be accessible inside the cluster, via the cluster IP.
ServiceTypeLoadBalancer means a service will be exposed via an external load balancer (if the cloud provider supports it), in addition to 'NodePort' type.
ServiceTypeNodePort means a service will be exposed on one port of every node, in addition to 'ClusterIP' type.

# Structs

Allows constraining which nodes the integration pod(s) are eligible to be scheduled on, based on labels on the node, or with inter-pod affinity and anti-affinity, based on labels on pods that are already running on the nodes.
The builder trait is internally used to determine the best strategy to build and configure IntegrationKits.
The Camel trait can be used to configure versions of Apache Camel K runtime and related libraries, it cannot be disabled.
Deprecated: for backward compatibility.
The Container trait can be used to configure properties of the container where the integration will run.
The Cron trait can be used to customize the behaviour of periodic timer/cron based integrations.
The Dependencies trait is internally used to automatically add runtime dependencies based on the integration that the user wants to run.
The deployer trait is responsible for deploying the resources owned by the integration, and can be used to explicitly select the underlying controller that will manage the integration pods.
The Deployment trait is responsible for generating the Kubernetes deployment that will make sure the integration will run in the cluster.
The environment trait is used internally to inject standard environment variables in the integration container, such as `NAMESPACE`, `POD_NAME` and others.
The error-handler is a platform trait used to inject Error Handler source into the integration runtime.
The GC Trait garbage-collects all resources that are no longer necessary upon integration updates.
The health trait is responsible for configuring the health probes on the integration container.
The Ingress trait can be used to expose the service associated with the integration to the outside world with a Kubernetes Ingress.
The Istio trait allows configuring properties related to the Istio service mesh, such as sidecar injection and outbound IP ranges.
The Jolokia trait activates and configures the Jolokia Java agent.
The JVM trait is used to configure the JVM that runs the integration.
The kamelets trait is a platform trait used to inject Kamelets into the integration runtime.
The Knative Service trait allows configuring options when running the Integration as a Knative service, instead of a standard Kubernetes Deployment.
The Knative trait automatically discovers addresses of Knative resources and inject them into the running integration.
The Logging trait is used to configure Integration runtime logging options (such as color and format).
The Mount trait can be used to configure volumes mounted on the Integration Pods.
The OpenAPI DSL trait is internally used to allow creating integrations from a OpenAPI specs.
The Owner trait ensures that all created resources belong to the integration being created and transfers annotations and labels on the integration onto these owned resources.
The PDB trait allows to configure the PodDisruptionBudget resource for the Integration pods.
The platform trait is a base trait that is used to assign an integration platform to an integration.
The pod trait allows the customization of the Integration pods.
The Prometheus trait configures a Prometheus-compatible endpoint.
The Pull Secret trait sets a pull secret on the pod, to allow Kubernetes to retrieve the container image from an external registry.
The Quarkus trait configures the Quarkus runtime.
The Registry trait sets up Maven to use the Image registry as a Maven repository.
The Route trait can be used to configure the creation of OpenShift routes for the integration.
The Service Binding trait allows users to connect to Services in Kubernetes: https://github.com/k8s-service-bindings/spec#service-binding As the specification is still evolving this is subject to change.
The Service trait exposes the integration with a Service resource so that it can be accessed by other applications (or integrations) in the same namespace.
This trait sets Tolerations over Integration pods.
Base type for all traits.

# Type aliases

+kubebuilder:validation:Enum=disabled;disk;memory.
Quarkus package type.
+kubebuilder:validation:Type=object +kubebuilder:validation:Format="" +kubebuilder:pruning:PreserveUnknownFields Deprecated: for backward compatibility.
No description provided by the author