Open chandrams opened 3 years ago
@chandrams Are you referring to the ID in here?
{
"experiment_name": "galaxies-autotune-min-http-response-time",
"objective_function": "request_sum/request_count",
"hpo_algo_impl": "optuna_tpe",
"deployment_name": "galaxies-sample",
"namespace": "default",
"id": "71d2096178fdb543a210eeac088c828ea2ca6e0a2ee3bbc0e1f4c0d263216f32",
"slo_class": "response_time",
"pod_name": "galaxies-sample-5f94d57558-f7jc4",
"direction": "minimize"
},
If so, I agree, a way to get the ID using kubectl get autotunes
would be great.
I can pick this up if everyone is OK with having the information in kubectl get autotunes
@dinogun @bharathappali
@chandrams Are you referring to the ID in here?
{ "experiment_name": "galaxies-autotune-min-http-response-time", "objective_function": "request_sum/request_count", "hpo_algo_impl": "optuna_tpe", "deployment_name": "galaxies-sample", "namespace": "default", "id": "71d2096178fdb543a210eeac088c828ea2ca6e0a2ee3bbc0e1f4c0d263216f32", "slo_class": "response_time", "pod_name": "galaxies-sample-5f94d57558-f7jc4", "direction": "minimize" },
If so, I agree, a way to get the ID using
kubectl get autotunes
would be great.
Yes, it is the same id
I can pick this up if everyone is OK with having the information in
kubectl get autotunes
@dinogun @bharathappali
I'm fine with it and happier if you wanna take it up :)
Sub issues: https://github.com/kruize/autotune/issues/326 - Currently looking at a separate trial crd. Will update the issue when I have more information
At present, the autotune object id can be obtained using the Dependency Analyzer APIs after applying the autotune.yaml. Instead there should be an easier way to get this info, might be displaying it as part of kubectl get autotune