Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Implement model registry inference service reconciliation #135
Implement model registry inference service reconciliation #135
Changes from 10 commits
490c0c4
4c03910
6eba8e2
d843346
3fe6458
015f6c6
609b1b5
1a765ee
e055b26
9a67c4e
c9cbe07
25db572
9c4e7b4
962bd76
4cbfd11
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
are all these resources needed?
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.
Actually I had to add all of them to make e2e tests working in the Kind cluster (i.e., they are used just for
deploy-dev
anddeploy-e2e
) - not sure if we want to move them directly in the overlay/e2e config folderThere 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.
@VedantMahabaleshwarkar may have a better answer about if these are OK here.
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.
@lampajr we have a the
overlays/dev
directory for this purpose (for local testing etc). I think adding these CRDs here is not necessary and IMO if these are needed to make local testing work they should be added to theoverlays/dev/kustomization.yaml
file and apply that overlay for local testingThere 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 would agree with you @VedantMahabaleshwarkar but I don't know how to reference to
crd/external
from theoverlays/dev
without directly changingcrd/external/kustomization.yaml
- I tried to directly add all CRDs into theoverlays/dev/kustomization
but I get:any idea?
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.
@lampajr looking at the manifests again, if the
crd/external
directory is not in the call chain for the actual deployment, then it's fine to add these here. We just want to avoid applying these CRDs on the cluster outside of development testing scenarios.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.
In practice, this is extending the
deploy-dev
installation to a more complete one.I'm not sure if that was the intended outcome of
make deploy-dev
. I think @VedantMahabaleshwarkar should comment about this.This is making the overlays quite similar from each other. We may want to rearrange the manifests to reduce duplication.
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.
Oh yeah I don't know what was the original motivation behind that, if that wasn't the original one I can revert the changes affecting
overlays/dev
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 don't think it's a good idea to duplicate the contents of these overlays as it'll increase the difficulty of maintaining changes. For the
deploy-dev
installation, theoverlays/dev/kustomization.yaml
can call theoverlays/odh/kustomization.yaml
directly to avoid duplicationThere 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.
yeah I couldn't find any reference to that
crd/external/kustomization.yaml
, at least not in this repo but I don't know if they could be referenced from other places outside this repo itself.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.
hmm, which rbac needs to be updated?
I am not about operators updating rbac. :)
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.
The reconcile loop has to update InferenceService CRs, adding some ad-hoc labels to keep the links between the CR and the record in model registry - that's why I had to add that
update
. Is there any other way I can do that?