-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add support for build manifests from different location in Dockerfile #43
Conversation
/hold Should not cherry-pick if its merge in upstream. |
this changes include 2 parts:
we can have 1st part in the upstream and sync down to RHODS, |
918c315
to
76553ff
Compare
- fetch manifests from component repo - componnets cannot fetch from component repo, then from odh-manifests - use red-hat-data-services for git org in script - since odh-modelmesh-controller is moved out from model-mesh need copy - kserve does not have 'base' folder in component repo, change path ref: https://github.com/opendatahub-io/odh-manifests/blob/master/kserve/hack/kustomization.yaml Signed-off-by: Wen Zhou <wenzhou@redhat.com>
we will still need the change in not only sync from ODH @VaishnaviHire after that, changes should be fine to sync. but have this PR hold, still upstream is merged and incubation for a bit time |
close this one, will use "monitroing-intergration" to get all out |
component manifests from component repo
componnet does not sync from component repo will still be from odh-manifests
refer midstream https://gitlab.cee.redhat.com/data-hub/rhods-cpaas-midstream/-/merge_requests/1067
ref: opendatahub-io#357
rebase after API change, test:
Test:
local image: quay.io/wenzhou/opendatahub-operator-catalog:v2.8.424-2
when enable all component
has no problem to start pods.