### Instrumentation

In v1.9 we focused on improving stability of the components owned by the SIG, including Heapster, Custom Metrics API adapters for Prometheus, and Stackdriver.

    /** The key of the message: Score: */
    public static final String LABELS_doc_score = "{labels.doc_score}";

    /** The key of the message: Fess is running in development mode. Please install OpenSearch separately in a production environment. */
    public static final String LABELS_development_mode_warning = "{labels.development_mode_warning}";

now always set to "systemd" unless the user is explicit about it. This requires existing machine setups to configure the container runtime to use the "systemd" driver. Documentation on this topic can be found here: https://kubernetes.io/docs/setup/production-environment/container-runtimes/. When upgrading existing clusters / nodes using "kubeadm upgrade" the old cgroupDriver value is preserved, but in 1.22 this change will also apply to "upgrade". For more information on migrating to the "systemd" driver...

- kube-apiserver

  - the `--basic-auth-file` flag and authentication mode is deprecated and will be removed in a future release. It is not recommended for production environments. ([#81152](https://github.com/kubernetes/kubernetes/pull/81152), [@tedyu](https://github.com/tedyu))

pro
pro.az
pro.br
pro.cy
pro.ec
pro.fj
pro.ht
pro.in
pro.mv
pro.om
pro.pr
pro.tt
pro.typeform.com
pro.vn
prochowice.pl
prod
production.aero
productions
prof
prof.pr
profesional.bo
progressive
project.space
promo
properties
property
protection
protonet.io
pru
prudential
pruszkow.pl
prvcy.page

## Changelog since v1.10.5

### Action Required

## Changelog since v1.11.0

### Action Required

CSI was first introduction as alpha in Kubernetes v1.9 and moved to beta in Kubernetes v1.10.

You can find a list of sample and production drivers in the [CSI Documentation](https://kubernetes.io/docs/concepts/storage/volumes/#csi).

## **Major Themes**

Kubernetes 1.7 is a milestone release that adds security, stateful application, and extensibility features motivated by widespread production use of Kubernetes.

  purposes, you can use older kernels, as far back as 5.4, if you set the
  `nftables.skipKernelVersionCheck` option in the kube-proxy config, but this is not
  recommended in production since it may cause problems with other nftables
  users on the system.) ([#124152](https://github.com/kubernetes/kubernetes/pull/124152), [@danwinship](https://github.com/danwinship)) [SIG Network]