You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 29, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: telemetry-aware-scheduling/docs/health-metric-example.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,7 +83,7 @@ This policy has three strategies included:
83
83
After the above policy is declared the Telemetry Policy Controller will begin updating metrics associated with it and tracking nodes that are violating the deschedule targets. At this point the controller logs should be printing out these metrics.
84
84
85
85
### scheduleonmetric
86
-
The Scheduler Extender will evaluate metrics for pods ahead of their placement. To see it at work run ``kubectl apply -f nginx-config-map.yaml; kubectl apply -f demo-pod.yaml`` in the health-metric-demo directory.
86
+
The Scheduler Extender will evaluate metrics for pods ahead of their placement. To see it at work run ``kubectl apply -f demo-pod.yaml`` in the health-metric-demo directory.
0 commit comments