-
Notifications
You must be signed in to change notification settings - Fork 137
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 kfdefs including all odh components on operate-first/odh #9
Comments
I think before going ahead with this and restructuring, we should confirm what the recommendation is from the odh team with regards to using 1 namespace or many, I've reached out to them on the channel and waiting for a response. |
As per #13 we'll be sticking to organizing by logical grouping of components per namespace, so for this issue we'd need kfdefs per such groupings |
#13 was re-opened due to increasing issues with multi-namespace deployments in the current state of odh. This issue is blocked until we come to a decisive conclusion on multi vs single ns. |
Let's have this be part of #10 as well |
All components should go in a single namespace, based on the examples for the kfdef files provided from upstream. This will require restructuring of the operate-first/odh repo.
The text was updated successfully, but these errors were encountered: