404 issue with GCE example about kube-lego HOT 15 CLOSED

The GCE has probably still a few problems...

@devth: can you provide me this:

• ingress yaml
• kubectl describe of the ingress
• a screenshot of the forwarding rule in gce console

from kube-lego.

Ingress

---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: foo
  annotations:
    kubernetes.io/tls-acme: "true"
    kubernetes.io/ingress.class: "gce"
spec:
  tls:
  - secretName: foo-tls
    hosts:
    - foo.redacted.com
  rules:
  - host: foo.redacted.com
    http:
      paths:
      - path: /*
        backend:
          serviceName: foo
          servicePort: 80

kubectl describe

Name:           foo
Namespace:      default
Address:        130.x.x.x
Default backend:    default-http-backend:80 (10.0.1.3:8080)
TLS:
  foo-tls terminates foo.redacted.com
Rules:
  Host          Path    Backends
  ----          ----    --------
  foo.redacted.com  
                /*  foo:80 (<none>)
Annotations:
  backends:     {"k8s-be-30314--c2cd235f2196d4d5":"HEALTHY","k8s-be-31354--c2cd235f2196d4d5":"HEALTHY"}
  forwarding-rule:  k8s-fw-default-foo--c2cd235f2196d4d5
  target-proxy:     k8s-tp-default-foo--c2cd235f2196d4d5
  url-map:      k8s-um-default-foo--c2cd235f2196d4d5
No events.

from kube-lego.

Your screenshot shows the firewall rule and not the forwarding rule. Should be here: https://console.cloud.google.com/networking/loadbalancing/list

Another thing: if you could give me the output of kubectl get ingress/foo -o yaml instead of the one provided. It should contain a path with /.well-known/acme-challenge/*

from kube-lego.

It doesn't contain a path with .well-known/acme-challenge/* so I'm guessing that is the problem.

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    ingress.kubernetes.io/backends: '{"k8s-be-30314--c2cd235f2196d4d5":"HEALTHY","k8s-be-31354--c2cd235f2196d4d5":"HEALTHY"}'
    ingress.kubernetes.io/forwarding-rule: k8s-fw-default-foo--c2cd235f2196d4d5
    ingress.kubernetes.io/target-proxy: k8s-tp-default-foo--c2cd235f2196d4d5
    ingress.kubernetes.io/url-map: k8s-um-default-foo--c2cd235f2196d4d5
    kubernetes.io/ingress.class: gce
    kubernetes.io/tls-acme: "true"
  creationTimestamp: 2016-08-14T16:59:07Z
  generation: 1
  name: foo
  namespace: default
  resourceVersion: "476436"
  selfLink: /apis/extensions/v1beta1/namespaces/default/ingresses/foo
  uid: 69e5e281-6240-11e6-bdc9-42010af00120
spec:
  rules:
  - host: foo.redacted.com
    http:
      paths:
      - backend:
          serviceName: foo
          servicePort: 80
        path: /*
  tls:
  - hosts:
    - foo.redacted.com
    secretName: foo-tls
status:
  loadBalancer:
    ingress:
    - ip: 130.x.x.x

from kube-lego.

That could be something really buggy in kube-lego. Can you give me the exact version of kube-lego. Should be in the log output:

$ kubectl logs --namespace kube-lego kube-lego-2628658575-3xejo | head -n1
time="2016-08-15T10:38:31Z" level=info msg="kube-lego 0.0.4-910cebed starting" context=kubelego

from kube-lego.

kubectl logs kube-lego-3701810767-k5qf3 | head -n1
time="2016-08-15T16:40:55Z" level=info msg="kube-lego 0.0.4-910cebed starting" context=kubelego

I'm running kube-lego in the default namespace instead.

from kube-lego.

I found that when I add the kube-lego-svc back, things start to work right (nginx in my case).
it seems that the challenge forwarding rule needs the kube-lego-svc to route to.

from kube-lego.

You are both sure that you are using Version 0.1.0 of Kube-Lego? (Image tag in Kube-Lego Deployment)

from kube-lego.

I was using the latest example version (0.0.4)

from kube-lego.

That's the problem then can you try the 0.1.0 tag. I will fix the docs in a minute

from kube-lego.

confirming it works as expected with image tag 0.1.0 on an nginx controller
Thanks!

also, the logs still shows "kube-lego 0.0.4-de70b08f starting" with the 0.1.0 image. a little confusing...
and btw, had to cleanup older ingress after switching images, as the old one was shadowing the new one

from kube-lego.

Seems like I need a release script to not forget the necessary steps around automation 😆. I will release 0.1.1 later with both issues (wrong docs + wrong output) fixed

from kube-lego.

@ram-argus ok released 0.1.1 and pushed to docker hub. Thanks a lot for spotting this versioning issues. It is really a big blocker for new users.

time="2016-08-16T10:36:52Z" level=info msg="kube-lego 0.1.1-81604d11 starting" context=kubelego

Feel free to create new issues as soon you hit them! Cheers

from kube-lego.

@devth let me know if 0.1.1 works for you

from kube-lego.

@simonswine thanks, it works!

I had to delete my existing kube-lego deployment, the service it created, and my ingress. After re-creating I waited about 5 minutes, saw a bunch of 404 errors in the reachability attempt, then it started working.

from kube-lego.