-
Notifications
You must be signed in to change notification settings - Fork 211
Conversation
Hi @ReToCode. Thanks for your PR. I'm waiting for a opendatahub-io member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
d3b1a4c
to
a0d8530
Compare
@ReToCode nice! I think the next step would be to have some basic testing (smoke tests) in https://github.com/opendatahub-io/odh-manifests/tree/master/tests/basictests? I am not aware of the CI work for ODH and KServe but it would be nice to be able to test the manifests and future work against Kserve examples etc. |
@ReToCode Opendatahub operator is using kfctl and it is using the base folder as an entry point. I can help to change the structure a little bit to be worked by kfctl . @VaishnaviHire do we have the plan to support kustomize for the odh-manifests? |
kserve/odh-overlays/controller/inferenceservice-config-patch.yaml
Outdated
Show resolved
Hide resolved
a0d8530
to
9120c2d
Compare
@Jooho I updated the folder structure according to this, then we could have the following: - kustomizeConfig:
repoRef:
name: odh-manifests
path: kserve/controller
name: kserve-controller
- kustomizeConfig:
repoRef:
name: odh-manifests
path: kserve/runtimes
name: kserve-runtimes Would that work? |
FYI ticket to discuss the inclusion of KServe into ODH |
@ReToCode Technically it should be ok but I don't know why we need 2 entry points. |
kserve/controller/odh-overlays/kserve-controller-manager-patch.yaml
Outdated
Show resolved
Hide resolved
Would have been for the runtimes (the namespace stuff). But if we omit it here, we can drop them. |
9120c2d
to
3696283
Compare
- kustomizeConfig:
repoRef:
name: odh-manifests
path: kserve
name: kserve Still assuming that Serverless + Service Mesh are installed prior to installing ODH. |
Issue for the PR (just for tracking) https://github.com/opendatahub-io/odh-manifests/issues/848 |
From the base dir we include the variant:
Should not this be the other way around and run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ReToCode Can you also, please, squash the commits?
Update folder structure and KServe fork url Pre-build KServe manifests to avoid issues with kfctl Change the webhook certificates Add runtime field to example InferenceService fix minor issues fix labels no cert-manager no certmanager Use images from quay.io/opendatahub version 0.10.2 Fetch manifests from opendatahub-io/kserve Revert back to assembled manifests KServe manifests using `kustomize` directly Remove istio-cni env variable in controller Simplify folder structure Use release-0.10 branch to generate built yaml Fix configuration params
d301eb1
to
d6827d4
Compare
Done and tested, see https://github.com/ReToCode/knative-kserve/tree/main and https://redhat-internal.slack.com/archives/C05742W6F7T/p1689149577193889. |
Pretty sure this is not related to my changes. /test odh-manifests-e2e |
/retest |
/retest Tests look unstable... :-/ |
This PR does not have an integration test script for kserve. This is modelmesh one(https://github.com/opendatahub-io/odh-manifests/blob/kserve-prototype/tests/basictests/modelmesh.sh). So the e2e test failure has nothing to do with this pr. I think we can add the test part with another PR after we merge this because we need these manifests as soon as possible. |
/retest One more time. If it doesn't pass, I'll find who can help with it. |
/approve |
/assign vaishnavihire |
/retest |
@@ -0,0 +1,8 @@ | |||
kserve-controller=quay.io/opendatahub/kserve-controller:v0.10.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@israel-hdez do we need to update this to latest
or v0.11-latest
to avoid the anyuid issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Manifests are for 0.10. So, we could use v0.10-latest
, which should also be patched. Doesn't it work?
Or, do we want to move to 0.11? In upstream 0.11 is still unreleased. So, I'm not sure...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am ok any version that includes the changes regarding anyuid.
/retest |
1 similar comment
/retest |
@ReToCode: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
This appears to be an failure due to the odh operator deploying successfully during the CI test run. I am going to debug the live system to see what is causing the issue. Since this PR has no CI tests or modifies the existing functionality of any other components, this should merge regardless of the debug session |
/approve Merging this since the ocp411 passed and we have initial confirmation that the ocp412 issues are due to a bug in one of the openshift-ci build images outside of our control. @israel-hdez @Jooho @ReToCode If there are plans to integrate this a feature into ODH, you'll need to add CI tests when these manifests are updated |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: israel-hdez, LaVLaS The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description
This PR adds the initial manifests for KServe and necessary patches to make it run in ODH. It fetches the manifests from opendatahub-io/kserve and adds some final patches. So updates should be fairly simple in the future.
How Has This Been Tested?
It was tested using https://github.com/ReToCode/knative-kserve#installation-of-knative-with-service-mesh.
Use then use:
And test an
InferenceService
Merge criteria: