Containers and Kubernetes

AWS Secrets Manager support

The VerticaDB operator can access secrets that you store in Amazon Web Service's AWS Secrets Manager. This lets you maintain a single location for all sensitive information that you share between AWS and Vertica on Kubernetes.

For details, see Secrets management.

VerticaRestorePointsQuery custom resource definition

The VerticaRestorePointsQuery custom resource definition (CRD) retrieves restore points from an archive so that you can restore objects or roll back your database to a previous state. The custom resource (CR) specifies an archive and an optional period of time, and the VerticaDB operator retrieves restore points saved to the archive.

For details, see VerticaRestorePointsQuery custom resource definition and Custom resource definition parameters.

VerticaDB CRD parameters

The VerticaDB custom resource definition provides the following CRD parameters to revive from a restore point:

• restorePoint.archive
• restorePoint.id
• restorePoint.index

You can use the VerticaRestorePointsQuery custom resource definition to retrieve saved restore points. For details about the CRD parameters, see Custom resource definition parameters.

VerticaScrutinize custom resource definition

The VerticaScrutinize CRD runs scrutinize to collect diagnostic information about a VerticaDB CR. Vertica support might request you provide this diagnostic information while resolving support cases.

For details, see VerticaScrutinize custom resource definition.

Namespace-scoped operators

You can use Helm charts to deploy the VerticaDB operator to watch only resources within a namespace. This requires that you set the following Helm chart parameters during installation:

• controllers.enable
• controllers.scope

For installation instructions, see Installing the VerticaDB operator. For details about each parameter, see Helm chart parameters.

Node Management Agent (NMA) sidecar

Vertica on Kubernetes runs the Node Management Agent in a sidecar container. The NMA exposes a REST API the VerticaDB operator uses to administer a cluster.

For details, see Containerized Vertica on Kubernetes.

Support OpenShift restricted-v2 SCC

Vertica on Kubernetes supports the restricted-v2 SCC for OpenShift. This is the most restrictive SCC available.

For details about the Vertica and OpenShift integration, see Red Hat OpenShift integration.

Namespace-scoped operators

You can use Helm charts to deploy the VerticaDB operator to watch only resources within a namespace. This requires that you set the following Helm chart parameters during installation:

• controllers.enable
• controllers.scope

For installation instructions, see Installing the VerticaDB operator. For details about each parameter, see Helm chart parameters.

Containerized Kafka Scheduler

Vertica on Kubernetes supports the Kafka scheduler, a mechanism that automatically loads data from Kafka into a Vertica database table. Vertica packages the scheduler in a Helm chart so you can easily deploy a scheduler into your Kubernetes environment.

For details, see Containerized Kafka Scheduler.