Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

ingress controllers should watch secrets #952

Closed
bprashanth opened this issue May 11, 2016 · 5 comments
Closed

ingress controllers should watch secrets #952

bprashanth opened this issue May 11, 2016 · 5 comments
Assignees
Labels
area/ingress lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@bprashanth
Copy link

Currently there is no code that translates secrets <-> ingress. we wait for the periodic relist, then lookup secrets and create certs. We should notice when secrets change and invoke a sync on the associated ingress.

@guybrush
Copy link

Isn't this solved with #1063 ?

@bprashanth
Copy link
Author

I don't think the gce controller watches yet, it does the re-list thing, so leaving open

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2017
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 17, 2018
@fejta-bot
Copy link

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/ingress lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

5 participants