labels.web_crawling_button_create=Erstellen
labels.web_crawling_button_create_job=Neue Aufgabe erstellen
labels.crawler_configuration=Allgemeine Konfiguration
labels.crawler_title_edit=Allgemeine Konfiguration
labels.schedule=Zeitplan
labels.enabled=Aktiviert
labels.day_for_cleanup=Dokumente entfernen nach
labels.day=Tag(en)
labels.crawl_button_update=Aktualisieren
labels.none=Keine

- **Cluster Lifecycle**
  - [alpha] Ensure critical cluster infrastructure pods (Heapster, DNS, etc.) can schedule by evicting regular pods when necessary to make the critical pods schedule. ([docs](http://kubernetes.io/docs/admin/rescheduler/#guaranteed-scheduling-of-critical-add-on-pods)) ([kubernetes/features#62](https://github.com/kubernetes/enhancements/issues/62))

			Status:    http.StatusText(http.StatusOK),
		})
	}

	// Remove the transitioned object whose object version is being overwritten.
	if !globalTierConfigMgr.Empty() {
		// Schedule object for immediate transition if eligible.
		enqueueTransitionImmediate(objInfo, lcEventSrc_s3CompleteMultipartUpload)
		os.Sweep()
	}
}

// AbortMultipartUploadHandler - Abort multipart upload

HSPLokhttp3/internal/concurrent/TaskQueue;->schedule$default(Lokhttp3/internal/concurrent/TaskQueue;Lokhttp3/internal/concurrent/Task;JI)V
HSPLokhttp3/internal/concurrent/TaskQueue;->schedule(Lokhttp3/internal/concurrent/Task;J)V
HSPLokhttp3/internal/concurrent/TaskQueue;->scheduleAndDecide$okhttp(Lokhttp3/internal/concurrent/Task;JZ)Z

    Future<?> scheduled = executorService.schedule(task, delay, timeUnit);
    /*
     * Even when the user interrupts the task, we pass `false` to `cancel` so that we don't
     * interrupt a second time after the interruption performed by TrustedListenableFutureTask.
     */
    task.addListener(() -> scheduled.cancel(false), directExecutor());
    return task;
  }

  /**

labels.user_agent = 사용자 에이전트
labels.web_crawling_button_create = 작성
labels.web_crawling_button_create_job = 새 작업 만들기
labels.crawler_configuration = 일반 설정
labels.crawler_title_edit = 일반 설정
labels.schedule = 스케줄
labels.enabled = 사용
labels.day_for_cleanup = 이전 문서를 삭제
labels.day = 일
labels.crawl_button_update = 업데이트
labels.none = 없음
labels.crawling_thread_count = 동시 크롤러 설정
labels.incremental_crawling = 마지막 수정일 확인

/docker/k8s-artifacts-prod/southamerica-east1/images/kube-scheduler) | [amd64](https://console.cloud.google.com/artifacts/docker/k8s-artifacts-prod/southamerica-east1/images/kube-scheduler-amd64), [arm64](https://console.cloud.google.com/artifacts/docker/k8s-artifacts-prod/southamerica-east1/images/kube-scheduler-arm64), [ppc64le](https://console.cloud.google.com/artifacts/docker/k8s-artifacts-prod/southamerica-east1/images/kube-scheduler-ppc64le), [s390x](https://console.cloud.google.com/artifa...

ing/config) feature allows you to tune the algorithms and other settings of the kube-scheduler. You can easily enable or disable specific functionality (contained in plugins) in selected scheduling phases without having to rewrite the rest of the configuration. Furthermore, a single kube-scheduler instance can serve different configurations, called profiles. Pods can select the profile they want to be scheduled under via the `.spec.schedulerName` field.

### CSI Migration - AzureDisk...

### SIG Scheduling

* Schedule DaemonSet Pods in scheduler, rather than the Daemonset controller.
([#63223](https://github.com/kubernetes/kubernetes/pull/63223), [@k82cn](https://github.com/k82cn))
* Added `MatchFields` to `NodeSelectorTerm`; in 1.11, it only supports `metadata.name`. ([#62002](https://github.com/kubernetes/kubernetes/pull/62002), [@k82cn](https://github.com/k82cn))

- Performance of the inter-pod affinity/anti-affinity feature is improved over 100X via algorithmic optimization.
- DaemonSet pods, which used to be scheduled by the DaemonSet controller, will be scheduled by the default scheduler in 1.12. This change allows DaemonSet pods to enjoy all the scheduling features of the default scheduler.