Question: when those paths route to backend, does backend see anything following that path as root domain?

Asked By
msparr
Asked At
2017-11-30 17:01:01

Found 15 possible answers.

User Answered At Possible Answer
lovan.artem 2017-11-30 17:02:01 Is it possible to configure an Ingress not to cut off the path. For example when:
and client requests `foo.bar.com/foo/time ` it should forward the call to `s1` with `foo/time`. Else it’s impractical to map and maintain all endpoints exposed by a service. Or what other solutions are there?
          servicePort: 80
          serviceName: s1
        backend:
      - path: /foo
      paths:
    http:
  - host: foo.bar.com 
rules:
msparr 2017-11-30 17:04:32 I think this makes sense. The goal is as I add more hosts to the Ingress, I will set their backend to the kong-proxy service and it will route to their services respectively. I think this will work but wasn't sure if I could have a single api.mydomain.com and diff paths /service1 /service2 but after routing to each, they see everything after the initial path as their root path so /service1/users they see as /users
mikej 2017-11-30 17:05:03 yeah
creepteed 2017-11-30 17:06:34 Hello, guys. Maybe someone can help me. I've setup ingress controller and app but when i
kubectl describe ingress
and ingress ip returns connection refused nginx:80 ()
  mysite.com   
  ----        ----  --------
Host Path Backends it has no ip after service name
cheng.wang1986 2017-11-30 17:12:49 Does anyone know if there is any pre-defined kubernetes env variable for cluster name that I can use in a deployment yml? something like KUBERNETES_CLUSTER_NAME? One of my containers need it
mikej 2017-11-30 17:14:21 it'd be the downward API but i dont see cluster name on the list @mikej uploaded a file: Untitled https://kubernetes.slack.com/files/U1A92LHRS/F88U8FHSB/-.sh you can use a label, set label = $clustername and set https://kubernetes-v1-4.github.io/docs/user-guide/downward-api/
cheng.wang1986 2017-11-30 17:23:45 @mikej Thanks for your quick response. However, as you mentioned, the downward API doesn't support clusterName
mikej 2017-11-30 17:24:23 i just told you how to get around it
cheng.wang1986 2017-11-30 17:24:40 @mikej oh so I can define my own downward api in that way?
kareem.straker 2017-11-30 17:24:53 hi everyone
mikej 2017-11-30 17:24:59 downwardapi can use labels, it kind of sucks but just set a clustername label and call it like in my example really easy to do actually its a deployment thing nvm just have to make sure the labels are on every node
kareem.straker 2017-11-30 17:25:56 i'm running into an issue using a new 1.8.4 cluster when I try to apply the latest 1.8.0 dashboard from the official repo. it seems to be erroring when creating the RBAC role
cheng.wang1986 2017-11-30 17:26:32 yeah, really helpful. Another question, @mikej I was using this cmd
kubectl cluster-info 
are you aware of another way to obtain such info?
Kubernetes master is running at   
but still couldn't obtain the cluster-name
msparr 2017-11-30 17:27:11 Every time I see @kareem.straker handle I want to scream that "Captain caaaaavvvvveeeeee mannnn". Am I the only one? :wink:
kareem.straker 2017-11-30 17:27:33 I commented on a thread https://github.com/kubernetes/dashboard/issues/2415

Related Questions