Revamp profile installation instructions for MR#854
Conversation
Signed-off-by: lucferbux <lferrnan@redhat.com>
2ba2892 to
6adeaaa
Compare
013e57d to
0c69e72
Compare
Signed-off-by: lucferbux <lferrnan@redhat.com>
0c69e72 to
985cf55
Compare
|
I need to read through them again with gained knowledge about the `profile'. Please give me some time to go through it again. |
Co-authored-by: Paul Boyd <paul@camelot.email> Signed-off-by: Lucas Fernandez <lucasfernandezaragon@gmail.com>
Signed-off-by: lucferbux <lferrnan@redhat.com>
|
I think this will help a lot. /lgtm |
| These instructions assume that you've installed Kubeflow from the [manifests](https://github.com/kubeflow/manifests/), if you're using a distribution consult its documentation instead. | ||
|
|
||
| As the default Kubeflow installation provides an Istio mesh, apply the necessary manifests: | ||
| Kubeflow Central Dashboard uses [Profiles](https://www.kubeflow.org/docs/components/central-dash/profiles/) to handle user namespaces and permissions. By default, the manifests deploy the Model Registry instance in the `kubeflow` namespace, to install a compatible version of Model Registry for Kubeflow, you should deploy a separate instance of Model Registry in the profile's namespace. For that just run: |
There was a problem hiding this comment.
Let us NOT install default Model Registry in 'Kubeflow'. Define a profile like kubeflow-model-registry and install there where UI can be used.
There was a problem hiding this comment.
We cannot define a profile if we don't know the user, that would be an opinionated way of installation. Profiles (https://www.kubeflow.org/docs/components/central-dash/profiles/) need to have a subject that you can then expand adding the required files, but you need to know the user in advance. We cannot enable a deafult profile.
| ```bash | ||
| kubectl apply -k options/istio | ||
| ```sh | ||
| PROFILE_NAME=<your-profile> |
There was a problem hiding this comment.
I recommend something like PROFILE_NAME=kubeflow-model-registry
There was a problem hiding this comment.
As I commented above, we cannot have an opinionated profile, the default one in regular kubeflow installation is kubeflow-user-example-com but you can have any other user.
| PROFILE_NAME=<your-profile> | ||
| for DIR in options/istio overlays/db ; do (cd $DIR; kustomize edit set namespace $PROFILE_NAME; kubectl delete -k .); done | ||
|
|
||
| # Uninstall Model Registry UI | ||
| kubectl delete -k options/ui/overlays/istio -n kubeflow |
There was a problem hiding this comment.
We cannot have default profiles.
| ## Model Registry as a separate component Installation | ||
|
|
There was a problem hiding this comment.
what is this and why is this needed? if were to add instructions to add additional MR instance ran as the profile again, IMO it is not acceptable to install without UI.
There was a problem hiding this comment.
This is the instructions if you only wanna install Model Registry without UI, we can rename it or completly remove it, it's basically what @pboyd did in https://github.com/kubeflow/website/pull/4042/files we can call it "standalone" here too, but it's basically that. If we should not install it wihtout UI I'm more than fine deleting this section.
There was a problem hiding this comment.
My understanding is that given that there's a full flegde API CLI users might wanna install MR without the UI in some cases.
| For a basic usage of the Kubeflow Model Registry, follow the [Kubeflow Model Registry getting started documentation](https://www.kubeflow.org/docs/components/model-registry/getting-started/) | ||
|
|
||
| ## Uninstall | ||
| ### Uninstall |
There was a problem hiding this comment.
shouldn't all the uninstalls be one place? can we please collate them in single section?
There was a problem hiding this comment.
These uninstalls are for the two sections, if we wanna remove the latter one this won't be needed, they are different because there's different steps.
I'm following most of what we've done here https://github.com/kubeflow/website/pull/4042/files there's the installation on profiles (concept for kubeflow) and installation in the default namespace. |
|
Lucas, I am sorry for the misunderstanding in my last comment. The process looks good to me and is aligned with the instructions that we have on the website from @pboyd PR's ! I agree with @rareddy that the solution presented both here and also on the website is not ideal from a user perspective, but it's the current the best that we can do with the current Kubeflow Central Dashboard profiles design. But indeed, we should talk with the central dashboard guys to provide more streamlined installation process for model registry. |
|
/lgtm |
|
looping here to make sure I'm on sync for this issue accordingly: #863 |
based on the reviews I've read in this PR and main ones linked above, my understanding is that for the current state-of-art is best to proceed in merging this PR as-is, and iterate on this with the future work currently tracked with: /approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ederign, tarilabs The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…l docker digest to c570170 (kubeflow#854) Signed-off-by: konflux-internal-p02 <170854209+konflux-internal-p02[bot]@users.noreply.github.com> Co-authored-by: konflux-internal-p02[bot] <170854209+konflux-internal-p02[bot]@users.noreply.github.com>
Description
Revamp docs for Kubeflow UI installation and installing MR in Profiles.
How Has This Been Tested?
Merge criteria:
DCOcheck)ok-to-testhas been added to the PR.If you have UI changes