-
Notifications
You must be signed in to change notification settings - Fork 350
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Improve KF authentication handling (#2257)
Enables the user to choose an authentication type for Kubeflow Runtime configurations Closes #2240 Closes #2107 Closes #2108
- Loading branch information
Showing
8 changed files
with
921 additions
and
249 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -92,6 +92,7 @@ To create a runtime configuration for a Kubeflow Pipelines deployment: | |
elyra-metadata install runtimes \ | ||
--display_name="My Kubeflow Pipelines Runtime" \ | ||
--api_endpoint=https://kubernetes-service.ibm.com/pipeline \ | ||
--auth_type="DEX_STATIC_PASSWORDS" \ | ||
[email protected] \ | ||
--api_password=mypassword \ | ||
--engine=Argo \ | ||
|
@@ -115,6 +116,7 @@ elyra-metadata install runtimes \ | |
--name="my_kubeflow_pipelines_runtime" \ | ||
--display_name="My Kubeflow Pipelines Runtime" \ | ||
--api_endpoint=https://kubernetes-service.ibm.com/pipeline \ | ||
--auth_type="DEX_STATIC_PASSWORDS" \ | ||
[email protected] \ | ||
--api_password=mynewpassword \ | ||
--engine=Argo \ | ||
|
@@ -181,16 +183,23 @@ The namespace used to run your pipeline in Kubeflow Pipelines. This setting is r | |
|
||
Example: `anonymous` | ||
|
||
##### Kubeflow authentication type (auth_type) | ||
Authentication type Elyra uses to gain access to Kubeflow Pipelines. This setting is required. Supported types are: | ||
- No authentication (`NO_AUTHENTICATION`). | ||
- Kubernetes service account token (`KUBERNETES_SERVICE _ACCOUNT_TOKEN`). This authentication type is only supported if Elyra runs as a pod in Kubernetes, e.g. as a Kubeflow notebook server. You must configure a service account token in Kubernetes, as outlined [here](https://www.kubeflow.org/docs/components/pipelines/sdk/connect-api/#multi-user-mode). | ||
- DEX configured for static password authentication (`DEX_STATIC_PASSWORDS`). This authentication requires a username and a password. | ||
- DEX configured for LDAP authentication (`DEX_LDAP`). This authentication requires a username and a password. | ||
- DEX (`DEX_LEGACY`). Use this type only if none of the other authentication types applies or if your Kubeflow deployment is not configured for any other listed type. This authentication requires a username and a password. | ||
|
||
##### Kubeflow Pipelines API endpoint username (api_username) | ||
Username used to access your KubeFlow Pipelines API endpoint. This setting is required if the Kubeflow Pipelines deployment is multi-user, auth enabled. | ||
Currently, only Dex `staticPasswords` and `LDAP Connector` authentication types are supported. | ||
|
||
(NOTE: if multiple Dex authentication types are enabled, we will try to use `staticPasswords`) | ||
A username is required for most authentication types. Refer to the Kubeflow authentication type setting for details. | ||
|
||
Example: `[email protected]` | ||
|
||
##### Kubeflow Pipelines API endpoint (api_password) | ||
Password used to access your KubeFlow Pipelines API endpoint. This setting is required if the Kubeflow Pipelines deployment is multi-user, auth enabled. | ||
##### Kubeflow Pipelines API endpoint password (api_password) | ||
|
||
A password is required for most authentication types. Refer to the Kubeflow authentication type setting for details. | ||
|
||
Example: `mypassword` | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.