vastdataorg/vms-operator repository overview

⁠VAST VMS Operator

⁠Introduction

This image runs the VAST VMS operator, a Kubernetes controller that manages objects in the VAST Management System (VMS) declaratively. VMS objects — tenants, views, view policies, quotas, users, groups, roles, S3 lifecycle rules, API tokens, Kafka topics — are represented as Custom Resources, and the operator continuously reconciles them against the VMS REST API.

Published as vastdataorg/vms-operator. The latest tag tracks the most recent GA release; pin a specific version with vastdataorg/vms-operator:TAG.

⁠What it does

• Reconciles each Custom Resource against the VMS REST API: fetch desired state, fetch external state, diff, actuate (POST / PATCH / DELETE), then report observed state in status.
• Corrects drift continuously. A change made directly in VMS — through vcli, the GUI or the API — is detected on the next poll and reverted to what the CR declares.
• Deletes safely. A finalizer holds the resource until the external object is verifiably gone, so a deleted CR never leaves an orphan behind in VMS.
• Refuses destructive updates. Changing an immutable field emits an UpdateFailed event and stops, rather than deleting and recreating the object.
• Backs off rather than overloading VMS. 429 and 5xx responses requeue with exponential backoff.
• Resolves references between resources. A resource whose dependency does not exist yet waits and retries; there is no required creation order.

⁠Resources

Custom Resources are served under the vms.vastdata.com API group, with the VMS-assigned identifier recorded in status.externalID for subsequent reads, updates and deletes.

⁠Configuration

This image is deployed by the vms-operator Helm chart and configured through its values.yaml: the VMS endpoint, the Secret holding VMS credentials, an optional tenant scope, and TLS verification settings. See the chart documentation for the full list of supported values.

⁠License

Refer to the VAST Data software license terms.