Skip to content

Latest commit

 

History

History
70 lines (52 loc) · 4.59 KB

README.md

File metadata and controls

70 lines (52 loc) · 4.59 KB
Raw

Heptio Contour

Heptio Contour is an Ingress controller for Kubernetes that works by deploying the Envoy proxy as a reverse proxy and load balancer. Unlike other Ingress controllers, Contour supports dynamic configuration updates out of the box while maintaining a lightweight profile.

Prerequisites

  • Kubernetes 1.10+
  • RBAC must be enabled.

Installing the Chart

To install the chart with the release name contour:

$ helm upgrade --install contour --namespace heptio-contour rimusz/contour

By default contour uses LoadBalancer to expose ports 80/443. You can change the service type via --set or in values.yaml file.

Tip: List all releases using helm list

Configuration

The following table lists the configurable parameters of the Contour chart and their default values.

Parameter Description Default
replicaCount Default replicaCount 1
annotationsprometheus.io/scrape Enable Prometheus scrape true
annotationsprometheus.io/port Set Prometheus scrape port 8002
annotationsprometheus.io/path Set Prometheus scrape path /stats/prometheus
controller.image.repository Set Controller image repository gcr.io/heptio-images/contour
controller.image.PullPolicy Set Controller image pull policy IfNotPresent
controller.statsd.enabled Enable Controller statsd false
controller.stats Set Controller stats {}
proxy.image.repository Set Proxy image repository docker.io/envoyproxy/envoy-alpine
proxy.image.tag Set Proxy image tag v1.9.1
proxy.image.PullPolicy Set Proxy image pull policy IfNotPresent
service.type Service type LoadBalancer
service.loadBalancerIP Loadbalancer IP ``
service.annotations Service annotations {}
ingressRoutes.enabled If true, Enable ingressRoutes CRD will be created false
resources Set Compute resources {}
rbac.enabled Specifies whether RBAC resources should be created true
nodeSelector Set node selector {}
tolerations Set node tolerations []
podDisruptionBudget.enabled Enables Pod Disruption Budget false
podDisruptionBudget.maxUnavailable Max unavailable Pods 1
podDisruptionBudget.minAvailable min unavailable Pods ``

Specify each parameter using the --set key=value[,key=value] argument to helm install/upgrade.

Alternatively, a YAML file that specifies the values for the configurable parameters can be provided while installing the chart. For example:

$ helm upgrade --install contour --namespace heptio-contour rimusz/contour -f values.yaml .

Tip: You can use the default values.yaml

Uninstalling the Chart

To uninstall/delete the contour deployment:

$ helm delete --purge contour

The command removes all the Kubernetes components associated with the chart and deletes the release.