Open tnozicka opened 3 years ago
@tnozicka why would we want to initiate a rolling restart whenever a new image is published using an existing tag? I've consulted this behaviour with @zimnx and he expressed concern as well.
the operator image is embedded in every scylla deployment for the side car so if the user:
latest
, currently pointing to 1.4.0
1.4.0
:latest
changes to 1.5.0
:latest
changes to 1.6.0
1.6.0
while the other two still run from 1.4.0
similar issues arise for the case when a tag is rewritten, sha is the only way to reliably reference the same image
The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
/lifecycle stale
This may be be replaced by splitting this logic into a separate image but until we have a plan for that let's keep this here. /remove-lifecycle stale
The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
/lifecycle stale
/remove-lifecycle stale
The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
/lifecycle stale
/remove-lifecycle stale
The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
/lifecycle stale
The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
/lifecycle rotten
/remove-lifecycle rotten /triage accepted
Is this a bug report or feature request?
What should the feature do: If someone useses a rolling update tag like
latest
or1.3
forSCYLLA_OPERATOR_IMAGE
, we won't initiate a rolling restart to update the sidecar image. We should always use sha in the objects we generate even if the user forgot to do so.