Skip to content

Revoke and rotate

After it enrolls, the agent holds its own long-lived credential in a Secret, seylo-agent-credential, in its namespace. Revoking an agent makes Seylo refuse that credential from then on. It is the quickest way to cut a cluster off from Seylo, and it needs nothing from the cluster.

An admin can revoke from two places:

  • Admin → Clusters, the cluster’s ⋯ menu, Revoke agent; or
  • the cluster’s Agent page.

Both ask you to confirm. The menu item is off for a cluster with no enrolled agent. Revoking does four things at once:

  • every agent credential for that cluster is revoked;
  • every enrollment token not yet used is invalidated;
  • the agent’s connection is dropped, on whichever Seylo server holds it;
  • an agent-revoked entry is written to your organisation’s audit log, with who did it and how many credentials and tokens it covered.

The cluster is then unmanageable until a new agent enrolls: Seylo can read nothing from it and apply nothing to it.

A revoked agent is refused when it tries to connect, with auth-agent-revoked. Pages that need the cluster answer straight away that the agent is offline, instead of waiting for a reconnect.

The agent keeps running in your cluster, and keeps trying. Revoking changes what Seylo accepts, not what runs in the cluster. Seylo slows the retries, each refusal answered later than the last, and the cluster’s agent status says that a revoked pod is still knocking, with how to stop it: re-enroll it or uninstall it. See troubleshooting.

There is no separate rotate button. To give a cluster a new credential, revoke the old one and enroll again:

  1. Revoke the agent, as above, if the old credential must stop working now.

  2. On the cluster’s Agent page, issue a new enrollment token. The cluster’s ⋯ menu has the same thing as Re-issue enrollment token. The token is shown once, and it works once.

  3. In the cluster, delete the old credential Secret:

    Terminal window
    kubectl --namespace seylo-agent delete secret seylo-agent-credential
  4. Run the install command from the Agent page, which carries the new token. Upgrade the agent shows the Helm form for an agent that is already installed.

To re-issue a token without revoking, use the same menu item. The connected agent keeps working; the token is for a new enrollment only.

Revoking does not remove anything. To remove the agent, the observability stores and what they leave behind, follow leaving Seylo.