[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

helm-charts/common/embedding-usvc/README.md

@@ -43,16 +43,17 @@ https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-promet
 ### Gotchas
 
 Why HPA is opt-in:
-* Enabling chart `horizontalPodAutoscaler` option will _overwrite_ cluster's current
+
+- Enabling chart `horizontalPodAutoscaler` option will _overwrite_ cluster's current
   `PrometheusAdapter` configuration with its own custom metrics configuration.
   Take copy of the existing one before install, if that matters:
   `kubectl -n monitoring get cm/adapter-config -o yaml > adapter-config.yaml`
-* `PrometheusAdapter` needs to be restarted after install, for it to read the new configuration:
+- `PrometheusAdapter` needs to be restarted after install, for it to read the new configuration:
   `ns=monitoring; kubectl -n $ns delete $(kubectl -n $ns get pod --selector app.kubernetes.io/name=prometheus-adapter -o name)`
-* By default Prometheus adds [k8s RBAC rules](https://github.com/prometheus-operator/kube-prometheus/blob/main/manifests/prometheus-roleBindingSpecificNamespaces.yaml)
-  for accessing metrics from `default`, `kube-system` and `monitoring` namespaces.  If Helm is
+- By default Prometheus adds [k8s RBAC rules](https://github.com/prometheus-operator/kube-prometheus/blob/main/manifests/prometheus-roleBindingSpecificNamespaces.yaml)
+  for accessing metrics from `default`, `kube-system` and `monitoring` namespaces. If Helm is
   asked to install OPEA services to some other namespace, those rules need to be updated accordingly
-* Provided HPA rules are examples for Xeon, for efficient scaling they need to be fine-tune for given setup
+- Provided HPA rules are examples for Xeon, for efficient scaling they need to be fine-tune for given setup
   (underlying HW, used models, OPEA version etc)
 
 ## Verify

helm-charts/common/embedding-usvc/templates/servicemonitor.yaml

@@ -14,4 +14,4 @@ spec:
   - interval: 4s
     port: service
     scheme: http
-{{- end }}
+{{- end }}

helm-charts/common/teirerank/README.md

@@ -37,16 +37,17 @@ https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-promet
 ### Gotchas
 
 Why HPA is opt-in:
-* Enabling chart `horizontalPodAutoscaler` option will _overwrite_ cluster's current
+
+- Enabling chart `horizontalPodAutoscaler` option will _overwrite_ cluster's current
   `PrometheusAdapter` configuration with its own custom metrics configuration.
   Take copy of the existing one before install, if that matters:
   `kubectl -n monitoring get cm/adapter-config -o yaml > adapter-config.yaml`
-* `PrometheusAdapter` needs to be restarted after install, for it to read the new configuration:
+- `PrometheusAdapter` needs to be restarted after install, for it to read the new configuration:
   `ns=monitoring; kubectl -n $ns delete $(kubectl -n $ns get pod --selector app.kubernetes.io/name=prometheus-adapter -o name)`
-* By default Prometheus adds [k8s RBAC rules](https://github.com/prometheus-operator/kube-prometheus/blob/main/manifests/prometheus-roleBindingSpecificNamespaces.yaml)
-  for accessing metrics from `default`, `kube-system` and `monitoring` namespaces.  If Helm is
+- By default Prometheus adds [k8s RBAC rules](https://github.com/prometheus-operator/kube-prometheus/blob/main/manifests/prometheus-roleBindingSpecificNamespaces.yaml)
+  for accessing metrics from `default`, `kube-system` and `monitoring` namespaces. If Helm is
   asked to install OPEA services to some other namespace, those rules need to be updated accordingly
-* Provided HPA rules are examples for Xeon, for efficient scaling they need to be fine-tune for given setup
+- Provided HPA rules are examples for Xeon, for efficient scaling they need to be fine-tune for given setup
   (underlying HW, used models, OPEA version etc)
 
 ## Verify

helm-charts/common/teirerank/templates/servicemonitor.yaml

@@ -14,4 +14,4 @@ spec:
   - interval: 4s
     port: service
     scheme: http
-{{- end }}
+{{- end }}

helm-charts/common/tgi/README.md

@@ -40,16 +40,17 @@ https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-promet
 ### Gotchas
 
 Why HPA is opt-in:
-* Enabling chart `horizontalPodAutoscaler` option will _overwrite_ cluster's current
+
+- Enabling chart `horizontalPodAutoscaler` option will _overwrite_ cluster's current
   `PrometheusAdapter` configuration with its own custom metrics configuration.
   Take copy of the existing one before install, if that matters:
   `kubectl -n monitoring get cm/adapter-config -o yaml > adapter-config.yaml`
-* `PrometheusAdapter` needs to be restarted after install, for it to read the new configuration:
+- `PrometheusAdapter` needs to be restarted after install, for it to read the new configuration:
   `ns=monitoring; kubectl -n $ns delete $(kubectl -n $ns get pod --selector app.kubernetes.io/name=prometheus-adapter -o name)`
-* By default Prometheus adds [k8s RBAC rules](https://github.com/prometheus-operator/kube-prometheus/blob/main/manifests/prometheus-roleBindingSpecificNamespaces.yaml)
-  for accessing metrics from `default`, `kube-system` and `monitoring` namespaces.  If Helm is
+- By default Prometheus adds [k8s RBAC rules](https://github.com/prometheus-operator/kube-prometheus/blob/main/manifests/prometheus-roleBindingSpecificNamespaces.yaml)
+  for accessing metrics from `default`, `kube-system` and `monitoring` namespaces. If Helm is
   asked to install OPEA services to some other namespace, those rules need to be updated accordingly
-* Provided HPA rules are examples for Xeon, for efficient scaling they need to be fine-tune for given setup
+- Provided HPA rules are examples for Xeon, for efficient scaling they need to be fine-tune for given setup
   (underlying HW, used models, OPEA version etc)
 
 ## Verify

helm-charts/common/tgi/servicemonitor.yaml

@@ -19,4 +19,4 @@ spec:
   - interval: 4s
     port: service
     scheme: http
-{{- end }}
+{{- end }}