- A TTL mechanism has been added to clean up Jobs after they finish. ([#66840](https://github.com/kubernetes/kubernetes/pull/66840), [@janetkuo](https://github.com/janetkuo)) Courtesy of SIG API Machinery, SIG Apps, SIG Architecture, and SIG Testing

          "cool\uFF61fr", // Alternate dot character
          "foo.bar.google.com",
          "google.Co.uK",
          "google.com",
          "home.netscape.com",
          "it-trace.ch",
          "jobs.kt.com.",
          "jprs.co.jp",
          "kt.co",
          "ledger-enquirer.com",
          "members.blah.nl.",
          "pvt.k12.ca.us",
          "site.ac.jp",
          "site.ad.jp",

Additional Annotations for the Kubernetes Job customCommandJob customCommandJob: securityContext: enabled: false runAsUser: 1000 runAsGroup: 1000 resources: requests: memory: 128Mi # Command to run after the main command on exit exitCommand: "" ## Merge jobs postJob: podAnnotations: {} annotations: {} securityContext: enabled: false runAsUser: 1000 runAsGroup: 1000 fsGroup: 1000 nodeSelector: {} tolerations: [] affinity: {} ## Use this field to add environment variables relevant to MinIO server. These...

Additional Annotations for the Kubernetes Job customCommandJob customCommandJob: securityContext: enabled: false runAsUser: 1000 runAsGroup: 1000 resources: requests: memory: 128Mi # Command to run after the main command on exit exitCommand: "" ## Merge jobs postJob: podAnnotations: {} annotations: {} securityContext: enabled: false runAsUser: 1000 runAsGroup: 1000 fsGroup: 1000 nodeSelector: {} tolerations: [] affinity: {} ## Use this field to add environment variables relevant to MinIO server. These...

Additional Annotations for the Kubernetes Job customCommandJob customCommandJob: securityContext: enabled: false runAsUser: 1000 runAsGroup: 1000 resources: requests: memory: 128Mi # Command to run after the main command on exit exitCommand: "" ## Merge jobs postJob: podAnnotations: {} annotations: {} securityContext: enabled: false runAsUser: 1000 runAsGroup: 1000 fsGroup: 1000 nodeSelector: {} tolerations: [] affinity: {} ## Use this field to add environment variables relevant to MinIO server. These...

Additional Annotations for the Kubernetes Job customCommandJob customCommandJob: securityContext: enabled: false runAsUser: 1000 runAsGroup: 1000 resources: requests: memory: 128Mi # Command to run after the main command on exit exitCommand: "" ## Merge jobs postJob: podAnnotations: {} annotations: {} securityContext: enabled: false runAsUser: 1000 runAsGroup: 1000 fsGroup: 1000 nodeSelector: {} tolerations: [] affinity: {} ## Use this field to add environment variables relevant to MinIO server. These...

		// call will report top level prefixes in deleted state, whereas spark/hadoop interpret this as non-empty
		// and throw a 404 exception. This is especially a problem for spark jobs overwriting the same partition
		// repeatedly. This workaround recursively lists the top 3 entries including delete markers to reflect the
		// correct state of the directory in the list results.

my-extra-policies-cm ## Additional volumeMounts to add to the custom commands container when ## running the post-job. extraVolumeMounts: [] # - name: extra-policies # mountPath: /mnt/extras/ # Command to run after the main command on exit exitCommand: "" ## Merge jobs postJob: podAnnotations: {} annotations: {} securityContext: enabled: false runAsUser: 1000 runAsGroup: 1000 fsGroup: 1000 nodeSelector: {} tolerations: [] affinity: {} ## Use this field to add environment variables relevant to MinIO server. These...

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), ...

  Jobs that are tracked using this mechanism get the annotation `batch.kubernetes.io/job-tracking`. This is a temporary measure. Two releases after this feature graduates to beta, the annotation won't be added to Jobs anymore. ([#98817](https://github.com/kubernetes/kubernetes/pull/98817), [@alculquicondor](https://github.com/alculquicondor))