### API Change

labels.file_auth_scheme_ftp=FTP
labels.pagination_page_guide_msg={0}/{1} ({2} items)
labels.list_could_not_find_crud_table=No data.
labels.scheduledjob_configuration=Job Scheduler
labels.scheduledjob_title_details=Jobs
labels.scheduledjob_name=Name
labels.scheduledjob_target=Target
labels.scheduledjob_status=Status
labels.scheduledjob_cronExpression=Schedule
labels.scheduledjob_scriptType=Executor

labels.file_auth_scheme_ftp	=	FTP
labels.pagination_page_guide_msg	=	{0}/{1} ({2} items)
labels.list_could_not_find_crud_table	=	Pas de données.
labels.scheduledjob_configuration	=	Job Scheduler
labels.scheduledjob_title_details	=	Jobs
labels.scheduledjob_name	=	Nom
labels.scheduledjob_target	=	Cible
labels.scheduledjob_status	=	État
labels.scheduledjob_cronExpression	=	Tableau
labels.scheduledjob_scriptType	=	Executor

* **[alpha]** All in one volume proposal - a new volume driver capable of projecting secrets, configmaps, and downward API items into the same directory.

## Deprecations
* Remove extensions/v1beta1 Jobs resource, and job/v1beta1 generator. ([#38614](https://github.com/kubernetes/kubernetes/pull/38614), [@soltysh](https://github.com/soltysh))

	"github.com/minio/sio"
)

// Multipart objectAPIHandlers

// NewMultipartUploadHandler - New multipart upload.
// Notice: The S3 client can send secret keys in headers for encryption related jobs,
// the handler should ensure to remove these keys before sending them to the object layer.
// Currently these keys are:
//   - X-Amz-Server-Side-Encryption-Customer-Key
//   - X-Amz-Copy-Source-Server-Side-Encryption-Customer-Key

to ci-cross/latest.txt. Users should know exactly where the builds are stored on Google Cloud storage buckets from now on. For example for 1.9 and 1.10, users can specify ci/latest-1.9 and ci/latest-1.10 as the CI build jobs what build images correctly updates those. The CI jobs for master update the ci-cross/latest location, so if you are looking for latest master builds, then the correct parameter to use would be ci-cross/latest. ([#63504](https://github.com/kubernetes/kubernetes/pull/63504), ...

labels.file_auth_scheme_ftp=FTP
labels.pagination_page_guide_msg={0}/{1} ({2} items)
labels.list_could_not_find_crud_table=No data.
labels.scheduledjob_configuration=Job Scheduler
labels.scheduledjob_title_details=Jobs
labels.scheduledjob_name=Name
labels.scheduledjob_target=Target
labels.scheduledjob_status=Status
labels.scheduledjob_cronExpression=Schedule
labels.scheduledjob_scriptType=Executor

- Enable the "Retriable and non-retriable pod failures for jobs" feature into beta ([#113360](https://github.com/kubernetes/kubernetes/pull/113360), [@mimowo](https://github.com/mimowo)) [SIG Apps, Auth, Node, Scheduling and Testing]
- Graduate JobTrackingWithFinalizers to stable.
  Jobs created before the feature was enabled are still tracked without finalizers.

### Cluster Federation

#### [alpha] Federated Jobs

Federated Jobs that are automatically deployed to multiple clusters
are now supported. Cluster selection and weighting determine how Job
parallelism and completions are spread across clusters. Federated Job
status reflects the aggregate status across all underlying cluster
jobs.

#### [alpha] Federated Horizontal Pod Autoscaling (HPA)

- **Apps**
  - [alpha] Introducing 'ScheduledJobs', which allow running time based Jobs, namely once at a specified time or repeatedly at specified point in time. ([docs](http://kubernetes.io/docs/user-guide/scheduled-jobs/)) ([kubernetes/features#19](https://github.com/kubernetes/enhancements/issues/19))
- **Auth**