Onboarding

Creating a team is how you onboard onto Core Platform. Teams own applications, environments, access, and the configuration that older docs and corectl commands may still call a tenant.

If you already have a team, you can jump to new-app to deploy a new application.

Create a team in the dashboard

Open the dashboard and go to Teams then Create. Enter the team name, description, contact email, and area.

Create team details in the dashboard

Continue through the wizard to choose where the team can deploy and review the generated configuration. When the change is merged, Core Platform provisions the team configuration and namespaces.

Create a team with corectl

Use corectl when you prefer a terminal workflow. The command still uses tenant terminology because the underlying platform configuration type is named tenancy.


corectl tenants create

You’ll be prompted for the following information about your new team:

name - Name of your team. Must be the same as your filename.
parent - Name of the parent team/tenant or root. Note: root is created implicitly.
description - Description for your team.
contactEmail - Metadata: Who is the contact for this team?
environments - which of the environments in Environments Repo you want to deploy to
repositories - if you have no existing applications then leave this empty. If migrating then add the repos with your applications (comma separated GitHub links)
adminGroup - will get permission to do all actions in the created namespaces - optional
readonlyGroup - will get read-only access to the created namespaces - optional

Both adminGroup and readonlyGroup are optional fields. However, without these set, the secret management feature will not work. You can still have access to the team’s namespaces by being in the parent’s admin and read-only groups, as it will inherit permissions to access children’s resources, with the exception of the secrets.

You are encouraged to use different adminGroup and readonlyGroup for each team because of cloud restrictions and security reasons. Maximum number of duplicated adminGroup or readonlyGroup is 20.

Once you fill the form, corectl will create a PR in the Environments Repo with a new file for the team tenancy configuration. Once the PR is merged, a configuration for the new team will be provisioned automatically.

Groups need to be in the gke-security-groups group! If you are a new team on the platform, you should create new admin and readOnly groups and either ask a platform operator to add them to gke-security-groups or add those groups to an already existing member of that group like platform-readonly.

Accessing your namespaces

Once the PR is merged, everyone in the groups will have access to the namespaces created for that team.

If you access the cluster from the local machine, you need to connect to the cluster. The easiest way to do this is using corectl:


corectl env connect <env-name>

For example, to check a namespace for a team named myfirstteam:


kubectl get namespace myfirstteam
NAME          STATUS   AGE
myfirstteam   Active   30s