dtab routing on kubernetes namespace

[Ingo Claro]

Hello!

I've configured likerd in a namespace (demo-linkerd) and I'm trying to access a service but it doesn't work for me.

> http_proxy=http://$(minikube ip):8081 curl -s http://frontend

No hosts are available for /svc/frontend, Dtab.base=[/svc=>/#/io.l5d.k8s.ns/default/http;/host=>/srv;/svc=>/host], Dtab.local=[]. Remote Info: Not Available

I've tried different configurations of dtab in the admin /delegator page and I'm not getting any match.

Here is the configuration I'm using: https://gist.github.com/ingoclaro/364295615c67fccbb728dc61cfb89d97 

Note that I've all of this in the demo-linkerd namespace.

Could somebody please take a look and tell me what I'm doing wrong? Thanks!

[Ingo Claro]

yes, I do have a deployment for the frontend service, also I can curl the frontend service directly and get a response.

The /svc/l5d does match, but /svc/frontend does not.

On Mon, Jul 17, 2017 at 10:10 AM, Andrew Seigner <si...@buoyant.io> wrote:

Hi Ingo,

Your linkerd, frontend service, and ingress configs look good, thanks for providing those!

Are you also running actual instances of your 'frontend' service? For example, a Deployment or ReplicationController? If there are no pods running instances of your 'frontend' service, there's nothing for linkerd to route to.

You can confirm linkerd is correctly routing in minkube by testing `/svc/l5d` in the admin dtab interface.

If you have more questions, try create an issue on https://discourse.linkerd.io/, it's easier for us to track, and you'll probably get a better response.

Cheers,

Andrew

--
You received this message because you are subscribed to the Google Groups "linkerd-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkerd-users+unsubscribe@googlegroups.com.
To post to this group, send email to linker...@googlegroups.com.
Visit this group at https://groups.google.com/group/linkerd-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkerd-users/6f96576d-f9e0-4505-9468-e3c6d3426a67%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Andrew Seigner]

Hi Ingo,

Your linkerd, frontend service, and ingress configs look good, thanks for providing those!

Are you also running actual instances of your 'frontend' service? For example, a Deployment or ReplicationController? If there are no pods running instances of your 'frontend' service, there's nothing for linkerd to route to.

You can confirm linkerd is correctly routing in minkube by testing `/svc/l5d` in the admin dtab interface.

If you have more questions, try create an issue on https://discourse.linkerd.io/, it's easier for us to track, and you'll probably get a better response.

Cheers,

Andrew

On Sat, Jul 15, 2017 at 12:23 PM, Ingo Claro <mic...@gmail.com> wrote:

--

[Andrew Seigner]

In frontend-service.yaml, try adding `- name: http` to the port:

```

kind: Service

apiVersion: v1

metadata:

  name: frontend

spec:

  selector:

    app: frontend

  ports:

    - name: http

      protocol: TCP

      port: 80

      targetPort: http

```