<c:if test="${fe:permission('admin-scheduler')}">
                                    <la:link styleClass="btn btn-success"
                                             href="/admin/scheduler/createnewjob/file_crawling/${f:u(id)}/${fe:base64(name)}">
                                        <em class="fa fa-plus-circle">

  //
  // +listType=atomic
  // +optional
  repeated ResourceHandle resourceHandles = 1;

  // This field will get set by the resource driver after it has allocated
  // the resource to inform the scheduler where it can schedule Pods using
  // the ResourceClaim.
  //
  // Setting this field is optional. If null, the resource is available
  // everywhere.
  // +optional
  optional k8s.io.api.core.v1.NodeSelector availableOnNodes = 2;

PersistentVolumeClaim.
  * Run multiple schedulers in parallel, e.g. one or more custom schedulers
alongside the default Kubernetes scheduler, using pod annotations to select
among the schedulers for each pod. Documentation is [here](http://kubernetes.io/docs/admin/multiple-schedulers.md), design doc is [here](docs/proposals/multiple-schedulers.md).
  * More expressive node affinity syntax, and support for “soft” node affinity.

### Scheduling

						</a>
					</li>
					</c:if>
					<c:if test="${fe:permission('admin-scheduler-view')}">
					<li class="nav-item">
						<a href="${fe:url('/admin/scheduler/')}" class="nav-link <c:if test="${param.menuType=='scheduler'}">active</c:if>">
							<em class='fa fa-genderless nav-icon'>
							<p><la:message key="labels.menu_scheduler_config" /></p>
						</a></li></c:if>
						

//
// They are consumed by the kube-scheduler when a CSI driver opts into
// capacity-aware scheduling with CSIDriverSpec.StorageCapacity. The scheduler
// compares the MaximumVolumeSize against the requested size of pending volumes
// to filter out unsuitable nodes. If MaximumVolumeSize is unset, it falls back
// to a comparison against the less precise Capacity. If that is also unset,

        checkMethodBase(requestBody).delete("/api/admin/searchlist/query");
        refresh();

        for (String sId : getSchedulerIds(NAME_PREFIX)) {
            deleteMethod("/api/admin/scheduler/setting/" + sId);
        }

        for (String fId : getFileConfigIds(NAME_PREFIX)) {
            deleteMethod("/api/admin/fileconfig/setting/" + fId);
        }

        deleteTestToken();
    }

    * to be scheduler by default scheduler, instead of Daemonset controller. When it is enabled,
    * the `NodeAffinity` term (instead of `.spec.nodeName`) is added to the DaemonSet Pods;
    * this enables the default scheduler to bind the Pod to the target host. If node affinity
    * of DaemonSet Pod already exists, it will be replaced.

Kubernetes manages stateless Spark and Hive containers elastically on the compute nodes. Spark has native scheduler integration with Kubernetes. Hive, for legacy reasons, uses YARN scheduler on top of Kubernetes.

- Scheduler framework interface moved from pkg/scheduler/framework/v1alpha to pkg/scheduler/framework ([#95069](https://github.com/kubernetes/kubernetes/pull/95069), [@farah](https://github.com/farah)) [SIG Scheduling, Storage and Testing]