Skip to content

Camel K Integration Platform

Apache Camel K provides a cloud-native integration platform for running Camel integrations on Kubernetes.

Overview

Camel K enables lightweight integration microservices with support for multiple languages and automatic scaling.

Configuration

Deployment Location

  • Configuration: apps/rciis/camel-k/
  • Environments: Local, Testing, Staging
  • Chart: Official Camel K Helm chart

Directory Structure

apps/rciis/camel-k/
├── local/
│   └── values.yaml
├── testing/
│   └── values.yaml
└── staging/
    └── values.yaml

Features

Integration Platform

  • Operator-based deployment
  • Auto-scaling integrations
  • Multi-language support (Java, XML, YAML, JavaScript)
  • Knative integration

Development Experience

  • Rapid prototyping
  • Hot reloading
  • Local development support
  • CLI tools integration

Cloud-Native Features

  • Serverless execution
  • Kubernetes-native
  • Service mesh integration
  • Observability support

Configuration Examples

Platform Configuration

# Camel K Operator configuration
operator:
  replicas: 1

# Integration Platform
platform:
  cluster: kubernetes
  registry:
    address: harbor.devops.africa
    secret: harbor-registry

# Build configuration
build:
  registry:
    address: harbor.devops.africa/camel-k
    secret: harbor-registry
  timeout: 10m

# Resource limits
resources:
  requests:
    memory: 256Mi
    cpu: 100m
  limits:
    memory: 512Mi
    cpu: 500m

Integration Examples

Simple Route Integration:

apiVersion: camel.apache.org/v1
kind: Integration
metadata:
  name: customs-processor
spec:
  sources:
  - content: |
      from("kafka:customs-declarations")
        .log("Processing declaration: ${body}")
        .process(exchange -> {
          // Custom processing logic
        })
        .to("kafka:customs-processed")
    name: customs-processor.java

Use Cases

Data Integration

  • Message transformation
  • Protocol bridging
  • Data synchronization
  • ETL processes

API Integration

  • REST API composition
  • Legacy system integration
  • Event streaming
  • Microservices communication

For detailed integration examples and patterns, refer to the Camel K documentation.