This document summarizes a presentation about Contour, an open source Ingress controller for Kubernetes. It discusses how Contour allows for cross-namespace routing configuration through its custom IngressRoute resource, which helps address issues with Kubernetes Ingress like lack of safeguards and an explosion of annotations in multi-team clusters. The presentation demonstrates Contour's features like prefix rewriting, canary deployments, and websocket support and recommends it as an alternative to standard Kubernetes Ingress. It also mentions Contour's integration with Envoy and potential future work on multi-cluster ingress with Gimbal.

1. CONFIDENTIELCONFIDENTIEL
Contour
CNCF Nantes Meetup - 10 décembre 2018

2. @Gaelleacas
Développeuse

3. Kubernetes cluster
Michael Gasch (VMware)
“Autonomous processes reacting to events from the API server”

4. Kubernetes : Services
https
Expose Pods
node
ClusterIp: no external access
NodePort: open port on all nodes
app=app1
service
service
app=app2
app=app1
Pod
app=app1
Pod
Pod
app=app2
Pod
app=app2
type: LoadBalancer

5. Kubernetes : Ingress
https
Expose Services
node
LoadBalancer: Expose to the world
NodePort: open port on all nodes
app=app1
service
service
app=app2
app=app1
Pod
app=app1
Pod
Pod
app=app2
Pod
app=app2
type: ClusterIp
Ingress

6. Kubernetes : Ingress
Ingress Controller
Component that allows to control a reverse-proxy (nginx / traefik …)
Ingress resource:
Rule that defines routing to a service in a cluster

7. Contour
by Craig McLuckie & Joe Beda
API objects
Manage Network
traffic translate
watch
Contour
(Ingress, Service et Endpoint)
(json)
How it works ?

8. 🦄

9. Ingress in
Multi-team
https://santa.local
https://santa.local/legohttps://santa.local/playmo
Ingress
Cluster
namespace
playmo
namespace
lego
namespace
santa
BigBoss

10. DEMO
Install: https://j.hept.io/contour-deployment-rbac

11. Ingress
‟Achilles’ heel of a multi-team cluster”
Not progressed beyond the beta stage v1.1🤨
Ingress / services in same namespace☹
Explosion of annotations🤯
No safeguards to avoid accidental changes☠
Deployment strategy
canaryblue/green
👾

12. Contour
IngressRoute to the rescue
Demo is better !
Custom resource definition (k8s > 1.10)
Cross-namespaces
Enables delegation of routing configuration
Safeguard
💡
🚀
)
*

13. Other good features
Demo :)
Websocket
Permit Insecure route (acme-challenge)
Prefix Rewrite Support
Blue/Green CanaryDeployment strategy🔀
🔓
🧦
/

14. Lost in routes ?
Directed acyclic graph
(Dag)
Envoy admin interface (No UI)
Kubectl -n heptio-contour port-forward [CONTOUR_POD] 6060

15. Contour What Next ?
Kubernetes multi-cluster ingressGimbal

16. Resources / Links
kubernetes.slack.com : Contour
https://github.com/heptio/contour
🎦 https://github.com/heptio/tgik
https://github.com/heptio/gimbal
Thank God It's Friday K8s

17. MERCI
:)