Replies: 3 comments 1 reply
-
I opened this before noticing #101 - much of that discussion may be relevant here. |
Beta Was this translation helpful? Give feedback.
-
Nice, also further to share and just for idea sake, there is another way we can clean it, and its here: https://github.com/Tatsinnit/aks-periscope-porter-poc |
Beta Was this translation helpful? Give feedback.
-
could there be any value in adding a "triggering" capability to allow periscope to be rerun on demand when the DaemonSet is left installed and running? Wouldn't be very useful on its own but if it could then be triggered by some kind of automated node-change-detection (or even just cron schedule) then you've got a use case for leaving periscope installed, providing periodic snapshots |
Beta Was this translation helpful? Give feedback.
-
This relates to #23. The concern is that by design, DaemonSet pods stay running, despite the fact they finish their useful work shortly after starting.
Others have pointed out the need for Kubernetes to support job-like behaviour that runs on all nodes, but so far there is no official Kubernetes resource type, and not much consensus about workarounds. Some suggestions are:
Neither of the above appear to be actively maintained.
Some considerations:
Beta Was this translation helpful? Give feedback.
All reactions