Identity Providers (OIDC)¶
This guide explains how you can integrate your Rok installation with an external Identity Provider so that you can continue using Rok services and your identity can be verified with a provider of your choice.
See also
What You’ll Need¶
- A configured management environment.
- Your clone of the Arrikto GitOps repository.
- An existing Kubernetes cluster.
- A working Rok deployment.
- A working Kubeflow deployment.
- Access to the cluster’s running services.
Procedure¶
Choose one of the following options, based on the Identity Provider you want to use.
This section will guide you through using GitLab for authenticating access to Rok and Kubeflow.
This section will guide you through using Google for authenticating access to Rok and Kubeflow.
This section will guide you through using Okta for authenticating access to Rok and Kubeflow.
This section will guide you through using PingID for authenticating access to Rok and Kubeflow.
This section will guide you through using Azure AD (Active Directory) for authenticating access to Rok and Kubeflow.
This section will guide you through using AWS Cognito for authenticating access to Rok and Kubeflow.