[NEW] kube-lego

[mgoodness]

This is a stand-alone chart for kube-lego, as mentioned and (briefly) discussed in #385. Should be generic enough to be used with nginx-ingress (PR coming soon) or the GCLB.

@jackzampolin

[k8s-ci-robot]

Hi @mgoodness. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with @k8s-bot ok to test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[viglesiasce]

Tested this over the weekend without any issues.

[viglesiasce]

@k8s-bot e2e test this

[jackzampolin]

Tested this with #399. LGTM

[viglesiasce]

@k8s-bot e2e test this

[mgoodness]

I suspect there's a problem with the post-delete hook I introduced in my last commit. Let me try something...

[mgoodness]

My fix for now is not to clean up. kube-lego creates its own secret, ingress, and service, but only when it finds an externally-created ingress to handle. The e2e runs in an isolated environment, so those resources are never created and the cleanup jobs are never able to delete them. The jobs just keep running until Jenkins times out. Best I can do is add a activeDeadlineSeconds to each job, but that also looks like a failure.

Cleanup in this case might best be done by the application itself.

Let's see if I can have...
@k8s-bot e2e test this

Edit: Ha! Guess not.

[k8s-ci-robot]

@mgoodness: you can't request testing unless you are a kubernetes member.

In response to this comment:

My fix for now is not to clean up. kube-lego creates its own secret, ingress, and service, but only when it finds an externally-created ingress to handle. The e2e runs in an isolated environment, so those resources are never created and the cleanup jobs are never able to delete them. The jobs just keep running until Jenkins times out. Best I can do is add a activeDeadlineSeconds to each job, but that also looks like a failure.

Cleanup in this case might best be done by the application itself.

Let's see if I can have...
@k8s-bot e2e test this

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[viglesiasce]

@k8s-bot e2e test this

[viglesiasce]

@mgoodness worked this time around