Install kamel with Homebrew

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• kamel

Project history

The Apache Camel K repository was created on 2018-08-31. The README describes Camel K as a lightweight integration framework built from Apache Camel, running natively on Kubernetes, and designed for serverless and microservice architectures.

The `kamel` CLI is documented as a utility released beside the Camel K operator. Its job is to install Camel K, run integrations from Camel DSL files, and support workflows such as development mode where changes are applied to the remote integration pod.

GitHub releases show nightly artifacts in 2020 and stable 2.x releases by the mid-2020s. Apache Camel release and blog material also ties Camel K to the wider Camel modernization track around Quarkus, Knative, Kubernetes operators, and cloud-native integration.

Adoption history

Camel K adoption sits inside the Apache Camel community and Kubernetes ecosystem. Users who already know Camel routes can run integrations as Kubernetes-native resources rather than packaging and operating their own standalone services for every integration.

The CLI packaging matters because installation instructions and day-to-day examples begin with `kamel`: installing the operator, running an integration file, and iterating in development mode. Homebrew packaging makes that entry point easy to install on developer workstations.

How it is used

`kamel run` is the core documented workflow: save an integration in a Camel DSL file and submit it to a Kubernetes cluster. The operator then transforms the Integration custom resource into a Camel application running on the cloud.

The CLI is also used for installation and local developer ergonomics; the official CLI page points to Apache mirrors and GitHub releases for the `kamel` binary.

Why package nerds care

kamel is a good package-manager example of an operator companion CLI. The executable is small, but the thing it controls is distributed infrastructure, so version alignment with the operator, release artifacts, and Kubernetes cluster behavior matters.

It also represents a common packaging pattern for cloud-native tools: a local command creates and manages remote resources, while the actual workload runs inside the cluster.

Timeline

• 2018: apache/camel-k repository created.
• 2020: Camel K nightly releases published on GitHub.
• 2020: Apache Camel Quarkus 1.0 material described Camel K 1.0 as a sibling project using Camel Quarkus runtime support.
• 2026: Camel K 2.10.x documentation documented the `kamel` CLI and release locations.

Related projects

• Apache Camel is the integration framework Camel K builds on.
• Camel Quarkus, Knative, Kubernetes, and OpenShift are adjacent technologies in the Camel K runtime and deployment story.

Sources

• https://api.github.com/repos/apache/camel-k
• https://camel.apache.org/blog/2020/08/camel-quarkus-release-1.0.0/
• https://camel.apache.org/camel-k/2.10.x/index.html
• https://camel.apache.org/camel-k/2.10.x/installation/installation.html
• https://camel.apache.org/camel-k/2.10.x/running/running-cli.html
• https://github.com/apache/camel-k
• https://github.com/apache/camel-k/releases