autotune
autotune copied to clipboard
kruize
Autonomous Performance Tuning for Kubernetes!
validation is required for blank, invalid, multiple-label-sections blank-label yaml ``` apiVersion: "recommender.com/v1" kind: "Autotune" metadata: name: "blank-label" spec: sla: objective_function: "transaction_response_time" sla_class: "response_time" direction: "minimize" function_variables: - name: "transaction_response_time" query:...
sla_class in app autotune yaml is not a mandatory field, currently DA is throwing error no-slaclass, null-slaclass, no-slaclass-value, blank-slaclass Expected behaviour: DA should create the object for the above cases
Supporting a categorial tunable type requires CRD changes to the AutotuneConfig, updating the `Tunable` class and code changes to be able to handle the same.
Applying autotune/examples/app-autotune.yaml failed with the below error with Autotune 0.0.5 release ``` kubectl apply -f app-autotune.yaml error: error validating "app-autotune.yaml": error validating data: ValidationError(Autotune.spec.datasource): missing required field "type" in com.recommender.v1.Autotune.spec.datasource;...
Autotune logs have a lot of information being logged. I see a lot of PodList details being logged with kruize/autotune_operator:0.0.5 docker image
Include matchDeployment as a match criteria option in the autotune object
Analyzer API doc needs to be updated with experiment_name and any other changes
First EM Patch #278 has been added to autotune. To make it easier for review and also for the followers of autotune I would like to make an incremental progress...
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...