Robots

Robot accounts are non-user accounts with unique credentials and permissions. Organization admins grant robot accounts access to individual repositories. Robot accounts access the repositories without using credentials tied to an individual user.

Warning
Upbound strongly recommends using robot accounts for any Kubernetes related authentication. For example, providing secrets required to install Kubernetes manifests. Use Upbound user accounts only with the up command-line or Upbound console.

Create a robot

You can create robot account from the Robots tab in the org settings pane. You can also create robots using the up CLI.

Assign a robot to a team

Make sure you’ve created the desired robot before assigning it to a team. To assign a robot to a team, do the following:

  1. Go to the Teams tab in the org settings pane.
  2. Select the team you want to assign a robot account.
  3. Select the Robot accounts tab
  4. Select the Add Robot Account button and select the robot you want.

Frequently asked questions

A robot token is like a service account. They have their own identity like service principals in a cloud provider.

A personal access token or “PAT” is a long-lived serialization of a specific Upbound user’s identity. Your personal access token can do everything your user can do in Upbound. Only use PATs when necessary and never share them with others.

In Upbound, robot tokens are currently scoped to inheriting Upbound Marketplace repository permissions from a team they’re assigned to.

You should use a robot token for your Upbound Marketplace CI to push new tags or as a package pull secret for private repositories.