Closed philips closed 5 years ago
The Omaha thingie could probably just be a sidecar that takes a deployment and can only update the tag of the spec.container.image.
Self-updating makes me nervous. It is somewhat antithetical to hermetic containers.
On Thu, Nov 17, 2016 at 10:17 PM, Brandon Philips notifications@github.com wrote:
The Omaha thingie could probably just be a sidecar that takes a deployment and can only update the tag of the spec.container.image.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kubernetes-incubator/spartakus/issues/11#issuecomment-261457701, or mute the thread https://github.com/notifications/unsubscribe-auth/AFVgVGYb0fajJHvbfzjtnz7wqIupuBvbks5q_UL_gaJpZM4K2J8Y .
@philips wouldn't it be better to use the API? For example, we could consider a cron job type of sidecar that is able to update image in a deployment spec. However, having said this, would Spartakus benefit from such functionality in significant way really?
@errordeveloper sure, the cron job needs to talk to Omaha or something that tells it what version to run though. Cron jobs aren't ideal because you want exponential backoffs.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
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
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
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
@fejta-bot: Closing this issue.
It would be great if spartakus would be able to update its own deployment and ideally we could roll out the update in a controlled manner with a feedback loop. Also, it would be cool if people could subscribe to alpha/beta/stable reporting channels.
We are building something that plugs into an Omaha server for the etcd and Prometheus Operator. Would that be OK for spartakus?