Drone automates the steps between a source-code change and a tested build. A repository's pipeline configuration describes the work, and a runner executes it using containers while reporting the result. It is useful when a team wants its build process declared alongside its code. The runner is a separate operational choice: a pipeline that works with Docker does not necessarily behave the same way when its tasks run as Kubernetes Pods.
Deployment and operating notes
Drone’s current Kubernetes runner page describes a standalone service that executes pipelines inside pods. It explicitly labels that runner beta and a community effort outside support services or service-level agreements. This is narrower than saying all Drone is unsupported, and more useful than treating the old server chart as a complete supported Kubernetes CI platform.
Inventory server version, source-control integration, webhook secrets, runner type and pipeline syntax before migration. Kubernetes and Docker runners have different filesystem, networking and privilege assumptions; a pipeline described as docker-compose-like is not automatically portable between them. Test checkout, secrets, service containers, artifact handling, cancellation and an untrusted pull request. Restrict runner service accounts and avoid granting build code broad cluster access. Preserve server data and authentication configuration independently of ephemeral jobs. If moving to another CI system, translate trigger and secret policies explicitly rather than merely copying YAML keys. Keep a known-working runner queue available until representative projects complete successfully.
Historical upstream link check · 2026-10-09
The recorded upstream address redirects to https://docs.drone.io/getting-started/ and returned HTTP 200 on 2026-10-09. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
Drone is a Continuous Integration platform built on container technology. Drone uses a simple YAML configuration file, a superset of docker-compose, to define and execute Pipelines inside Docker containers.
Activation
To activate your project navigate to your account settings. You will see a list of repositories which can be activated with a simple toggle. When you activate your repository, Drone automatically adds webhooks to your version control system (e.g. GitHub).
Webhooks are used to trigger pipeline executions. When you push code to your repository, open a pull request, or create a tag, your version control system will automatically send a webhook to Drone which will in turn trigger pipeline execution.
Execution
To trigger your first pipeline execution you can push code to your repository, open a pull request, or push a tag. Any of these events triggers a webhook from your version control system and execute your pipeline.
You can view your pipeline execution in realtime in the user interface.
Installation and Administration
If you are installing Drone we recommend starting with a basic installation. Once you are familiar with Drone, this section will help you setup a distributed, secure, production-ready instance.
Project Configuration
Drone looks for a special .drone.yml file in the root of your repository for the pipeline definition. If you are trying to configure a continuous delivery pipeline for your repository, this is the place to start.
- Pipeline
- Services
- Cloning
- Secrets
- Volumes
- Conditions
- Triggers
- Multi-Machine
- Multi-Platform
Extending Drone
If Drone does almost everything you need but is missing a really important feature, don’t give up just yet. Drone has a flexible plugin system and can be extended to meet the unique needs of your organization.
Sources & further reading
Spotted something that needs another look?
Help improve this page →