Table: nomad_plugin - Query Nomad Plugins using SQL

A Nomad Plugin is a crucial component in the Nomad ecosystem, enabling extensibility and customization. Plugins are leveraged to integrate with various external systems, providing a wide range of functionality, from task drivers to device plugins and log storage. It is an essential tool for managing and extending the capabilities of your Nomad environment.

Table Usage Guide

The nomad_plugin table provides insights into Plugins within Nomad. As a DevOps engineer, explore plugin-specific details through this table, including its configuration, status, and driver details. Utilize it to uncover information about plugins, such as their current state, associated tasks, and the overall health of the plugin.

Examples

Basic info

Explore which plugins are required for your controller by determining their version and provider. This aids in assessing the elements within your system for better management and updates.

select
  id,
  controller_required,
  version,
  create_index,
  modify_index,
  provider
from
  nomad_plugin;

select
  id,
  controller_required,
  version,
  create_index,
  modify_index,
  provider
from
  nomad_plugin;

List CSI plugins that require a controller

Analyze the settings to understand which CSI plugins necessitate a controller. This allows you to pinpoint the specific locations where controllers are required, ensuring your system configuration is optimized.

select
  id,
  title,
  version,
  create_index,
  modify_index,
  provider
from
  nomad_plugin
where
  controller_required;

select
  id,
  title,
  version,
  create_index,
  modify_index,
  provider
from
  nomad_plugin
where
  controller_required = 1;

Show the number of nodes and controllers associated with each plugin

Discover the health status of your system by identifying the number of healthy nodes and controllers for each plugin. This information can be instrumental in assessing system performance and identifying potential areas for improvement.

select
  id,
  version,
  nodes_healthy,
  controllers_healthy
from
  nomad_plugin;

select
  id,
  version,
  nodes_healthy,
  controllers_healthy
from
  nomad_plugin;

Show the number of expected nodes for each plugin

Assess the elements within each plugin to understand the expected number of nodes. This information can be useful in planning and allocating resources effectively.

select
  id,
  version,
  nodes_healthy,
  nodes_expected
from
  nomad_plugin;

select
  id,
  version,
  nodes_healthy,
  nodes_expected
from
  nomad_plugin;

Schema for nomad_plugin

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form, e.g. connection_name.
allocations	jsonb		An array of AllocationListStub structures that represent the storage allocations made by the CSI plugin.
controller_required	boolean		A boolean indicating whether the CSI plugin requires a controller.
controllers	jsonb		A map that associates the ID of each node with the CSIInfo fingerprint results for that node's controller.
controllers_expected	bigint		The number of expected controllers.
controllers_healthy	bigint		The number of healthy controllers.
create_index	bigint		The Raft index at which the CSI plugin was created.
id	text	=	A unique identifier for the CSI plugin.
modify_index	bigint		The Raft index at which the CSI plugin was last modified.
nodes	jsonb		A map that associates the ID of each node with the CSIInfo fingerprint results for that node.
nodes_expected	bigint		The number of expected nodes.
nodes_healthy	bigint		The number of healthy nodes.
provider	text		The name of the provider that created the CSI plugin.
title	text		The title of the plugin.
version	text		The version of the CSI plugin.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- nomad

You can pass the configuration to the command with the --config argument:

steampipe_export_nomad --config '<your_config>' nomad_plugin