-
Notifications
You must be signed in to change notification settings - Fork 40
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
[clearml-serving] Specification of model platform not possible #74
Comments
Hi @ockaro, Can you please verify there is a clearml triton pod running? Side note - can you please move the issue to clearml-serving repo? This seems not to be related to the helm chart, but to the serving itself. |
Hi @jkhenning , The triton pod is up and running. The mentioned error message occurs within the triton pod. I tried these two commands in order to register the model
where the config.pbtxt looks like this
|
Hi @jkhenning, are there any news on this issue? :) |
Describe the bug a clear and concise description of what the bug is.
Hi there, it seems that when adding a pytorch model to the self-hosted clearml-serving the platform also needs to be added. But neither specifying the platform with the aux-config flag, nor passing a config.pbtxt file with the aux-config flag works. In both cases I get an error
E0405 14:55:27.962135 35 model_repository_manager.cc:996] Poll failed for model directory 'advanced_basic_classifier.pytorch': unexpected 'platform' and 'backend' pair, got:, pytorch
What's your helm version?
3.14.3
What's your kubectl version?
1.25.2
What's the chart version?
7.8.1
Enter the changed values of values.yaml?
-- ClearMl generic configurations
clearml:
apiAccessKey: ***
apiSecretKey: ***
apiHost: https://api.***.com
filesHost: https://files.***.com
webHost: https://app.***.com
servingTaskId: "fec7d23cc2b848b48d15041ce965ed81"
-- ClearML serving inference configurations
clearml_serving_inference:
# -- Ingress exposing configurations
ingress:
enabled: true
hostName: "serving.***.com"
ingressClassName: "nginx"
tlsSecretName: "ingress-tls-clearml-serving"
annotations:
cert-manager.io/cluster-issuer: letsencrypt-production
The text was updated successfully, but these errors were encountered: