ations | indent 4 }} {{- end }} spec: {{- if (or (eq .Values.service.type "ClusterIP" "") (empty .Values.service.type)) }} type: ClusterIP {{- if not (empty .Values.service.clusterIP) }} clusterIP: {{ .Values.service.clusterIP }} {{end}} {{- else if eq .Values.service.type "LoadBalancer" }} type: {{ .Values.service.type }} loadBalancerIP: {{ default "" .Values.service.loadBalancerIP }} {{- else }} type: {{ .Values.service.type }} {{- end }} ports: - name: {{ $scheme }} port: {{ .Values.service.port...

ations | indent 4 }} {{- end }} spec: {{- if (or (eq .Values.service.type "ClusterIP" "") (empty .Values.service.type)) }} type: ClusterIP {{- if not (empty .Values.service.clusterIP) }} clusterIP: {{ .Values.service.clusterIP }} {{end}} {{- else if eq .Values.service.type "LoadBalancer" }} type: {{ .Values.service.type }} loadBalancerIP: {{ default "" .Values.service.loadBalancerIP }} {{- else }} type: {{ .Values.service.type }} {{- end }} ports: - name: {{ $scheme }} port: {{ .Values.service.port...

ations | indent 4 }} {{- end }} spec: {{- if (or (eq .Values.service.type "ClusterIP" "") (empty .Values.service.type)) }} type: ClusterIP {{- if not (empty .Values.service.clusterIP) }} clusterIP: {{ .Values.service.clusterIP }} {{end}} {{- else if eq .Values.service.type "LoadBalancer" }} type: {{ .Values.service.type }} loadBalancerIP: {{ default "" .Values.service.loadBalancerIP }} {{- else }} type: {{ .Values.service.type }} {{- end }} ports: - name: {{ $scheme }} port: {{ .Values.service.port...

### Deprecated/changed metrics

- kubelet probe metrics are now of the counter type rather than the gauge type, and the `prober_probe_result` has been replaced by `prober_probe_total`. ([#76074](https://github.com/kubernetes/kubernetes/pull/76074), [@danielqsj](https://github.com/danielqsj))

direct YAML support in the API available today), the Content-Type and Accept
headers are now properly handled as per the HTTP spec.  As a consequence, if
you had a client that was sending an invalid Content-Type or Accept header to
the API, in 1.2 you will either receive a 415 or 406 error.
The only client
this is known to affect is curl when you use -d with JSON but don't set a
content type, helpfully sends "application/x-www-urlencoded", which is not

# Ensure release_base is set on linux
build:release_linux_base --config=release_base

# Disable clang extension that rejects type definitions within offsetof.
# This was added in clang-16 by https://reviews.llvm.org/D133574.
# Can be removed once upb is updated, since a type definition is used within
# offset of in the current version of ubp.

                            content_type_value = request.headers.get("content-type")
                            if not content_type_value:
                                json_body = await request.json()
                            else:
                                message = email.message.Message()
                                message["content-type"] = content_type_value

   ([#123611](https://github.com/kubernetes/kubernetes/pull/123611), [@ritazh](https://github.com/ritazh))

    a = Arrays.<@Nullable Integer>asList(4, 8, null, 16, 23, 42);
    b = Arrays.<@Nullable Integer>asList(4, 8, null, 16, 23, 42);
    assertTrue(elementsEqual(a.iterator(), b.iterator()));

    // Different Iterable types (still equal elements, though).
    a = ImmutableList.of(4, 8, 15, 16, 23, 42);
    b = asList(4, 8, 15, 16, 23, 42);
    assertTrue(elementsEqual(a.iterator(), b.iterator()));

    // An element differs.

- Removed attachable volume limits from the capacity of the node for the following volume type when the kubelet is started, affecting the following volume types when the corresponding csi driver is installed:
  - `awsElasticBlockStore` for `ebs.csi.aws.com`
  - `azureDisk` for `disk.csi.azure.com`
  - `gcePersistentDisk` for `pd.csi.storage.googleapis.com`