more pre-commit file fixes

Signed-off-by: Michael Clifford <mcliffor@redhat.com>

Author: MichaelClifford

demos/rag_agentic/src/4_OCP_version_info_email.py

@@ -75,7 +75,7 @@
         """Summarize the latest Red Hat OpenShift version number and any significant features, fixes, or changes that occure in this version.""",
         """Draft and format an email to convey this information to my team members."""
     ]
-    for i, prompt in enumerate(prompts):    
+    for i, prompt in enumerate(prompts):
         turn_response = agent.create_turn(
             messages=[
                 {
@@ -103,4 +103,3 @@
     )
     for log in EventLogger().log(turn_response):
         log.print()
-

kubernetes/llama-stack/otel-collector-sidecar.yaml

@@ -55,4 +55,3 @@ spec:
     resources: {}
   replicas: 1
   ipFamilyPolicy: SingleStack
-

kubernetes/mcp-servers/ansible-mcp/ansible-service.yaml

@@ -10,4 +10,3 @@ spec:
   - port: 8000
     targetPort: http
     protocol: TCP
-

kubernetes/observability/README.md

@@ -18,8 +18,8 @@ Metrics and traces will be distributed from the OTC to various backends. Tempo i
 2. **Tempo Operator**: Provides `TempoStack` Custom Resource. This is the backend for distributed tracing.
 An S3-compatible storage (Minio) is paired with Tempo.
 
-3. **Cluster Observability Operator**: This provides PodMonitor and ServiceMonitor Custom Resources which are necessary for 
-user-workload monitoring's prometheus to scrape workload metrics. Also, the COO provides UIPlugins for viewing telemetry. 
+3. **Cluster Observability Operator**: This provides PodMonitor and ServiceMonitor Custom Resources which are necessary for
+user-workload monitoring's prometheus to scrape workload metrics. Also, the COO provides UIPlugins for viewing telemetry.
 
 3. **(optional) Grafana Operator**: Provides Grafana APIs including `GrafanaDashboard`, `Grafana`, and `GrafanaDataSource` that will be used to visualize telemetry.
 
@@ -48,7 +48,7 @@ In order to view distributed tracing data from LLamastack and/or vLLM, you must
 is Tempo. See the OpenShift Tempo
 [documentation](https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/distributed_tracing/distributed-tracing-platform-tempo#distr-tracing-tempo-install-tempostack-web-console_dist-tracing-tempo-installing)
 for further details. Tempo must be paired with a storage solution. For this example, `MinIO` is used. The necessary resources can be created by
-applying the `./tempo` manifests. 
+applying the `./tempo` manifests.
 
 ```bash
 # edit storageclassName & secret as necessary
@@ -113,15 +113,15 @@ oc patch deployment deployment-name \
 
 The Jaeger frontend feature of TempoStack is no longer supported by Red Hat. This has been replaced by the COO UIPlugin. To create the UIPlugin for
 Tracing, first ensure the TempoStack described above is created. This is a prerequisite. Then, all that's necessary to view traces from
-the OpenShift console at `Observe -> Traces` is to create the following [Tracing UIPlugin resource](./tracing-ui-plugin.yaml). 
+the OpenShift console at `Observe -> Traces` is to create the following [Tracing UIPlugin resource](./tracing-ui-plugin.yaml).
 
 ```bash
 oc apply ./tracing-ui-plugin.yaml
 ```
 
-You should now see traces and metrics in the OpenShift console, from the `Oberve` tab. 
+You should now see traces and metrics in the OpenShift console, from the `Oberve` tab.
 
-### Grafana 
+### Grafana
 
 Most users are familiar with Grafana for visualizing and analyzing telemetry. To create the Grafana resources necessary to view
 Llamastack and vLLM telemetry, follow the below example.
@@ -143,7 +143,7 @@ Upon success, you can explore metrics and traces from Grafana route.
 To create a `vLLM` GrafanaDashboard, run
 
 ```bash
-oc apply -n observability-hub -f vllml-dashboard/vllm-dashboard.yaml 
+oc apply -n observability-hub -f vllml-dashboard/vllm-dashboard.yaml
 ```
 
 You should now see a dashboard named `vLLM` in the Grafana console by choosing `Dashboards` from the left navigation bar.
@@ -157,8 +157,7 @@ This [dashboard](./grafana/cluster-metrics-dashboard/cluster_metrics.ocp.json) i
 https://github.com/kevchu3/openshift4-grafana/blob/master/dashboards/json_raw/cluster_metrics.ocp416.json
 
 ```bash
-oc apply -n observability-hub -f cluster-metrics-dashboard/cluster-metrics.yaml 
+oc apply -n observability-hub -f cluster-metrics-dashboard/cluster-metrics.yaml
 ```
 
 You should now see a dashboard named `cluster-metrics` in the Grafana console by choosing `Dashboards` from the left navigation bar.
-

kubernetes/observability/grafana/cluster-metrics-dashboard/cluster-metrics.yaml

@@ -10,4 +10,3 @@ spec:
       dashboards: grafana   # This label matches the grafana Grafana instance
   # This json was copied and modified from https://github.com/kevchu3/openshift4-grafana/blob/master/dashboards/json_raw/cluster_metrics.ocp416.json
   url: https://raw.githubusercontent.com/redhat-et/edge-ocp-observability/refs/heads/main/observability-hub/grafana/cluster-metrics-dashboard/cluster_metrics_ocp.json
-

kubernetes/observability/grafana/instance-with-prom-tempo-ds/kustomization.yaml

@@ -1,6 +1,6 @@
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
-  
+
 namespace: observability-hub
 resources:
 - grafana-instance.yaml
@@ -9,4 +9,3 @@ resources:
 - grafana-sa.yaml
 - route.yaml
 - datasources.yaml
-

kubernetes/observability/grafana/vllm-dashboard/vllm-grafana-openshift.json

@@ -1566,4 +1566,4 @@
   "title": "vLLM",
   "uid": "b281712d-8bff-41ef-9f3f-71ad43c05e9b7",
   "version": 4
-}
+}

kubernetes/observability/otel-collector/clusterrole.yaml

@@ -26,4 +26,3 @@ subjects:
     name: otel-collector
     # update if not using observability-hub namespace
     namespace: observability-hub
-

kubernetes/observability/otel-collector/kustomization.yaml

@@ -1,6 +1,6 @@
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
-  
+
 namespace: observability-hub
 resources:
 - sa.yaml

kubernetes/observability/otel-collector/sa.yaml

@@ -2,4 +2,3 @@ apiVersion: v1
 kind: ServiceAccount
 metadata:
   name: otel-collector
-