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

ingress: controller doesn't reread template when it was modified inside the pod #1805

Closed
kayrus opened this issue Sep 29, 2016 · 8 comments
Closed
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@kayrus
Copy link
Contributor

kayrus commented Sep 29, 2016

I use this example https://github.com/kubernetes/contrib/blob/6bc22addcdf29c531ebd1fa449aa8de2d840e242/ingress/controllers/nginx/examples/custom-template/custom-template.yaml#L52..L55
And when I update configmap with the new template I don't see any changes or related logs inside the ingress pod. I suppose it is related to inotify, but I'm not sure.

@aledbf
Copy link
Contributor

aledbf commented Sep 29, 2016

@kayrus this is fixed in master but not released #1498

@kayrus
Copy link
Contributor Author

kayrus commented Sep 29, 2016

@aledbf significant change. is there a way to beta-test the image without compiling it on my side?

@aledbf
Copy link
Contributor

aledbf commented Sep 29, 2016

@kayrus yes. Please use aledbf/nginx-third-party:0.40 (contains most of this list)

@kayrus
Copy link
Contributor Author

kayrus commented Oct 13, 2016

@aledbf could you let me know when new nginx controller release is expected? or how can I force current 0.8.3 release reread template file when it was changed?

@aledbf
Copy link
Contributor

aledbf commented Oct 13, 2016

or how can I force current 0.8.3 release reread template file when it was changed?

that's not possible in 0.8.3

could you let me know when new nginx controller release is expected?

I don't know. There are 4 pending PRs (#1847 is the most important one) before the next release

@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
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

4 participants