ModelsPDF version

Cloudera AI Registry permissions

Cloudera AI Registry's permissions for the following actions are separate from workbench permissions, but they are inherited from environment level workbench permissions.

  • create
  • delete
  • getKubeconfig
  • grant/list/revoke access

Therefore, if you have the MLAdmin role on an environment, you can perform these actions for Cloudera AI Registry instances, but an MLUser cannot.

Remote access to a Cloudera AI Registry works similarly to workbench remote access. In addition to AI Registry, but an MLUser cannot.

Remote access to a AI Registry works similarly to workbench remote access. In addition to downloading the kubeconfig file, you need to use Grant/List/RevokeModelRegistryAccess endpoints to manage what cloud user identity can access the Kubernetes cluster using your cloud credential.

We want your opinion

How can we improve this page?

What kind of feedback do you have?