## Changes since v1.3.0-alpha.4

### Action Required

* Add direct serializer ([#26251](https://github.com/kubernetes/kubernetes/pull/26251), [@caesarxuchao](https://github.com/caesarxuchao))

[Kubernetes](http://kubernetes.io) using the [Helm](https://helm.sh) package manager. ## Prerequisites - Helm cli with Kubernetes cluster configured. - PV provisioner support in the underlying infrastructure. (We recommend using <https://github.com/minio/direct-csi>) - Use Kubernetes version v1.19 and later for best experience. ## Configure MinIO Helm repo ```bash helm repo add minio https://charts.min.io/ ``` ### Installing the Chart Install this chart using: ```bash helm install --namespace minio --set...

[Kubernetes](http://kubernetes.io) using the [Helm](https://helm.sh) package manager. ## Prerequisites - Helm cli with Kubernetes cluster configured. - PV provisioner support in the underlying infrastructure. (We recommend using <https://github.com/minio/direct-csi>) - Use Kubernetes version v1.19 and later for best experience. ## Configure MinIO Helm repo ```bash helm repo add minio https://charts.min.io/ ``` ### Installing the Chart Install this chart using: ```bash helm install --namespace minio --set...

public final class okhttp3/MultipartBody : okhttp3/RequestBody {
	public static final field ALTERNATIVE Lokhttp3/MediaType;
	public static final field Companion Lokhttp3/MultipartBody$Companion;
	public static final field DIGEST Lokhttp3/MediaType;
	public static final field FORM Lokhttp3/MediaType;
	public static final field MIXED Lokhttp3/MediaType;
	public static final field PARALLEL Lokhttp3/MediaType;

you must keep the following in mind:

* **JSON configuration files that contain fields with incorrect case will no longer be valid. You must correct these files before upgrading.** When specifying keys in JSON resource definitions during direct API server communication, the keys are case-sensitive. A bug introduced in Kubernetes 1.8 caused the API server to accept a request with incorrect case and coerce it to correct case, but this behaviour has been fixed in 1.11 and the API server will...

"chiar", "cînd", "cine", "cineva", "cît", "cîte", "cîţi", "cîtva", "contra", "cu", "cum", "cumva", "curând", "curînd", "da", "dă", "dacă", "dar", "datorită", "de", "deci", "deja", "deoarece", "departe", "deşi", "din", "dinaintea", "dintr", "dintre", "drept", "după", "ea", "ei", "el", "ele", "eram", "este", "eşti", "eu", "face", "fără", "fi", "fie", "fiecare", "fii", "fim", "fiţi", "iar", "ieri", "îi", "îl", "îmi", "împotriva", "în ", "înainte", "înaintea", "încât", "încît", "încotro", "între", "întrucât",...

"chiar", "cînd", "cine", "cineva", "cît", "cîte", "cîţi", "cîtva", "contra", "cu", "cum", "cumva", "curând", "curînd", "da", "dă", "dacă", "dar", "datorită", "de", "deci", "deja", "deoarece", "departe", "deşi", "din", "dinaintea", "dintr", "dintre", "drept", "după", "ea", "ei", "el", "ele", "eram", "este", "eşti", "eu", "face", "fără", "fi", "fie", "fiecare", "fii", "fim", "fiţi", "iar", "ieri", "îi", "îl", "îmi", "împotriva", "în ", "înainte", "înaintea", "încât", "încît", "încotro", "între", "întrucât",...

- To enhance usability and developer experience, CRD validation rules now support direct use of (CEL) reserved keywords as field names in object validation expressions.

    /** The key of the message: Basic */
    public static final String LABELS_webauth_scheme_basic = "{labels.webauth_scheme_basic}";

    /** The key of the message: Digest */
    public static final String LABELS_webauth_scheme_digest = "{labels.webauth_scheme_digest}";

    /** The key of the message: NTLM */

- Fixed a panic when using invalid output format in `kubectl create secret` command. ([#107221](https://github.com/kubernetes/kubernetes/pull/107221), [@rikatz](https://github.com/rikatz))