teleport-plugin-pagerduty Chart Reference
The teleport-plugin-pagerduty
Helm chart is used to configure the PagerDuty Teleport plugin, which allows users to receive Access Requests as pages via PagerDuty.
You can browse the source on GitHub.
This reference details available values for the teleport-plugin-pagerduty
chart.
Backing up production instances, environments, and/or settings before making permanent modifications is encouraged as a best practice. Doing so allows you to roll back to an existing state if needed.
teleport
teleport
contains the configuration describing how the plugin connects to
your Teleport cluster.
teleport.address
Type | Default |
---|---|
string | "" |
teleport.address
is the address of the Teleport cluster the plugin
connects to. The address must contain both the domain name and the port of
the Teleport cluster. It can be either the address of the auth servers or the
proxy servers.
For example:
- joining a Proxy:
teleport.example.com:443
orteleport.example.com:3080
- joining an Auth:
teleport-auth.example.com:3025
teleport.identitySecretName
Type | Default |
---|---|
string | "" |
teleport.identitySecretName
is the name of the Kubernetes secret
that contains the credentials for the connection to your Teleport cluster.
The secret should be in the following format:
apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: teleport-plugin-identity
data:
auth_id: #...
Check out the Access Requests with PagerDuty guide for more information about how to acquire these credentials.
teleport.identitySecretPath
Type | Default |
---|---|
string | "auth_id" |
teleport.identitySecretPath
is the key in the Kubernetes secret
specified by teleport.identitySecretName
that holds the credentials for
the connection to your Teleport cluster. If the secret has the path,
"auth_id"
, you can omit this field.
pagerduty
pagerduty
contains the configuration used by the plugin to authenticate to PagerDuty.
You can pass the PagerDuty API key:
- via the chart Values by setting
pagerduty.apiKey
- via an existing Kubernetes Secret by setting
pagerduty.apiKeyFromSecret
pagerduty.apiKey
Type | Default |
---|---|
string | "" |
pagerduty.apiKey
is the PagerDuty API key used by the plugin to interact
with PagerDuty. When set, the Chart creates a Kubernetes Secret for you.
This value has no effect if pagerduty.apiKeyFromSecret
is set.
pagerduty.apiKeyFromSecret
Type | Default |
---|---|
string | "" |
pagerduty.apiKeyFromSecret
is the name of the Kubernetes Secret
containing the PagerDuty apiKey. When this value is set, you must create the
Secret before creating the chart release.
pagerduty.apiKeySecretPath
Type | Default |
---|---|
string | "pagerdutyApiKey" |
pagerduty.apiKeySecretPath
is the Kubernetes Secret key
containing the PagerDuty API key. The secret name is set via pagerduty.apiKeyFromSecret
.
pagerduty.userEmail
Type | Default |
---|---|
string | "" |
pagerduty.userEmail
is the PagerDuty bot email.
log
log
controls the plugin logging.
log.severity
Type | Default |
---|---|
string | "INFO" |
log.severity
is the log level for the Teleport process.
Available log levels are: DEBUG
, INFO
, WARN
, ERROR
.
The default is INFO
, which is recommended in production.
DEBUG
is useful during first-time setup or to see more detailed logs for debugging.