Camel K

Apache Camel K is a lightweight integration platform, born on Kubernetes, with serverless superpowers: the easiest way to build and manage your Camel applications on Kubernetes.

This chart deploys the Camel K operator and all resources needed to natively run Apache Camel integrations on any Kubernetes cluster.

Prerequisites

• Kubernetes 1.11+
• Container Image Registry installed and configured for pull (optional in Openshift or Minikube)

Installing the Chart

To install the chart, first add the Camel K repository:

$ helm repo add camel-k https://apache.github.io/camel-k/charts

Depending on the cloud platform of choice, you will need to specify a container registry at installation time.

Plain Kubernetes

A regular installation requires you to provide a registry, used by Camel K to build application containers. See official Camel K registry documentation.

$ helm install camel-k \
  --set platform.build.registry.address=<my-registry> \
  camel-k/camel-k

You may install Camel K and specify a container registry later.

Openshift

If you are installing on OpenShift, Camel K can use the OpenShift internal registry to store and pull images:

$ helm install camel-k \
  --set platform.cluster=OpenShift \
  camel-k/camel-k

Minikube

Minikube offers a container registry addon, which it makes very well suited for local Camel K development and testing purposes. You can export the cluster IP registry addon using the following script:

$ minikube addons enable registry
$ export REGISTRY_ADDRESS=$(kubectl -n kube-system get service registry -o jsonpath='{.spec.clusterIP}')

Then you can install Camel K with:

$ helm install camel-k \
  --set platform.build.registry.address=${REGISTRY_ADDRESS} \
  --set platform.build.registry.insecure=true \
  camel-k/camel-k

Knative configuration

Camel K offers the possibility to run serverless Integrations in conjunction with Knative operator. Once Knative and Camel K are installed on the same platform, you can configure Knative resources to be played by Camel K.

See instructions how to enable Knative on Camel K.

Additional installation time configuration

The configuration section lists additional parameters that can be set during installation.

Tip: List all releases using helm list

Upgrading the Chart

If you are upgrading the camel-k Deployment, you should always use a specific version of the chart and pre-install the CRDS:

# Upgrade the CRDs
$ curl -LO "https://github.com/apache/camel-k/raw/main/docs/charts/camel-k-x.y.z.tgz"
$ tar xvzf camel-k-x.y.z.tgz
$ kubectl replace -f camel-k/crds
# Upgrade the `camel-k` Deployment
$ helm upgrade camel-k/camel-k --version x.y.z

Note: If you are using a custom ClusterRole instead of the default one camel-k:edit from camel-k/crds/cluster-role.yaml you should handle it appropriately.

Uninstalling the Chart

To uninstall/delete the camel-k Deployment:

$ helm uninstall camel-k

The command removes all of the Kubernetes resources installed, except the CRDs.

To remove them:

$ curl -LO "https://github.com/apache/camel-k/raw/main/docs/charts/camel-k-x.y.z.tgz"
$ tar xvzf camel-k-x.y.z.tgz
$ kubectl delete -f camel-k/crds

Configuration

The following table lists the most commonly configured parameters of the Camel K chart and their default values. The chart allows configuration of an IntegrationPlatform resource, which among others includes build properties and traits configuration. A full list of parameters can be found in the operator specification.

Contributing

We'd like to hear your feedback and we love any kind of contribution!

The main contact points for the Camel K project are the GitHub repository and the Camel K chat room.