Onboarding an EKS Cluster
    • PDF

    Onboarding an EKS Cluster

    • PDF

    Article Summary

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

    Britive configuration

    1. Login 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 Add Application page, click Add (+) sign inline 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 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 about getting this URL, see 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, Overview tab.

    Cluster configuration 

    1. On the EKS admin dashboard, click Associate Identity Provider in the OIDC identity provider section on the Access tab.
    2. Enter the name. For example, britive.
    3. Copy over the Issuer URL and Client ID attributes from the Britive application configuration.
    4. The username should map to the “sub” claim from the token and the group memberships will be available on the “groups” claim.

    Was this article helpful?