Links

Supported Integrations (connectors)

Supported integrations for agents
Kubiya offers out-of-the-box integrations that can provisioned and work with agents without further configuration

Supported Integrations

Integration Behavior with agents

Kubiya will require any user attempting to start an instance of an agent with a defined connector to also enable access to the relevant connector (e.g. enabling access for GitHub so that the agent can clone private repositories).
GitHub
  • An environment variable called GH_TOKEN (supported by the GitHub CLI interface) will be passed to the agent container environment automatically, allowing users to user GitHub from within the agent. The environment variable value will be based on the GitHub temporary OAuth2 token granted by Kubiya
Amazon Web Services (AWS)
  • For organizations that connected their AWS account - the agent container environment will get temporary AWS credentials from Kubiya automatically, allowing the agent to use AWS libraries or the AWS CLI with the defined role
Kubernetes
  • The agent base image will automatically set an in-cluster context on boot time - which means the agent will be able to access the Kubernetes API using kubectl without further integration (as it lives inside the cluster already)
Atlassian JIRA
  • An environment variable called JIRA_CLI_TOKEN (supported by the JIRA CLI interface) will be passed to the agent container environment automatically, allowing users to user JIRA from within the agent. The environment variable value will be based on the JIRA temporary OAuth2 token granted by Kubiya
Slack
  • The organization Slack OAuth2 token will be passed to the container environment, allowing Slack-based requests to the agent to be able to interact with the Slack API in order to send messages, create channels, etc