Read an application's rollback targets
What this application’s deployment on the named cluster could be rolled back to: the shape of deployment found, the image tag it is running, the builds still in the registry, whether push-to-deploy is armed, and the list of things a rollback does NOT undo. Browser session authentication only (no bearer twin).
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Query Parameters
Response
Successful Response
What a deployment could be rolled back to. target_kind is one of "stack", "installation", "none" (a successful read that found nothing deployed) or "unknown" (Ankra could not establish what runs the application); unavailable_reason explains the last two. current_image_tag is null when the running tag could not be established - a digest pin, no tag, or containers that disagree - and never means "no image". A non-null targets_reason with an empty targets list means the registry listing did not succeed, not that nothing has been published.
One rollback as it happened. previous_image_tag is null when Ankra could not read what was running - never that nothing was running. watermark_commit_sha names the push-to-deploy build the rollback stamped so the convergence loop would not undo it, or "" when no build had been observed. not_reverted repeats what a rollback leaves untouched.