Extend the configuration for limitting the number of workloads with p…

…osition

keps/168-pending-workloads-visibility/README.md

@@ -78,7 +78,8 @@ know that this has succeeded?
 
 ### Non-Goals
 
-- expose the information about workload position for each workload individually
+- expose the information about workload position for each pending workload in
+  in case of very long queues
 
 <!--
 What is out of scope for this KEP? Listing non-goals helps to focus discussion
@@ -282,10 +283,20 @@ type Configuration struct {
 }
 
 type PendingWorkloadsVisibility struct {
-	// MaxPendingWorkloadsInStatus indicates the maximal number of pending
+	// LocalQueuePendingWorkloads indicates the maximal number of pending
 	// workloads for which their local queue order is exposed.
 	// Defaults to 100.
-	MaxTopPendingWorkloads *int32
+	LocalQueuePendingWorkloads *int32
+
+	// LocalQueuePendingWorkloadsWithPosition indicates the maximal number of
+	// pending workloads for which their position in the cluster queue is exposed.
+	// Defaults to 10.
+	LocalQueuePendingWorkloadsWithPosition *int32
+
+	// ClusterQueuePendingWorkloads indicates the maximal number of pending
+	// workloads for which their cluster queue order is exposed.
+	// Defaults to 100.
+	ClusterQueuePendingWorkloads *int32
 }
 ```