IsValidSubclusterName validates the subcluster name is valid.

MakeCondition create and initialize a new metav1.Condition.

MakeVDB is a helper that constructs a fully formed VerticaDB struct using the sample name.

MakeVDBForHTTP is a helper that constructs a VerticaDB struct with http enabled.

MakeVDBForScrutinize is a helper that constructs a VerticaDB struct for scrutinize.

MakeVDBForVclusterOps is a helper that constructs a VerticaDB struct for vclusterops.

MakeVDBName is a helper that creates a sample name for test purposes.

ParseVersionOutput will parse the raw output from the --version call and build an annotation map.

Starting in this version, new databases would have HTTPS certs be auto generated during the bootstrap process.

AutoRestartVertica indicates whether the operator should restart the vertica process.

This automatically picks between offline and online upgrade.

The version of the server that doesn't support cgroup v2.

The database in the communal path will be initialized with a create_db.

Like CommunalInitPolicyCreate, except it will skip the install of the packages.

The database in the communal path will be initialized in the VerticaDB through a revive_db.

Only schedule pods to run with the vertica container.

The minimum version that we can use the option with create DB to skip the package install.

DBInitialized indicates the database has been created or revived.

Starting in v23.4.0, we added some new config parameters for settings that were typically done post create using SQL -- setting the default subcluster name and preferred k-safety.

the default condition reason in case that field was left unset.

Valid values for EncryptSpreadComm.

Valid values for EncryptSpreadComm.

Starting in v24.3.0, we call vclusterops API to get node details instead of executing vsql within the pod.

When httpServerMode is Auto, this is the minimum server version that will start Vertica's http server.

The minimum version that can start Vertica's http server.

Starting in v24.1.0, we use server logrotate and not depend on cron job.

This is the minimum vertica version that the operator currently supports.

starting in v24.3-4, v24.4-1, and v25.0-0 pausing sessions works a little differently.

Starting in v24.2.0, NMA is deployed in a sidecar container.

The NMA TLS secret can be stored in an external secret store.

The version that added read-only state.

The version that added sandbox state.

Upgrade is done fully offline.

Like read-only online upgrade, however it allows for writes.

The minimum version that allows for online upgrade.

The different type names for the subcluster type.

Upgrade is done online.

The minimum version that allows for read-only online upgrade.

The version that added the --force option to reip to handle up nodes.

Starting in v24.3.0, database replication via vclusterops is supported.

Starting in v24.2.0, restoring from a restore point in archive is supported.

Additional server config parameters.

A sandbox primary subcluster is a secondary subcluster that was the first subcluster in a sandbox.

Starting in v24.3.0, sandboxing a subcluster with the operator is supported.

SaveRestorePointNeeded is a condition that when set to true, make the operator create a restore point, using the spec.restorePoint.archive as the archive name to save to.

Starting in v24.4.0, saving a restore point to an existing archive is supported.

Starting in v24.2.0, vcluster scrutinize command can read the database password from secret(k8s, aws, gsm).

Starting in v24.2.0, vcluster scrutinize command accepts a time range for collecting logs.

In 23.3.0, the EncryptSpreadComm config parm can be set during the create db call.

SuperUser is an automatically-created user in database creation.

list of reasons for conditions' transitions.

UpgradeInProgress indicates if the vertica server is in the process of having its image change.

Set constant Upgrade Requeue Time.

Starting in v24.1.0, the default deployment method supported changes from admintools to vclusterops for official releases of vertica-k8s images.

VerticaRestartNeeded is a condition that when set to true will force the operator to stop/start the vertica pods.

AddToScheme adds the types in this group-version to the given scheme.

GroupVersion is group version used to register these objects.

SchemeBuilder is used to add go types to the GroupVersionKind scheme.

Affinity is used instead of corev1.Affinity and behaves the same.

Holds details about the communal storage.

LocalObjectReference is used instead of corev1.LocalObjectReference and behaves the same.

RestorePointPolicy is used to locate the exact archive and restore point within archive when a database restore is intended.

Defines a number of pods for a specific subcluster.

SubclusterSelection is used to select between existing subcluster by name or provide a template for a new subcluster.

SubclusterStatus defines the per-subcluster status that we track.

VerticaDB is the CR that defines a Vertica Eon mode cluster that is managed by the verticadb-operator.

VerticaDBList contains a list of VerticaDB.

VerticaDBPodStatus holds state for a single pod in a subcluster.

VerticaDBSpec defines the desired state of VerticaDB.

VerticaDBStatus defines the observed state of VerticaDB.