projectcontour/helm-charts

Contour Helm charts

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

projectcontour/helm-charts has 10+ stars and 10+ forks on GitHub, is written in Go, and was last pushed on Sep 7, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 30 minutes ago
Type:Template / ExampleCategory(s):Kubernetes & OperatorsCloud Native & Infrastructure
Added to GitGenius on October 15th, 2026
Created on August 25th, 2025
Open Issues & Pull Requests: 18 (+0)
GitHub issues: Enabled
Number of forks: 10
Total Stargazers: 13 (+0)
Total Subscribers: 4 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.9 hours
Mean response time: 24.1 days
90th percentile: 84.2 days
Tracked items: 8

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 279 days
Stale 30+ days: 7
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • help wanted (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Helm Charts for Contour is a collection of Helm charts that package Contour, an open-source Kubernetes ingress controller.

Contour solves the problem of managing ingress traffic in Kubernetes clusters by providing a controller that configures Envoy as a reverse proxy and load balancer. The approach uses Helm charts to standardize and simplify the deployment of both the Contour controller and its associated Envoy proxy components into Kubernetes environments.

The project suits teams already using Helm for Kubernetes package management who need an ingress solution built on Envoy. It is appropriate for organizations that have standardized on Contour and want a declarative, version-controlled way to deploy and manage the controller across clusters. The charts handle the complexity of configuring both the Contour controller and Envoy proxy together, reducing manual setup work.

The project maintains a structured contribution process with documented guidelines for environment setup and development workflow. The repository includes a certificate of origin requirement for contributors, indicating a formal approach to code provenance and community participation.