Onboarding an EKS Cluster

This article describes the steps to onboard an Amazon Elastic Kubernetes Service (EKS) cluster to Britive. 

Britive configuration

1. Log in to Britive with administrator privileges.
2. Click Admin -> Application and Access Profile Management.
3. From the Tenant Applications page, click on Create Application.
4. On the Add Application page, click the Add (+) sign next to the Kubernetes application.
5. In the Application tab, enter the following values:
   1. Enter the Application Name.
   2. Enter the Application Description, if required.
6. Click Next. The Settings tab is displayed.
7. Check the Display programmatic access keys to allow the user to copy the credentials to the clipboard after they check out programmatic access profiles. Users can only access the keys through CLI or scripts if the option is not selected.
8. Click Save.
9. Click the Create Entity button.
10. Enter the following details in the Create Environment/Environment Group page:
    1. Select Environment in the Entity Type.
    2. Enter Entity Name.
    3. Enter Entity Description.
    4. Click Save.
11. On the Settings tab, Britive automatically creates OIDC attributes to use when setting up the federation trust with the EKS cluster. In the next steps, you need to add these attributes to the EKS cluster.
12. Enter the API server endpoint in the Kubernetes API Server URL. Copy this URL from the EKS Admin portal, Overview tab. For more information on obtaining this URL, see the Amazon EKS cluster endpoint.
13. Enter Certificate Authority information in the Certificate (CA Cert). You can get the certificate authority information from the EKS admin portal, the Overview tab.

Cluster configuration 

1. On the EKS admin dashboard, select the cluster you are working with and click Associate Identity Provider in the OIDC identity provider section on the Access tab.
2. Enter a name for this connection, e.g., britive
3. Paste the values for the Issuer URL and Client ID attributes generated on the Britive application configuration for this specific cluster entity.
4. Add the following values for the claims mapping. These values refer to the user and group claims present in the OIDC token created by Britive.
   1. The Username claim is sub.
   2. The Groups claim is groups.