Skip to content

Rollback

A rollback in Seylo is always a new forward change that re-applies an older version. History is never rewound, so the rollback is itself a new entry in the history. This page covers the three ways to do it through approval, which differ in what they restore.

Release an earlier tag History: Rollback to this version Manifest editor: Load into editor to roll back
Restores The image tag The image tag, plus the env (exactly, removing variables added since) and CPU and memory of the first container, as recorded at that version The whole Deployment, Service or Ingress YAML
Goes through approval Yes Yes Yes
Can proceed over Argo CD, Flux or Helm with an acknowledgement Yes Yes Yes
Who releaser releaser releaser

If your organisation has approvals turned off, each of the three applies straight away instead of waiting for an approver, and is still recorded.

This is an ordinary release of the old tag. On the namespace page, tick the component, enter the earlier tag (1.4.2) and press Deploy selected. It goes through approval, shows a live rollout, and is recorded in Activity.

It moves the image only. Configuration changed since then stays as it is, unless you also turn on Also change configuration and set it back yourself.

Roll back to a recorded version from History

Section titled “Roll back to a recorded version from History”

Use this when you want the image and the configuration a release set to go back together, without typing either.

  1. On the namespace page, under Per-component tools, press History for the component. The page is titled checkout-api history and lists every recorded version, newest first.

  2. Find the version you want and press Rollback to this version. Nothing is submitted yet. Seylo works out what the rollback would change, and the button reads Checking… meanwhile.

  3. Read what it removes. A confirmation card, Roll back checkout-api to <commit>?, says Nothing has been submitted yet. and lists what the rollback does to environment variables, by name:

    • This rollback removes: X, Y from the container. These were added after that version, and rolling back deletes them. If there are none, it says This rollback removes no environment variables.
    • Adds back: variables that version had and the container doesn’t have now.
    • Sets back to that revision’s value: variables on both whose value differs.
    • Secret-backed entries, by key, which a rollback doesn’t change.

    If that version has no container Seylo can restore env from, the card says This rollback writes no environment variables (there is no recorded env to restore).

    Values are never shown. Press Confirm rollback to submit it, or Cancel.

  4. Read the result at the top of the page. It reports what the server did:

    • Rollback applied, with the id of the new version it recorded.
    • Sent for approval: Nothing has changed yet. An approver must approve request … before the rollback runs. The request appears in the approvals queue as a Release.
    • This rollback was REFUSED: another controller owns this Deployment, naming the owner and the evidence. See reconciler-owned components.
    • The error, if the rollback could not be worked out or the cluster did not take the write.

The rollback goes through the same path as Deploy selected: the ownership check, then approval (or an immediate apply when approvals are off), an operation in Activity and an audit record. Every write is read back.

What you confirmed is what is submitted. If the rollback’s list of removals has changed between the preview and Confirm rollback, for example because someone added a variable meanwhile, nothing is submitted:

The rollback changed since it was previewed, so nothing was submitted: it now removes …, and you confirmed …. Review the new list and confirm again.

The card then shows the new list. Read it and press Confirm rollback again.

Seylo reads the Deployment as it was recorded at that version and turns it into a forward release. The approver sees that resolved release — the tag, the env and the resources — and that is exactly what runs.

  • Image tag. The tag that version ran.
  • Environment variables, exactly as they were. The container’s environment variables, inline values and ConfigMap keys, are replaced with that version’s set. A variable that version set is set back to its value then. A variable added since that version is removed. A version that recorded no environment variables empties them. This is different from an ordinary release, which merges the variables it sets and leaves the rest alone.
  • Secret-sourced variables are left alone. A variable whose value comes from a Secret is not part of what is restored. One added since stays, and one that version had and that has since gone isn’t put back. The confirmation names them by key so you know.
  • CPU and memory. If that version set any request or limit, all four (CPU request, CPU limit, memory request, memory limit) are set back to that version’s values, and one that version did not have is removed. If that version set none, resources are left as they are.

Only the first container of the Deployment is restored. Probes, volumes, sidecars, the Service and the Ingress are not touched. To restore those, use the manifest editor.

The request’s summary ends with what the rollback removes, such as [env REPLACED: removes FEATURE_X, LEGACY_URL] or [env REPLACED: removes nothing]. Its detail has a section, Rollback to commit …: what it does to env, with the same list the requester confirmed.

If a variable is added to the workload after that review and before the change is applied, the rollback would delete a variable nobody saw. It is refused instead, and nothing is applied:

Refused, nothing was applied: this change replaces the env of …, and it would now also remove …, which was not in the list of removals that was reviewed (…).

Review the rollback again from History, so the removal is seen, or add the variable to that version first.

Use this when you need to undo a change that a release cannot express, such as a probe, a volume, a Service port or an Ingress host.

  1. Open the manifest editor for the component (Per-component tools → Edit manifests) and choose the tab: deployment, service or ingress.

  2. In History, press View deployment @ this on the version you want. You see that resource as it was, with a diff against the version before it.

  3. Press Load into editor to roll back. The old YAML replaces the editor’s content and the notes are filled in as Roll back deployment to commit ….

  4. Press Validate, then Submit for approval.

This restores every field of that one resource, including removing anything added since. Repeat for the Service and the Ingress if they changed as well. It goes through approval like any manifest edit. For a resource that a reconciler owns, it is refused until you acknowledge the owner.

If Argo CD or Flux owns the Deployment, a rollback through Seylo is reverted at the next sync, and Helm overwrites it at the next helm upgrade. Seylo refuses these writes unless you acknowledge the owner by name. The durable rollback is at the source: revert the commit in the repository Argo CD or Flux watches, or set the chart values back.

If you need the old version running now, all three paths let you proceed on the record. The refusal names the owner and offers a box that starts “I understand this change will be reverted by the controller above…” (“…overwritten by that owner” for Helm). Tick it and press the same button again: Deploy selected, Confirm rollback for the same version, or Submit for approval in the manifest editor. Your acknowledgement and your name are stored on the request, shown to the approver, and written to the audit log. Then change the source too, or the controller puts the newer version back.

When a release breaks a workload - pods that crash-loop soon after a change, or an image that cannot be pulled - Nightshift proposes the rollback for you, as a fix with its evidence, a check that it worked, and an undo. It goes back to:

  • the previous version in Seylo’s history, when the release was made through Seylo and the live image is the one Seylo recorded; or
  • the Deployment’s own previous revision, when the release was made with kubectl, a pipeline or another tool, so Seylo has no record of what ran before. That is the previous ReplicaSet, the revision kubectl rollout undo goes back to. Only the fields that differ are changed, container by container, each checked against the live Deployment just before it is applied.

The second kind always waits for a person’s approval and never runs unattended, whatever grants you have signed: Seylo did not make the change it undoes, so only a person knows whether going back is wanted. It is refused when the previous revision adds or removes a container; use kubectl rollout undo for that. Details are in Nightshift’s fixes.

You see What it means What to do
No history recorded yet for this component Seylo has never written this component Release an earlier tag instead. Seylo starts recording from the first change it makes
No commit matching "…" found in history for acme-prod/shop/checkout-api. The version is not in this component’s history Refresh the history and pick again
Could not find an image: line when you release a tag of a workload Seylo had not deployed before A defect fixed in 0.4.0. Before it, releasing a new tag of a workload Seylo had not yet recorded failed this way; and where an image-only release did run, it set the tag on the first container listed (which can be a sidecar) rather than the one named Release the tag again on 0.4.0 or later: it is set on the container you named
Could not determine the image tag from deployment.yaml at commit …. That version’s Deployment has no image line Seylo can read a tag from Use the manifest editor path for that version
This rollback was REFUSED: another controller owns this Deployment A controller owns the Deployment. Nothing was applied Roll back at the source, or tick the acknowledgement and press Confirm rollback for the same version again
Could not work out what this rollback would change, so it was not offered: … Seylo couldn’t read that version or the current Deployment to compare them. Nothing was submitted Read the rest of the message, check the agent is connected, and try again
The rollback changed since it was previewed, so nothing was submitted: The list of variables the rollback removes changed after you saw it Read the new list on the card and press Confirm rollback again
Refused, nothing was applied: this change replaces the env of A variable was added after the rollback was reviewed, and the rollback would delete it unseen Review the rollback again from History, or add the variable to that version first
Refusing to change Deployment shop/checkout-api: … A controller owns the Deployment Roll back at the source, or acknowledge the owner as described above
This needs the releaser role, which … does not hold. Rolling back is a write Ask an administrator
Rollout FAILED: … after a rollback The old version does not run either, for example its tag was deleted See what a failure looks like