Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get the PoC of Tekton pipeline for building a container of an AzureML model working on the PoC test cluster. #16

Closed
Tracked by #2
devguyio opened this issue Aug 11, 2023 · 1 comment
Assignees
Labels
kind/documentation Improvements or additions to documentation kind/enhancement New feature or request priority/high Important issue that needs to be resolved asap. Releases should not have too many o

Comments

@devguyio
Copy link
Contributor

devguyio commented Aug 11, 2023

User Story

@stefan-bergstein PoC code.

A/C

  • Any software needed to be installed on the test cluster is identified as a prerequisites
  • A small README of how to get successfully get that PoC running on the cluster
@devguyio devguyio added kind/enhancement New feature or request priority/high Important issue that needs to be resolved asap. Releases should not have too many o labels Aug 11, 2023
@devguyio devguyio moved this from Backlog to In Progress in AI Edge Tracking Aug 11, 2023
@devguyio devguyio added the kind/documentation Improvements or additions to documentation label Aug 11, 2023
@piotrpdev
Copy link
Member

Got Stefan's code working by following his README. You will need the OpenShift Pipelines Operator (which RHODS provides), a Quay repo, and an AzureML workspace with a MLFlow model (model is in Stefan's repo).


Note
As of writing this I haven't tested the final step in the README that describes how to deploy the model to the target system, since it isn't part of this issue.

If you plan to reproduce this, I would advise is the following:

Tips

Note

Building the mlflow container does take a while.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Improvements or additions to documentation kind/enhancement New feature or request priority/high Important issue that needs to be resolved asap. Releases should not have too many o
Projects
Archived in project
Development

No branches or pull requests

2 participants