teleport-plugin-jira Helm 차트는 Jira Teleport 플러그인을 실행하며, 사용자가 Jira 프로젝트의 작업으로 Access Request를 수신하고 관리할 수 있도록 합니다.

GitHub에서 소스를 탐색할 수 있습니다.

이 레퍼런스는 teleport-plugin-jira 차트에서 사용 가능한 값들을 상세히 설명합니다.

teleport#

teleport contains the configuration describing how the plugin connects to your Teleport cluster.

teleport.address#

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 or teleport.example.com:3080
• joining an Auth: teleport-auth.example.com:3025 When the address is empty, tbot.teleportProxyAddress or tbot.teleportAuthAddress will be used if they are set.

teleport.identityFromSecret#

teleport.identityFromSecret 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 Jira guide for more information about how to acquire these credentials.

teleport.identitySecretPath#

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.

jira#

jira contains the configuration used by the plugin to authenticate to Jira and open issues.

You can pass the Jira apiToken:

• via the chart Values by setting jira.apiToken
• via an existing Kubernetes Secret by setting jira.apiTokenFromSecret

jira.url#

jira.url is the Jira URL. For example:

• a self-hosted Jira instance URL would be https://jira.example.com/.
• a Jira Cloud URL would be https://[your-jira].atlassian.net.

jira.url#

jira.url is the Jira username or email address associated with the API token.

jira.apiToken#

jira.apiToken is the Jira apiToken used by the plugin to interact with Jira. When set, the Chart creates a Kubernetes Secret for you.

This value has no effect if jira.apiTokenFromSecret is set.

jira.apiTokenFromSecret#

jira.apiTokenFromSecret is the name of the Kubernetes Secret containing the Jira apiToken. When this value is set, you must create the Secret before creating the chart release.

jira.apiTokenSecretPath#

jira.apiTokenSecretPath is the Kubernetes Secret key containing the Jira apiToken. The secret name is set via jira.apiTokenFromSecret.

jira.project#

jira.project is the Jira project in which the issues are opened. This value is mandatory.

jira.issueType#

jira.issueType is the issue type used when opening Jira issues.

http#

http contains the webhook configuration. When an issue is updated in Jira (approved or denied), Jira contacts the plugin via webhook to trigger the Teleport Access Request approval.

http.publicAddress#

http.publicAddress is the URL on which the callback server is accessible externally, e.g. [https://]teleport-proxy.example.com.

http.tlsFromSecret#

http.tlsFromSecret is the name of the Kubernetes Secret containing the TLS private key and certificate used by the webhook server.

http.tlsKeySecretPath#

http.tlsKeySecretPath is the field of the Kubernetes Secret containing the TLS private key used by the webhook server.

http.tlsCertSecretPath#

http.tlsCertSecretPath is the field of the Kubernetes Secret containing the TLS certificate used by the webhook server.

chartMode#

chartMode enables cloud-specific helpers. aws is the only supported value. When chartMode is aws, the created service wears the in-tree AWS LB controller annotations.

log#

log controls the plugin logging.

log.severity#

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.

log.output#

log.output sets the output destination for the Teleport process. This can be set to any of the built-in values: stdout, stderr.

The value can also be set to a file path (such as /var/log/teleport.log) to write logs to a file. Bear in mind that a few service startup messages will still go to stderr for resilience.

tbot#

tbot controls the optional tbot deployment that obtains and renews credentials for the plugin to connect to Teleport. Only default and mandatory values are described here, see the tbot chart reference for the full list of supported values.

tbot.enabled#

tbot.enabled controls if tbot should be deployed with the Jira plugin.

tbot.clusterName#

tbot.clusterName is the name of the Teleport cluster tbot and the Jira plugin will join. Setting this value is mandatory when tbot is enabled.

tbot.teleportProxyAddress#

tbot.teleportProxyAddress is the teleport Proxy Service address the bot will connect to. This must contain the port number, usually 443 or 3080 for Proxy Service. Connecting to the Proxy Service is the most common and recommended way to connect to Teleport. This is mandatory to connect to Teleport Enterprise (Cloud).

This setting is mutually exclusive with teleportAuthAddress.

For example:

tbot:
  teleportProxyAddress: "test.teleport.sh:443"

tbot.teleportAuthAddress#

tbot.teleportAuthAddress is the teleport Auth Service address the bot will connect to. This must contain the port number, usually 3025 for Auth Service. Direct Auth Service connection should be used when you are deploying the bot in the same Kubernetes cluster than your teleport-cluster Helm release and have direct access to the Auth Service. Else, you should prefer connecting via the Proxy Service.

This setting is mutually exclusive with teleportProxyAddress.

For example:

teleportAuthAddress: "teleport-auth.teleport-namespace.svc.cluster.local:3025"

tbot.joinMethod#

tbot.joinMethod describes how tbot joins the Teleport cluster. See the join method reference for a list of supported values and detailed explanations.

annotations#

annotations contains annotations to apply to the different Kubernetes objects created by the chart. See the Kubernetes annotation documentation for more details.

annotations.config#

annotations.config contains the Kubernetes annotations put on the ConfigMap resource created by the chart.

annotations.deployment#

annotations.deployment contains the Kubernetes annotations put on the Deployment or StatefulSet resource created by the chart.

annotations.pod#

annotations.pod contains the Kubernetes annotations put on the Pod resources created by the chart.

annotations.secret#

annotations.secret contains the Kubernetes annotations put on the Secret resource created by the chart. This has no effect when joinTokenSecret.create is false.

annotations.service#

annotations.service contains the Kubernetes annotations put on the Service resource created by the chart.

image#

image sets the container image used for plugin pods created by the chart.

You can override this to use your own plugin image rather than a Teleport-published image.

image.repository#

image.repository is the image repository.

image.pullPolicy#

image.pullPolicy is the Kubernetes image pull policy.

image.tag#

image.tag Overrides the image tag whose default is the chart appVersion.

Normally, the version of the Teleport plugin matches the version of the chart. If you install chart version 15.0.0, you'll use the plugin version 15.0.0. Upgrading the plugin is done by upgrading the chart.

imagePullSecrets#

imagePullSecrets is a list of secrets containing authorization tokens which can be optionally used to access a private Docker registry.

See the Kubernetes reference for more details.

podSecurityContext#

podSecurityContext sets the pod security context for any pods created by the chart. See the Kubernetes documentation for more details.

To unset the security context, set it to null or ~.

securityContext#

securityContext sets the container security context for any pods created by the chart. See the Kubernetes documentation for more details.

To unset the security context, set it to null or ~.

resources#

resources sets the resource requests/limits for any pods created by the chart. See the Kubernetes documentation for more details.

nodeSelector#

nodeSelector sets the node selector for any pods created by the chart. See the Kubernetes documentation for more details.

tolerations#

tolerations sets the tolerations for any pods created by the chart. See the Kubernetes documentation for more details.

affinity#

affinity sets the affinities for any pods created by the chart. See the Kubernetes documentation for more details.

serviceType#

serviceType sets the service type of the Kubernetes Service resource created by the chart.