.Values.podDisruptionBudget.maxUnavailable }} selector: matchLabels: app: {{ template "minio.name" . }} {{- end }} minio/templates/post-job.yaml {{- if or .Values.buckets .Values.users .Values.policies .Values.customCommands .Values.svcaccts }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-post-job labels: app: {{ template "minio.name" . }}-post-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook":...

.Values.podDisruptionBudget.maxUnavailable }} selector: matchLabels: app: {{ template "minio.name" . }} {{- end }} minio/templates/post-job.yaml {{- if or .Values.buckets .Values.users .Values.policies .Values.customCommands .Values.svcaccts }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-post-job labels: app: {{ template "minio.name" . }}-post-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook":...

maxUnavailable: {{ .Values.podDisruptionBudget.maxUnavailable }} selector: matchLabels: app: {{ template "minio.name" . }} {{- end }} minio/templates/post-job.yaml apiVersion: batch/v1 kind: Job metadata: name: { { template "minio.fullname" . } }-post-job namespace: { { .Release.Namespace | quote } } labels: app: { { template "minio.name" . } }-post-job chart: { { template "minio.chart" . } } release: { { .Release.Name } } heritage: { { .Release.Service } } annotations: "helm.sh/hook": post-install,post-upgrade...

- **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**

## Deprecations

* extensions/v1beta1.Jobs is deprecated, use batch/v1.Job instead ([#36355](https://github.com/kubernetes/kubernetes/pull/36355), [@soltysh](https://github.com/soltysh))

// ----------
// This implementation of the PUT operation adds an object to a bucket
// while reading the object from another source.
// 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

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

- ACTION_REQUIRED

- Failed pods associated with a job with `parallelism = 1` are recreated by the job controller honoring exponential backoff delay again. However, for jobs with `parallelism > 1`, pods might be created without exponential backoff delay. ([#115021](https://github.com/kubernetes/kubernetes/pull/115021), [@nikhita](https://github.com/nikhita)) [SIG...

available }} selector: matchLabels: app: {{ template "minio.name" . }} {{- end }} minio/templates/post-job.yaml {{- if or .Values.buckets .Values.users .Values.policies .Values.customCommands .Values.svcaccts }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-post-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-post-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations:...