Questions tagged [heptio-contour]

Contour is a Kubernetes ingress controller for Lyft's Envoy proxy.

Contour is a Kubernetes ingress controller for Lyft's Envoy proxy. https://github.com/heptio/contour

6 questions
4
votes
2 answers

Is there an order to how an Ingress rule is chosen?

Is there an order to Ingress rule specification i.e. will the first qualifying rule be honored? The intention of following spec is to route all requests that do not have headers Host: foo.com and Host: bar.com and route them to service3. I am not…
siberiancrane
  • 586
  • 1
  • 6
  • 20
2
votes
1 answer

Authentication methods using a JSON key file: unauthorized: GCR login failed

Mostly addressed to: google-cloud-platform Overall problem I am trying to solve is; to pull images from Google Container Registry from private Kubernetes. Update Just added heptio-contour if some one over there have come across this - as the good…
Chris G.
  • 23,930
  • 48
  • 177
  • 302
2
votes
1 answer

heptio-contour external ip on bare metal

I've setup a kubernetes cluster using kubespray, and now I am trying to follow this guide root@node1 ~ # kubectl get -n heptio-contour service contour -o wide NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE …
nha
  • 17,623
  • 13
  • 87
  • 133
1
vote
1 answer

Metric for Ingress Route

I have two Ingress (Contour managing Envoy) host header based routes (among others) where both the routes point to the same service. spec: rules: - host: foo.com http: paths: - backend: serviceName: s1 …
0
votes
1 answer

How to share an AWS NLB between two EKS Services?

We have a cross AZ deployment in an EKS cluster inside an AWS region where every AZ is independent, meaning that components do not talk to other components that are not in the same AZ. We are using Contour as our ingress and have different Daemon…
Michael
  • 1,209
  • 2
  • 12
  • 25
0
votes
0 answers

Is it possible to create a port based ingressroute in k8s?

I have a Debian k8s cluster. I need to route all traffic from http://fqdn_of_my-service to pod_my_service:8080 and route https://fqdn_of_my-service to pod_my_service:8443. (fqdn_of_my-service and pod_my_service are in both cases the same) To put…
A.M.
  • 1