Skip to main content
This page documents the runtime contract between you and the Vantage operator: the phases the operator runs through on every reconcile, the conditions it publishes back on the Vantage resource, how to force a retry, and what happens when you delete the resource. For the field-level schema, see API reference. For the conceptual overview, see Architecture.

Reconcile phases

The operator’s reconcile is structured as five sequential phases. Each phase contains validators or steps that must all succeed before the operator advances to the next phase. A failure in any step is fatal to the reconcile and surfaces on status.degradationReasons[].

Status conditions

The operator publishes installation state through condition types on status.conditions[]:
  • Progressing: status is True while the process is ongoing.
  • Ready: status is True on success.
  • Degraded: status is True if an error is encountered at any point. In this case, status.degradationReasons[] contains the details of the error(s).
Preflight also publishes one condition per check. A failed check sets its condition to False with reason ValidationFailed and a message that names the problem. The reason on Progressing and Degraded shows where the reconcile stopped:
The Azure and self-managed installation procedures wait on condition=Ready (kubectl wait --for=condition=Ready vantages.vantage.abbyy.com/$release_name). Ready does not cover skill installation, which runs as a separate job (see below), and you should also verify the generated ArgoCD applications. See the Vantage.status reference for the full status schema.

Skill installation runs separately

Skills are installed by a separate Kubernetes job in the install namespace, not by an ArgoCD application. The job is not surfaced via ArgoCD and is not reflected in the conditions above, so Ready does not indicate that skill installation has finished. You can use Vantage while the job is running. Monitor the job directly:

Forcing a retry

To retry installation (for example, after fixing a Key Vault permission), annotate the Vantage resource with vantage.abbyy.com/reprocess (any value):
Any change to spec starts a new reconcile from Preflight, including a helm upgrade that changes a value mapped to the resource. Changes outside the resource do not: a Key Vault permission, a Kubernetes Secret, a database, or chart values that only change the workloads ConfigMap, such as workloadsConfigMap.additionalMetadata or defaultSkills. After such a change, apply the annotation. When the operator processes the annotation, it sets Ready and Degraded to False, deletes the OCI migration job so that the migration runs again, removes the annotation, and restarts the reconcile from Preflight. Because the annotation is removed, apply it again for each retry.

Deleting a Vantage resource

The operator adds the vantage.abbyy.com/cleanup finalizer to the Vantage resource. When you delete the resource (for example with helm uninstall of the vantage-selfhosted release), the operator deletes its ArgoCD ApplicationSet, waits for ArgoCD to remove the generated Applications and the workloads they installed, removes the SecretProviderClass resources it created, and then removes the finalizer. Keep the operator and ArgoCD running until the resource is gone. If either is removed first, the resource stays in Terminating. Deleting the resource does not remove your databases, Redis, Azure storage accounts, Key Vault or Kubernetes Secret resources, or the artifacts in your destination registry. With custom storage (storage.custom), the storage PVC is part of the deleted workloads; whether its data survives depends on the reclaimPolicy of its StorageClass.

What’s next

API reference

Field-by-field reference for every spec and status property.

Troubleshooting

Symptom → diagnosis → fix for common reconcile failures.