-
Notifications
You must be signed in to change notification settings - Fork 121
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
Manager config mounted wrongly #205
Comments
Interesting. I plan to take a look at this in the next couple of days. |
@adrwong-lora while not very tidy, I don't think this is actually a bug since I'm pretty sure the controller process is looking for the file where it's currently mounted. There would be no harm in simplifying though to remove the intermediate Did you actually run into any problems functionally or this was just something you noticed that looked odd? |
It works fine, just a bit confused when I tried to look for the config-defaults.yaml it's actually reading in the pods. |
Fixes kserve#205 Signed-off-by: Christian Kadner <[email protected]>
#### Motivation The file containing the default configuration for the ModelMesh Controller is called `config-defaults.yaml`, which resides in a directory also called `config-defaults.yaml` as pointed out by @adrwong-lora in issue #205 ``` /etc/model-serving/config-defaults.yaml/config-defaults.yaml ``` #### Modifications Change `mountPath` from `/etc/model-serving/config-defaults.yaml` to `/etc/model-serving/config/default` #### Result The file containing the default configuration file after this fix: ``` /etc/model-serving/config/default/config-defaults.yaml ``` Which more closely reflects the path of the [`config-defaults.yaml`](https://github.com/kserve/modelmesh-serving/blob/main/config/default/config-defaults.yaml) file in the `modelmesh-serving` repository: ``` config/default/config-defaults.yaml ``` Resolves #205 /cc @njhill /fyi @adrwong-lora Signed-off-by: Christian Kadner <[email protected]>
formatting README.md
To Reproduce
kubectl exec
to get in the manager podExpected behavior
the config-defaults.yaml should not be a directory itself
The text was updated successfully, but these errors were encountered: