Development

We’re happy you’re interested in contributing to the Cilium project.

This section of the Cilium documentation will help you make sure you have an environment capable of testing changes to the Cilium source code, and that you understand the workflow of getting these changes reviewed and merged upstream.

• How To Contribute
  • Cilium Feature Proposals
  • Clone and Provision Environment
  • Submitting a pull request
  • Getting a pull request merged
  • Pull requests review process for committers
  • Weekly duties
  • Developer’s Certificate of Origin
• Development Setup
  • Verifying Your Development Setup
  • Requirements
  • Vagrant Setup
  • Local Development in Vagrant Box
  • Making Changes
  • Add/update a golang dependency
  • Add/update a new Kubernetes version
  • Optional: Docker and IPv6
  • Debugging
• Building Container Images
  • Developer images
  • Official release images
  • Experimental Docker BuildKit and Buildx support
  • Official Cilium repositories
  • Update cilium-builder and cilium-runtime images
  • Nightly Docker image
  • Image Building Process
• Code Overview
  • High-level
  • Cilium
  • Hubble
  • Important common packages
• Debugging
  • toFQDNs and DNS Debugging
  • Mutexes / Locks and Data Races
• Hubble
  • Bumping the vendored Cilium dependency
• Introducing New CRDs
  • Defining And Generating CRDs

The best way to get help if you get stuck is to ask a question on the Cilium Slack channel. With Cilium contributors across the globe, there is almost always someone available to help.