Romeo Mihalcea

I get the same error. Did you manage to get around it?

Something like this from dante would be awesome because you can limit all users with a few lines. There are many setups where limiting all users makes sense. ``` client...

+1 docker in docker is also what I need. Any news on this? Update: I think this works: ``` "parameters": [ {"key": "privileged", "value": "true"} ], ```

I have the same issue. Placing constraints on the job leads to them being queued but never executed.

The values don't match: On the ingress describe I get: `k8s-ssl-default-loadbalancer--cbee26f7d1895ddb` and in the load balancer console I get: `k8s-um-default-loadbalancer--41dc2c3938d90731`

yes the certificate or title point to the same "id": `k8s-ssl-default-loadbalancer--41dc2c3938d90731` Whatever is loaded in the loadbalancer expired on april 26: ``` Expires Apr 26, 2017, 3:03:00 AM Serial Number...

This one seems ok. ``` Certificate: Data: Version: 3 (0x2) Serial Number: 03:86:3c:38:40:8a:1c:e3:be:41:7c:ab:8a:77:67:b8:4a:10 Signature Algorithm: sha256WithRSAEncryption Issuer: C=US, O=Let's Encrypt, CN=Let's Encrypt Authority X3 Validity Not Before: Apr 28 13:47:00...

Bummer. I loaded this thing into a lot of applications. I'm still hoping it's some sort of a "my fault". This project has quite some time behind it and I...

Apart from upgrading my kubernetes version to 1.6.2 (latest offering by GKE) and trying to re-apply my ingress in hope of it picking up the new changes I don't know...

In other words...global components don't work. This seems like a major bug to me.