Skip to main content

Bring in your teams

Developers ship and roll back without cluster-admin. Your CI ships the same way with its own key. Each team's apps live in their own namespace, with their own cost.

Members and roles come with a team organization on the Enterprise plan.

Add developers​

  1. Open Organization settings > Members and select Add Member.

  2. Enter their User ID and pick a Role: Editor for developers, who deploy, update and roll back; Administrator for the platform team, who own clusters, add-ons and profiles.

    Open zoom view

    Add New Member: the User ID and the role picker with Viewer, Editor and Administrator

    Add New Member: the User ID and the role picker with Viewer, Editor and AdministratorAdd New Member: the User ID and the role picker with Viewer, Editor and Administrator

Give CI its own key​

  1. Open Service Accounts and select Create service account. Name it ci-deploy, pick Editor, and say what uses it.

    Open zoom view

    Create service account: the name ci-deploy, a role and a description

    Create service account: the name ci-deploy, a role and a descriptionCreate service account: the name ci-deploy, a role and a description
  2. Create its key with an expiry, and store it in your CI's secrets. It is shown once.

Give each team its namespace​

When a team deploys, it sets its own Namespace on the wizard's Options step, such as team-checkout. Its apps stay together there, and the cluster's Cost tab shows each team's spend under Cost allocation by Namespace.

Teams that must not see each other at all get their own organization.

Next​

Deploy an app