ingress controllers (full)-chain support?

[MaxDaten]

Hi,

we are currently using a Lets Encrypt service to create and renew certificates. Besides #952 makes it currently impossible (?) to update the cert for the ingress controller automatically (maybe an kubectl apply/replace on the ingress is enough to force a reload?), we need to install the full-chain, otherwise android would reject the cert (https://community.letsencrypt.org/t/on-android-6-0-1-the-certificate-is-untrusted/7815). Is there a support for the full-chain? The certificates for the GCE Load-Balancer offers a field to enter the (full)chain.pem.

[bprashanth]

Besides #952 makes it currently impossible (?) to update the cert for the ingress controller automaticall

Not automatically in verions < 0.6.3, you can do so through gcloud still.
Cert updates work in 0.6.3, which is the version of the controller that we ship with the next kube release (you can get it right now by just changing the image version in your RC with kubectl edit and deleting the current pod).

Is there a support for the full-chain? The certificates for the GCE Load-Balancer offers a field to enter the (full)chain.pem.

Can you just concat your certs? kubernetes/kubernetes#24669

[MaxDaten]

Not automatically in verions < 0.6.3, you can do so through gcloud still.
Cert updates work in 0.6.3, which is the version of the controller that we ship with the next kube release

Thanks for clearing this up. I'm looking forward to it.

Can you just concat your certs? kubernetes/kubernetes#24669

I will try it next week. Thanks.

[fejta-bot]

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close