{"_id":"q-en-website-00b44408a3ade2884986795b330c856ef2d37da834bf453e0a21c58540392863","text":"<ins> --- title: ReplicaSet id: replica-set date: 2018-04-12 full_link: /ja/docs/concepts/workloads/controllers/replicaset/ short_description: > ReplicaSetは、指定された数のPodレプリカが一度に動作するように保証します。 aka: tags: - fundamental - core-object - workload --- ReplicaSetは、任意の時点で動作しているレプリカPodの集合を保持します。(保持することを目指します。) <!--more--> {{< glossary_tooltip term_id=\"deployment\" >}}などのワークロードオブジェクトは、ReplicaSetの仕様に基づいて、 設定された数の{{< glossary_tooltip term_id=\"pod\" text=\"Pods\" >}}がクラスターで稼働することを保証するために、 ReplicaSetを使用します。 </ins>"}
{"_id":"q-en-website-0131b3cf171ebce25201685759bb09324016e9d2074e036d39fbb0811320f0cc","text":"<ins> # *Stop.  This guide has been superseded by [Minikube](../minikube/). The link below is present only for historical purposes* The document has been moved to [here](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/local-cluster/docker.md) </ins>"}
{"_id":"q-en-website-0207c751d7a056d4e4339bf5a96b968343a847f922179dac47139930d4d493e6","text":"Attempt to drain the node on which `zk-2` is scheduled. ```shell <del> kubectl drain $(kubectl get pod zk-2 --template {{.spec.nodeName}}) --ignore-daemonsets --force --delete-local-data </del> <ins> kubectl drain $(kubectl get pod zk-2 --template {{.spec.nodeName}}) --ignore-daemonsets --force --delete-emptydir-data </ins> ``` The output:"}
{"_id":"q-en-website-025dc021e1633379fa2c6a581abe4c6445e2a7b8d6842553c1e3289d61259363","text":"Follow the [Konnectivity service task](/docs/tasks/extend-kubernetes/setup-konnectivity/) to set up the Konnectivity service in your cluster. <ins> ## {{% heading \"whatsnext\" %}} * Read about the [Kubernetes control plane components](/docs/concepts/overview/components/#control-plane-components) * Learn more about [Hubs and Spoke model](https://book.kubebuilder.io/multiversion-tutorial/conversion-concepts.html#hubs-spokes-and-other-wheel-metaphors) * Learn how to [Secure a Cluster](/docs/tasks/administer-cluster/securing-a-cluster/) * Learn more about the [Kubernetes API](/docs/concepts/overview/kubernetes-api/) * [Set up Konnectivity service](/docs/tasks/extend-kubernetes/setup-konnectivity/) * [Use Port Forwarding to Access Applications in a Cluster](/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) * Learn how to [Fetch logs for Pods](/docs/tasks/debug/debug-application/debug-running-pod/#examine-pod-logs), [use kubectl port-forward](/docs/tasks/access-application-cluster/port-forward-access-application-cluster/#forward-a-local-port-to-a-port-on-the-pod) </ins>  No newline at end of file"}
{"_id":"q-en-website-03e61fb03a710b2080a4e5cd0bd40bc485b86cad62b75564650174b508f3e3fa","text":"1. Validate the binary (optional) <del> Download the kubectl-convert checksum file: </del> <ins> Download the `kubectl-convert` checksum file: </ins> ```powershell curl -LO \"https://dl.k8s.io/{{< param \"fullversion\" >}}/bin/windows/amd64/kubectl-convert.exe.sha256\" ``` <del> Validate the kubectl-convert binary against the checksum file: </del> <ins> Validate the `kubectl-convert` binary against the checksum file: </ins> - Using Command Prompt to manually compare `CertUtil`'s output to the checksum file downloaded:"}
{"_id":"q-en-website-050fa3b4a42eb4746c334f00db6417127cae641747fa7452450651007a4fad60","text":"{{% tab name=\"Linux\" %}} <!-- <del> 1. Install the `containerd.io` package from the official Docker repositories. Instructions for setting up the Docker repository for your respective Linux distribution and installing the `containerd.io` package can be found at [Install Docker Engine](https://docs.docker.com/engine/install/#server). </del> <ins> 1. Install the `containerd.io` package from the official Docker repositories. Instructions for setting up the Docker repository for your respective Linux distribution and installing the `containerd.io` package can be found at [Install Docker Engine](https://docs.docker.com/engine/install/#server). </ins> --> 1. 从官方Docker仓库安装 `containerd.io` 软件包。可以在 [安装 Docker 引擎](https://docs.docker.com/engine/install/#server)"}
{"_id":"q-en-website-05c82aeb721fc079c480dc4a89ae94bb5b1777f4b5b39dc14ab4c3f0cfad16fb","text":"/docs/concepts/scheduling-eviction/eviction-policy/     /docs/concepts/scheduling-eviction/node-pressure-eviction/ 301 /docs/concepts/service-catalog/     /docs/concepts/extend-kubernetes/service-catalog/ 301 /docs/concepts/services-networking/networkpolicies/     /docs/concepts/services-networking/network-policies/ 301 <ins> /docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/     /docs/tasks/network/customize-hosts-file-for-pods/ 301 </ins> /docs/concepts/storage/etcd-store-api-object/     /docs/tasks/administer-cluster/configure-upgrade-etcd/ 301 /docs/concepts/storage/volumes/emptyDirapiVersion/     /docs/concepts/storage/volumes/#emptydir/ 301 /docs/concepts/tools/kubectl/object-management-overview/     /docs/concepts/overview/object-management-kubectl/overview/ 301"}
{"_id":"q-en-website-08b05c7e2efa36361f7cb00fa78cadf4e0eed86a367de3ab735dae3fe5c086c8","text":"## kubeadm upgrade guidance <del> The steps for performing a upgrade using kubeadm are outlined in [this document](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/). </del> <ins> The steps for performing an upgrade using kubeadm are outlined in [this document](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/). </ins> For older versions of kubeadm, please refer to older documentation sets of the Kubernetes website. You can use `kubeadm upgrade diff` to see the changes that would be applied to static pod manifests."}
{"_id":"q-en-website-08cac924b91dc61c251d898a33d63d05d0b56f71fa7cc9a7b573bf9a0ffd8112","text":"<ins> apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: example-ingress annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1 spec: rules: - host: hello-world.info http: paths: - path: / pathType: Prefix backend: service: name: web port: number: 8080 </ins>  No newline at end of file"}
{"_id":"q-en-website-0a4567cfd1a3859111997989c5b45427dfbbb0f37a5ab453ac4f6f6e1122ff25","text":"/* DOCS */ .launch-cards { <del> button { cursor: pointer; box-sizing: border-box; background: none; margin: 0; border: 0; } </del> <ins> padding: 0; display: grid; grid-template-columns: repeat(3, 1fr); row-gap: 1em; .launch-card { display: flex; padding: 0 30px 0 0; .card-content{ width: fit-content; display: flex; flex-direction: column; margin: 0; row-gap: 1em; h2 { font-size: 1.75em; padding: 0.5em 0; margin: 0; a { display: none; } } p { margin: 0; } ul { list-style: none; height: fit-content; line-height: 1.6; padding: 0; margin-block-end: auto; } br { display: none; } button { height: min-content; width: auto; padding: .5em 1em; cursor: pointer; box-sizing: border-box; } } } </ins> <del> ul, li { list-style: none; padding-left: 0; } </del> <ins> @media only screen and (max-width: 1000px) { grid-template-columns: 1fr; .launch-card { width: 100%; } } </ins> } // table of contents .td-toc { padding-top: 1.5rem !important;"}
{"_id":"q-en-website-0b944463633971e8baea55b9c3e34dedd415eb4421527bd7a0ea067ee137614d","text":"For more information about the authentication process, refer to [Authentication](/docs/reference/access-authn-authz/authentication/#service-account-tokens). <del> ### Authenticating service account credentials in your own code {authenticating-in-code} </del> <ins> ### Authenticating service account credentials in your own code {#authenticating-in-code} </ins> If you have services of your own that need to validate Kubernetes service account credentials, you can use the following methods:"}
{"_id":"q-en-website-0e4147819ad7a6101406dfe4e3ba7da5d35e7380b0833b1cfa61b64bfa824f9a","text":"if you have 3 registered clusters and you create a federated ReplicaSet with `spec.replicas = 9`, then each ReplicaSet in the 3 clusters will have `spec.replicas=3`. <del> To modify the number of replicas in each cluster, you can specify [FederatedReplicaSetPreference](https://github.com/kubernetes/federation/blob/{{page.githubbranch}}/apis/federation/types.go) as an annotation with key `federation.kubernetes.io/replica-set-preferences` on the federated ReplicaSet. </del> <ins> To modify the number of replicas in each cluster, you can add an annotation with key `federation.kubernetes.io/replica-set-preferences` to the federated ReplicaSet. The value of the annoation is a serialized JSON that contains fields shown in the following example: ``` { \"rebalance\": true, \"clusters\": { \"foo\": { \"minReplicas\": 10, \"maxReplicas\": 50, \"weight\": 100 }, \"bar\": { \"minReplicas\": 10, \"maxReplicas\": 100, \"weight\": 200 } } } ``` The `rebalance` boolean field specifies whether replicas already scheduled and running may be moved in order to match current state to the specified preferences. The `clusters` object field contains a map where users can specify the constraints for replica placement across the clusters (`foo` and `bar` in the example). For each cluster, you can specify the minimum number of replicas that should be assigned to it (default is zero), the maximum number of replicas the cluster can accept (default is unbounded) and a number expressing the relative weight of preferences to place additional replicas to that cluster. </ins> ## Updating a Federated ReplicaSet"}
{"_id":"q-en-website-0e7ebc11c1b876291b45fe8ffa6286e7eedb4c4af076efb11e2b772de2e10046","text":"<ins> --- title: Minikube上でNGINX Ingressコントローラーを使用してIngressをセットアップする content_type: task weight: 100 --- <!-- overview --> [Ingress](/ja/docs/concepts/services-networking/ingress/)とは、クラスター内のServiceに外部からのアクセスを許可するルールを定義するAPIオブジェクトです。[Ingressコントローラー](/ja/docs/concepts/services-networking/ingress-controllers/)はIngress内に設定されたルールを満たすように動作します。 このページでは、簡単なIngressをセットアップして、HTTPのURIに応じてwebまたはweb2というServiceにリクエストをルーティングする方法を説明します。 ## {{% heading \"prerequisites\" %}} {{< include \"task-tutorial-prereqs.md\" >}} {{< version-check >}} <!-- steps --> ## Minikubeクラスターを作成する 1. **Launch Terminal**をクリックします。 {{< kat-button >}} 1. (オプション) Minikubeをローカル環境にインストールした場合は、次のコマンドを実行します。 ```shell minikube start ``` ## Ingressコントローラーを有効化する 1. NGINX Ingressコントローラーを有効にするために、次のコマンドを実行します。 ```shell minikube addons enable ingress ``` 1. NGINX Ingressコントローラーが起動したことを確認します。 ```shell kubectl get pods -n kube-system ``` {{< note >}} このコマンドの実行には数分かかる場合があります。 {{< /note >}} 出力は次のようになります。 ```shell NAME                                        READY     STATUS    RESTARTS   AGE default-http-backend-59868b7dd6-xb8tq       1/1       Running   0          1m kube-addon-manager-minikube                 1/1       Running   0          3m kube-dns-6dcb57bcc8-n4xd4                   3/3       Running   0          2m kubernetes-dashboard-5498ccf677-b8p5h       1/1       Running   0          2m nginx-ingress-controller-5984b97644-rnkrg   1/1       Running   0          1m storage-provisioner                         1/1       Running   0          2m ``` ## Hello Worldアプリをデプロイする 1. 次のコマンドを実行して、Deploymentを作成します。 ```shell kubectl create deployment web --image=gcr.io/google-samples/hello-app:1.0 ``` 出力は次のようになります。 ```shell deployment.apps/web created ``` 1. Deploymentを公開します。 ```shell kubectl expose deployment web --type=NodePort --port=8080 ``` 出力は次のようになります。 ```shell service/web exposed ``` 1. Serviceが作成され、NodePort上で利用できるようになったことを確認します。 ```shell kubectl get service web ``` 出力は次のようになります。 ```shell NAME      TYPE       CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE web       NodePort   10.104.133.249   <none>        8080:31637/TCP   12m ``` 1. NodePort経由でServiceを訪問します。 ```shell minikube service web --url ``` 出力は次のようになります。 ```shell http://172.17.0.15:31637 ``` {{< note >}} Katacoda環境の場合のみ: 上部のterminalパネルでプラスのアイコンをクリックして、**Select port to view on Host 1**(Host 1を表示するポートを選択)をクリックします。NodePort(上の例では`31637`)を入力して、**Display Port**(ポートを表示)をクリックしてください。 {{< /note >}} 出力は次のようになります。 ```shell Hello, world! Version: 1.0.0 Hostname: web-55b8c6998d-8k564 ``` これで、MinikubeのIPアドレスとNodePort経由で、サンプルアプリにアクセスできるようになりました。次のステップでは、Ingressリソースを使用してアプリにアクセスできるように設定します。 ## Ingressリソースを作成する 以下に示すファイルは、hello-world.info経由で送られたトラフィックをServiceに送信するIngressリソースです。 1. 以下の内容で`example-ingress.yaml`を作成します。 ```yaml apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: example-ingress annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1 spec: rules: - host: hello-world.info http: paths: - path: / backend: serviceName: web servicePort: 8080 ``` 1. 次のコマンドを実行して、Ingressリソースを作成します。 ```shell kubectl apply -f example-ingress.yaml ``` 出力は次のようになります。 ```shell ingress.networking.k8s.io/example-ingress created ``` 1. 次のコマンドで、IPアドレスが設定されていることを確認します。 ```shell kubectl get ingress ``` {{< note >}} このコマンドの実行には数分かかる場合があります。 {{< /note >}} ```shell NAME              HOSTS              ADDRESS       PORTS     AGE example-ingress   hello-world.info   172.17.0.15   80        38s ``` 1. 次の行を`/etc/hosts`ファイルの最後に書きます。 {{< note >}} Minikubeをローカル環境で実行している場合、`minikube ip`コマンドを使用すると外部のIPが取得できます。Ingressのリスト内に表示されるIPアドレスは、内部のIPになるはずです。 {{< /note >}} ``` 172.17.0.15 hello-world.info ``` この設定により、リクエストがhello-world.infoからMinikubeに送信されるようになります。 1. Ingressコントローラーがトラフィックを制御していることを確認します。 ```shell curl hello-world.info ``` 出力は次のようになります。 ```shell Hello, world! Version: 1.0.0 Hostname: web-55b8c6998d-8k564 ``` {{< note >}} Minikubeをローカル環境で実行している場合、ブラウザからhello-world.infoにアクセスできます。 {{< /note >}} ## 2番目のDeploymentを作成する 1. 次のコマンドを実行して、v2のDeploymentを作成します。 ```shell kubectl create deployment web2 --image=gcr.io/google-samples/hello-app:2.0 ``` 出力は次のようになります。 ```shell deployment.apps/web2 created ``` 1. Deploymentを公開します。 ```shell kubectl expose deployment web2 --port=8080 --type=NodePort ``` 出力は次のようになります。 ```shell service/web2 exposed ``` ## Ingressを編集する 1. 既存の`example-ingress.yaml`を編集して、以下の行を追加します。 ```yaml - path: /v2 backend: serviceName: web2 servicePort: 8080 ``` 1. 次のコマンドで変更を適用します。 ```shell kubectl apply -f example-ingress.yaml ``` 出力は次のようになります。 ```shell ingress.networking/example-ingress configured ``` ## Ingressを試す 1. Hello Worldアプリの1番目のバージョンにアクセスします。 ```shell curl hello-world.info ``` 出力は次のようになります。 ```shell Hello, world! Version: 1.0.0 Hostname: web-55b8c6998d-8k564 ``` 1. Hello Worldアプリの2番目のバージョンにアクセスします。 ```shell curl hello-world.info/v2 ``` 出力は次のようになります。 ```shell Hello, world! Version: 2.0.0 Hostname: web2-75cd47646f-t8cjk ``` {{< note >}} Minikubeをローカル環境で実行している場合、ブラウザからhello-world.infoおよびhello-world.info/v2にアクセスできます。 {{< /note >}} ## {{% heading \"whatsnext\" %}} * [Ingress](/ja/docs/concepts/services-networking/ingress/)についてさらに学ぶ。 * [Ingressコントローラー](/ja/docs/concepts/services-networking/ingress-controllers/)についてさらに学ぶ。 * [Service](/ja/docs/concepts/services-networking/service/)についてさらに学ぶ。 </ins>"}
{"_id":"q-en-website-0f00ca41e6af3362e87594bd2906baca7db53b34ca3017606974c111277b1cba","text":"--> 仅当 `Guaranteed` Pod 中所有容器都被指定了请求和限制并且二者相等时，才保证 Pod 不被驱逐。 这些 Pod 永远不会因为另一个 Pod 的资源消耗而被驱逐。 <del> 如果系统守护进程（例如 `kubelet`、`docker` 和 `journald`） </del> <ins> 如果系统守护进程（例如 `kubelet` 和 `journald`） </ins> 消耗的资源比通过 `system-reserved` 或 `kube-reserved` 分配保留的资源多， 并且该节点只有 `Guaranteed` 或 `Burstable` Pod 使用的资源少于其上剩余的请求， 那么 kubelet 必须选择驱逐这些 Pod 中的一个以保持节点稳定性并减少资源匮乏对其他 Pod 的影响。"}
{"_id":"q-en-website-121da4feb787e365949cf511ed93916e5988f133779efcc8d10a5507b46bbe1e","text":"cgroupDriver: systemd ``` <ins> {{< note >}} Starting with v1.22 and later, when creating a cluster with kubeadm, if the user does not set the `cgroupDriver` field under `KubeletConfiguration`, kubeadm defaults it to `systemd`. {{< /note >}} </ins> If you configure `systemd` as the cgroup driver for the kubelet, you must also configure `systemd` as the cgroup driver for the container runtime. Refer to the documentation for your container runtime for instructions. For example:"}
{"_id":"q-en-website-1317bde09d61c92e98f6ab4576e1409779037ed8a32213665b9db553e643bb28","text":"<ins> --- title: \"通过 gcloud 安装 kubectl\" description: \"用各个特定操作系统标签页中包含的 gcloud 指令片段安装 kubectl。\" headless: true --- <!-- --- title: \"gcloud kubectl install\" description: \"How to install kubectl with gcloud snippet for inclusion in each OS-specific tab.\" headless: true --- --> <!-- You can install kubectl as part of the Google Cloud SDK. --> kubectl 可以作为 Google Cloud SDK 的一部分被安装。 <!-- 1. Install the [Google Cloud SDK](https://cloud.google.com/sdk/). 1. Run the `kubectl` installation command: --> 1. 安装 [Google Cloud SDK](https://cloud.google.com/sdk/)。 1. 运行安装 `kubectl` 的命令： ```shell gcloud components install kubectl ``` <!-- 1. Test to ensure the version you installed is up-to-date: --> 1. 验证一下，确保安装的是最新的版本： ```shell kubectl version --client ``` </ins>  No newline at end of file"}
{"_id":"q-en-website-133bbe6cbc61dda136292a6ad16083aab31fc278aa771a81c8f6e8c3ec88d6e3","text":"cat <<EOF >./kustomization.yaml configMapGenerator: - name: game-config-5 <del> labels: game-config: config-5 </del> <ins> options: labels: game-config: config-5 </ins> files: - game-special-key=configure-pod-container/configmap/game.properties EOF"}
{"_id":"q-en-website-136384196b08438466eb349f339d5333739b2a13835b82a6cf6ec305903a5144","text":"* `apiserver_flowcontrol_priority_level_request_count_watermarks` is a histogram vector of high or low water marks of the number of requests broken down by the labels `phase` (which takes on the <del> values `waiting` and `executing`) and `priorityLevel`; the label </del> <ins> values `waiting` and `executing`) and `priority_level`; the label </ins> `mark` takes on values `high` and `low`.  The water marks are accumulated over windows bounded by the times when an observation was added to"}
{"_id":"q-en-website-13723dce4f1ad8fae0515a3b701c8828a6b396b2c12310ffba065e0535630a76","text":"<ins> --- no_issue: true title: Instalação main_menu: true weight: 30 content_type: concept --- <!-- overview --> Essa seção lista as diferentes formas de instalar e executar o Kubernetes. Quando você realiza a instalação de um cluster Kubernetes, deve decidir o tipo de instalação baseado em critérios como facilidade de manutenção, segurança, controle, quantidade de recursos disponíveis e a experiência necessária para gerenciar e operar o cluster. Você pode criar um cluster Kubernetes em uma máquina local, na nuvem, em um datacenter on-premises ou ainda escolher uma oferta de um cluster Kubernetes gerenciado pelo seu provedor de computação em nuvem. Existem ainda diversos outros tipos de soluções customizadas, que você pode se deparar ao buscar formas de instalação e gerenciamento de seu cluster. <!-- body --> ## Ambientes de aprendizado Se você está aprendendo ou pretende aprender mais sobre o Kubernetes, use ferramentas suportadas pela comunidade, ou ferramentas no ecossistema que te permitam criar um cluster Kubernetes em sua máquina virtual. Temos como exemplo aqui o [Minikube](/docs/tasks/tools/install-minikube/) e o [KinD](https://kind.sigs.k8s.io/docs/user/quick-start/) ## Ambientes de produção Ao analisar uma solução para um ambiente de produção, devem ser considerados quais aspectos de operação de um cluster Kubernetes você deseja gerenciar, ou então delegar ao seu provedor. Temos diversas opções para esse provisionamento, desde o uso de uma ferramenta de deployment de um cluster tal qual o [Kubeadm](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/) ou o [Kubespray](/docs/setup/production-environment/tools/kubespray/) quando se trata de um cluster local, ou ainda o uso de um cluster gerenciado por seu provedor de nuvem. Para a escolha do melhor ambiente e da melhor forma para fazer essa instalação, você deve considerar: * Se você deseja se preocupar com a gestão de backup da sua estrutura do ambiente de gerenciamento * Se você deseja ter um cluster mais atualizado, com novas funcionalidades, ou se deseja seguir a versão suportada pelo fornecedor * Se você deseja ter um cluster com um alto nível de serviço, ou com auto provisionamento de alta disponibilidade * Quanto você deseja pagar por essa produção </ins>"}
{"_id":"q-en-website-15a27e82fd3d2192fa3c8262c694ad4c7301d5086e7f783731d77c65bfa87b39","text":"<ins> --- title: 临时卷 content_type: concept weight: 50 --- <!-- reviewers: - jsafrane - saad-ali - msau42 - xing-yang - pohly title: Ephemeral Volumes content_type: concept weight: 50 --> <!-- overview --> <!-- This document describes _ephemeral volumes_ in Kubernetes. Familiarity with [volumes](/docs/concepts/storage/volumes/) is suggested, in particular PersistentVolumeClaim and PersistentVolume. --> 本文档描述 Kubernetes 中的 _临时卷（Ephemeral Volume）_。 建议先了解[卷](/zh/docs/concepts/storage/volumes/)，特别是 PersistentVolumeClaim 和 PersistentVolume。 <!-- body --> <!-- Some application need additional storage but don't care whether that data is stored persistently across restarts. For example, caching services are often limited by memory size and can move infrequently used data into storage that is slower than memory with little impact on overall performance. --> 有些应用程序需要额外的存储，但并不关心数据在重启后仍然可用，既是否被持久地保存。 例如，缓存服务经常受限于内存大小，将不常用的数据转移到比内存慢、但对总体性能的影响很小的存储中。 <!-- Other applications expect some read-only input data to be present in files, like configuration data or secret keys. --> 另有些应用程序需要以文件形式注入的只读数据，比如配置数据或密钥。 <!-- _Ephemeral volumes_ are designed for these use cases. Because volumes follow the Pod's lifetime and get created and deleted along with the Pod, Pods can be stopped and restarted without being limited to where some persistent volume is available. --> _临时卷_ 就是为此类用例设计的。因为卷会遵从 Pod 的生命周期，与 Pod 一起创建和删除， 所以停止和重新启动 Pod 时，不会受持久卷在何处可用的限制。 <!-- Ephemeral volumes are specified _inline_ in the Pod spec, which simplifies application deployment and management. --> 临时卷在 Pod 规范中以 _内联_ 方式定义，这简化了应用程序的部署和管理。 <!-- ### Types of ephemeral volumes --> ### 临时卷的类型 {#types-of-ephemeral-volumes} <!-- Kubernetes supports several different kinds of ephemeral volumes for different purposes: - [emptyDir](/docs/concepts/storage/volumes/#emptydir): empty at Pod startup, with storage coming locally from the kubelet base directory (usually the root disk) or RAM - [configMap](/docs/concepts/storage/volumes/#configmap), [downwardAPI](/docs/concepts/storage/volumes/#downwardapi), [secret](/docs/concepts/storage/volumes/#secret): inject different kinds of Kubernetes data into a Pod - [CSI ephemeral volumes](docs/concepts/storage/volumes/#csi-ephemeral-volumes): similar to the previous volume kinds, but provided by special [CSI drivers](https://github.com/container-storage-interface/spec/blob/master/spec.md) which specifically [support this feature](https://kubernetes-csi.github.io/docs/drivers.html) - [generic ephemeral volumes](#generic-ephemeral-volumes), which can be provided by all storage drivers that also support persistent volumes --> Kubernetes 为了不同的目的，支持几种不同类型的临时卷： - [emptyDir](/zh/docs/concepts/storage/volumes/#emptydir)： Pod 启动时为空，存储空间来自本地的 kubelet 根目录（通常是根磁盘）或内存 - [configMap](/zh/docs/concepts/storage/volumes/#configmap)、 [downwardAPI](/zh/docs/concepts/storage/volumes/#downwardapi)、 [secret](/zh/docs/concepts/storage/volumes/#secret)： 将不同类型的 Kubernetes 数据注入到 Pod 中 - [CSI 临时卷](/zh/docs/concepts/storage/volumes/#csi-ephemeral-volumes)： 类似于前面的卷类型，但由专门[支持此特性](https://kubernetes-csi.github.io/docs/drivers.html) 的指定 [CSI 驱动程序](https://github.com/container-storage-interface/spec/blob/master/spec.md)提供 - [通用临时卷](#generic-ephemeral-volumes)： 它可以由所有支持持久卷的存储驱动程序提供 <!-- `emptyDir`, `configMap`, `downwardAPI`, `secret` are provided as [local ephemeral storage](/docs/concepts/configuration/manage-resources-containers/#local-ephemeral-storage). They are managed by kubelet on each node. CSI ephemeral volumes *must* be provided by third-party CSI storage drivers. --> `emptyDir`、`configMap`、`downwardAPI`、`secret` 是作为 [本地临时存储](/zh/docs/concepts/configuration/manage-resources-containers/#local-ephemeral-storage) 提供的。它们由各个节点上的 kubelet 管理。 CSI 临时卷 *必须* 由第三方 CSI 存储驱动程序提供。 <!-- Generic ephemeral volumes *can* be provided by third-party CSI storage drivers, but also by any other storage driver that supports dynamic provisioning. Some CSI drivers are written specifically for CSI ephemeral volumes and do not support dynamic provisioning: those then cannot be used for generic ephemeral volumes. --> 通用临时卷 *可以* 由第三方 CSI 存储驱动程序提供，也可以由支持动态配置的任何其他存储驱动程序提供。 一些专门为 CSI 临时卷编写的 CSI 驱动程序，不支持动态供应：因此这些驱动程序不能用于通用临时卷。 <!-- The advantage of using third-party drivers is that they can offer functionality that Kubernetes itself does not support, for example storage with different performance characteristics than the disk that is managed by kubelet, or injecting different data. --> 使用第三方驱动程序的优势在于，它们可以提供 Kubernetes 本身不支持的功能， 例如，与 kubelet 管理的磁盘具有不同运行特征的存储，或者用来注入不同的数据 <!-- ### CSI ephemeral volumes --> ### CSI 临时卷 {#csi-ephemeral-volumes} {{< feature-state for_k8s_version=\"v1.16\" state=\"beta\" >}} <!-- This feature requires the `CSIInlineVolume` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to be enabled. It is enabled by default starting with Kubernetes 1.16. CSI ephemeral volumes are only supported by a subset of CSI drivers. The Kubernetes CSI [Drivers list](https://kubernetes-csi.github.io/docs/drivers.html) shows which drivers support ephemeral volumes. --> 该特性需要启用参数 `CSIInlineVolume` [特性门控（feature gate）](/zh/docs/reference/command-line-tools-reference/feature-gates/)。 该参数从 Kubernetes 1.16 开始默认启用。 {{< note >}} 只有一部分 CSI 驱动程序支持 CSI 临时卷。Kubernetes CSI [驱动程序列表](https://kubernetes-csi.github.io/docs/drivers.html) 显示了支持临时卷的驱动程序。 {{< /note >}} <!-- Conceptually, CSI ephemeral volumes are similar to `configMap`, `downwardAPI` and `secret` volume types: the storage is managed locally on each node and is created together with other local resources after a Pod has been scheduled onto a node. Kubernetes has no concept of rescheduling Pods anymore at this stage. Volume creation has to be unlikely to fail, otherwise Pod startup gets stuck. In particular, [storage capacity aware Pod scheduling](/docs/concepts/storage-capacity/) is *not* supported for these volumes. They are currently also not covered by the storage resource usage limits of a Pod, because that is something that kubelet can only enforce for storage that it manages itself. Here's an example manifest for a Pod that uses CSI ephemeral storage: --> 从概念上讲，CSI 临时卷类似于 `configMap`、`downwardAPI` 和 `secret` 类型的卷： 其存储在每个节点本地管理，并在将 Pod 调度到节点后与其他本地资源一起创建。 在这个阶段，Kubernetes 没有重新调度 Pods 的概念。卷创建不太可能失败，否则 Pod 启动将会受阻。 特别是，这些卷 *不* 支持[感知存储容量的 Pod 调度](/zh/docs/concepts/storage/storage-capacity/)。 它们目前也没包括在 Pod 的存储资源使用限制中，因为 kubelet 只能对它自己管理的存储强制执行。 下面是使用 CSI 临时存储的 Pod 的示例清单： ```yaml kind: Pod apiVersion: v1 metadata: name: my-csi-app spec: containers: - name: my-frontend image: busybox volumeMounts: - mountPath: \"/data\" name: my-csi-inline-vol command: [ \"sleep\", \"1000000\" ] volumes: - name: my-csi-inline-vol csi: driver: inline.storage.kubernetes.io volumeAttributes: foo: bar ``` <!-- The `volumeAttributes` determine what volume is prepared by the driver. These attributes are specific to each driver and not standardized. See the documentation of each CSI driver for further instructions. As a cluster administrator, you can use a [PodSecurityPolicy](/docs/concepts/policy/pod-security-policy/) to control which CSI drivers can be used in a Pod, specified with the [`allowedCSIDrivers` field](/docs/reference/generated/kubernetes-api/{{< param \"version\" >}}/#podsecuritypolicyspec-v1beta1-policy). --> `volumeAttributes` 决定驱动程序准备什么样的卷。这些属性特定于每个驱动程序，且没有实现标准化。 有关进一步的说明，请参阅每个 CSI 驱动程序的文档。 作为一个集群管理员，你可以使用 [PodSecurityPolicy](/zh/docs/concepts/policy/pod-security-policy/) 来控制在 Pod 中可以使用哪些 CSI 驱动程序， 具体则是通过 [`allowedCSIDrivers` 字段](/docs/reference/generated/kubernetes-api/{{< param \"version\" >}}/#podsecuritypolicyspec-v1beta1-policy) 指定。 <!-- ### Generic ephemeral volumes --> ### 通用临时卷 {#generic-ephemeral-volumes} {{< feature-state for_k8s_version=\"v1.19\" state=\"alpha\" >}} <!-- This feature requires the `GenericEphemeralVolume` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to be enabled. Because this is an alpha feature, it is disabled by default. --> 这个特性需要启用 `GenericEphemeralVolume` [特性门控](/zh/docs/reference/command-line-tools-reference/feature-gates/)。 因为这是一个alpha特性，默认禁用。 <!-- Generic ephemeral volumes are similar to `emptyDir` volumes, just more flexible: - Storage can be local or network-attached. - Volumes can have a fixed size that Pods are not able to exceed. - Volumes may have some initial data, depending on the driver and parameters. - Typical operations on volumes are supported assuming that the driver supports them, including ([snapshotting](/docs/concepts/storage/volume-snapshots/), [cloning](/docs/concepts/storage/volume-pvc-datasource/), [resizing](/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims), and [storage capacity tracking](/docs/concepts/storage-capacity/). Example: --> 通用临时卷类似于 `emptyDir` 卷，但更加灵活： - 存储可以是本地的，也可以是网络连接的。 - 卷可以有固定的大小，pod不能超量使用。 - 卷可能有一些初始数据，这取决于驱动程序和参数。 - 当驱动程序支持，卷上的典型操作将被支持，包括（[快照](/zh/docs/concepts/storage/volume-snapshots/)、[克隆](/zh/docs/concepts/storage/volume-pvc-datasource/)、[调整大小](/zh/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims)和[存储容量跟踪](/zh/docs/concepts/storage/storage-capacity/)）。 示例： ```yaml kind: Pod apiVersion: v1 metadata: name: my-app spec: containers: - name: my-frontend image: busybox volumeMounts: - mountPath: \"/scratch\" name: scratch-volume command: [ \"sleep\", \"1000000\" ] volumes: - name: scratch-volume ephemeral: volumeClaimTemplate: metadata: labels: type: my-frontend-volume spec: accessModes: [ \"ReadWriteOnce\" ] storageClassName: \"scratch-storage-class\" resources: requests: storage: 1Gi ``` <!-- ### Lifecycle and PersistentVolumeClaim --> ### 生命周期和 PersistentVolumeClaim {#lifecycle-and-persistentvolumeclaim} <!-- The key design idea is that the [parameters for a volume claim](/docs/reference/generated/kubernetes-api/#ephemeralvolumesource-v1alpha1-core) are allowed inside a volume source of the Pod. Labels, annotations and the whole set of fields for a PersistentVolumeClaim are supported. When such a Pod gets created, the ephemeral volume controller then creates an actual PersistentVolumeClaim object in the same namespace as the Pod and ensures that the PersistentVolumeClaim gets deleted when the Pod gets deleted. --> 关键的设计思想是在 Pod 的卷来源中允许使用 [卷申领的参数](/docs/reference/generated/kubernetes-api/#ephemeralvolumesource-v1alpha1-core)。 PersistentVolumeClaim 的标签、注解和整套字段集均被支持。 创建这样一个 Pod 后， 临时卷控制器在 Pod 所属的命名空间中创建一个实际的 PersistentVolumeClaim 对象， 并确保删除 Pod 时， 同步删除PersistentVolumeClaim 。 <!-- That triggers volume binding and/or provisioning, either immediately if the {{< glossary_tooltip text=\"StorageClass\" term_id=\"storage-class\" >}} uses immediate volume binding or when the Pod is tentatively scheduled onto a node (`WaitForFirstConsumer` volume binding mode). The latter is recommended for generic ephemeral volumes because then the scheduler is free to choose a suitable node for the Pod. With immediate binding, the scheduler is forced to select a node that has access to the volume once it is available. --> 如上设置将触发卷的绑定与/或准备操作，相应动作或者在 {{< glossary_tooltip text=\"StorageClass\" term_id=\"storage-class\" >}} 使用即时卷绑定时立即执行， 或者当 Pod 被暂时性调度到某节点时执行 (`WaitForFirstConsumer` 卷绑定模式)。 对于常见的临时卷，建议采用后者，这样调度器就可以自由地为 Pod 选择合适的节点。 对于即时绑定，调度器则必须选出一个节点，使得在卷可用时，能立即访问该卷。 <!-- In terms of [resource ownership](/docs/concepts/workloads/controllers/garbage-collection/#owners-and-dependents), a Pod that has generic ephemeral storage is the owner of the PersistentVolumeClaim(s) that provide that ephemeral storage. When the Pod is deleted, the Kubernetes garbage collector deletes the PVC, which then usually triggers deletion of the volume because the default reclaim policy of storage classes is to delete volumes. You can create quasi-ephemeral local storage using a StorageClass with a reclaim policy of `retain`: the storage outlives the Pod, and in this case you need to ensure that volume clean up happens separately. --> 就[资源所有权](/zh/docs/concepts/workloads/controllers/garbage-collection/#owners-and-dependents)而言， 拥有通用临时存储的 Pod 是提供临时存储 (ephemeral storage) 的 PersistentVolumeClaim 的所有者。 当 Pod 被删除时，Kubernetes 垃圾收集器会删除 PVC， 然后 PVC 通常会触发卷的删除，因为存储类的默认回收策略是删除卷。 你可以使用带有 `retain` 回收策略的 StorageClass 创建准临时 (quasi-ephemeral) 本地存储： 该存储比 Pod 寿命长，在这种情况下，你需要确保单独进行卷清理。 <!-- While these PVCs exist, they can be used like any other PVC. In particular, they can be referenced as data source in volume cloning or snapshotting. The PVC object also holds the current status of the volume. --> 当这些 PVC 存在时，它们可以像其他 PVC 一样使用。 特别是，它们可以被引用作为批量克隆或快照的数据源。 PVC对象还保持着卷的当前状态。 <!-- ### PersistentVolumeClaim naming --> ### PersistentVolumeClaim 的命名 {#persistentvolumeclaim-naming} <!-- Naming of the automatically created PVCs is deterministic: the name is a combination of Pod name and volume name, with a hyphen (`-`) in the middle. In the example above, the PVC name will be `my-app-scratch-volume`.  This deterministic naming makes it easier to interact with the PVC because one does not have to search for it once the Pod name and volume name are known. --> 自动创建的 PVCs 的命名是确定的：此名称是 Pod 名称和卷名称的组合，中间由连字符(`-`)连接。 在上面的示例中，PVC 将命名为 `my-app-scratch-volume` 。 这种确定性命名方式使得与 PVC 交互变得更容易，因为一旦知道 Pod 名称和卷名，就不必搜索它。 <!-- The deterministic naming also introduces a potential conflict between different Pods (a Pod \"pod-a\" with volume \"scratch\" and another Pod with name \"pod\" and volume \"a-scratch\" both end up with the same PVC name \"pod-a-scratch\") and between Pods and manually created PVCs. --> 这种确定性命名方式也引入了潜在的冲突， 比如在不同的 Pod 之间（名为 “Pod-a” 的 Pod 挂载名为 \"scratch\" 的卷， 名为 \"pod\" 的 Pod 挂载名为 “a-scratch” 的卷，这两者均会生成名为 \"pod-a-scratch\" 的PVC）， 或者在 Pod 和手工创建的 PVC 之间。 <!-- Such conflicts are detected: a PVC is only used for an ephemeral volume if it was created for the Pod. This check is based on the ownership relationship. An existing PVC is not overwritten or modified. But this does not resolve the conflict because without the right PVC, the Pod cannot start. --> 以下冲突会被检测到：如果 PVC 是为 Pod 创建的，那么它只用于临时卷。 此检测基于所有权关系。现有的 PVC 不会被覆盖或修改。 但这并不能解决冲突，因为如果没有正确的 PVC，Pod 就无法启动。 <!-- Take care when naming Pods and volumes inside the same namespace, so that these conflicts can't occur. --> {{< caution >}} 当命名 Pods 和卷出现在同一个命名空间中时，要小心，以防止发生此类冲突。 {{< /caution >}} <!-- ### Security --> ### 安全 {#security} <!-- Enabling the GenericEphemeralVolume feature allows users to create PVCs indirectly if they can create Pods, even if they do not have permission to create PVCs directly. Cluster administrators must be aware of this. If this does not fit their security model, they have two choices: --> 启用 GenericEphemeralVolume 特性会导致那些没有 PVCs 创建权限的用户， 在创建 Pods 时，被允许间接的创建 PVCs。 集群管理员必须意识到这一点。 如果这不符合他们的安全模型，他们有两种选择： <!-- - Explicitly disable the feature through the feature gate, to avoid being surprised when some future Kubernetes version enables it by default. - Use a [Pod Security Policy](/docs/concepts/policy/pod-security-policy/) where the `volumes` list does not contain the `ephemeral` volume type. --> - 通过特性门控显式禁用该特性，可以避免将来的 Kubernetes 版本默认启用时带来混乱。 - 当`卷`列表不包含 `ephemeral` 卷类型时，使用 [Pod 安全策略](/zh/docs/concepts/policy/pod-security-policy/)。 <!-- The normal namespace quota for PVCs in a namespace still applies, so even if users are allowed to use this new mechanism, they cannot use it to circumvent other policies. --> 在一个命名空间中，用于 PVCs 的常规命名空间配额仍然适用， 因此即使允许用户使用这种新机制，他们也不能使用它来规避其他策略。 ## {{% heading \"whatsnext\" %}} <!-- ### Ephemeral volumes managed by kubelet See [local ephemeral storage](/docs/concepts/configuration/manage-resources-containers/#local-ephemeral-storage). --> ### kubelet 管理的临时卷 {#ephemeral-volumes-managed-by-kubelet} 参阅[本地临时存储](/zh/docs/concepts/configuration/manage-resources-containers/#local-ephemeral-storage)。 <!-- ### CSI ephemeral volumes - For more information on the design, see the [Ephemeral Inline CSI volumes KEP](https://github.com/kubernetes/enhancements/blob/ad6021b3d61a49040a3f835e12c8bb5424db2bbb/keps/sig-storage/20190122-csi-inline-volumes.md). - For more information on further development of this feature, see the [enhancement tracking issue #596](https://github.com/kubernetes/enhancements/issues/596). --> ### CSI 临时卷 {#csi-ephemeral-volumes} - 有关设计的更多信息，参阅 [Ephemeral Inline CSI volumes KEP](https://github.com/kubernetes/enhancements/blob/ad6021b3d61a49040a3f835e12c8bb5424db2bbb/keps/sig-storage/20190122-csi-inline-volumes.md)。 - 本特性下一步开发的更多信息，参阅 [enhancement tracking issue #596](https://github.com/kubernetes/enhancements/issues/596)。 <!-- ### Generic ephemeral volumes - For more information on the design, see the [Generic ephemeral inline volumes KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1698-generic-ephemeral-volumes/README.md). - For more information on further development of this feature, see the [enhancement tracking issue #1698](https://github.com/kubernetes/enhancements/issues/1698). --> ### 通用临时卷 {#generic-ephemeral-volumes} - 有关设计的更多信息，参阅 [Generic ephemeral inline volumes KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1698-generic-ephemeral-volumes/README.md)。 - 本特性下一步开发的更多信息，参阅 [enhancement tracking issue #1698](https://github.com/kubernetes/enhancements/issues/1698). </ins>  No newline at end of file"}
{"_id":"q-en-website-1637248fb2847514e29f4d1eac0726384ce5af1dd8420a1d76f990e459c7cef6","text":"name: game-config namespace: default resourceVersion: \"516\" <del> selfLink: /api/v1/namespaces/default/configmaps/game-config-2 </del> <ins> selfLink: /api/v1/namespaces/default/configmaps/game-config </ins> uid: b4952dc3-d670-11e5-8cd0-68f728db1985 ```"}
{"_id":"q-en-website-174492f5288b30d380780d6139bfeb1171fd07c5928c6113b3c116e723e572c6","text":"placement policies while keeping the abstraction free from explicit placement directives. <ins> For detailed information on resource management, please refer to the [Resource Management for Pods and Containers](/docs/concepts/configuration/manage-resources-containers) documentation. </ins> ## {{% heading \"prerequisites\" %}}"}
{"_id":"q-en-website-17b6380a62a23b3de2deede9ddc35c9a9b79fa8e7086dc58af58bf40ccd17a18","text":"### Docker <!-- <del> 1. On each of your nodes, install the Docker for your Linux distribution as per [Install Docker Engine](https://docs.docker.com/engine/install/#server). You can find the latest validated version of Docker in this [dependencies](https://git.k8s.io/kubernetes/build/dependencies.yaml) file. </del> <ins> 1. On each of your nodes, install the Docker for your Linux distribution as per [Install Docker Engine](https://docs.docker.com/engine/install/#server). You can find the latest validated version of Docker in this [dependencies](https://git.k8s.io/kubernetes/build/dependencies.yaml) file. </ins> --> 1. 在每个节点上，根据[安装 Docker 引擎](https://docs.docker.com/engine/install/#server) 为你的 Linux 发行版安装 Docker。"}
{"_id":"q-en-website-192092393a6877573c512db2382361ae58776b93bfeb174b5cd80c73d1980a55","text":"| strategic-merge-patch | The new endpoints support PATCH with `Content-Type: application/strategic-merge-patch+json`. Useful for updating objects that may be modified both locally, and by the server. For more information, see [\"Update API Objects in Place Using kubectl patch\"](/docs/tasks/manage-kubernetes-objects/update-api-object-kubectl-patch/) | No | Yes | | Protocol Buffers | The new resource supports clients that want to use Protocol Buffers | No | Yes | | OpenAPI Schema | Is there an OpenAPI (swagger) schema for the types that can be dynamically fetched from the server? Is the user protected from misspelling field names by ensuring only allowed fields are set? Are types enforced (in other words, don't put an `int` in a `string` field?) | Yes, based on the [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation) schema (GA in 1.16). | Yes | <ins> | Instance Name | Does this extension mechanism impose any constraints on the names of objects whose kind/resource is defined this way? | Yes, such an object's name must be a valid DNS subdomain name. | No | </ins> ### Common Features"}
{"_id":"q-en-website-194c2e4035ee5a3cfccfce9da5238683c87e77bf323c5d9108440691cdb90f2c","text":"### Volume snapshot <del> If etcd is running on a storage volume that supports backup, such as Amazon Elastic Block Store, back up etcd data by taking a snapshot of the storage volume. </del> <ins> If etcd is running on a storage volume that supports backup, such as Amazon Elastic Block Store, back up etcd data by taking a snapshot of the storage volume. </ins> ## Scaling up etcd clusters <del> Scaling up etcd clusters increases availability by trading off performance. Scaling does not increase cluster performance nor capability. A general rule is not to scale up or down etcd clusters. Do not configure any auto scaling groups for etcd clusters. It is highly recommended to always run a static five-member etcd cluster for production Kubernetes clusters at any officially supported scale. </del> <ins> Scaling up etcd clusters increases availability by trading off performance. Scaling does not increase cluster performance nor capability. A general rule is not to scale up or down etcd clusters. Do not configure any auto scaling groups for etcd clusters. It is highly recommended to always run a static five-member etcd cluster for production Kubernetes clusters at any officially supported scale. </ins> <del> A reasonable scaling is to upgrade a three-member cluster to a five-member one, when more reliability is desired. See [etcd Reconfiguration Documentation](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/runtime-configuration.md#remove-a-member) for information on how to add members into an existing cluster. </del> <ins> A reasonable scaling is to upgrade a three-member cluster to a five-member one, when more reliability is desired. See [etcd reconfiguration documentation](https://etcd.io/docs/current/op-guide/runtime-configuration/#remove-a-member) for information on how to add members into an existing cluster. </ins> ## Restoring an etcd cluster <del> etcd supports restoring from snapshots that are taken from an etcd process of the [major.minor](http://semver.org/) version. Restoring a version from a different patch version of etcd also is supported. A restore operation is employed to recover the data of a failed cluster. Before starting the restore operation, a snapshot file must be present. It can either be a snapshot file from a previous backup operation, or from a remaining [data directory](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/configuration.md#--data-dir). For more information and examples on restoring a cluster from a snapshot file, see [etcd disaster recovery documentation](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/recovery.md#restoring-a-cluster). If the access URLs of the restored cluster is changed from the previous cluster, the Kubernetes API server must be reconfigured accordingly. In this case, restart Kubernetes API server with the flag `--etcd-servers=$NEW_ETCD_CLUSTER` instead of the flag `--etcd-servers=$OLD_ETCD_CLUSTER`. Replace `$NEW_ETCD_CLUSTER` and `$OLD_ETCD_CLUSTER` with the respective IP addresses. If a load balancer is used in front of an etcd cluster, you might need to update the load balancer instead. If the majority of etcd members have permanently failed, the etcd cluster is considered failed. In this scenario, Kubernetes cannot make any changes to its current state. Although the scheduled pods might continue to run, no new pods can be scheduled. In such cases, recover the etcd cluster and potentially reconfigure Kubernetes API server to fix the issue. </del> <ins> etcd supports restoring from snapshots that are taken from an etcd process of the [major.minor](http://semver.org/) version. Restoring a version from a different patch version of etcd also is supported. A restore operation is employed to recover the data of a failed cluster. Before starting the restore operation, a snapshot file must be present. It can either be a snapshot file from a previous backup operation, or from a remaining [data directory]( https://etcd.io/docs/current/op-guide/configuration/#--data-dir). For more information and examples on restoring a cluster from a snapshot file, see [etcd disaster recovery documentation](https://etcd.io/docs/current/op-guide/recovery/#restoring-a-cluster). If the access URLs of the restored cluster is changed from the previous cluster, the Kubernetes API server must be reconfigured accordingly. In this case, restart Kubernetes API servers with the flag `--etcd-servers=$NEW_ETCD_CLUSTER` instead of the flag `--etcd-servers=$OLD_ETCD_CLUSTER`. Replace `$NEW_ETCD_CLUSTER` and `$OLD_ETCD_CLUSTER` with the respective IP addresses. If a load balancer is used in front of an etcd cluster, you might need to update the load balancer instead. If the majority of etcd members have permanently failed, the etcd cluster is considered failed. In this scenario, Kubernetes cannot make any changes to its current state. Although the scheduled pods might continue to run, no new pods can be scheduled. In such cases, recover the etcd cluster and potentially reconfigure Kubernetes API servers to fix the issue. </ins> {{< note >}} <del> If any API servers are running in your cluster, you should not attempt to restore instances of etcd. Instead, follow these steps to restore etcd: </del> <ins> If any API servers are running in your cluster, you should not attempt to restore instances of etcd. Instead, follow these steps to restore etcd: </ins> <del> - stop *all* kube-apiserver instances </del> <ins> - stop *all* API server instances </ins> - restore state in all etcd instances <del> - restart all kube-apiserver instances </del> <ins> - restart all API server instances </ins> <del> We also recommend restarting any components (e.g. kube-scheduler, kube-controller-manager, kubelet) to ensure that they don't rely on some stale data. Note that in practice, the restore takes a bit of time. During the restoration, critical components will lose leader lock and restart themselves. </del> <ins> We also recommend restarting any components (e.g. `kube-scheduler`, `kube-controller-manager`, `kubelet`) to ensure that they don't rely on some stale data. Note that in practice, the restore takes a bit of time.  During the restoration, critical components will lose leader lock and restart themselves. </ins> {{< /note >}} <del> ## Upgrading and rolling back etcd clusters As of Kubernetes v1.13.0, etcd2 is no longer supported as a storage backend for new or existing Kubernetes clusters. The timeline for Kubernetes support for etcd2 and etcd3 is as follows: - Kubernetes v1.0: etcd2 only - Kubernetes v1.5.1: etcd3 support added, new clusters still default to etcd2 - Kubernetes v1.6.0: new clusters created with `kube-up.sh` default to etcd3, and `kube-apiserver` defaults to etcd3 - Kubernetes v1.9.0: deprecation of etcd2 storage backend announced - Kubernetes v1.13.0: etcd2 storage backend removed, `kube-apiserver` will refuse to start with `--storage-backend=etcd2`, with the message `etcd2 is no longer a supported storage backend` Before upgrading a v1.12.x kube-apiserver using `--storage-backend=etcd2` to v1.13.x, etcd v2 data must be migrated to the v3 storage backend and kube-apiserver invocations must be changed to use `--storage-backend=etcd3`. The process for migrating from etcd2 to etcd3 is highly dependent on how the etcd cluster was deployed and configured, as well as how the Kubernetes cluster was deployed and configured. We recommend that you consult your cluster provider's documentation to see if there is a predefined solution. If your cluster was created via `kube-up.sh` and is still using etcd2 as its storage backend, please consult the [Kubernetes v1.12 etcd cluster upgrade docs](https://v1-12.docs.kubernetes.io/docs/tasks/administer-cluster/configure-upgrade-etcd/#upgrading-and-rolling-back-etcd-clusters) ## Known issue: etcd client balancer with secure endpoints The etcd v3 client, released in etcd v3.3.13 or earlier, has a [critical bug](https://github.com/kubernetes/kubernetes/issues/72102) which affects the kube-apiserver and HA deployments. The etcd client balancer failover does not properly work against secure endpoints. As a result, etcd servers may fail or disconnect briefly from the kube-apiserver. This affects kube-apiserver HA deployments. The fix was made in [etcd v3.4](https://github.com/etcd-io/etcd/pull/10911) (and backported to v3.3.14 or later): the new client now creates its own credential bundle to correctly set authority target in dial function. Because the fix requires gRPC dependency upgrade (to v1.23.0), downstream Kubernetes [did not backport etcd upgrades](https://github.com/kubernetes/kubernetes/issues/72102#issuecomment-526645978). Which means the [etcd fix in kube-apiserver](https://github.com/etcd-io/etcd/pull/10911/commits/db61ee106ca9363ba3f188ecf27d1a8843da33ab) is only available from Kubernetes 1.16. To urgently fix this bug for Kubernetes 1.15 or earlier, build a custom kube-apiserver. You can make local changes to [`vendor/google.golang.org/grpc/credentials/credentials.go`](https://github.com/kubernetes/kubernetes/blob/7b85be021cd2943167cd3d6b7020f44735d9d90b/vendor/google.golang.org/grpc/credentials/credentials.go#L135) with [etcd@db61ee106](https://github.com/etcd-io/etcd/pull/10911/commits/db61ee106ca9363ba3f188ecf27d1a8843da33ab). See [\"kube-apiserver 1.13.x refuses to work when first etcd-server is not available\"](https://github.com/kubernetes/kubernetes/issues/72102). </del>"}
{"_id":"q-en-website-197b1e8bd8f87194941b7c4efc822d45dd3d52e532f959d6e8079839a2f403bf","text":"* [vsphereVolume](/docs/concepts/storage/volumes/#vspherevolume) ##### FlexVolume Plugins <del> Code associated with [FlexVolume](/docs/concepts/storage/volumes/#flexVolume) plugins ship as out-of-tree scripts or binaries that need to be deployed directly on the host. FlexVolume plugins handle attaching/detaching of volumes to/from a Kubernetes node and mounting/dismounting a volume to/from individual containers in a pod. Provisioning/De-provisioning of persistent volumes associated with FlexVolume plugins may be handled through an external provisioner that is typically separate from the FlexVolume plugins. The following FlexVolume [plugins](https://github.com/Microsoft/K8s-Storage-Plugins/tree/master/flexvolume/windows), deployed as powershell scripts on the host, support Windows nodes: </del> <ins> [FlexVolume](/docs/concepts/storage/volumes/#flexVolume)プラグインに関連付けられたコードは、ホストに直接デプロイする必要があるout-of-treeのスクリプトまたはバイナリとして出荷されます。FlexVolumeプラグインは、Kubernetesノードとの間のボリュームのアタッチ/デタッチ、およびPod内の個々のコンテナとの間のボリュームのマウント/マウント解除を処理します。FlexVolumeプラグインに関連付けられた永続ボリュームのプロビジョニング/プロビジョニング解除は、通常FlexVolumeプラグインとは別の外部プロビジョニング担当者を通じて処理できます。次のFlexVolume[プラグイン](https://github.com/Microsoft/K8s-Storage-Plugins/tree/master/flexvolume/windows)は、Powershellスクリプトとしてホストにデプロイされ、Windowsノードをサポートします。: </ins> * [SMB](https://github.com/microsoft/K8s-Storage-Plugins/tree/master/flexvolume/windows/plugins/microsoft.com~smb.cmd) * [iSCSI](https://github.com/microsoft/K8s-Storage-Plugins/tree/master/flexvolume/windows/plugins/microsoft.com~iscsi.cmd) <del> ##### CSI Plugins </del> <ins> ##### CSIプラグイン </ins> {{< feature-state for_k8s_version=\"v1.16\" state=\"alpha\" >}} <del> Code associated with {{< glossary_tooltip text=\"CSI\" term_id=\"csi\" >}} plugins ship as out-of-tree scripts and binaries that are typically distributed as container images and deployed using standard Kubernetes constructs like DaemonSets and StatefulSets. CSI plugins handle a wide range of volume management actions in Kubernetes: provisioning/de-provisioning/resizing of volumes, attaching/detaching of volumes to/from a Kubernetes node and mounting/dismounting a volume to/from individual containers in a pod, backup/restore of persistent data using snapshots and cloning. CSI plugins typically consist of node plugins (that run on each node as a DaemonSet) and controller plugins. </del> <ins> {{< glossary_tooltip text=\"CSI\" term_id=\"csi\" >}}プラグインに関連付けられたコードは、通常、コンテナイメージとして配布され、DaemonSetsやStatefulSetsなどの標準のKubernetesコンポーネントを使用してデプロイされるout-of-treeのスクリプトおよびバイナリとして出荷されます。CSIプラグインは、Kubernetesの幅広いボリューム管理アクションを処理します:ボリュームのプロビジョニング/プロビジョニング解除/サイズ変更、Kubernetesノードへのボリュームのアタッチ/ボリュームからのデタッチ、Pod内の個々のコンテナへのボリュームのマウント/マウント解除、バックアップ/スナップショットとクローニングを使用した永続データのバックアップ/リストア。CSIプラグインは通常、ノードプラグイン（各ノードでDaemonSetとして実行される）とコントローラープラグインで構成されます。 </ins> <del> CSI node plugins (especially those associated with persistent volumes exposed as either block devices or over a shared file-system) need to perform various privileged operations like scanning of disk devices, mounting of file systems, etc. These operations differ for each host operating system. For Linux worker nodes, containerized CSI node plugins are typically deployed as privileged containers. For Windows worker nodes, privileged operations for containerized CSI node plugins is supported using [csi-proxy](https://github.com/kubernetes-csi/csi-proxy), a community-managed, stand-alone binary that needs to be pre-installed on each Windows node. Please refer to the deployment guide of the CSI plugin you wish to deploy for further details. </del> <ins> CSIノードプラグイン（特に、ブロックデバイスまたは共有ファイルシステムとして公開された永続ボリュームに関連付けられているプラ​​グイン）は、ディスクデバイスのスキャン、ファイルシステムのマウントなど、さまざまな特権操作を実行する必要があります。これらの操作は、ホストオペレーティングシステムごとに異なります。Linuxワーカーノードの場合、コンテナ化されたCSIノードプラグインは通常、特権コンテナとしてデプロイされます。Windowsワーカーノードの場合、コンテナ化されたCSIノードプラグインの特権操作は、[csi-proxy](https://github.com/kubernetes-csi/csi-proxy)を使用してサポートされます。各Windowsノードにプリインストールされている。詳細については、展開するCSIプラグインの展開ガイドを参照してください。 </ins> <del> #### Networking </del> <ins> #### ネットワーキング </ins> <del> Networking for Windows containers is exposed through [CNI plugins](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/). Windows containers function similarly to virtual machines in regards to networking. Each container has a virtual network adapter (vNIC) which is connected to a Hyper-V virtual switch (vSwitch). The Host Networking Service (HNS) and the Host Compute Service (HCS) work together to create containers and attach container vNICs to networks. HCS is responsible for the management of containers whereas HNS is responsible for the management of networking resources such as: </del> <ins> Windowsコンテナのネットワークは、[CNIプラグイン](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/)を通じて公開されます。Windowsコンテナは、ネットワークに関して仮想マシンと同様に機能します。各コンテナには、Hyper-V仮想スイッチ（vSwitch）に接続されている仮想ネットワークアダプター（vNIC）があります。Host Network Service（HNS）とHost Compute Service（HCS）は連携してコンテナを作成し、コンテナvNICをネットワークに接続します。HCSはコンテナの管理を担当するのに対し、HNSは次のようなネットワークリソースの管理を担当します。: </ins> <del> * Virtual networks (including creation of vSwitches) * Endpoints / vNICs * Namespaces * Policies (Packet encapsulations, Load-balancing rules, ACLs, NAT'ing rules, etc.) </del> <ins> * 仮想ネットワーク（vSwitchの作成を含む） * エンドポイント/vNIC * ネームスペース * ポリシー（パケットのカプセル化、負荷分散ルール、ACL、NATルールなど） </ins> <del> The following service spec types are supported: </del> <ins> 次のServiceタイプがサポートされています。: </ins> * NodePort * ClusterIP * LoadBalancer * ExternalName <del> Windows supports five different networking drivers/modes: L2bridge, L2tunnel, Overlay, Transparent, and NAT. In a heterogeneous cluster with Windows and Linux worker nodes, you need to select a networking solution that is compatible on both Windows and Linux. The following out-of-tree plugins are supported on Windows, with recommendations on when to use each CNI: </del> <ins> Windowsは、L2bridge、L2tunnel、Overlay、Transparent、NATの5つの異なるネットワークドライバー/モードをサポートしています。WindowsとLinuxのワーカーノードを持つ異種クラスターでは、WindowsとLinuxの両方で互換性のあるネットワークソリューションを選択する必要があります。以下のツリー外プラグインがWindowsでサポートされており、各CNIをいつ使用するかに関する推奨事項があります。: </ins> <del> | Network Driver | Description | Container Packet Modifications | Network Plugins | Network Plugin Characteristics | </del> <ins> | ネットワークドライバー | 説明 | コンテナパケットの変更 | ネットワークプラグイン | ネットワークプラグインの特性 | </ins> | -------------- | ----------- | ------------------------------ | --------------- | ------------------------------ | <del> | L2bridge       | Containers are attached to an external vSwitch. Containers are attached to the underlay network, although the physical network doesn't need to learn the container MACs because they are rewritten on ingress/egress. Inter-container traffic is bridged inside the container host. | MAC is rewritten to host MAC, IP remains the same. | [win-bridge](https://github.com/containernetworking/plugins/tree/master/plugins/main/windows/win-bridge), [Azure-CNI](https://github.com/Azure/azure-container-networking/blob/master/docs/cni.md), Flannel host-gateway uses win-bridge | win-bridge uses L2bridge network mode, connects containers to the underlay of hosts, offering best performance. Requires user-defined routes (UDR) for inter-node connectivity. | | L2Tunnel | This is a special case of l2bridge, but only used on Azure. All packets are sent to the virtualization host where SDN policy is applied. | MAC rewritten, IP visible on the underlay network | [Azure-CNI](https://github.com/Azure/azure-container-networking/blob/master/docs/cni.md) | Azure-CNI allows integration of containers with Azure vNET, and allows them to leverage the set of capabilities that [Azure Virtual Network provides](https://azure.microsoft.com/en-us/services/virtual-network/). For example, securely connect to Azure services or use Azure NSGs. See [azure-cni for some examples](https://docs.microsoft.com/en-us/azure/aks/concepts-network#azure-cni-advanced-networking) | | Overlay (Overlay networking for Windows in Kubernetes is in *alpha* stage) | Containers are given a vNIC connected to an external vSwitch. Each overlay network gets its own IP subnet, defined by a custom IP prefix.The overlay network driver uses VXLAN encapsulation. | Encapsulated with an outer header. | [Win-overlay](https://github.com/containernetworking/plugins/tree/master/plugins/main/windows/win-overlay), Flannel VXLAN (uses win-overlay) | win-overlay should be used when virtual container networks are desired to be isolated from underlay of hosts (e.g. for security reasons). Allows for IPs to be re-used for different overlay networks (which have different VNID tags)  if you are restricted on IPs in your datacenter. This option requires [KB4489899](https://support.microsoft.com/help/4489899) on Windows Server 2019. | | Transparent (special use case for [ovn-kubernetes](https://github.com/openvswitch/ovn-kubernetes)) | Requires an external vSwitch. Containers are attached to an external vSwitch which enables intra-pod communication via logical networks (logical switches and routers). | Packet is encapsulated either via [GENEVE](https://datatracker.ietf.org/doc/draft-gross-geneve/) or [STT](https://datatracker.ietf.org/doc/draft-davie-stt/) tunneling to reach pods which are not on the same host.  <br/> Packets are forwarded or dropped via the tunnel metadata information supplied by the ovn network controller. <br/> NAT is done for north-south communication. | [ovn-kubernetes](https://github.com/openvswitch/ovn-kubernetes) | [Deploy via ansible](https://github.com/openvswitch/ovn-kubernetes/tree/master/contrib). Distributed ACLs can be applied via Kubernetes policies. IPAM support. Load-balancing can be achieved without kube-proxy. NATing is done without using iptables/netsh. | | NAT (*not used in Kubernetes*) | Containers are given a vNIC connected to an internal vSwitch. DNS/DHCP is provided using an internal component called [WinNAT](https://blogs.technet.microsoft.com/virtualization/2016/05/25/windows-nat-winnat-capabilities-and-limitations/) | MAC and IP is rewritten to host MAC/IP. | [nat](https://github.com/Microsoft/windows-container-networking/tree/master/plugins/nat) | Included here for completeness | </del> <ins> | L2bridge       | コンテナは外部のvSwitchに接続されます。コンテナはアンダーレイネットワークに接続されますが、物理ネットワークはコンテナのMACを上り/下りで書き換えるため、MACを学習する必要はありません。コンテナ間トラフィックは、コンテナホスト内でブリッジされます。 | MACはホストのMACに書き換えられ、IPは変わりません。| [win-bridge](https://github.com/containernetworking/plugins/tree/master/plugins/main/windows/win-bridge)、[Azure-CNI](https://github.com/Azure/azure-container-networking/blob/master/docs/cni.md)、Flannelホストゲートウェイは、win-bridgeを使用します。 | win-bridgeはL2bridgeネットワークモードを使用して、コンテナをホストのアンダーレイに接続して、最高のパフォーマンスを提供します。ノード間接続にはユーザー定義ルート（UDR）が必要です。 | | L2Tunnel | これはl2bridgeの特殊なケースですが、Azureでのみ使用されます。すべてのパケットは、SDNポリシーが適用されている仮想化ホストに送信されます。| MACが書き換えられ、IPがアンダーレイネットワークで表示されます。 | [Azure-CNI](https://github.com/Azure/azure-container-networking/blob/master/docs/cni.md) | Azure-CNIを使用すると、コンテナをAzure vNETと統合し、[Azure Virtual Networkが提供](https://azure.microsoft.com/en-us/services/virtual-network/)する一連の機能を活用できます。たとえば、Azureサービスに安全に接続するか、Azure NSGを使用します。[azure-cniのいくつかの例](https://docs.microsoft.com/en-us/azure/aks/concepts-network#azure-cni-advanced-networking)を参照してください。| | オーバーレイ（KubernetesのWindows用のオーバーレイネットワークは *アルファ* 段階です）| コンテナには、外部のvSwitchに接続されたvNICが付与されます。各オーバーレイネットワークは、カスタムIPプレフィックスで定義された独自のIPサブネットを取得します。オーバーレイネットワークドライバーは、VXLANを使用してカプセル化します。 | 外部ヘッダーでカプセル化されます。 | [Win-overlay](https://github.com/containernetworking/plugins/tree/master/plugins/main/windows/win-overlay)、Flannel VXLAN (win-overlayを使用) | win-overlayは、仮想コンテナーネットワークをホストのアンダーレイから分離する必要がある場合に使用する必要があります（セキュリティ上の理由など）。データセンター内のIPが制限されている場合に、（異なるVNIDタグを持つ）異なるオーバーレイネットワークでIPを再利用できるようにします。このオプションには、Windows Server 2019で[KB4489899](https://support.microsoft.com/help/4489899)が必要です。| | 透過的（[ovn-kubernetes](https://github.com/openvswitch/ovn-kubernetes)の特別な使用例） | 外部のvSwitchが必要です。コンテナは外部のvSwitchに接続され、論理ネットワーク（論理スイッチおよびルーター）を介したPod内通信を可能にします。 | パケットは、[GENEVE](https://datatracker.ietf.org/doc/draft-gross-geneve/)または[STT](https://datatracker.ietf.org/doc/draft-davie-stt/)トンネリングを介してカプセル化され、同じホスト上にないポッドに到達します。パケットは、ovnネットワークコントローラーによって提供されるトンネルメタデータ情報を介して転送またはドロップされます。NATは南北通信のために行われます。 | [ovn-kubernetes](https://github.com/openvswitch/ovn-kubernetes) | [ansible経由でデプロイ](https://github.com/openvswitch/ovn-kubernetes/tree/master/contrib)します。分散ACLは、Kubernetesポリシーを介して適用できます。 IPAMをサポートします。負荷分散は、kube-proxyなしで実現できます。 NATは、ip​​tables/netshを使用せずに行われます。 | | NAT（*Kubernetesでは使用されません*） | コンテナには、内部のvSwitchに接続されたvNICが付与されます。DNS/DHCPは、[WinNAT](https://blogs.technet.microsoft.com/virtualization/2016/05/25/windows-nat-winnat-capabilities-and-limitations/)と呼ばれる内部コンポーネントを使用して提供されます。 | MACおよびIPはホストMAC/IPに書き換えられます。 | [nat](https://github.com/Microsoft/windows-container-networking/tree/master/plugins/nat) | 完全を期すためにここに含まれています。 | </ins> <del> As outlined above, the [Flannel](https://github.com/coreos/flannel) CNI [meta plugin](https://github.com/containernetworking/plugins/tree/master/plugins/meta/flannel) is also supported on [Windows](https://github.com/containernetworking/plugins/tree/master/plugins/meta/flannel#windows-support-experimental) via the [VXLAN network backend](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan) (**alpha support** ; delegates to win-overlay) and [host-gateway network backend](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#host-gw) (stable support; delegates to win-bridge). This plugin supports delegating to one of the reference CNI plugins (win-overlay, win-bridge), to work in conjunction with Flannel daemon on Windows (Flanneld) for automatic node subnet lease assignment and HNS network creation. This plugin reads in its own configuration file (cni.conf), and aggregates it with the environment variables from the FlannelD generated subnet.env file. It then delegates to one of the reference CNI plugins for network plumbing, and sends the correct configuration containing the node-assigned subnet to the IPAM plugin (e.g. host-local). </del> <ins> 上で概説したように、[Flannel](https://github.com/coreos/flannel) CNI[メタプラグイン](https://github.com/containernetworking/plugins/tree/master/plugins/meta/flannel)は、[VXLANネットワークバックエンド](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan)（**アルファサポート**、win-overlayへのデリゲート）および[ホストゲートウェイネットワークバックエンド](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#host-gw)（安定したサポート、win-bridgeへのデリゲート）を介して[Windows](https://github.com/containernetworking/plugins/tree/master/plugins/meta/flannel#windows-support-experimental)でもサポートされます。このプラグインは、参照CNIプラグイン（win-overlay、win-bridge）の1つへの委任をサポートし、WindowsのFlannelデーモン（Flanneld）と連携して、ノードのサブネットリースの自動割り当てとHNSネットワークの作成を行います。このプラグインは、独自の構成ファイル（cni.conf）を読み取り、FlannelDで生成されたsubnet.envファイルからの環境変数と統合します。次に、ネットワークプラミング用の参照CNIプラグインの1つに委任し、ノード割り当てサブネットを含む正しい構成をIPAMプラグイン（ホストローカルなど）に送信します。 </ins> <del> For the node, pod, and service objects, the following network flows are supported for TCP/UDP traffic: </del> <ins> Node、Pod、およびServiceオブジェクトの場合、TCP/UDPトラフィックに対して次のネットワークフローがサポートされます。: </ins> * Pod -> Pod (IP) * Pod -> Pod (Name) * Pod -> Service (Cluster IP) <del> * Pod -> Service (PQDN, but only if there are no \".\") </del> <ins> * Pod -> Service (PQDN、ただし、「.」がない場合のみ) </ins> * Pod -> Service (FQDN) * Pod -> External (IP) * Pod -> External (DNS) * Node -> Pod * Pod -> Node <del> The following IPAM options are supported on Windows: </del> <ins> Windowsでは、次のIPAMオプションがサポートされています。 </ins> <del> * [Host-local](https://github.com/containernetworking/plugins/tree/master/plugins/ipam/host-local) * HNS IPAM (Inbox platform IPAM, this is a fallback when no IPAM is set) * [Azure-vnet-ipam](https://github.com/Azure/azure-container-networking/blob/master/docs/ipam.md) (for azure-cni only) </del> <ins> * [ホストローカル](https://github.com/containernetworking/plugins/tree/master/plugins/ipam/host-local) * HNS IPAM (受信トレイプラットフォームIPAM、これはIPAMが設定されていない場合のフォールバック) * [Azure-vnet-ipam](https://github.com/Azure/azure-container-networking/blob/master/docs/ipam.md)（azure-cniのみ） </ins> <del> ### Limitations </del> <ins> ### 制限 </ins> <del> #### Control Plane </del> <ins> #### コントロールプレーン </ins> <del> Windows is only supported as a worker node in the Kubernetes architecture and component matrix. This means that a Kubernetes cluster must always include Linux master nodes, zero or more Linux worker nodes, and zero or more Windows worker nodes. </del> <ins> Windowsは、Kubernetesアーキテクチャとコンポーネントマトリックスのワーカーノードとしてのみサポートされています。つまり、Kubernetesクラスタには常にLinuxマスターノード、0以上のLinuxワーカーノード、0以上のWindowsワーカーノードが含まれている必要があります。 </ins> <del> #### Compute </del> <ins> #### コンピュート </ins> <del> ##### Resource management and process isolation </del> <ins> ##### リソース管理とプロセス分離 </ins> <del> Linux cgroups are used as a pod boundary for resource controls in Linux. Containers are created within that boundary for network, process and file system isolation. The cgroups APIs can be used to gather cpu/io/memory stats. In contrast, Windows uses a Job object per container with a system namespace filter to contain all processes in a container and provide logical isolation from the host. There is no way to run a Windows container without the namespace filtering in place. This means that system privileges cannot be asserted in the context of the host, and thus privileged containers are not available on Windows. Containers cannot assume an identity from the host because the Security Account Manager (SAM) is separate. </del> <ins> Linux cgroupsは、Linuxのリソースを制御するPodの境界として使用されます。コンテナは、ネットワーク、プロセス、およびファイルシステムを分離するのために、その境界内に作成されます。cgroups APIを使用して、cpu/io/memoryの統計を収集できます。対照的に、Windowsはシステムネームスペースフィルターを備えたコンテナごとのジョブオブジェクトを使用して、コンテナ内のすべてのプロセスを格納し、ホストからの論理的な分離を提供します。ネームスペースフィルタリングを行わずにWindowsコンテナを実行する方法はありません。これは、ホストの環境ではシステム特権を主張できないため、Windowsでは特権コンテナを使用できないことを意味します。セキュリティアカウントマネージャー（SAM）が独立しているため、コンテナはホストからIDを引き受けることができません。 </ins> <del> ##### Operating System Restrictions </del> <ins> ##### オペレーティングシステムの制限 </ins> <del> Windows has strict compatibility rules, where the host OS version must match the container base image OS version. Only Windows containers with a container operating system of Windows Server 2019 are supported. Hyper-V isolation of containers, enabling some backward compatibility of Windows container image versions, is planned for a future release. </del> <ins> Windowsには厳密な互換性ルールがあり、ホストOSのバージョンとコンテナのベースイメージOSのバージョンは、一致する必要があります。Windows Server 2019のコンテナオペレーティングシステムを備えたWindowsコンテナのみがサポートされます。Hyper-V分離のコンテナは、Windowsコンテナのイメージバージョンに下位互換性を持たせることは、将来のリリースで計画されています。 </ins> <del> ##### Feature Restrictions </del> <ins> ##### 機能制限 </ins> <del> * TerminationGracePeriod: not implemented * Single file mapping: to be implemented with CRI-ContainerD * Termination message: to be implemented with CRI-ContainerD * Privileged Containers: not currently supported in Windows containers * HugePages: not currently supported in Windows containers * The existing node problem detector is Linux-only and requires privileged containers. In general, we don't expect this to be used on Windows because privileged containers are not supported * Not all features of shared namespaces are supported (see API section for more details) </del> <ins> * TerminationGracePeriod：実装されていません * 単一ファイルのマッピング：CRI-ContainerDで実装されます * 終了メッセージ：CRI-ContainerDで実装されます * 特権コンテナ：現在Windowsコンテナではサポートされていません * HugePages：現在Windowsコンテナではサポートされていません * 既存のノード問題を検出する機能はLinux専用であり、特権コンテナが必要です。一般的に、特権コンテナはサポートされていないため、これがWindowsで使用されることは想定していません。 * ネームスペース共有については、すべての機能がサポートされているわけではありません（詳細については、APIセクションを参照してください） </ins> <del> ##### Memory Reservations and Handling </del> <ins> ##### メモリ予約と処理 </ins> <del> Windows does not have an out-of-memory process killer as Linux does. Windows always treats all user-mode memory allocations as virtual, and pagefiles are mandatory. The net effect is that Windows won't reach out of memory conditions the same way Linux does, and processes page to disk instead of being subject to out of memory (OOM) termination. If memory is over-provisioned and all physical memory is exhausted, then paging can slow down performance. </del> <ins> Windowsには、Linuxのようなメモリ不足のプロセスキラーはありません。Windowsは常に全ユーザーモードのメモリ割り当てを仮想として扱い、ページファイルは必須です。正味の効果は、WindowsはLinuxのようなメモリ不足の状態にはならず、メモリ不足（OOM）終了の影響を受ける代わりにページをディスクに処理します。メモリが過剰にプロビジョニングされ、物理メモリのすべてが使い果たされると、ページングによってパフォーマンスが低下する可能性があります。 </ins> <del> Keeping memory usage within reasonable bounds is possible with a two-step process. First, use the kubelet parameters `--kubelet-reserve` and/or `--system-reserve` to account for memory usage on the node (outside of containers). This reduces [NodeAllocatable](/ja/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable)). As you deploy workloads, use resource limits (must set only limits or limits must equal requests) on containers. This also subtracts from NodeAllocatable and prevents the scheduler from adding more pods once a node is full. </del> <ins> 2ステップのプロセスで、メモリ使用量を妥当な範囲内に保つことが可能です。まず、kubeletパラメータ`--kubelet-reserve`や`--system-reserve`を使用して、ノード（コンテナ外）でのメモリ使用量を明確にします。これにより、[NodeAllocatable](/ja/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable))が削減されます。ワークロードをデプロイするときは、コンテナにリソース制限をかけます（制限のみを設定するか、制限が要求と等しくなければなりません）。これにより、NodeAllocatableも差し引かれ、ノードのリソースがフルな状態になるとSchedulerがPodを追加できなくなります。 </ins> <del> A best practice to avoid over-provisioning is to configure the kubelet with a system reserved memory of at least 2GB to account for Windows, Docker, and Kubernetes processes. </del> <ins> 過剰なプロビジョニングを回避するためのベストプラクティスは、Windows、Docker、およびKubernetesのプロセスに対応するために、最低2GBのメモリを予約したシステムでkubeletを構成することです。 </ins> <del> The behavior of the flags behave differently as described below: </del> <ins> フラグの振舞いについては、次のような異なる動作をします。: </ins> <del> * `--kubelet-reserve`, `--system-reserve` , and `--eviction-hard` flags update Node Allocatable * Eviction by using `--enforce-node-allocable` is not implemented * Eviction by using `--eviction-hard` and `--eviction-soft` are not implemented * MemoryPressure Condition is not implemented * There are no OOM eviction actions taken by the kubelet * Kubelet running on the windows node does not have memory restrictions. `--kubelet-reserve` and `--system-reserve` do not set limits on kubelet or processes running on the host. This means kubelet or a process on the host could cause memory resource starvation outside the node-allocatable and scheduler </del> <ins> * `--kubelet-reserve`、`--system-reserve`、および`--eviction-hard`フラグはノードの割り当て可能数を更新します * `--enforce-node-allocable`を使用した排除は実装されていません * `--eviction-hard`および`--eviction-soft`を使用した排除は実装されていません * MemoryPressureの制約は実装されていません * kubeletによって実行されるOOMを排除することはありません * Windowsノードで実行されているKubeletにはメモリ制限がありません。`--kubelet-reserve`と`--system-reserve`は、ホストで実行されているkubeletまたはプロセスに制限を設定しません。これは、ホスト上のkubeletまたはプロセスが、NodeAllocatableとSchedulerの外でメモリリソース不足を引き起こす可能性があることを意味します。 </ins> <del> #### Storage </del> <ins> #### ストレージ </ins> <del> Windows has a layered filesystem driver to mount container layers and create a copy filesystem based on NTFS. All file paths in the container are resolved only within the context of that container. </del> <ins> Windowsには、コンテナレイヤーをマウントして、NTFSに基づいて複製されたファイルシステムを作るためのレイヤー構造のファイルシステムドライバーがあります。コンテナ内のすべてのファイルパスは、そのコンテナの環境内だけで決められます。 </ins> <del> * Volume mounts can only target a directory in the container, and not an individual file * Volume mounts cannot project files or directories back to the host filesystem * Read-only filesystems are not supported because write access is always required for the Windows registry and SAM database. However, read-only volumes are supported * Volume user-masks and permissions are not available. Because the SAM is not shared between the host & container, there's no mapping between them. All permissions are resolved within the context of the container </del> <ins> * ボリュームマウントは、コンテナ内のディレクトリのみを対象にすることができ、個別のファイルは対象にできません * ボリュームマウントは、ファイルまたはディレクトリをホストファイルシステムに投影することはできません * WindowsレジストリとSAMデータベースには常に書き込みアクセスが必要であるため、読み取り専用ファイルシステムはサポートされていません。ただし、読み取り専用ボリュームはサポートされています * ボリュームのユーザーマスクと権限は使用できません。SAMはホストとコンテナ間で共有されないため、それらの間のマッピングはありません。すべての権限はコンテナの環境内で決められます </ins> <del> As a result, the following storage functionality is not supported on Windows nodes </del> <ins> その結果、次のストレージ機能はWindowsノードではサポートされません。 </ins> <del> * Volume subpath mounts. Only the entire volume can be mounted in a Windows container. * Subpath volume mounting for Secrets * Host mount projection * DefaultMode (due to UID/GID dependency) * Read-only root filesystem. Mapped volumes still support readOnly * Block device mapping * Memory as the storage medium * File system features like uui/guid, per-user Linux filesystem permissions * NFS based storage/volume support * Expanding the mounted volume (resizefs) </del> <ins> * ボリュームサブパスのマウント。Windowsコンテナにマウントできるのはボリューム全体だけです。 * シークレットのサブパスボリュームのマウント * ホストマウントプロジェクション * DefaultMode（UID/GID依存関係による） * 読み取り専用のルートファイルシステム。マップされたボリュームは引き続き読み取り専用をサポートします * ブロックデバイスマッピング * 記憶媒体としてのメモリ * uui/guid、ユーザーごとのLinuxファイルシステム権限などのファイルシステム機能 * NFSベースのストレージ/ボリュームのサポート * マウントされたボリュームの拡張（resizefs） </ins> <del> #### Networking </del> <ins> #### ネットワーキング </ins> <del> Windows Container Networking differs in some important ways from Linux networking. The [Microsoft documentation for Windows Container Networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture) contains additional details and background. </del> <ins> Windowsコンテナネットワーキングは、Linuxネットワーキングとはいくつかの重要な実装方法の違いがあります。[Microsoft documentation for Windows Container Networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture)には、追加の詳細と背景があります。 </ins> <del> The Windows host networking networking service and virtual switch implement namespacing and can create virtual NICs as needed for a pod or container. However, many configurations such as DNS, routes, and metrics are stored in the Windows registry database rather than /etc/... files as they are on Linux. The Windows registry for the container is separate from that of the host, so concepts like mapping /etc/resolv.conf from the host into a container don't have the same effect they would on Linux. These must be configured using Windows APIs run in the context of that container. Therefore CNI implementations need to call the HNS instead of relying on file mappings to pass network details into the pod or container. </del> <ins> Windowsホストネットワーキングサービスと仮想スイッチはネームスペースを実装して、Podまたはコンテナの必要に応じて仮想NICを作成できます。ただし、DNS、ルート、メトリックなどの多くの構成は、Linuxのような/etc/...ファイルではなく、Windowsレジストリデータベースに保存されます。コンテナのWindowsレジストリはホストのレジストリとは別であるため、ホストからコンテナへの/etc/resolv.confのマッピングなどの概念は、Linuxの場合と同じ効果をもたらしません。これらは、そのコンテナの環境で実行されるWindows APIを使用して構成する必要があります。したがって、CNIの実装は、ファイルマッピングに依存する代わりにHNSを呼び出して、ネットワークの詳細をPodまたはコンテナに渡す必要があります。 </ins> <del> The following networking functionality is not supported on Windows nodes </del> <ins> 次のネットワーク機能はWindowsノードではサポートされていません </ins> <del> * Host networking mode is not available for Windows pods * Local NodePort access from the node itself fails (works for other nodes or external clients) * Accessing service VIPs from nodes will be available with a future release of Windows Server * Overlay networking support in kube-proxy is an alpha release. In addition, it requires [KB4482887](https://support.microsoft.com/en-us/help/4482887/windows-10-update-kb4482887) to be installed on Windows Server 2019 * Local Traffic Policy and DSR mode * Windows containers connected to l2bridge, l2tunnel, or overlay networks do not support communicating over the IPv6 stack. There is outstanding Windows platform work required to enable these network drivers to consume IPv6 addresses and subsequent Kubernetes work in kubelet, kube-proxy, and CNI plugins. * Outbound communication using the ICMP protocol via the win-overlay, win-bridge, and Azure-CNI plugin. Specifically, the Windows data plane ([VFP](https://www.microsoft.com/en-us/research/project/azure-virtual-filtering-platform/)) doesn't support ICMP packet transpositions. This means: * ICMP packets directed to destinations within the same network (e.g. pod to pod communication via ping) work as expected and without any limitations * TCP/UDP packets work as expected and without any limitations * ICMP packets directed to pass through a remote network (e.g. pod to external internet communication via ping) cannot be transposed and thus will not be routed back to their source * Since TCP/UDP packets can still be transposed, one can substitute `ping <destination>` with `curl <destination>` to be able to debug connectivity to the outside world. </del> <ins> * ホストネットワーキングモードはWindows Podでは使用できません * ノード自体からのローカルNodePortアクセスは失敗します（他のノードまたは外部クライアントで機能） * ノードからのService VIPへのアクセスは、Windows Serverの将来のリリースで利用可能になる予定です * kube-proxyのオーバーレイネットワーキングサポートはアルファリリースです。さらに、[KB4482887](https://support.microsoft.com/en-us/help/4482887/windows-10-update-kb4482887)がWindows Server 2019にインストールされている必要があります * ローカルトラフィックポリシーとDSRモード * l2bridge、l2tunnel、またはオーバーレイネットワークに接続されたWindowsコンテナは、IPv6スタックを介した通信をサポートしていません。これらのネットワークドライバーがIPv6アドレスを使用できるようにするために必要な機能として、優れたWindowsプラットフォームの機能があり、それに続いて、kubelet、kube-proxy、およびCNIプラグインといったKubernetesの機能があります。 * win-overlay、win-bridge、およびAzure-CNIプラグインを介したICMPプロトコルを使用したアウトバウンド通信。具体的には、Windowsデータプレーン([VFP](https://www.microsoft.com/en-us/research/project/azure-virtual-filtering-platform/))は、ICMPパケットの置き換えをサポートしていません。これの意味は： * 同じネットワーク内の宛先に向けられたICMPパケット（pingを介したPod間通信など）は期待どおりに機能し、制限はありません * TCP/UDPパケットは期待どおりに機能し、制限はありません * リモートネットワーク（Podからping経由の外部インターネット通信など）を通過するように指示されたICMPパケットは置き換えできないため、ソースにルーティングされません。 * TCP/UDPパケットは引き続き置き換えできるため、`ping <destination>`を`curl <destination>`に置き換えることで、外部への接続をデバッグできます。 </ins> <del> These features were added in Kubernetes v1.15: </del> <ins> これらの機能はKubernetes v1.15で追加されました。 </ins> * `kubectl port-forward` <del> ##### CNI Plugins </del> <ins> ##### CNIプラグイン </ins> <del> * Windows reference network plugins win-bridge and win-overlay do not currently implement [CNI spec](https://github.com/containernetworking/cni/blob/master/SPEC.md) v0.4.0 due to missing \"CHECK\" implementation. * The Flannel VXLAN CNI has the following limitations on Windows: </del> <ins> * Windowsリファレンスネットワークプラグインのwin-bridgeとwin-overlayは、[CNI仕様](https://github.com/containernetworking/cni/blob/master/SPEC.md)v0.4.0において「CHECK」実装がないため、今のところ実装されていません。 * Flannel VXLAN CNIについては、Windowsで次の制限があります。: </ins> <del> 1. Node-pod connectivity isn't possible by design. It's only possible for local pods with Flannel [PR 1096](https://github.com/coreos/flannel/pull/1096) 2. We are restricted to using VNI 4096 and UDP port 4789. The VNI limitation is being worked on and will be overcome in a future release (open-source flannel changes). See the official [Flannel VXLAN](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan) backend docs for more details on these parameters. </del> <ins> 1. Node-podの直接間接続は設計上不可能です。Flannel[PR 1096](https://github.com/coreos/flannel/pull/1096)を使用するローカルPodでのみ可能です 2. VNI 4096とUDPポート4789の使用に制限されています。VNIの制限は現在取り組んでおり、将来のリリースで解決される予定です（オープンソースのflannelの変更）。これらのパラメーターの詳細については、公式の[Flannel VXLAN](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan)バックエンドのドキュメントをご覧ください。 </ins> ##### DNS {#dns-limitations} <del> * ClusterFirstWithHostNet is not supported for DNS. Windows treats all names with a '.' as a FQDN and skips PQDN resolution * On Linux, you have a DNS suffix list, which is used when trying to resolve PQDNs. On Windows, we only have 1 DNS suffix, which is the DNS suffix associated with that pod's namespace (mydns.svc.cluster.local for example). Windows can resolve FQDNs and services or names resolvable with just that suffix. For example, a pod spawned in the default namespace, will have the DNS suffix **default.svc.cluster.local**. On a Windows pod, you can resolve both **kubernetes.default.svc.cluster.local** and **kubernetes**, but not the in-betweens, like **kubernetes.default** or **kubernetes.default.svc**. * On Windows, there are multiple DNS resolvers that can be used. As these come with slightly different behaviors, using the `Resolve-DNSName` utility for name query resolutions is recommended. </del> <ins> * ClusterFirstWithHostNetは、DNSでサポートされていません。Windowsでは、FQDNとしてすべての名前を「.」で扱い、PQDNでの名前解決はスキップします。 * Linuxでは、PQDNで名前解決しようとするときに使用するDNSサフィックスリストがあります。Windowsでは、1つのDNSサフィックスしかありません。これは、そのPodのNamespaceに関連付けられているDNSサフィックスです（たとえば、mydns.svc.cluster.local）。Windowsでは、そのサフィックスだけで名前解決可能なFQDNおよびServiceまたはNameでの名前解決ができます。たとえば、defaultのNamespaceで生成されたPodには、DNSサフィックス**default.svc.cluster.local**が付けられます。WindowsのPodでは、**kubernetes.default.svc.cluster.local**と**kubernetes**の両方を名前解決できますが、**kubernetes.default**や**kubernetes.default.svc**のような中間での名前解決はできません。 * Windowsでは、複数のDNSリゾルバーを使用できます。これらには少し異なる動作が付属しているため、ネームクエリの解決には`Resolve-DNSName`ユーティリティを使用することをお勧めします。 </ins> <del> ##### Security </del> <ins> ##### セキュリティ </ins> <del> Secrets are written in clear text on the node's volume (as compared to tmpfs/in-memory on linux). This means customers have to do two things </del> <ins> Secretはノードのボリュームに平文テキストで書き込まれます（Linuxのtmpfs/in-memoryの比較として）。これはカスタマーが2つのことを行う必要があります </ins> <del> 1. Use file ACLs to secure the secrets file location 2. Use volume-level encryption using [BitLocker](https://docs.microsoft.com/en-us/windows/security/information-protection/bitlocker/bitlocker-how-to-deploy-on-windows-server) </del> <ins> 1. ファイルACLを使用してSecretファイルの場所を保護する 2.  [BitLocker](https://docs.microsoft.com/en-us/windows/security/information-protection/bitlocker/bitlocker-how-to-deploy-on-windows-server)を使って、ボリュームレベルの暗号化を使用する </ins> <del> [RunAsUser ](/docs/concepts/policy/pod-security-policy/#users-and-groups)is not currently supported on Windows. The workaround is to create local accounts before packaging the container. The RunAsUsername capability may be added in a future release. </del> <ins> [RunAsUser](/docs/concepts/policy/pod-security-policy/#users-and-groups)は、現在Windowsではサポートされていません。回避策は、コンテナをパッケージ化する前にローカルアカウントを作成することです。RunAsUsername機能は、将来のリリースで追加される可能性があります。 </ins> <del> Linux specific pod security context privileges such as SELinux, AppArmor, Seccomp, Capabilities (POSIX Capabilities), and others are not supported. </del> <ins> SELinux、AppArmor、Seccomp、特性（POSIX機能）のような、Linux固有のPodセキュリティ環境の権限はサポートされていません。 </ins> <del> In addition, as mentioned already, privileged containers are not supported on Windows. </del> <ins> さらに、既に述べたように特権付きコンテナは、Windowsにおいてサポートされていません。 </ins> #### API <del> There are no differences in how most of the Kubernetes APIs work for Windows. The subtleties around what's different come down to differences in the OS and container runtime. In certain situations, some properties on workload APIs such as Pod or Container were designed with an assumption that they are implemented on Linux, failing to run on Windows. </del> <ins> ほとんどのKubernetes APIがWindowsでも機能することに違いはありません。そのわずかな違いはOSとコンテナランタイムの違いによるものです。特定の状況では、PodやコンテナなどのワークロードAPIの一部のプロパティが、Linuxで実装されているが、Windowsでは実行できないことを前提に設計されています。 </ins> <del> At a high level, these OS concepts are different: </del> <ins> 高いレベルで、これらOSのコンセプトに違いがります。: </ins> <del> * Identity - Linux uses userID (UID) and groupID (GID) which are represented as integer types. User and group names are not canonical - they are just an alias in `/etc/groups` or `/etc/passwd` back to UID+GID. Windows uses a larger binary security identifier (SID) which is stored in the Windows Security Access Manager (SAM) database. This database is not shared between the host and containers, or between containers. * File permissions - Windows uses an access control list based on SIDs, rather than a bitmask of permissions and UID+GID * File paths - convention on Windows is to use `` instead of `/`. The Go IO libraries typically accept both and just make it work, but when you're setting a path or command line that's interpreted inside a container, `` may be needed. * Signals - Windows interactive apps handle termination differently, and can implement one or more of these: * A UI thread handles well-defined messages including WM_CLOSE * Console apps handle ctrl-c or ctrl-break using a Control Handler * Services register a Service Control Handler function that can accept SERVICE_CONTROL_STOP control codes </del> <ins> * ID - Linuxでは、Integer型として表されるuserID（UID）とgroupID（GID）を使用します。ユーザー名とグループ名は正規ではありません - それらは、UID+GIDの背後にある`/etc/groups`または`/etc/passwd`の単なるエイリアスです。Windowsは、Windows Security Access Manager（SAM）データベースに格納されているより大きなバイナリセキュリティ識別子（SID）を使用します。このデータベースは、ホストとコンテナ間、またはコンテナ間で共有されません。 * ファイル権限 - Windowsは、権限とUID+GIDのビットマスクではなく、SIDに基づくアクセス制御リストを使用します * ファイルパス - Windowsの規則では、`/`ではなく``を使用します。Go IOライブラリは通常両方を受け入れ、それを機能させるだけですが、コンテナ内で解釈されるパスまたはコマンドラインを設定する場合、``が必要になる場合があります。 * シグナル - Windowsのインタラクティブなアプリは終了を異なる方法で処理し、次の1つ以上を実装できます。: * UIスレッドは、WM_CLOSEを含む明確に定義されたメッセージを処理します * コンソールアプリは、コントロールハンドラーを使用してctrl-cまたはctrl-breakを処理します * サービスは、SERVICE_CONTROL_STOP制御コードを受け入れることができるサービスコントロールハンドラー関数を登録します。 </ins> <del> Exit Codes follow the same convention where 0 is success, nonzero is failure. The specific error codes may differ across Windows and Linux. However, exit codes passed from the Kubernetes components (kubelet, kube-proxy) are unchanged. </del> <ins> 終了コードは、0が成功、0以外が失敗の場合と同じ規則に従います。特定のエラーコードは、WindowsとLinuxで異なる場合があります。ただし、Kubernetesのコンポーネント（kubelet、kube-proxy）から渡される終了コードは変更されていません。 </ins> ##### V1.Container <del> * V1.Container.ResourceRequirements.limits.cpu and V1.Container.ResourceRequirements.limits.memory - Windows doesn't use hard limits for CPU allocations. Instead, a share system is used. The existing fields based on millicores are scaled into relative shares that are followed by the Windows scheduler. [see: kuberuntime/helpers_windows.go](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/kuberuntime/helpers_windows.go), [see: resource controls in Microsoft docs](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/resource-controls) * Huge pages are not implemented in the Windows container runtime, and are not available. They require [asserting a user privilege](https://docs.microsoft.com/en-us/windows/desktop/Memory/large-page-support) that's not configurable for containers. * V1.Container.ResourceRequirements.requests.cpu and V1.Container.ResourceRequirements.requests.memory - Requests are subtracted from node available resources, so they can be used to avoid overprovisioning a node. However, they cannot be used to guarantee resources in an overprovisioned node. They should be applied to all containers as a best practice if the operator wants to avoid overprovisioning entirely. * V1.Container.SecurityContext.allowPrivilegeEscalation - not possible on Windows, none of the capabilities are hooked up * V1.Container.SecurityContext.Capabilities - POSIX capabilities are not implemented on Windows * V1.Container.SecurityContext.privileged - Windows doesn't support privileged containers * V1.Container.SecurityContext.procMount - Windows doesn't have a /proc filesystem * V1.Container.SecurityContext.readOnlyRootFilesystem - not possible on Windows, write access is required for registry & system processes to run inside the container * V1.Container.SecurityContext.runAsGroup - not possible on Windows, no GID support * V1.Container.SecurityContext.runAsNonRoot - Windows does not have a root user. The closest equivalent is ContainerAdministrator which is an identity that doesn't exist on the node. * V1.Container.SecurityContext.runAsUser - not possible on Windows, no UID support as int. * V1.Container.SecurityContext.seLinuxOptions - not possible on Windows, no SELinux * V1.Container.terminationMessagePath - this has some limitations in that Windows doesn't support mapping single files. The default value is /dev/termination-log, which does work because it does not exist on Windows by default. </del> <ins> * V1.Container.ResourceRequirements.limits.cpuおよびV1.Container.ResourceRequirements.limits.memory - Windowsは、CPU割り当てにハード制限を使用しません。代わりに、共有システムが使用されます。ミリコアに基づく既存のフィールドは、Windowsスケジューラーによって追従される相対共有にスケーリングされます。[参照: kuberuntime/helpers_windows.go](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/kuberuntime/helpers_windows.go)、[参照: resource controls in Microsoft docs](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/resource-controls) * Huge Pagesは、Windowsコンテナランタイムには実装されてないので、使用できません。コンテナに対して設定できない[ユーザー特権を主張](https://docs.microsoft.com/en-us/windows/desktop/Memory/large-page-support)する必要があります。 * V1.Container.ResourceRequirements.requests.cpuおよびV1.Container.ResourceRequirements.requests.memory - リクエストはノードの利用可能なリソースから差し引かれるので、ノードのオーバープロビジョニングを回避するために使用できます。ただし、過剰にプロビジョニングされたノードのリソースを保証するために使用することはできません。オペレーターが完全にプロビジョニングし過ぎないようにする場合は、ベストプラクティスとしてこれらをすべてのコンテナに適用する必要があります。 * V1.Container.SecurityContext.allowPrivilegeEscalation - Windowsでは使用できません、接続されている機能はありません * V1.Container.SecurityContext.Capabilities - POSIX機能はWindowsでは実装されていません * V1.Container.SecurityContext.privileged - Windowsでは特権コンテナをサポートしていません * V1.Container.SecurityContext.procMount - Windowsでは/procファイルシステムがありません * V1.Container.SecurityContext.readOnlyRootFilesystem - Windowsでは使用できません、レジストリおよびシステムプロセスがコンテナ内で実行するには、書き込みアクセスが必要です * V1.Container.SecurityContext.runAsGroup - Windowsでは使用できません、GIDのサポートもありません * V1.Container.SecurityContext.runAsNonRoot - Windowsではrootユーザーが存在しません。最も近いものは、ノードに存在しないIDであるContainerAdministratorです。 * V1.Container.SecurityContext.runAsUser - Windowsでは使用できません。intとしてのUIDはサポートされていません。 * V1.Container.SecurityContext.seLinuxOptions - Windowsでは使用できません、SELinuxがありません * V1.Container.terminationMessagePath - これは、Windowsが単一ファイルのマッピングをサポートしないという点でいくつかの制限があります。デフォルト値は/dev/termination-logであり、デフォルトではWindowsに存在しないため動作します。 </ins> ##### V1.Pod <del> * V1.Pod.hostIPC, v1.pod.hostpid - host namespace sharing is not possible on Windows * V1.Pod.hostNetwork - There is no Windows OS support to share the host network * V1.Pod.dnsPolicy - ClusterFirstWithHostNet - is not supported because Host Networking is not supported on Windows. * V1.Pod.podSecurityContext - see V1.PodSecurityContext below * V1.Pod.shareProcessNamespace - this is a beta feature, and depends on Linux namespaces which are not implemented on Windows. Windows cannot share process namespaces or the container's root filesystem. Only the network can be shared. * V1.Pod.terminationGracePeriodSeconds - this is not fully implemented in Docker on Windows, see: [reference](https://github.com/moby/moby/issues/25982). The behavior today is that the ENTRYPOINT process is sent CTRL_SHUTDOWN_EVENT, then Windows waits 5 seconds by default, and finally shuts down all processes using the normal Windows shutdown behavior. The 5 second default is actually in the Windows registry [inside the container](https://github.com/moby/moby/issues/25982#issuecomment-426441183), so it can be overridden when the container is built. * V1.Pod.volumeDevices - this is a beta feature, and is not implemented on Windows. Windows cannot attach raw block devices to pods. * V1.Pod.volumes - EmptyDir, Secret, ConfigMap, HostPath - all work and have tests in TestGrid * V1.emptyDirVolumeSource - the Node default medium is disk on Windows. Memory is not supported, as Windows does not have a built-in RAM disk. * V1.VolumeMount.mountPropagation - mount propagation is not supported on Windows. </del> <ins> * V1.Pod.hostIPC、v1.pod.hostpid - Windowsではホストのネームスペースを共有することはできません * V1.Pod.hostNetwork - ホストのネットワークを共有するためのWindows OSサポートはありません * V1.Pod.dnsPolicy - ClusterFirstWithHostNet - Windowsではホストネットワーキングがサポートされていないため、サポートされていません。 * V1.Pod.podSecurityContext - 以下のV1.PodSecurityContextを参照 * V1.Pod.shareProcessNamespace - これはベータ版の機能であり、Windowsに実装されていないLinuxのNamespace機能に依存しています。Windowsでは、プロセスのネームスペースまたはコンテナのルートファイルシステムを共有できません。共有できるのはネットワークだけです。 * V1.Pod.terminationGracePeriodSeconds - これはWindowsのDockerに完全には実装されていません。[リファレンス](https://github.com/moby/moby/issues/25982)を参照してください。今日の動作では、ENTRYPOINTプロセスにCTRL_SHUTDOWN_EVENTが送信され、Windowsではデフォルトで5秒待機し、最後に通常のWindowsシャットダウン動作を使用してすべてのプロセスをシャットダウンします。5秒のデフォルトは、実際にはWindowsレジストリー[コンテナ内](https://github.com/moby/moby/issues/25982#issuecomment-426441183)にあるため、コンテナ作成時にオーバーライドできます。 * V1.Pod.volumeDevices - これはベータ機能であり、Windowsには実装されていません。Windowsでは、rawブロックデバイスをPodに接続できません。 * V1.Pod.volumes-EmptyDir、Secret、ConfigMap、HostPath - すべて動作し、TestGridにテストがあります * V1.emptyDirVolumeSource - ノードのデフォルトのメディアはWindowsのディスクです。Windowsでは、RAMディスクが組み込まれていないため、メモリはサポートされていません。 * V1.VolumeMount.mountPropagation - mount propagationは、Windowsではサポートされていません。 </ins> ##### V1.PodSecurityContext <del> None of the PodSecurityContext fields work on Windows. They're listed here for reference. </del> <ins> Windowsでは、PodSecurityContextフィールドはどれも機能しません。これらは参照用にここにリストされています。 </ins> <del> * V1.PodSecurityContext.SELinuxOptions - SELinux is not available on Windows * V1.PodSecurityContext.RunAsUser - provides a UID, not available on Windows * V1.PodSecurityContext.RunAsGroup - provides a GID, not available on Windows * V1.PodSecurityContext.RunAsNonRoot - Windows does not have a root user. The closest equivalent is ContainerAdministrator which is an identity that doesn't exist on the node. * V1.PodSecurityContext.SupplementalGroups - provides GID, not available on Windows * V1.PodSecurityContext.Sysctls - these are part of the Linux sysctl interface. There's no equivalent on Windows. </del> <ins> * V1.PodSecurityContext.SELinuxOptions - SELinuxは、Windowsでは使用できません * V1.PodSecurityContext.RunAsUser - UIDを提供しますが、Windowsでは使用できません * V1.PodSecurityContext.RunAsGroup - GIDを提供しますが、Windowsでは使用できません * V1.PodSecurityContext.RunAsNonRoot - Windowsにはrootユーザーがありません。最も近いものは、ノードに存在しないIDであるContainerAdministratorです。 * V1.PodSecurityContext.SupplementalGroups - GIDを提供しますが、Windowsでは使用できません * V1.PodSecurityContext.Sysctls - これらはLinuxのsysctlインターフェースの一部です。Windowsには同等のものはありません。 </ins> <del> ## Getting Help and Troubleshooting {#troubleshooting} </del> <ins> ## ヘルプとトラブルシューティングを学ぶ {#troubleshooting} </ins> <del> Your main source of help for troubleshooting your Kubernetes cluster should start with this [section](/docs/tasks/debug-application-cluster/troubleshooting/). Some additional, Windows-specific troubleshooting help is included in this section. Logs are an important element of troubleshooting issues in Kubernetes. Make sure to include them any time you seek troubleshooting assistance from other contributors. Follow the instructions in the SIG-Windows [contributing guide on gathering logs](https://github.com/kubernetes/community/blob/master/sig-windows/CONTRIBUTING.md#gathering-logs). </del> <ins> Kubernetesクラスターのトラブルシューティングの主なヘルプソースは、この[セクション](/docs/tasks/debug-application-cluster/troubleshooting/)から始める必要があります。このセクションには、いくつか追加的な、Windows固有のトラブルシューティングヘルプが含まれています。ログは、Kubernetesにおけるトラブルシューティング問題の重要な要素です。他のコントリビューターからトラブルシューティングの支援を求めるときは、必ずそれらを含めてください。SIG-Windows[ログ収集に関するコントリビュートガイド](https://github.com/kubernetes/community/blob/master/sig-windows/CONTRIBUTING.md#gathering-logs)の指示に従ってください。 </ins> <del> 1. How do I know start.ps1 completed successfully? </del> <ins> 1. start.ps1が正常に完了したことをどのように確認できますか？ </ins> <del> You should see kubelet, kube-proxy, and (if you chose Flannel as your networking solution) flanneld host-agent processes running on your node, with running logs being displayed in separate PowerShell windows. In addition to this, your Windows node should be listed as \"Ready\" in your Kubernetes cluster. </del> <ins> ノード上でkubelet、kube-proxy、および（ネットワーキングソリューションとしてFlannelを選択した場合）flanneldホストエージェントプロセスが実行され、実行ログが個別のPowerShellウィンドウに表示されます。これに加えて、WindowsノードがKubernetesクラスターで「Ready」として表示されているはずです。 </ins> <del> 1. Can I configure the Kubernetes node processes to run in the background as services? </del> <ins> 1. Kubernetesノードのプロセスをサービスとしてバックグラウンドで実行するように構成できますか？ </ins> <del> Kubelet and kube-proxy are already configured to run as native Windows Services, offering resiliency by re-starting the services automatically in the event of failure (for example a process crash). You have two options for configuring these node components as services. </del> <ins> Kubeletとkube-proxyは、ネイティブのWindowsサービスとして実行するように既に構成されています、障害（例えば、プロセスのクラッシュ）が発生した場合にサービスを自動的に再起動することにより、復元性を提供します。これらのノードコンポーネントをサービスとして構成するには、2つのオプションがあります。 </ins> <del> 1. As native Windows Services </del> <ins> 1. ネイティブWindowsサービスとして </ins> <del> Kubelet & kube-proxy can be run as native Windows Services using `sc.exe`. </del> <ins> Kubeletとkube-proxyは、`sc.exe`を使用してネイティブのWindowsサービスとして実行できます。 </ins> ```powershell <del> # Create the services for kubelet and kube-proxy in two separate commands </del> <ins> # 2つの個別のコマンドでkubeletおよびkube-proxyのサービスを作成する </ins> sc.exe create <component_name> binPath= \"<path_to_binary> --service <other_args>\" <del> # Please note that if the arguments contain spaces, they must be escaped. </del> <ins> # 引数にスペースが含まれている場合は、エスケープする必要があることに注意してください。 </ins> sc.exe create kubelet binPath= \"C:kubelet.exe --service --hostname-override 'minion' <other_args>\" <del> # Start the services </del> <ins> # サービスを開始する </ins> Start-Service kubelet Start-Service kube-proxy <del> # Stop the service </del> <ins> # サービスを停止する </ins> Stop-Service kubelet (-Force) Stop-Service kube-proxy (-Force) <del> # Query the service status </del> <ins> # サービスの状態を問い合わせる </ins> Get-Service kubelet Get-Service kube-proxy ``` <del> 1. Using nssm.exe </del> <ins> 1. nssm.exeの使用 </ins> <del> You can also always use alternative service managers like [nssm.exe](https://nssm.cc/) to run these processes (flanneld, kubelet & kube-proxy) in the background for you. You can use this [sample script](https://github.com/Microsoft/SDN/tree/master/Kubernetes/flannel/register-svc.ps1), leveraging nssm.exe to register kubelet, kube-proxy, and flanneld.exe to run as Windows services in the background. </del> <ins> また、[nssm.exe](https://nssm.cc/)などの代替サービスマネージャーを使用して、これらのプロセス（flanneld、kubelet、kube-proxy）をバックグラウンドで実行することもできます。この[サンプルスクリプト](https://github.com/Microsoft/SDN/tree/master/Kubernetes/flannel/register-svc.ps1)を使用すると、nssm.exeを利用してkubelet、kube-proxy、flanneld.exeを登録し、Windowsサービスとしてバックグラウンドで実行できます。 </ins> ```powershell register-svc.ps1 -NetworkMode <Network mode> -ManagementIP <Windows Node IP> -ClusterCIDR <Cluster subnet> -KubeDnsServiceIP <Kube-dns Service IP> -LogDir <Directory to place logs> <del> # NetworkMode      = The network mode l2bridge (flannel host-gw, also the default value) or overlay (flannel vxlan) chosen as a network solution # ManagementIP     = The IP address assigned to the Windows node. You can use ipconfig to find this # ClusterCIDR      = The cluster subnet range. (Default value 10.244.0.0/16) # KubeDnsServiceIP = The Kubernetes DNS service IP (Default value 10.96.0.10) # LogDir           = The directory where kubelet and kube-proxy logs are redirected into their respective output files (Default value C:k) </del> <ins> # NetworkMode      = ネットワークソリューションとして選択されたネットワークモードl2bridge（flannel host-gw、これもデフォルト値）またはoverlay（flannel vxlan） # ManagementIP     = Windowsノードに割り当てられたIPアドレス。 ipconfigを使用してこれを見つけることができます # ClusterCIDR      = クラスターのサブネット範囲。（デフォルト値 10.244.0.0/16） # KubeDnsServiceIP = Kubernetes DNSサービスIP（デフォルト値 10.96.0.10） # LogDir           = kubeletおよびkube-proxyログがそれぞれの出力ファイルにリダイレクトされるディレクトリ（デフォルト値 C:k） </ins> ``` <del> If the above referenced script is not suitable, you can manually configure nssm.exe using the following examples. </del> <ins> 上記のスクリプトが適切でない場合は、次の例を使用してnssm.exeを手動で構成できます。 </ins> ```powershell <del> # Register flanneld.exe </del> <ins> # flanneld.exeを登録する </ins> nssm install flanneld C:flannelflanneld.exe nssm set flanneld AppParameters --kubeconfig-file=c:kconfig --iface=<ManagementIP> --ip-masq=1 --kube-subnet-mgr=1 nssm set flanneld AppEnvironmentExtra NODE_NAME=<hostname> nssm set flanneld AppDirectory C:flannel nssm start flanneld <del> # Register kubelet.exe # Microsoft releases the pause infrastructure container at mcr.microsoft.com/k8s/core/pause:1.2.0 # For more info search for \"pause\" in the \"Guide for adding Windows Nodes in Kubernetes\" </del> <ins> # kubelet.exeを登録 # マイクロソフトは、mcr.microsoft.com/k8s/core/pause:1.2.0としてポーズインフラストラクチャコンテナをリリース # 詳細については、「KubernetesにWindowsノードを追加するためのガイド」で「pause」を検索してください </ins> nssm install kubelet C:kkubelet.exe nssm set kubelet AppParameters --hostname-override=<hostname> --v=6 --pod-infra-container-image=mcr.microsoft.com/k8s/core/pause:1.2.0 --resolv-conf=\"\" --allow-privileged=true --enable-debugging-handlers --cluster-dns=<DNS-service-IP> --cluster-domain=cluster.local --kubeconfig=c:kconfig --hairpin-mode=promiscuous-bridge --image-pull-progress-deadline=20m --cgroups-per-qos=false  --log-dir=<log directory> --logtostderr=false --enforce-node-allocatable=\"\" --network-plugin=cni --cni-bin-dir=c:kcni --cni-conf-dir=c:kcniconfig nssm set kubelet AppDirectory C:k nssm start kubelet <del> # Register kube-proxy.exe (l2bridge / host-gw) </del> <ins> # kube-proxy.exeを登録する (l2bridge / host-gw) </ins> nssm install kube-proxy C:kkube-proxy.exe nssm set kube-proxy AppDirectory c:k nssm set kube-proxy AppParameters --v=4 --proxy-mode=kernelspace --hostname-override=<hostname>--kubeconfig=c:kconfig --enable-dsr=false --log-dir=<log directory> --logtostderr=false"}
{"_id":"q-en-website-1a5754185e814786a09d4e42a468a5df3e68e90bc04cef1ce5cc4359f9907c09","text":"<ins> --- title: Pod 拓扑分布约束 content_type: concept weight: 40 --- <!-- title: Pod Topology Spread Constraints content_type: concept weight: 40 --> <!-- overview --> <!-- You can use _topology spread constraints_ to control how {{< glossary_tooltip text=\"Pods\" term_id=\"Pod\" >}} are spread across your cluster among failure-domains such as regions, zones, nodes, and other user-defined topology domains. This can help to achieve high availability as well as efficient resource utilization. You can set [cluster-level constraints](#cluster-level-default-constraints) as a default, or configure topology spread constraints for individual workloads. --> 你可以使用 **拓扑分布约束（Topology Spread Constraints）** 来控制 {{< glossary_tooltip text=\"Pod\" term_id=\"Pod\" >}} 在集群内故障域之间的分布， 例如区域（Region）、可用区（Zone）、节点和其他用户自定义拓扑域。 这样做有助于实现高可用并提升资源利用率。 你可以将[集群级约束](#cluster-level-default-constraints)设为默认值，或为个别工作负载配置拓扑分布约束。 <!-- body --> <!-- ## Motivation Imagine that you have a cluster of up to twenty nodes, and you want to run a {{< glossary_tooltip text=\"workload\" term_id=\"workload\" >}} that automatically scales how many replicas it uses. There could be as few as two Pods or as many as fifteen. When there are only two Pods, you'd prefer not to have both of those Pods run on the same node: you would run the risk that a single node failure takes your workload offline. In addition to this basic usage, there are some advanced usage examples that enable your workloads to benefit on high availability and cluster utilization. --> ## 动机 {#motivation} 假设你有一个最多包含二十个节点的集群，你想要运行一个自动扩缩的 {{< glossary_tooltip text=\"工作负载\" term_id=\"workload\" >}}，请问要使用多少个副本？ 答案可能是最少 2 个 Pod，最多 15 个 Pod。 当只有 2 个 Pod 时，你倾向于这 2 个 Pod 不要同时在同一个节点上运行： 你所遭遇的风险是如果放在同一个节点上且单节点出现故障，可能会让你的工作负载下线。 除了这个基本的用法之外，还有一些高级的使用案例，能够让你的工作负载受益于高可用性并提高集群利用率。 <!-- As you scale up and run more Pods, a different concern becomes important. Imagine that you have three nodes running five Pods each. The nodes have enough capacity to run that many replicas; however, the clients that interact with this workload are split across three different datacenters (or infrastructure zones). Now you have less concern about a single node failure, but you notice that latency is higher than you'd like, and you are paying for network costs associated with sending network traffic between the different zones. You decide that under normal operation you'd prefer to have a similar number of replicas [scheduled](/docs/concepts/scheduling-eviction/) into each infrastructure zone, and you'd like the cluster to self-heal in the case that there is a problem. Pod topology spread constraints offer you a declarative way to configure that. --> 随着你的工作负载扩容，运行的 Pod 变多，将需要考虑另一个重要问题。 假设你有 3 个节点，每个节点运行 5 个 Pod。这些节点有足够的容量能够运行许多副本； 但与这个工作负载互动的客户端分散在三个不同的数据中心（或基础设施可用区）。 现在你可能不太关注单节点故障问题，但你会注意到延迟高于自己的预期， 在不同的可用区之间发送网络流量会产生一些网络成本。 你决定在正常运营时倾向于将类似数量的副本[调度](/zh-cn/docs/concepts/scheduling-eviction/) 到每个基础设施可用区，且你想要该集群在遇到问题时能够自愈。 Pod 拓扑分布约束使你能够以声明的方式进行配置。 <!-- ## `topologySpreadConstraints` field The Pod API includes a field, `spec.topologySpreadConstraints`. Here is an example: --> ## `topologySpreadConstraints` 字段 Pod API 包括一个 `spec.topologySpreadConstraints` 字段。这里有一个示例： ```yaml --- apiVersion: v1 kind: Pod metadata: name: example-pod spec: # 配置一个拓扑分布约束 topologySpreadConstraints: - maxSkew: <integer> minDomains: <integer> # 可选；自从 v1.24 开始成为 Alpha topologyKey: <string> whenUnsatisfiable: <string> labelSelector: <object> ### 其他 Pod 字段置于此处 ``` <!-- You can read more about this field by running `kubectl explain Pod.spec.topologySpreadConstraints`. --> 你可以运行 `kubectl explain Pod.spec.topologySpreadConstraints` 阅读有关此字段的更多信息。 <!-- ### Spread constraint definition You can define one or multiple `topologySpreadConstraints` entries to instruct the kube-scheduler how to place each incoming Pod in relation to the existing Pods across your cluster. Those fields are: --> ### 分布约束定义 你可以定义一个或多个 `topologySpreadConstraints` 条目以指导 kube-scheduler 如何将每个新来的 Pod 与跨集群的现有 Pod 相关联。这些字段包括： <!-- - **maxSkew** describes the degree to which Pods may be unevenly distributed. You must specify this field and the number must be greater than zero. Its semantics differ according to the value of `whenUnsatisfiable`: - if you select `whenUnsatisfiable: DoNotSchedule`, then `maxSkew` defines the maximum permitted difference between the number of matching pods in the target topology and the _global minimum_ (the minimum number of pods that match the label selector in a topology domain). For example, if you have 3 zones with 2, 4 and 5 matching pods respectively, then the global minimum is 2 and `maxSkew` is compared relative to that number. - if you select `whenUnsatisfiable: ScheduleAnyway`, the scheduler gives higher precedence to topologies that would help reduce the skew. --> - **maxSkew** 描述这些 Pod 可能被均匀分布的程度。你必须指定此字段且该数值必须大于零。 其语义将随着 `whenUnsatisfiable` 的值发生变化： - 如果你选择 `whenUnsatisfiable: DoNotSchedule`，则 `maxSkew` 定义目标拓扑中匹配 Pod 的数量与 **全局最小值**（与拓扑域中标签选择算符匹配的最小 Pod 数量）之间的最大允许差值。 例如，如果你有 3 个可用区，分别有 2、4 和 5 个匹配的 Pod，则全局最小值为 2， 而 `maxSkew` 相对于该数字进行比较。 - 如果你选择 `whenUnsatisfiable: ScheduleAnyway`，则该调度器会更为偏向能够降低偏差值的拓扑域。 <!-- - **minDomains** indicates a minimum number of eligible domains. This field is optional. A domain is a particular instance of a topology. An eligible domain is a domain whose nodes match the node selector. The `minDomains` field is an alpha field added in 1.24. You have to enable the `MinDomainsInPodToplogySpread` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) in order to use it. --> - **minDomains** 表示符合条件的域的最小数量。此字段是可选的。域是拓扑的一个特定实例。 符合条件的域是其节点与节点选择器匹配的域。 {{< note >}} `minDomains` 字段是 1.24 中添加的一个 Alpha 字段。 你必须启用 `MinDomainsInPodToplogySpread` [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)，才能使用该字段。 {{< /note >}} <!-- - The value of `minDomains` must be greater than 0, when specified. You can only specify `minDomains` in conjunction with `whenUnsatisfiable: DoNotSchedule`. - When the number of eligible domains with match topology keys is less than `minDomains`, Pod topology spread treats global minimum as 0, and then the calculation of `skew` is performed. The global minimum is the minimum number of matching Pods in an eligible domain, or zero if the number of eligible domains is less than `minDomains`. - When the number of eligible domains with matching topology keys equals or is greater than `minDomains`, this value has no effect on scheduling. - If you do not specify `minDomains`, the constraint behaves as if `minDomains` is 1. --> - 指定的 `minDomains` 值必须大于 0。你可以结合 `whenUnsatisfiable: DoNotSchedule` 仅指定 `minDomains`。 - 当符合条件的、拓扑键匹配的域的数量小于 `minDomains` 时，拓扑分布将“全局最小值”（global minimum）设为 0， 然后进行 `skew` 计算。“全局最小值” 是一个符合条件的域中匹配 Pod 的最小数量， 如果符合条件的域的数量小于 `minDomains`，则全局最小值为零。 - 当符合条件的拓扑键匹配域的个数等于或大于 `minDomains` 时，该值对调度没有影响。 - 如果你未指定 `minDomains`，则约束行为类似于 `minDomains` 等于 1。 <!-- - **topologyKey** is the key of [node labels](#node-labels). If two Nodes are labelled with this key and have identical values for that label, the scheduler treats both Nodes as being in the same topology. The scheduler tries to place a balanced number of Pods into each topology domain. - **whenUnsatisfiable** indicates how to deal with a Pod if it doesn't satisfy the spread constraint: - `DoNotSchedule` (default) tells the scheduler not to schedule it. - `ScheduleAnyway` tells the scheduler to still schedule it while prioritizing nodes that minimize the skew. - **labelSelector** is used to find matching Pods. Pods that match this label selector are counted to determine the number of Pods in their corresponding topology domain. See [Label Selectors](/docs/concepts/overview/working-with-objects/labels/#label-selectors) for more details. --> - **topologyKey** 是[节点标签](#node-labels)的键。如果两个节点使用此键标记并且具有相同的标签值， 则调度器会将这两个节点视为处于同一拓扑域中。该调度器尝试在每个拓扑域中放置数量均衡的 Pod。 - **whenUnsatisfiable** 指示如果 Pod 不满足分布约束时如何处理： - `DoNotSchedule`（默认）告诉调度器不要调度。 - `ScheduleAnyway` 告诉调度器仍然继续调度，只是根据如何能将偏差最小化来对节点进行排序。 - **labelSelector** 用于查找匹配的 Pod。匹配此标签的 Pod 将被统计，以确定相应拓扑域中 Pod 的数量。 有关详细信息，请参考[标签选择算符](/zh-cn/docs/concepts/overview/working-with-objects/labels/#label-selectors)。 <!-- When a Pod defines more than one `topologySpreadConstraint`, those constraints are combined using a logical AND operation: the kube-scheduler looks for a node for the incoming Pod that satisfies all the configured constraints. --> 当 Pod 定义了不止一个 `topologySpreadConstraint`，这些约束之间是逻辑与的关系。 kube-scheduler 会为新的 Pod 寻找一个能够满足所有约束的节点。 <!-- ### Node labels Topology spread constraints rely on node labels to identify the topology domain(s) that each {{< glossary_tooltip text=\"node\" term_id=\"node\" >}} is in. For example, a node might have labels: --> ### 节点标签 {#node-labels} 拓扑分布约束依赖于节点标签来标识每个{{< glossary_tooltip text=\"节点\" term_id=\"node\" >}}所在的拓扑域。例如，某节点可能具有标签： ```yaml region: us-east-1 zone: us-east-1a ``` <!-- For brevity, this example doesn't use the [well-known](/docs/reference/labels-annotations-taints/) label keys `topology.kubernetes.io/zone` and `topology.kubernetes.io/region`. However, those registered label keys are nonetheless recommended rather than the private (unqualified) label keys `region` and `zone` that are used here. You can't make a reliable assumption about the meaning of a private label key between different contexts. --> {{< note >}} 为了简便，此示例未使用[众所周知](/zh-cn/docs/reference/labels-annotations-taints/)的标签键 `topology.kubernetes.io/zone` 和 `topology.kubernetes.io/region`。 但是，建议使用那些已注册的标签键，而不是此处使用的私有（不合格）标签键 `region` 和 `zone`。 你无法对不同上下文之间的私有标签键的含义做出可靠的假设。 {{< /note >}} <!-- Suppose you have a 4-node cluster with the following labels: --> 假设你有一个 4 节点的集群且带有以下标签： ``` NAME    STATUS   ROLES    AGE     VERSION   LABELS node1   Ready    <none>   4m26s   v1.16.0   node=node1,zone=zoneA node2   Ready    <none>   3m58s   v1.16.0   node=node2,zone=zoneA node3   Ready    <none>   3m17s   v1.16.0   node=node3,zone=zoneB node4   Ready    <none>   2m43s   v1.16.0   node=node4,zone=zoneB ``` <!-- Then the cluster is logically viewed as below: --> 那么，从逻辑上看集群如下： {{<mermaid>}} graph TB subgraph \"zoneB\" n3(Node3) n4(Node4) end subgraph \"zoneA\" n1(Node1) n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4 k8s; class zoneA,zoneB cluster; {{< /mermaid >}} <!-- ## Consistency You should set the same Pod topology spread constraints on all pods in a group. Usually, if you are using a workload controller such as a Deployment, the pod template takes care of this for you. If you mix different spread constraints then Kubernetes follows the API definition of the field; however, the behavior is more likely to become confusing and troubleshooting is less straightforward. You need a mechanism to ensure that all the nodes in a topology domain (such as a cloud provider region) are labelled consistently. To avoid you needing to manually label nodes, most clusters automatically populate well-known labels such as `topology.kubernetes.io/hostname`. Check whether your cluster supports this. --> ## 一致性 {#Consistency} 你应该为一个组中的所有 Pod 设置相同的 Pod 拓扑分布约束。 通常，如果你正使用一个工作负载控制器，例如 Deployment，则 Pod 模板会你你解决这个问题。 如果你混合不同的分布约束，则 Kubernetes 会遵循该字段的 API 定义； 但是，该行为可能更令人困惑，并且故障排除也没那么简单。 你需要一种机制来确保拓扑域（例如云提供商区域）中的所有节点具有一致的标签。 为了避免你需要手动为节点打标签，大多数集群会自动填充知名的标签， 例如 `topology.kubernetes.io/hostname`。检查你的集群是否支持此功能。 <!-- ## Topology spread constraint examples ### Example: one topology spread constraint {#example-one-topologyspreadconstraint} Suppose you have a 4-node cluster where 3 Pods labelled `foo: bar` are located in node1, node2 and node3 respectively: --> ## 拓扑分布约束示例 {#topology-spread-constraint-examples} ### 示例：一个拓扑分布约束 {#example-one-topologyspreadconstraint} 假设你拥有一个 4 节点集群，其中标记为 `foo: bar` 的 3 个 Pod 分别位于 node1、node2 和 node3 中： {{<mermaid>}} graph BT subgraph \"zoneB\" p3(Pod) --> n3(Node3) n4(Node4) end subgraph \"zoneA\" p1(Pod) --> n1(Node1) p2(Pod) --> n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4,p1,p2,p3 k8s; class zoneA,zoneB cluster; {{< /mermaid >}} <!-- If you want an incoming Pod to be evenly spread with existing Pods across zones, you can use a manifest similar to: --> 如果你希望新来的 Pod 均匀分布在现有的可用区域，则可以按如下设置其清单： {{< codenew file=\"pods/topology-spread-constraints/one-constraint.yaml\" >}} <!-- From that manifest, `topologyKey: zone` implies the even distribution will only be applied to nodes that are labelled `zone: <any value>` (nodes that don't have a `zone` label are skipped). The field `whenUnsatisfiable: DoNotSchedule` tells the scheduler to let the incoming Pod stay pending if the scheduler can't find a way to satisfy the constraint. If the scheduler placed this incoming Pod into zone `A`, the distribution of Pods would become `[3, 1]`. That means the actual skew is then 2 (calculated as `3 - 1`), which violates `maxSkew: 1`. To satisfy the constraints and context for this example, the incoming Pod can only be placed onto a node in zone `B`: --> 从此清单看，`topologyKey: zone` 意味着均匀分布将只应用于存在标签键值对为 `zone: <any value>` 的节点 （没有 `zone` 标签的节点将被跳过）。如果调度器找不到一种方式来满足此约束， 则 `whenUnsatisfiable: DoNotSchedule` 字段告诉该调度器将新来的 Pod 保持在 pending 状态。 如果该调度器将这个新来的 Pod 放到可用区 `A`，则 Pod 的分布将成为 `[3, 1]`。 这意味着实际偏差是 2（计算公式为 `3 - 1`），这违反了 `maxSkew: 1` 的约定。 为了满足这个示例的约束和上下文，新来的 Pod 只能放到可用区 `B` 中的一个节点上： {{<mermaid>}} graph BT subgraph \"zoneB\" p3(Pod) --> n3(Node3) p4(mypod) --> n4(Node4) end subgraph \"zoneA\" p1(Pod) --> n1(Node1) p2(Pod) --> n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4,p1,p2,p3 k8s; class p4 plain; class zoneA,zoneB cluster; {{< /mermaid >}} 或者 {{<mermaid>}} graph BT subgraph \"zoneB\" p3(Pod) --> n3(Node3) p4(mypod) --> n3 n4(Node4) end subgraph \"zoneA\" p1(Pod) --> n1(Node1) p2(Pod) --> n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4,p1,p2,p3 k8s; class p4 plain; class zoneA,zoneB cluster; {{< /mermaid >}} <!-- You can tweak the Pod spec to meet various kinds of requirements: - Change `maxSkew` to a bigger value - such as `2` -  so that the incoming Pod can be placed into zone `A` as well. - Change `topologyKey` to `node` so as to distribute the Pods evenly across nodes instead of zones. In the above example, if `maxSkew` remains `1`, the incoming Pod can only be placed onto the node `node4`. - Change `whenUnsatisfiable: DoNotSchedule` to `whenUnsatisfiable: ScheduleAnyway` to ensure the incoming Pod to be always schedulable (suppose other scheduling APIs are satisfied). However, it's preferred to be placed into the topology domain which has fewer matching Pods. (Be aware that this preference is jointly normalized with other internal scheduling priorities such as resource usage ratio). --> 你可以调整 Pod 规约以满足各种要求： - 将 `maxSkew` 更改为更大的值，例如 `2`，这样新来的 Pod 也可以放在可用区 `A` 中。 - 将 `topologyKey` 更改为 `node`，以便将 Pod 均匀分布在节点上而不是可用区中。 在上面的例子中，如果 `maxSkew` 保持为 `1`，则新来的 Pod 只能放到 `node4` 节点上。 - 将 `whenUnsatisfiable: DoNotSchedule` 更改为 `whenUnsatisfiable: ScheduleAnyway`， 以确保新来的 Pod 始终可以被调度（假设满足其他的调度 API）。但是，最好将其放置在匹配 Pod 数量较少的拓扑域中。 请注意，这一优先判定会与其他内部调度优先级（如资源使用率等）排序准则一起进行标准化。 <!-- ### Example: multiple topology spread constraints {#example-multiple-topologyspreadconstraints} This builds upon the previous example. Suppose you have a 4-node cluster where 3 existing Pods labeled `foo: bar` are located on node1, node2 and node3 respectively: --> ### 示例：多个拓扑分布约束 {#example-multiple-topologyspreadconstraints} 下面的例子建立在前面例子的基础上。假设你拥有一个 4 节点集群， 其中 3 个标记为 `foo: bar` 的 Pod 分别位于 node1、node2 和 node3 上： {{<mermaid>}} graph BT subgraph \"zoneB\" p3(Pod) --> n3(Node3) n4(Node4) end subgraph \"zoneA\" p1(Pod) --> n1(Node1) p2(Pod) --> n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4,p1,p2,p3 k8s; class p4 plain; class zoneA,zoneB cluster; {{< /mermaid >}} <!-- You can combine two topology spread constraints to control the spread of Pods both by node and by zone: --> 可以组合使用 2 个拓扑分布约束来控制 Pod 在节点和可用区两个维度上的分布： {{< codenew file=\"pods/topology-spread-constraints/two-constraints.yaml\" >}} <!-- In this case, to match the first constraint, the incoming Pod can only be placed onto nodes in zone `B`; while in terms of the second constraint, the incoming Pod can only be scheduled to the node `node4`. The scheduler only considers options that satisfy all defined constraints, so the only valid placement is onto node `node4`. --> 在这种情况下，为了匹配第一个约束，新的 Pod 只能放置在可用区 `B` 中； 而在第二个约束中，新来的 Pod 只能调度到节点 `node4` 上。 该调度器仅考虑满足所有已定义约束的选项，因此唯一可行的选择是放置在节点 `node4` 上。 <!-- ### Example: conflicting topology spread constraints {#example-conflicting-topologyspreadconstraints} Multiple constraints can lead to conflicts. Suppose you have a 3-node cluster across 2 zones: --> ### 示例：有冲突的拓扑分布约束 {#example-conflicting-topologyspreadconstraints} 多个约束可能导致冲突。假设有一个跨 2 个可用区的 3 节点集群： {{<mermaid>}} graph BT subgraph \"zoneB\" p4(Pod) --> n3(Node3) p5(Pod) --> n3 end subgraph \"zoneA\" p1(Pod) --> n1(Node1) p2(Pod) --> n1 p3(Pod) --> n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4,p1,p2,p3,p4,p5 k8s; class zoneA,zoneB cluster; {{< /mermaid >}} <!-- If you were to apply [`two-constraints.yaml`](https://raw.githubusercontent.com/kubernetes/website/main/content/en/examples/pods/topology-spread-constraints/two-constraints.yaml) (the manifest from the previous example) to **this** cluster, you would see that the Pod `mypod` stays in the `Pending` state. This happens because: to satisfy the first constraint, the Pod `mypod` can only be placed into zone `B`; while in terms of the second constraint, the Pod `mypod` can only schedule to node `node2`. The intersection of the two constraints returns an empty set, and the scheduler cannot place the Pod. To overcome this situation, you can either increase the value of `maxSkew` or modify one of the constraints to use `whenUnsatisfiable: ScheduleAnyway`. Depending on circumstances, you might also decide to delete an existing Pod manually - for example, if you are troubleshooting why a bug-fix rollout is not making progress. --> 如果你将 [`two-constraints.yaml`](https://raw.githubusercontent.com/kubernetes/website/main/content/en/examples/pods/topology-spread-constraints/two-constraints.yaml) （来自上一个示例的清单）应用到**这个**集群，你将看到 Pod `mypod` 保持在 `Pending` 状态。 出现这种情况的原因为：为了满足第一个约束，Pod `mypod` 只能放置在可用区 `B` 中； 而在第二个约束中，Pod `mypod` 只能调度到节点 `node2` 上。 两个约束的交集将返回一个空集，且调度器无法放置该 Pod。 为了应对这种情形，你可以提高 `maxSkew` 的值或修改其中一个约束才能使用 `whenUnsatisfiable: ScheduleAnyway`。 根据实际情形，例如若你在故障排查时发现某个漏洞修复工作毫无进展，你还可能决定手动删除一个现有的 Pod。 <!-- #### Interaction with node affinity and node selectors The scheduler will skip the non-matching nodes from the skew calculations if the incoming Pod has `spec.nodeSelector` or `spec.affinity.nodeAffinity` defined. --> #### 与节点亲和性和节点选择算符的相互作用 {#interaction-with-node-affinity-and-node-selectors} 如果 Pod 定义了 `spec.nodeSelector` 或 `spec.affinity.nodeAffinity`， 调度器将在偏差计算中跳过不匹配的节点。 <!-- ### Example: topology spread constraints with node affinity {#example-topologyspreadconstraints-with-nodeaffinity} Suppose you have a 5-node cluster ranging across zones A to C: --> ### 示例：带节点亲和性的拓扑分布约束 {#example-topologyspreadconstraints-with-nodeaffinity} 假设你有一个跨可用区 A 到 C 的 5 节点集群： {{<mermaid>}} graph BT subgraph \"zoneB\" p3(Pod) --> n3(Node3) n4(Node4) end subgraph \"zoneA\" p1(Pod) --> n1(Node1) p2(Pod) --> n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4,p1,p2,p3 k8s; class p4 plain; class zoneA,zoneB cluster; {{< /mermaid >}} {{<mermaid>}} graph BT subgraph \"zoneC\" n5(Node5) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n5 k8s; class zoneC cluster; {{< /mermaid >}} <!-- and you know that zone `C` must be excluded. In this case, you can compose a manifest as below, so that Pod `mypod` will be placed into zone `B` instead of zone `C`. Similarly, Kubernetes also respects `spec.nodeSelector`. --> 而且你知道可用区 `C` 必须被排除在外。在这种情况下，可以按如下方式编写清单， 以便将 Pod `mypod` 放置在可用区 `B` 上，而不是可用区 `C` 上。 同样，Kubernetes 也会一样处理 `spec.nodeSelector`。 {{< codenew file=\"pods/topology-spread-constraints/one-constraint-with-nodeaffinity.yaml\" >}} <!-- ## Implicit conventions There are some implicit conventions worth noting here: - Only the Pods holding the same namespace as the incoming Pod can be matching candidates. - The scheduler bypasses any nodes that don't have any `topologySpreadConstraints[*].topologyKey` present. This implies that: 1. any Pods located on those bypassed nodes do not impact `maxSkew` calculation - in the above example, suppose the node `node1` does not have a label \"zone\", then the 2 Pods will be disregarded, hence the incoming Pod will be scheduled into zone `A`. 2. the incoming Pod has no chances to be scheduled onto this kind of nodes - in the above example, suppose a node `node5` has the **mistyped** label `zone-typo: zoneC` (and no `zone` label set). After node `node5` joins the cluster, it will be bypassed and Pods for this workload aren't scheduled there. --> ## 隐式约定 {#implicit-conventions} 这里有一些值得注意的隐式约定： - 只有与新来的 Pod 具有相同命名空间的 Pod 才能作为匹配候选者。 - 调度器会忽略没有任何 `topologySpreadConstraints[*].topologyKey` 的节点。这意味着： 1. 位于这些节点上的 Pod 不影响 `maxSkew` 计算，在上面的例子中，假设节点 `node1` 没有标签 \"zone\"， 则 2 个 Pod 将被忽略，因此新来的 Pod 将被调度到可用区 `A` 中。 2. 新的 Pod 没有机会被调度到这类节点上。在上面的例子中， 假设节点 `node5` 带有 **拼写错误的** 标签 `zone-typo: zoneC`（且没有设置 `zone` 标签）。 节点 `node5` 接入集群之后，该节点将被忽略且针对该工作负载的 Pod 不会被调度到那里。 <!-- - Be aware of what will happen if the incoming Pod's `topologySpreadConstraints[*].labelSelector` doesn't match its own labels. In the above example, if you remove the incoming Pod's labels, it can still be placed onto nodes in zone `B`, since the constraints are still satisfied. However, after that placement, the degree of imbalance of the cluster remains unchanged - it's still zone `A` having 2 Pods labelled as `foo: bar`, and zone `B` having 1 Pod labelled as `foo: bar`. If this is not what you expect, update the workload's `topologySpreadConstraints[*].labelSelector` to match the labels in the pod template. --> - 注意，如果新 Pod 的 `topologySpreadConstraints[*].labelSelector` 与自身的标签不匹配，将会发生什么。 在上面的例子中，如果移除新 Pod 的标签，则 Pod 仍然可以放置到可用区 `B` 中的节点上，因为这些约束仍然满足。 然而，在放置之后，集群的不平衡程度保持不变。可用区 `A` 仍然有 2 个 Pod 带有标签 `foo: bar`， 而可用区 `B` 有 1 个 Pod 带有标签 `foo: bar`。如果这不是你所期望的， 更新工作负载的 `topologySpreadConstraints[*].labelSelector` 以匹配 Pod 模板中的标签。 <!-- ## Cluster-level default constraints It is possible to set default topology spread constraints for a cluster. Default topology spread constraints are applied to a Pod if, and only if: - It doesn't define any constraints in its `.spec.topologySpreadConstraints`. - It belongs to a Service, ReplicaSet, StatefulSet or ReplicationController. Default constraints can be set as part of the `PodTopologySpread` plugin arguments in a [scheduling profile](/docs/reference/scheduling/config/#profiles). The constraints are specified with the same [API above](#api), except that `labelSelector` must be empty. The selectors are calculated from the Services, ReplicaSets, StatefulSets or ReplicationControllers that the Pod belongs to. An example configuration might look like follows: --> ## 集群级别的默认约束 {#cluster-level-default-constraints} 为集群设置默认的拓扑分布约束也是可能的。默认拓扑分布约束在且仅在以下条件满足时才会被应用到 Pod 上： - Pod 没有在其 `.spec.topologySpreadConstraints` 中定义任何约束。 - Pod 隶属于某个 Service、ReplicaSet、StatefulSet 或 ReplicationController。 默认约束可以设置为[调度方案](/zh-cn/docs/reference/scheduling/config/#profiles)中 `PodTopologySpread` 插件参数的一部分。约束的设置采用[如前所述的 API](#api)， 只是 `labelSelector` 必须为空。 选择算符是根据 Pod 所属的 Service、ReplicaSet、StatefulSet 或 ReplicationController 来设置的。 配置的示例可能看起来像下面这个样子： ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta3 kind: KubeSchedulerConfiguration profiles: - schedulerName: default-scheduler pluginConfig: - name: PodTopologySpread args: defaultConstraints: - maxSkew: 1 topologyKey: topology.kubernetes.io/zone whenUnsatisfiable: ScheduleAnyway defaultingType: List ``` <!-- The [`SelectorSpread` plugin](/docs/reference/scheduling/config/#scheduling-plugins) is disabled by default. The Kubernetes project recommends using `PodTopologySpread` to achieve similar behavior. --> {{< note >}} 默认配置下，[`SelectorSpread` 插件](/zh-cn/docs/reference/scheduling/config/#scheduling-plugins)是被禁用的。 Kubernetes 项目建议使用 `PodTopologySpread` 以执行类似行为。 {{< /note >}} <!-- ### Built-in default constraints {#internal-default-constraints} --> ### 内置默认约束 {#internal-default-constraints} {{< feature-state for_k8s_version=\"v1.24\" state=\"stable\" >}} <!-- If you don't configure any cluster-level default constraints for pod topology spreading, then kube-scheduler acts as if you specified the following default topology constraints: --> 如果你没有为 Pod 拓扑分布配置任何集群级别的默认约束， kube-scheduler 的行为就像你指定了以下默认拓扑约束一样： ```yaml defaultConstraints: - maxSkew: 3 topologyKey: \"kubernetes.io/hostname\" whenUnsatisfiable: ScheduleAnyway - maxSkew: 5 topologyKey: \"topology.kubernetes.io/zone\" whenUnsatisfiable: ScheduleAnyway ``` <!-- Also, the legacy `SelectorSpread` plugin, which provides an equivalent behavior, is disabled by default. --> 此外，原来用于提供等同行为的 `SelectorSpread` 插件默认被禁用。 <!-- The `PodTopologySpread` plugin does not score the nodes that don't have the topology keys specified in the spreading constraints. This might result in a different default behavior compared to the legacy `SelectorSpread` plugin when using the default topology constraints. If your nodes are not expected to have **both** `kubernetes.io/hostname` and `topology.kubernetes.io/zone` labels set, define your own constraints instead of using the Kubernetes defaults. --> {{< note >}} 对于分布约束中所指定的拓扑键而言，`PodTopologySpread` 插件不会为不包含这些拓扑键的节点评分。 这可能导致在使用默认拓扑约束时，其行为与原来的 `SelectorSpread` 插件的默认行为不同。 如果你的节点不会 **同时** 设置 `kubernetes.io/hostname` 和 `topology.kubernetes.io/zone` 标签， 你应该定义自己的约束而不是使用 Kubernetes 的默认约束。 {{< /note >}} <!-- If you don't want to use the default Pod spreading constraints for your cluster, you can disable those defaults by setting `defaultingType` to `List` and leaving empty `defaultConstraints` in the `PodTopologySpread` plugin configuration: --> 如果你不想为集群使用默认的 Pod 分布约束，你可以通过设置 `defaultingType` 参数为 `List`， 并将 `PodTopologySpread` 插件配置中的 `defaultConstraints` 参数置空来禁用默认 Pod 分布约束： ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta3 kind: KubeSchedulerConfiguration profiles: - schedulerName: default-scheduler pluginConfig: - name: PodTopologySpread args: defaultConstraints: [] defaultingType: List ``` <!-- ## Comparison with podAffinity and podAntiAffinity {#comparison-with-podaffinity-podantiaffinity} In Kubernetes, [inter-Pod affinity and anti-affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity) control how Pods are scheduled in relation to one another - either more packed or more scattered. `podAffinity` : attracts Pods; you can try to pack any number of Pods into qualifying topology domain(s) `podAntiAffinity` : repels Pods. If you set this to `requiredDuringSchedulingIgnoredDuringExecution` mode then only a single Pod can be scheduled into a single topology domain; if you choose `preferredDuringSchedulingIgnoredDuringExecution` then you lose the ability to enforce the constraint. --> ## 比较 podAffinity 和 podAntiAffinity {#comparison-with-podaffinity-podantiaffinity} 在 Kubernetes 中，Pod 间亲和性和反亲和性控制 Pod 彼此的调度方式（更密集或更分散）。 对于 `podAffinity`：吸引 Pod；你可以尝试将任意数量的 Pod 集中到符合条件的拓扑域中。 对于 `podAntiAffinity`：驱逐 Pod。如果将此设为 `requiredDuringSchedulingIgnoredDuringExecution` 模式， 则只有单个 Pod 可以调度到单个拓扑域；如果你选择 `preferredDuringSchedulingIgnoredDuringExecution`， 则你将丢失强制执行此约束的能力。 <!-- For finer control, you can specify topology spread constraints to distribute Pods across different topology domains - to achieve either high availability or cost-saving. This can also help on rolling update workloads and scaling out replicas smoothly. For more context, see the [Motivation](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/895-pod-topology-spread#motivation) section of the enhancement proposal about Pod topology spread constraints. --> 要实现更细粒度的控制，你可以设置拓扑分布约束来将 Pod 分布到不同的拓扑域下，从而实现高可用性或节省成本。 这也有助于工作负载的滚动更新和平稳地扩展副本规模。 有关详细信息，请参阅有关 Pod 拓扑分布约束的增强倡议的 [动机](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/895-pod-topology-spread#motivation)一节。 <!-- ## Known limitations - There's no guarantee that the constraints remain satisfied when Pods are removed. For example, scaling down a Deployment may result in imbalanced Pods distribution. You can use a tool such as the [Descheduler](https://github.com/kubernetes-sigs/descheduler) to rebalance the Pods distribution. - Pods matched on tainted nodes are respected. See [Issue 80921](https://github.com/kubernetes/kubernetes/issues/80921). --> ## 已知局限性 {#known-limitations} - 当 Pod 被移除时，无法保证约束仍被满足。例如，缩减某 Deployment 的规模时，Pod 的分布可能不再均衡。 你可以使用 [Descheduler](https://github.com/kubernetes-sigs/descheduler) 来重新实现 Pod 分布的均衡。 - 具有污点的节点上匹配的 Pod 也会被统计。 参考 [Issue 80921](https://github.com/kubernetes/kubernetes/issues/80921)。 <!-- - The scheduler doesn't have prior knowledge of all the zones or other topology domains that a cluster has. They are determined from the existing nodes in the cluster. This could lead to a problem in autoscaled clusters, when a node pool (or node group) is scaled to zero nodes, and you're expecting the cluster to scale up, because, in this case, those topology domains won't be considered until there is at least one node in them. You can work around this by using an cluster autoscaling tool that is aware of Pod topology spread constraints and is also aware of the overall set of topology domains. --> - 该调度器不会预先知道集群拥有的所有可用区和其他拓扑域。 拓扑域由集群中存在的节点确定。在自动扩缩的集群中，如果一个节点池（或节点组）的节点数量缩减为零， 而用户正期望其扩容时，可能会导致调度出现问题。 因为在这种情况下，调度器不会考虑这些拓扑域，因为其中至少有一个节点。 你可以通过使用感知 Pod 拓扑分布约束并感知整个拓扑域集的集群自动扩缩工具来解决此问题。 ## {{% heading \"whatsnext\" %}} <!-- - The blog article [Introducing PodTopologySpread](/blog/2020/05/introducing-podtopologyspread/) explains `maxSkew` in some detail, as well as covering some advanced usage examples. - Read the [scheduling](/docs/reference/kubernetes-api/workload-resources/pod-v1/#scheduling) section of the API reference for Pod. --> - 博客：[PodTopologySpread 介绍](/blog/2020/05/introducing-podtopologyspread/)详细解释了 `maxSkew`， 并给出了一些进阶的使用示例。 - 阅读针对 Pod 的 API 参考的 [调度](/zh-cn/docs/reference/kubernetes-api/workload-resources/pod-v1/#scheduling)一节。 </ins>"}
{"_id":"q-en-website-1b20ff615eb779ee53f3bd556c29cdaad9359f34552620f24754c2469d6e1780","text":"<ins> --- title: クラウドプロバイダー content_type: concept weight: 30 --- <!-- overview --> このページでは、特定のクラウドプロバイダーで実行されているKubernetesを管理する方法について説明します。 <!-- body --> ### kubeadm [kubeadm](/ja/docs/reference/setup-tools/kubeadm/kubeadm/)は、Kubernetesクラスターを作成する選択肢として人気があります。 kubeadmには、クラウドプロバイダーの設定情報を指定する設定オプションがあります。 例えば、典型的なインツリークラウドプロバイダーは、以下のようにkubeadmを使用して設定することができます。 ```yaml apiVersion: kubeadm.k8s.io/v1beta2 kind: InitConfiguration nodeRegistration: kubeletExtraArgs: cloud-provider: \"openstack\" cloud-config: \"/etc/kubernetes/cloud.conf\" --- apiVersion: kubeadm.k8s.io/v1beta2 kind: ClusterConfiguration kubernetesVersion: v1.13.0 apiServer: extraArgs: cloud-provider: \"openstack\" cloud-config: \"/etc/kubernetes/cloud.conf\" extraVolumes: - name: cloud hostPath: \"/etc/kubernetes/cloud.conf\" mountPath: \"/etc/kubernetes/cloud.conf\" controllerManager: extraArgs: cloud-provider: \"openstack\" cloud-config: \"/etc/kubernetes/cloud.conf\" extraVolumes: - name: cloud hostPath: \"/etc/kubernetes/cloud.conf\" mountPath: \"/etc/kubernetes/cloud.conf\" ``` 典型的なインツリークラウドプロバイダーは、通常、[kube-apiserver](/ja/docs/reference/command-line-tools-reference/kube-apiserver/)および[kube-controller-manager](ja//docs/reference/command-line-tools-reference/kube-controller-manager/)、[kubelet](/ja/docs/reference/command-line-tools-reference/kubelet/)のコマンドラインで指定される`--cloud-provider`と`--cloud-config`の両方が必要です。 プロバイダーごとに`--cloud-config`で指定されるファイルの内容についても、以下に記載します。 すべての外部クラウドプロバイダーについては、以下の見出しに列挙されている個々のリポジトリーの案内に従ってください。または[すべてのリポジトリーのリスト](https://github.com/kubernetes?q=cloud-provider-&type=&language=)もご覧ください。 ## AWS ここでは、Amazon Web ServicesでKubernetesを実行する際に使用できるすべての設定について説明します。 この外部クラウドプロバイダーを利用したい場合、[kubernetes/cloud-provider-aws](https://github.com/kubernetes/cloud-provider-aws#readme)リポジトリーを参照してください。 ### ノード名 AWSクラウドプロバイダーは、AWSインスタンスのプライベートDNS名をKubernetesのNodeオブジェクトの名前として使用します。 ### ロードバランサー 以下のようにアノテーションを設定することで、[外部ロードバランサー](/ja/docs/tasks/access-application-cluster/create-external-load-balancer/)をAWS上で特定の機能を利用するように構成できます。 ```yaml apiVersion: v1 kind: Service metadata: name: example namespace: kube-system labels: run: example annotations: service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:xx-xxxx-x:xxxxxxxxx:xxxxxxx/xxxxx-xxxx-xxxx-xxxx-xxxxxxxxx #replace this value service.beta.kubernetes.io/aws-load-balancer-backend-protocol: http spec: type: LoadBalancer ports: - port: 443 targetPort: 5556 protocol: TCP selector: app: example ``` AWSのロードバランサーサービスには、_アノテーション_ を使ってさまざまな設定を適用することができます。以下では、AWS ELBでサポートされているアノテーションについて説明します。 * `service.beta.kubernetes.io/aws-load-balancer-access-log-emit-interval`: アクセスログの送信間隔を指定するために使用します。 * `service.beta.kubernetes.io/aws-load-balancer-access-log-enabled`: アクセスログを有効または無効にするためにサービスで使用します。 * `service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-name`: アクセスログ用のs3バケット名を指定するために使用します。 * `service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-prefix`: アクセスログ用のs3バケットのプレフィックスを指定するために使用します。 * `service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags`: ELBに追加タグとして記録されるキーとバリューのペアのコンマ区切りリストとして指定するためにサービスで使用します。例えば、`\"Key1=Val1,Key2=Val2,KeyNoVal1=,KeyNoVal2\"`のように指定できます。 * `service.beta.kubernetes.io/aws-load-balancer-backend-protocol`: リスナーの背後にあるバックエンド(Pod)が使用するプロトコルを指定するためにサービスで使用します。`http`(デフォルト)または`https`を指定すると、接続を終端してヘッダーを解析するHTTPSリスナーが生成されます。`ssl`または`tcp`を指定すると、「生の」SSLリスナーが使われます。`http`を指定して`aws-load-balancer-ssl-cert`を使わない場合は、HTTPリスナーが使われます。 * `service.beta.kubernetes.io/aws-load-balancer-ssl-cert`: セキュアなリスナーを要求するためにサービスで使用します。値は有効な証明書のARNです。詳細は、[ELBリスナーの設定](https://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-listener-config.html)を参照してください。CertARNは、IAMまたはCM証明書のARNで、例えば`arn:aws:acm:us-east-1:123456789012:certificate/12345678-1234-1234-1234-123456789012`のようになります。 * `service.beta.kubernetes.io/aws-load-balancer-connection-draining-enabled`: 接続ドレインを有効または無効にするためにサービスで使用します。 * `service.beta.kubernetes.io/aws-load-balancer-connection-draining-timeout`: 接続ドレインのタイムアウトを指定するためにサービスで使用します。 * `service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout`: アイドル接続タイムアウトを指定するためにサービスで使用します。 * `service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled`: クロスゾーン負荷分散を有効または無効にするためにサービスで使用されます。 * `service.beta.kubernetes.io/aws-load-balancer-security-groups`: 作成されたELBに追加するセキュリティーグループを指定するために使用します。これは、以前にELBに割り当てられた他のすべてのセキュリティーグループを置き換えます。ここで定義されたセキュリティーグループは、サービス間で共有してはいけません。 * `service.beta.kubernetes.io/aws-load-balancer-extra-security-groups`: 作成されたELBに加える追加のセキュリティーグループを指定するためにサービスで使用します。 * `service.beta.kubernetes.io/aws-load-balancer-internal`: 内部ELBが必要であることを示すためにサービスで使用します。 * `service.beta.kubernetes.io/aws-load-balancer-proxy-protocol`: ELB上でプロキシープロトコルを有効にするためにサービスで使用します。現在は、すべてのELBバックエンドでプロキシープロトコルを有効にすることを意味する`*`という値しか受け付けません。将来的には、特定のバックエンドでのみプロキシープロトコルを設定できるように調整できます。 * `service.beta.kubernetes.io/aws-load-balancer-ssl-ports`: SSL/HTTPSリスナーを使用するポートのコンマ区切りリストを指定するためにサービスで使用します。デフォルトは`*`(すべて)です。 AWSのアノテーションの情報は、[aws.go](https://github.com/kubernetes/legacy-cloud-providers/blob/master/aws/aws.go)のコメントから引用しています。 ## Azure この外部クラウドプロバイダーを利用したい場合、[kubernetes/cloud-provider-azure](https://github.com/kubernetes/cloud-provider-azure#readme)リポジトリーを参照してください。 ### ノード名 Azureクラウドプロバイダーは、ノードのホスト名(kubeletで決定されたもの、または`--hostname-override`で上書きされたもの)を、Kubernetes Nodeオブジェクトの名前として使用します。 Kubernetesノード名は、Azure VM名と一致しなければならないことに注意してください。 ## CloudStack この外部クラウドプロバイダーを利用したい場合、[apache/cloudstack-kubernetes-provider](https://github.com/apache/cloudstack-kubernetes-provider)リポジトリーを参照してください。 ### ノード名 CloudStackクラウドプロバイダーは、ノードのホスト名(kubeletで決定されたもの、または`--hostname-override`で上書きされたもの)を、Kubernetes Nodeオブジェクトの名前として使用します。 Kubernetesノード名は、CloudStack VM名と一致しなければならないことに注意してください。 ## GCE この外部クラウドプロバイダーを利用したい場合、[kubernetes/cloud-provider-gcp](https://github.com/kubernetes/cloud-provider-gcp#readme)リポジトリーを参照してください。 ### ノード名 GCEクラウドプロバイダーは、ノードのホスト名(kubeletで決定されたもの、または`--hostname-override`で上書きされたもの)を、Kubernetes Nodeオブジェクトの名前として使用します。 Kubernetesノード名の最初のセグメントは、GCEインスタンス名と一致しなければならないことに注意してください。例えば、`kubernetes-node-2.c.my-proj.internal`という名前のノードは、`kubernetes-node-2`という名前のインスタンスに対応していなければなりません。 ## HUAWEI CLOUD この外部クラウドプロバイダーを利用したい場合、[kubernetes-sigs/cloud-provider-huaweicloud](https://github.com/kubernetes-sigs/cloud-provider-huaweicloud)リポジトリーを参照してください。 ### ノード名 HUAWEI CLOUDプロバイダーは、ノードのプライベートIPアドレスをKubernetesノード名として使用します。 ノードでkubeletを開始するときは、必ず`--hostname-override=<node private IP>`を指定してください。 ## OpenStack ここでは、OpenStackでKubernetesを実行する際に使用できるすべての設定について説明します。 この外部クラウドプロバイダーを利用したい場合、[kubernetes/cloud-provider-openstack](https://github.com/kubernetes/cloud-provider-openstack#readme)リポジトリーを参照してください。 ### ノード名 OpenStackクラウドプロバイダーは、インスタンス名(OpenStackのメタデータで決定されたもの)を、Kubernetes Nodeオブジェクトの名前として使用します。 インスタンス名は必ず、Kubernetesノード名は、CloudStack VM名と一致しなければならないことに注意してください。 kubeletがNodeオブジェクトを正常に登録できるように、インスタンス名は有効なKubernetesノード名である必要があります。 ### サービス KubernetesのOpenStackクラウドプロバイダーの実装では、利用可能な場合、基盤となるクラウドからこれらのOpenStackのサービスの使用をサポートします。 | サービス名                 | APIバージョン    | 必須か    | |--------------------------|----------------|----------| | Block Storage (Cinder)   | V1†, V2, V3    | No       | | Compute (Nova)           | V2             | No       | | Identity (Keystone)      | V2‡,  V3       | Yes      | | Load Balancing (Neutron) | V1§, V2        | No       | | Load Balancing (Octavia) | V2             | No       | † Block Storage V1 APIのサポートは非推奨ですが、Kubernetes 1.9ではBlock Storage V3 APIのサポートが追加されました。 ‡ Identity V2 APIのサポートは非推奨となり、将来のリリースでプロバイダーから削除される予定です。「Queens」のリリース時点で、OpenStackはIdentity V2 APIを公開しません。 § Load Balancing V1 APIのサポートは、Kubernetes 1.9で削除されました。 サービスディスカバリーは、プロバイダー設定で提供される`auth-url`を使用して、OpenStack Identity(Keystone)が管理するサービスカタログを一覧表示することで実現されます。 プロバイダーは、Keystone以外のOpenStackサービスが利用できなくなった場合には、機能を緩やかに低下させ、影響を受ける機能のサポートを放棄します。 特定の機能は、基盤となるクラウドでNeutronが公開している拡張機能のリストに基づいて有効または無効にされます。 ### cloud.conf Kubernetesはcloud.confというファイルを介して、OpenStackとのやりとり方法を知っています。 これは、KubernetesにOpenStack認証エンドポイントの認証情報と場所を提供するファイルです。 ファイル内に以下の詳細を指定することで、cloud.confファイルを作成できます。 #### 典型的な設定 以下の設定例は、最も頻繁に設定が必要な値に関するものです。 プロバイダーをOpenStackクラウドのKeystoneエンドポイントに指定し、そのエンドポイントでの認証方法の詳細を提供し、さらにロードバランサーを設定します。 ```yaml [Global] username=user password=pass auth-url=https://<keystone_ip>/identity/v3 tenant-id=c869168a828847f39f7f06edd7305637 domain-id=2a73b8f597c04551a0fdc8e95544be8a [LoadBalancer] subnet-id=6937f8fa-858d-4bc9-a3a5-18d2c957166a ``` ##### グローバル これらのOpenStackプロバイダーの設定オプションは、グローバル設定に関連しており、`cloud.conf`ファイルの`[Global]`セクションに記述する必要があります。 * `auth-url`(必死): 認証に使用するKeystone APIのURLです。OpenStackのコントロールパネルでは、Access and Security > API Access > Credentialsで確認できます。 * `username`(必須): Keystoneに設定されている有効なユーザーのユーザー名を参照します。 * `password`(必須): Keystoneで設定された有効なユーザーのパスワードを参照します。 * `tenant-id`(必須): リソースを作成するプロジェクトのIDを指定するために使用します。 * `tenant-name`(任意): リソースを作成するプロジェクトの名前を指定します。 * `trust-id`(任意): 認証に使用するtrustの識別子を指定するために使用します。trustは、ユーザー(委託者)が他のユーザー(受託者)に役割を委譲したり、受託者が委託者になりすますことを許可したりする権限を表します。利用可能なtrustは、Keystone APIの`/v3/OS-TRUST/trusts`エンドポイントの下にあります。 * `domain-id`(任意): ユーザーが所属するドメインのIDを指定するために使用します。 * `domain-name`(任意): ユーザーが所属するドメイン名を指定するために使用します。 * `region`(任意): マルチリージョンのOpenStackクラウド上で実行する際に使うリージョンの識別子を指定するために使用します。リージョンはOpenStackデプロイメントの一般的な区分です。リージョンには厳密な地理的な意味合いはありませんが、デプロイメントでは`us-east`のような地理的な名前をリージョンの識別子に使うことができます。利用可能なリージョンはKeystone APIの`/v3/regions`エンドポイントの下にあります。 * `ca-file`(任意): カスタムCAファイルのパスを指定するために使用します。 テナントをプロジェクトに変更するKeystone V3を使用している場合、`tenant-id`の値は自動的にAPIのプロジェクト構造体にマッピングされます。 ##### ロードバランサー これらのOpenStackプロバイダーの設定オプションは、ロードバランサー設定に関連しており、`cloud.conf`ファイルの`[LoadBalancer]`セクションに記述する必要があります。 * `lb-version`(任意): 自動バージョン検出を上書きするために使用します。有効な値は`v1`または`v2`です。値が指定されていない場合、自動検出は基盤となるOpenStackクラウドが公開するサポートバージョンのうち、最も高いものを選択します。 * `use-octavia`(任意): Octavia LBaaS V2サービスカタログエンドポイントを探して、利用するかどうかを決定するために使用します。有効な値は`true`または`false`です。`true`が指定され、Octaiva LBaaS V2エントリーが見つからなかった場合、プロバイダーはフォールバックして代わりにNeutron LBaaS V2エンドポイントを見つけようとします。デフォルト値は`false` です。 * `subnet-id`(任意): ロードバランサーを作成したいサブネットのIDを指定します。Network > Networksにあります。サブネットを取得するには、それぞれのネットワークをクリックします。 * `floating-network-id`(任意): 指定した場合、ロードバランサーのフローティングIPを作成します。 * `lb-method`(任意): ロードバランサープールのメンバー間で負荷分散させるアルゴリズムを指定するために使用します。値には`ROUND_ROBIN`、`LEAST_CONNECTIONS`、`SOURCE_IP`を指定できます。何も指定しない場合のデフォルトの動作は`ROUND_ROBIN` です。 * `lb-provider`(任意): ロードバランサーのプロバイダーを指定するために使用します。指定しない場合は、Neutronで設定されたデフォルトのプロバイダサービスが使用されます。 * `create-monitor`(任意): Neutronロードバランサーのヘルスモニターを作成するかどうかを表します。有効な値は`true`と`false`で、デフォルト値は`false`です。`true`を指定した場合は、`monitor-delay`、`monitor-timeout`、`monitor-max-retries`も設定しなければなりません。 * `monitor-delay`(任意): ロードバランサーのメンバーにプローブを送信するまでの時間です。有効な時間単位を指定してください。有効な時間単位は\"ns\"、\"us\"(または\"μs\")、\"ms\"、\"s\"、\"m\"、\"h\"です。 * `monitor-timeout`(任意): モニタリングがタイムアウトする前にpingの応答を待つための最大の時間です。この値はdelay値よりも小さくする必要があります。有効な時間単位を指定してください。有効な時間単位は\"ns\"、\"us\"(または\"μs\")、\"ms\"、\"s\"、\"m\"、\"h\"です。 * `monitor-max-retries`(任意): ロードバランサーメンバーのステータスをINACTIVEに変更する前に許容されるpingの失敗の数です。1から10の間の数値でなければなりません。 * `manage-security-groups`(任意): ロードバランサーがセキュリティーグループのルールを自動的に管理するかどうかを決定します。有効な値は`true`と`false`で、デフォルト値は`false`です。`true`を指定した場合は、`node-security-group`も指定しなければなりません。 * `node-security-group`(任意): 管理するセキュリティーグループのIDです。 ##### ブロックストレージ これらのOpenStackプロバイダーの設定オプションは、ブロックストレージ設定に関連しており、`cloud.conf`ファイルの`[BlockStorage]`セクションに記述する必要があります。 * `bs-version`(任意): 自動バージョン検出を上書きするために使用します。有効な値は`v1`、`v2`、`v3`、`auto`です。`auto`が指定された場合、自動検出は基盤となるOpenStackクラウドが公開するサポートバージョンのうち、最も高いものを選択します。何も指定しない場合のデフォルト値は`auto`です。 * `trust-device-path`(任意): ほとんどのシナリオでは、Cinderが提供するブロックデバイス名(例: `/dev/vda`)は信頼できません。このブール値はこの動作をトグルします。`true`に設定すると、Cinderが提供するブロックデバイス名を信頼することになります。デフォルト値の`false`は、シリアル番号と`/dev/disk/by-id`のマッピングに基づいてデバイスのパスを検出します。 * `ignore-volume-az`(任意): Cinderボリュームをアタッチする際のアベイラビリティーゾーンの使用に影響を与えます。NovaとCinderのアベイラビリティーゾーンが異なる場合は、`true`に設定する必要があります。これは、Novaのアベイラビリティーゾーンが多くあるにも関わらず、Cinderのアベイラビリティーゾーンが1つしかない場合によく見られます。デフォルト値は以前のリリースで使用されていた動作を維持するために`false`になっていますが、将来的には変更される可能性があります。 * `node-volume-attach-limit`(任意): ノードにアタッチできるボリュームの最大数で、デフォルトはCinderの256です。 エンドポイントを区別するためにポートではなくパスを使用しているOpenStackデプロイメントにおいて、Kubernetesのバージョン1.8以下をデプロイする際、明示的に`bs-version`パラメーターの設定が必要な場合があります。パスベースのエンドポイントは`http://foo.bar/volume`の形式であり、ポートベースのエンドポイントは`http://foo.bar:xxx`の形式です。 パスベースのエンドポイントを使う環境で、Kubernetesが古い自動検出ロジックを使用している場合、ボリュームの切り離しを試みると`BS API version autodetection failed.`というエラーが返されます。この問題を回避するには、クラウドプロバイダー設定に以下のように追記することで、Cinder APIバージョン2を強制的に使用することができます。 ```yaml [BlockStorage] bs-version=v2 ``` ##### メタデータ これらのOpenStackプロバイダーの設定オプションは、メタデータ設定に関連しており、`cloud.conf`ファイルの`[Metadata]`セクションに記述する必要があります。 * `search-order`(任意): この設定のキーは、プロバイダーが実行するインスタンスに関連するメタデータの取得方法に影響します。デフォルト値の`configDrive,metadataService`について、プロバイダーは、コンフィグドライブが利用可能な場合は最初にインスタンスに関連するメタデータをそこから取得し、次にメタデータサービスから取得します。代替値は以下の通りです。 * `configDrive` - コンフィグドライブからのみ、インスタンスのメタデータを取得します。 * `metadataService` - メタデータサービスからのみ、インスタンスのメタデータを取得します。 * `metadataService,configDrive` - 最初にメタデータサービスからインスタンスのメタデータを取得し、次にコンフィグドライブから取得します。 コンフィグドライブ上のメタデータは時間の経過とともに陳腐化する可能性がありますが、メタデータサービスは常に最新の情報を提供するため、この動作を調整するのが望ましいです。しかし、すべてのOpenStackクラウドがコンフィグドライブとメタデータサービスの両方を提供しているわけではなく、どちらか一方しか利用できない場合もあるため、デフォルトでは両方をチェックするようになっています。 ##### ルート これらのOpenStackプロバイダーの設定オプションは、[kubenet](/ja/docs/concepts/cluster-administration/network-plugins/#kubenet)のKubernetesネットワークプラグインに関連しており、`cloud.conf`ファイルの`[Route]`セクションに記述する必要があります。 * `router-id`(任意): 基盤となるクラウドのNeutronデプロイメントが`extraroutes`拡張機能をサポートしている場合は、`router-id`を使用してルートを追加するルーターを指定します。選択したルーターは、クラスターノードを含むプライベートネットワークにまたがっていなければなりません(通常、ノードネットワークは1つしかないので、この値はノードネットワークのデフォルトルーターになります)。この値は、OpenStackで[kubenet](/docs/concepts/cluster-administration/network-plugins/#kubenet)を使用するために必要です。 ## OVirt ### ノード名 OVirtクラウドプロバイダーは、ノードのホスト名(kubeletで決定されたもの、または`--hostname-override`で上書きされたもの)を、Kubernetes Nodeオブジェクトの名前として使用します。 Kubernetesノード名は、VMのFQDN(`<vm><guest_info><fqdn>...</fqdn></guest_info></vm>`の下でOVirtによって報告されたもの)と一致しなければならないことに注意してください。 ## Photon ### ノード名 Photonクラウドプロバイダーは、ノードのホスト名(kubeletで決定されたもの、または`--hostname-override`で上書きされたもの)を、Kubernetes Nodeオブジェクトの名前として使用します。 Kubernetesノード名はPhoton VM名と一致しなければならないことに注意してください(もしくは、`--cloud-config`で`overrideIP`がtrueに設定されている場合は、Kubernetesノード名はPhoton VMのIPアドレスと一致しなければなりません)。 ## vSphere {{< tabs name=\"vSphere cloud provider\" >}} {{% tab name=\"vSphere 6.7U3以上\" %}} vSphere 6.7U3以上のすべてのvSphereデプロイメントでは、[external vSphere cloud provider](https://github.com/kubernetes/cloud-provider-vsphere)と[vSphere CSI driver](https://github.com/kubernetes-sigs/vsphere-csi-driver)の使用を推奨します。クイックスタートガイドについては、[Deploying a Kubernetes Cluster on vSphere with CSI and CPI](https://cloud-provider-vsphere.sigs.k8s.io/tutorials/kubernetes-on-vsphere-with-kubeadm.html)を参照してください。 {{% /tab %}} {{% tab name=\"vSphere 6.7U3未満\" %}} vSphere 6.7U3未満を実行している場合は、インツリーのvSphereクラウドプロバイダーを推奨します。クイックスタートガイドについては、[Running a Kubernetes Cluster on vSphere with kubeadm](https://cloud-provider-vsphere.sigs.k8s.io/tutorials/k8s-vcp-on-vsphere-with-kubeadm.html)を参照してください。 {{% /tab %}} {{< /tabs >}} vSphereクラウドプロバイダーの詳細なドキュメントについては、[vSphereクラウドプロバイダーのドキュメントサイト](https://cloud-provider-vsphere.sigs.k8s.io)を参照してください。 ## IBM Cloud Kubernetes Service ### コンピュートノード IBM Cloud Kubernetes Serviceプロバイダーを使用することで、仮想ノードと物理ノード(ベアメタル)を混在させたクラスターを単一のゾーン、またはリージョン内の複数のゾーンにまたがって作成することができます。詳細については、[Planning your cluster and worker node setup](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodes)を参照してください。 Kubernetes Nodeオブジェクトの名前は、IBM Cloud Kubernetes ServiceワーカーノードインスタンスのプライベートIPアドレスです。 ### ネットワーク IBM Cloud Kubernetes Serviceプロバイダーは、高品質なネットワークパフォーマンスとノードのネットワーク分離のためにVLANを提供します。カスタムファイアウォールやCalicoネットワークポリシーを設定して、クラスターにセキュリティーの追加レイヤーを加えたり、VPNを使用してクラスターをオンプレミスデータセンターに接続したりすることができます。詳細については、[Planning your cluster network setup](https://cloud.ibm.com/docs/containers?topic=containers-plan_clusters)を参照してください。 アプリケーションをパブリックまたはクラスター内で公開するには、NodePort、LoadBalancer、Ingressサービスを利用できます。また、Ingressアプリケーションのロードバランサーをアノテーションでカスタマイズすることもできます。詳細については、[Choosing an app exposure service](https://cloud.ibm.com/docs/containers?topic=containers-cs_network_planning#cs_network_planning)を参照してください。 ### ストレージ IBM Cloud Kubernetes Serviceプロバイダーは、Kubernetesネイティブの永続ボリュームを活用して、ユーザーがファイル、ブロック、およびクラウドオブジェクトストレージをアプリケーションにマウントできるようにします。また、データの永続ストレージにDatabase as a Serviceやサードパーティーのアドオンを使用することもできます。詳しくは、[Planning highly available persistent storage](https://cloud.ibm.com/docs/containers?topic=containers-storage_planning#storage_planning)を参照してください。 ## Baidu Cloud Container Engine ### ノード名 Baiduクラウドプロバイダーは、ノードのプライベートIPアドレス(kubeletで決定されたもの、または`--hostname-override`で上書きされたもの)を、Kubernetes Nodeオブジェクトの名前として使用します。 Kubernetesノード名はBaidu VMのプライベートIPと一致しなければならないことに注意してください。 ## Tencent Kubernetes Engine この外部クラウドプロバイダーを利用したい場合、[TencentCloud/tencentcloud-cloud-controller-manager](https://github.com/TencentCloud/tencentcloud-cloud-controller-manager)リポジトリーを参照してください。 ### ノード名 Baiduクラウドプロバイダーは、ノードのホスト名(kubeletで決定されたもの、または`--hostname-override`で上書きされたもの)を、Kubernetes Nodeオブジェクトの名前として使用します。 Kubernetesノード名はTencent VMのプライベートIPと一致しなければならないことに注意してください。 ## Alibaba Cloud Kubernetes この外部クラウドプロバイダーを利用したい場合、[kubernetes/cloud-provider-alibaba-cloud](https://github.com/kubernetes/cloud-provider-alibaba-cloud)リポジトリーを参照してください。 ### ノード名 Alibaba Cloudではノード名の書式は必要ありませんが、kubeletでは`--provider-id=${REGION_ID}.${INSTANCE_ID}`を追加する必要があります。パラメーター`${REGION_ID}`はKubernetesのリージョンのIDを、`${INSTANCE_ID}`はAlibaba ECS(Elastic Compute Service)のIDを表します。 ### ロードバランサー [アノテーション](https://www.alibabacloud.com/help/en/doc-detail/86531.htm)を設定することで、Alibaba Cloudの特定の機能を使用するように外部のロードバランサーを設定できます。 </ins>"}
{"_id":"q-en-website-1b319bee184e279ba2e9a07490955fc847f7d2746626bff7bfb4bf51c01c7e2b","text":"* [kube-controller-manager](/docs/reference/command-line-tools-reference/kube-controller-manager/) - Kubernetesに同梱された、コアのコントロールループを埋め込むデーモンです。 * [kube-proxy](/docs/reference/command-line-tools-reference/kube-proxy/) - 単純なTCP/UDPストリームのフォワーディングや、一連のバックエンド間でTCP/UDPのラウンドロビンでのフォワーディングを実行できます。 * [kube-scheduler](/docs/reference/command-line-tools-reference/kube-scheduler/) - 可用性、パフォーマンス、およびキャパシティを管理するスケジューラーです。 <del> * [kube-schedulerポリシー](/docs/reference/scheduling/policies) * [kube-schedulerプロファイル](/docs/reference/scheduling/profiles) </del> <ins> * [kube-schedulerポリシー](/ja/docs/reference/scheduling/policies) * [Schedulerプロファイル](/ja/docs/reference/scheduling/config#プロファイル) * コントロールプレーンとワーカーノードで開いておくべき[ポートとプロトコル](/ja/docs/reference/networking/ports-and-protocols/)の一覧 ## 設定APIリファレンス このセクションでは、Kubernetesのコンポーネントやツールを設定するのに使われている「未公開」のAPIのドキュメントをまとめています。 クラスターを使ったり管理したりするユーザーやオペレーターにとって必要不可欠ではありますが、これらのAPIの大半はRESTful方式のAPIサーバーでは提供されません。 * [kubeconfig (v1)](/docs/reference/config-api/kubeconfig.v1/) * [kube-apiserver admission (v1)](/docs/reference/config-api/apiserver-admission.v1/) * [kube-apiserver configuration (v1alpha1)](/docs/reference/config-api/apiserver-config.v1alpha1/)および * [kube-apiserver configuration (v1beta1)](/docs/reference/config-api/apiserver-config.v1beta1/)および [kube-apiserver configuration (v1)](/docs/reference/config-api/apiserver-config.v1/) * [kube-apiserver encryption (v1)](/docs/reference/config-api/apiserver-encryption.v1/) * [kube-apiserver event rate limit (v1alpha1)](/docs/reference/config-api/apiserver-eventratelimit.v1alpha1/) * [kubelet configuration (v1alpha1)](/docs/reference/config-api/kubelet-config.v1alpha1/)および [kubelet configuration (v1beta1)](/docs/reference/config-api/kubelet-config.v1beta1/) [kubelet configuration (v1)](/docs/reference/config-api/kubelet-config.v1/) * [kubelet credential providers (v1alpha1)](/docs/reference/config-api/kubelet-credentialprovider.v1alpha1/)、 [kubelet credential providers (v1beta1)](/docs/reference/config-api/kubelet-credentialprovider.v1beta1/)および [kubelet credential providers (v1)](/docs/reference/config-api/kubelet-credentialprovider.v1/) * [kube-scheduler configuration (v1beta2)](/docs/reference/config-api/kube-scheduler-config.v1beta2/)、 [kube-scheduler configuration (v1beta3)](/docs/reference/config-api/kube-scheduler-config.v1beta3/)および [kube-scheduler configuration (v1)](/docs/reference/config-api/kube-scheduler-config.v1/) * [kube-controller-manager configuration (v1alpha1)](/docs/reference/config-api/kube-controller-manager-config.v1alpha1/) * [kube-proxy configuration (v1alpha1)](/docs/reference/config-api/kube-proxy-config.v1alpha1/) * [`audit.k8s.io/v1` API](/docs/reference/config-api/apiserver-audit.v1/) * [Client authentication API (v1beta1)](/docs/reference/config-api/client-authentication.v1beta1/)および [Client authentication API (v1)](/docs/reference/config-api/client-authentication.v1/) * [WebhookAdmission configuration (v1)](/docs/reference/config-api/apiserver-webhookadmission.v1/) * [ImagePolicy API (v1alpha1)](/docs/reference/config-api/imagepolicy.v1alpha1/) ## kubeadmの設定APIリファレンス * [v1beta3](/docs/reference/config-api/kubeadm-config.v1beta3/) </ins> ## 設計のドキュメント <del> Kubernetesの機能に関する設計ドキュメントのアーカイブです。[Kubernetesアーキテクチャ](https://git.k8s.io/community/contributors/design-proposals/architecture/architecture.md) と[Kubernetesデザイン概要](https://git.k8s.io/community/contributors/design-proposals)から読み始めると良いでしょう。 </del> <ins> Kubernetesの機能に関する設計ドキュメントのアーカイブです。[Kubernetesアーキテクチャ](https://git.k8s.io/community/contributors/design-proposals/architecture/architecture.md) と[Kubernetesデザイン概要](https://git.k8s.io/design-proposals-archive)から読み始めると良いでしょう。 </ins>"}
{"_id":"q-en-website-1b9ef5fab246f59661743e884b7964edd50acb6daf4b05f110846c218022e821","text":"```shell kubectl apply -f services.yaml ``` <ins> 実行結果は下記のようになります。 </ins> ``` service/myservice created service/mydb created"}
{"_id":"q-en-website-1c66ca62b0f1d7cc7a2d0f19a8f6ded05ec0d5818ce0ff527087a0803acfeb5f","text":"`Guaranteed` pods are guaranteed only when requests and limits are specified for all the containers and they are equal. These pods will never be evicted because of another pod's resource consumption. If a system daemon (such as `kubelet`, <del> `docker`, and `journald`) is consuming more resources than were reserved via </del> <ins> and `journald`) is consuming more resources than were reserved via </ins> `system-reserved` or `kube-reserved` allocations, and the node only has `Guaranteed` or `Burstable` pods using less resources than requests left on it, then the kubelet must choose to evict one of these pods to preserve node stability"}
{"_id":"q-en-website-1d93df0b5443343f8a09ddaeda8d38983f8718030eb42036d75144b37a806968","text":"1. Download the latest release with the command: <del> ```bash </del> <ins> {{< tabs name=\"download_convert_binary_linux\" >}} {{< tab name=\"x86-64\" codelang=\"bash\" >}} </ins> curl -LO \"https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl-convert\" <del> ``` </del> <ins> {{< /tab >}} {{< tab name=\"ARM64\" codelang=\"bash\" >}} curl -LO \"https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/arm64/kubectl-convert\" {{< /tab >}} {{< /tabs >}} </ins> 1. Validate the binary (optional) Download the kubectl-convert checksum file: <del> ```bash </del> <ins> {{< tabs name=\"download_convert_checksum_linux\" >}} {{< tab name=\"x86-64\" codelang=\"bash\" >}} </ins> curl -LO \"https://dl.k8s.io/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl-convert.sha256\" <del> ``` </del> <ins> {{< /tab >}} {{< tab name=\"ARM64\" codelang=\"bash\" >}} curl -LO \"https://dl.k8s.io/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/arm64/kubectl-convert.sha256\" {{< /tab >}} {{< /tabs >}} </ins> Validate the kubectl-convert binary against the checksum file:"}
{"_id":"q-en-website-1ed66f9c2f3bb1b4e2f72141c5ab03abcc0e3a2d53a93251ce16479179666237","text":"--- title: Workload <del> id: workloads </del> <ins> id: workload </ins> date: 2019-02-13 full_link: /docs/concepts/workloads/ short_description: >"}
{"_id":"q-en-website-1f0ea27053853e86cc163013d137453c6161d266e136eeee69b8a58972d77de3","text":"The output is similar to this: <del> NAME                      READY   UP-TO-DATE   AVAILABLE   AGE </del> <ins> NAME                   READY   UP-TO-DATE   AVAILABLE   AGE </ins> ... <del> dns-autoscaler            1/1     1            1           ... </del> <ins> kube-dns-autoscaler    1/1     1            1           ... </ins> ... <del> If you see \"dns-autoscaler\" in the output, DNS horizontal autoscaling is </del> <ins> If you see \"kube-dns-autoscaler\" in the output, DNS horizontal autoscaling is </ins> already enabled, and you can skip to [Tuning autoscaling parameters](#tuning-autoscaling-parameters)."}
{"_id":"q-en-website-1f75261602bcd19ea0b8a82fd25920bd8f5bd719824882ab1e6e494a5db9a718","text":"<ins> You need to have shell access to all the nodes, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. </ins>"}
{"_id":"q-en-website-1fa2a87f9d03a046c19d1dd6fffc47313325531440d18afe554b62449579d7f2","text":"<ins> --- title: ConfigMap id: configmap date: 2018-04-12 full_link: /ja/docs/concepts/configuration/configmap/ short_description: > 機密性のないデータをキーと値のペアで保存するために使用されるAPIオブジェクトです。環境変数、コマンドライン引数、またはボリューム内の設定ファイルとして使用できます。 aka: tags: - core-object --- 機密性のないデータをキーと値のペアで保存するために使用されるAPIオブジェクトです。{{< glossary_tooltip text=\"Pod\" term_id=\"pod\" >}}は、環境変数、コマンドライン引数、または{{< glossary_tooltip text=\"ボリューム\" term_id=\"volume\" >}}内の設定ファイルとしてConfigMapを使用できます。 <!--more--> ConfigMapを使用すると、環境固有の設定を{{< glossary_tooltip text=\"コンテナイメージ\" term_id=\"image\" >}}から分離できるため、アプリケーションを簡単に移植できるようになります。 </ins>"}
{"_id":"q-en-website-203f37b200db88b91a4eaa11287ab731a304e7e130d4cc61e721bad6ae63d95a","text":"<ins> --- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: default-deny-egress spec: podSelector: {} policyTypes: - Egress </ins>"}
{"_id":"q-en-website-212e112d3780964d15e7ca0470d7b3c8b7d83fda93d5879b4f7136475d4a4119","text":"We recommend moving this block and the preceding CSS link to the HEAD of your HTML file. */ </style> <br> <del> <br> </del> <div id=\"mc_embed_signup\"> <form action=\"https://kubeweekly.us10.list-manage.com/subscribe/post?u=3885586f8f1175194017967d6&amp;id=11c1b8bcb2\" method=\"post\" id=\"mc-embedded-subscribe-form\" name=\"mc-embedded-subscribe-form\" class=\"validate\" target=\"_blank\" novalidate> <div id=\"mc_embed_signup_scroll\"> <p style=\"font-size: 20px\">{{ T \"main_kubeweekly_baseline\" }}</p> <del> <br /> </del> <input type=\"email\" value=\"\" name=\"EMAIL\" class=\"email\" id=\"mce-EMAIL\" placeholder=\"{{ T \"input_placeholder_email_address\" }}\" aria-label=\"email\" required> <!-- real people should not fill this in and expect good things - do not remove this or risk form bot signups--> <div style=\"position: absolute; left: -5000px;\" aria-hidden=\"true\"><input type=\"text\" name=\"b_3885586f8f1175194017967d6_11c1b8bcb2\" tabindex=\"-1\" value=\"\"></div>"}
{"_id":"q-en-website-2195eb1cb992192de73e64980dbf76386a540d331fea42cf0b16d3904883ca9d","text":"max_line_length = 80 trim_trailing_whitespace = true <ins> [*.md] trim_trailing_whitespace = false </ins> [*.{css,html,js,json,sass,md,mmark,toml,yaml}] indent_style = space indent_size = 2"}
{"_id":"q-en-website-21cf11b49e498fe2b74a12a9f76ff1ebdec69534cc6ced5fb2d2b5fd9e24cb16","text":"} ``` <del> Non-resource paths include: `/api`, `/apis`, `/metrics`, `/resetMetrics`, `/logs`, `/debug`, `/healthz`, `/swagger-ui/`, `/swaggerapi/`, `/ui`, and </del> <ins> Non-resource paths include: `/api`, `/apis`, `/metrics`, `/logs`, `/debug`, `/healthz`, `/livez`, `/openapi/v2`, `/readyz`, and </ins> `/version.` Clients require access to `/api`, `/api/*`, `/apis`, `/apis/*`, and `/version` to discover what resources and versions are present on the server. Access to other non-resource paths can be disallowed without restricting access"}
{"_id":"q-en-website-22c0f22b2b5c1a519d3775645dc4efffec4e776f192786cbc7faee712209fb68","text":"Pod level control groups (cgroups) are based on the effective Pod request and limit, the same as the scheduler. <ins> {{< comment >}} This section also present under [sidecar containers](/docs/concepts/workloads/pods/sidecar-containers/) page. If you're editing this section, change both places. {{< /comment >}} </ins> ### Pod restart reasons"}
{"_id":"q-en-website-22cc306c3156634b7a303125a7673ee8b63ea46d9c120d69d8a17eb0bdea3759","text":"### Metrics <ins> {{< note >}} In versions of Kubernetes before v1.20, the labels `flow_schema` and `priority_level` were inconsistently named `flowSchema` and `priorityLevel`, respectively. If you're running Kubernetes versions v1.19 and earlier, you should refer to the documentation for your version. {{< /note >}} </ins> When you enable the API Priority and Fairness feature, the kube-apiserver exports additional metrics. Monitoring these can help you determine whether your configuration is inappropriately throttling important traffic, or find"}
{"_id":"q-en-website-296fcaf6116c62d075df414be1ba2af36e409f6a99f80b33be79a4f9f198669a","text":"main_menu: true weight: 70 content_type: concept <ins> no_list: true </ins> --- <!-- overview --> 本セクションには、Kubernetesのドキュメントのリファレンスが含まれています。 <!-- body --> ## APIリファレンス <del> * [Kubernetes API概要](/docs/reference/using-api/) - Kubernetes APIの概要です。 * [Kubernetes APIリファレンス {{< latest-version >}}](/docs/reference/generated/kubernetes-api/{{< latest-version >}}/) </del> <ins> * [標準化用語集](/ja/docs/reference/glossary) - Kubernetesの用語の包括的で標準化されたリストです。 * [Kubernetes APIリファレンス](/docs/reference/using-api/) * [Kubernetes {{< param \"version\" >}}の単一ページのAPIリファレンス](/docs/reference/generated/kubernetes-api/{{< param \"version\" >}}/) * [Kubernetes APIの使用](/ja/docs/reference/using-api/) - KubernetesのAPIの概要です。 * [API アクセスコントロール](/docs/reference/access-authn-authz/) - KubernetesがAPIアクセスをどのように制御するかの詳細です。 * [よく知られたラベル、アノテーション、テイント](/docs/reference/labels-annotations-taints/) </ins> <del> ## APIクライアントライブラリー </del> <ins> ## 公式にサポートされているクライアントライブラリー </ins> プログラミング言語からKubernetesのAPIを呼ぶためには、[クライアントライブラリー](/docs/reference/using-api/client-libraries/)を使うことができます。公式にサポートしているクライアントライブラリー:"}
{"_id":"q-en-website-2b645f1714025727ee4c2789a309282e61c5216e6a3616f9b88772518cc20e72","text":"Kubelet auto-discovers these filesystems and ignores other filesystems. Kubelet does not support other configurations. <del> {{<note>}} Some kubelet garbage collection features are deprecated in favor of eviction. For a list of the deprecated features, see [kubelet garbage collection deprecation](/docs/concepts/architecture/garbage-collection/#deprecation). {{</note>}} </del> <ins> Some kubelet garbage collection features are deprecated in favor of eviction: | Existing Flag | New Flag | Rationale | | ------------- | -------- | --------- | | `--image-gc-high-threshold` | `--eviction-hard` or `--eviction-soft` | existing eviction signals can trigger image garbage collection | | `--image-gc-low-threshold` | `--eviction-minimum-reclaim` | eviction reclaims achieve the same behavior | | `--maximum-dead-containers` | | deprecated once old logs are stored outside of container's context | | `--maximum-dead-containers-per-container` | | deprecated once old logs are stored outside of container's context | | `--minimum-container-ttl-duration` | | deprecated once old logs are stored outside of container's context | </ins> ### Eviction thresholds"}
{"_id":"q-en-website-2c0c555c3434db3fe855847dfb2155065ee869b1d9b6ecfa8670fb3766f103b1","text":"If you would like to write a concept page, see <del> [Page Content Types](/docs/home/contribute/style/page-content-types/#concept) </del> <ins> [Page Content Types](/docs/contribute/style/page-content-types/#concept) </ins> for information about the concept page types."}
{"_id":"q-en-website-2c95abf77ef2dee09d081cf4927a5c11b56b162c0a0a6634b8dcaa128b0e73bc","text":"<ins> --- layout: blog title: \"Kubernetes v1.28：可追溯的默认 StorageClass 进阶至 GA\" date: 2023-08-18 slug: retroactive-default-storage-class-ga --- <!-- layout: blog title: \"Kubernetes v1.28: Retroactive Default StorageClass move to GA\" date: 2023-08-18 slug: retroactive-default-storage-class-ga --> <!-- **Author:** Roman Bednář (Red Hat) --> **作者:** Roman Bednář (Red Hat) **译者:** [Michael Yao](https://github.com/windsonsea) (DaoCloud) <!-- Announcing graduation to General Availability (GA) - Retroactive Default StorageClass Assignment in Kubernetes v1.28! --> 可追溯的默认 StorageClass 赋值（Retroactive Default StorageClass Assignment）在 Kubernetes v1.28 中宣布进阶至正式发布（GA）！ <!-- Kubernetes SIG Storage team is thrilled to announce that the \"Retroactive Default StorageClass Assignment\" feature, introduced as an alpha in Kubernetes v1.25, has now graduated to GA and is officially part of the Kubernetes v1.28 release. This enhancement brings a significant improvement to how default [StorageClasses](/docs/concepts/storage/storage-classes/) are assigned to PersistentVolumeClaims (PVCs). --> Kubernetes SIG Storage 团队非常高兴地宣布，在 Kubernetes v1.25 中作为 Alpha 特性引入的 “可追溯默认 StorageClass 赋值” 现已进阶至 GA， 并正式成为 Kubernetes v1.28 发行版的一部分。 这项增强特性极大地改进了默认的 [StorageClasses](/zh-cn/docs/concepts/storage/storage-classes/) 为 PersistentVolumeClaim (PVC) 赋值的方式。 <!-- With this feature enabled, you no longer need to create a default StorageClass first and then a PVC to assign the class. Instead, any PVCs without a StorageClass assigned will now be retroactively updated to include the default StorageClass. This enhancement ensures that PVCs no longer get stuck in an unbound state, and storage provisioning works seamlessly, even when a default StorageClass is not defined at the time of PVC creation. --> 启用此特性后，你不再需要先创建默认的 StorageClass，再创建 PVC 来指定存储类。 现在，未分配 StorageClass 的所有 PVC 都将被自动更新为包含默认的 StorageClass。 此项增强特性确保即使默认的 StorageClass 在 PVC 创建时未被定义， PVC 也不会再滞留在未绑定状态，存储制备工作可以无缝进行。 <!-- ## What changed? The PersistentVolume (PV) controller has been modified to automatically assign a default StorageClass to any unbound PersistentVolumeClaim with the `storageClassName` not set. Additionally, the PersistentVolumeClaim admission validation mechanism within the API server has been adjusted to allow changing values from an unset state to an actual StorageClass name. --> ## 有什么变化？   {#what-changed} PersistentVolume (PV) 控制器已修改为：当未设置 `storageClassName` 时，自动向任何未绑定的 PersistentVolumeClaim 分配一个默认的 StorageClass。此外，API 服务器中的 PersistentVolumeClaim 准入验证机制也已调整为允许将值从未设置状态更改为实际的 StorageClass 名称。 <!-- ## How to use it? As this feature has graduated to GA, there's no need to enable a feature gate anymore. Simply make sure you are running Kubernetes v1.28 or later, and the feature will be available for use. --> ## 如何使用？  {#how-to-use-it} 由于此特性已进阶至 GA，所以不再需要启用特性门控。 只需确保你运行的是 Kubernetes v1.28 或更高版本，此特性即可供使用。 <!-- For more details, read about [default StorageClass assignment](/docs/concepts/storage/persistent-volumes/#retroactive-default-storageclass-assignment) in the Kubernetes documentation. You can also read the previous [blog post](/blog/2023/01/05/retroactive-default-storage-class/) announcing beta graduation in v1.26. --> 有关更多细节，可以查阅 Kubernetes 文档中的[默认 StorageClass 赋值](/zh-cn/docs/concepts/storage/persistent-volumes/#retroactive-default-storageclass-assignment)。 你也可以阅读以前在 v1.26 中宣布进阶至 Beta 的[博客文章](/zh-cn/blog/2023/01/05/retroactive-default-storage-class/)。 <!-- To provide feedback, join our [Kubernetes Storage Special-Interest-Group](https://github.com/kubernetes/community/tree/master/sig-storage) (SIG) or participate in discussions on our [public Slack channel](https://app.slack.com/client/T09NY5SBT/C09QZFCE5). --> 要提供反馈，请加入我们的 [Kubernetes 存储特别兴趣小组](https://github.com/kubernetes/community/tree/master/sig-storage) (SIG) 或参与[公共 Slack 频道](https://app.slack.com/client/T09NY5SBT/C09QZFCE5)上的讨论。 </ins>"}
{"_id":"q-en-website-2ca184619ef4caf0e5cc95e80f5cc4b5d3df8ec5275af5a182e093275d127ce6","text":"<ins> --- title: Kindを使用してKubernetesをインストールする weight: 40 content_type: concept --- <!-- overview --> Kindは、Dockerコンテナをノードとして使用して、ローカルのKubernetesクラスターを実行するためのツールです。 <!-- body --> ## インストール [Kindをインストールする](https://kind.sigs.k8s.io/docs/user/quick-start/)を参照してください。 </ins>"}
{"_id":"q-en-website-2ce02b5e125a9f0426e33b42cb3a04fff0c5f588e26bcdb7a7d4c33842816428","text":"{{< tab name=\"bootstrap-token\" include=\"generated/kubeadm_init_phase_bootstrap-token.md\" />}} {{< /tabs >}} <ins> ## kubeadm init phase kubelet-finialize {#cmd-phase-kubelet-finalize-all} Use the following phase to update settings relevant to the kubelet after TLS bootstrap. You can use the `all` subcommand to run all `kubelet-finalize` phases. {{< tabs name=\"tab-kubelet-finalize\" >}} {{< tab name=\"kublet-finalize\" include=\"generated/kubeadm_init_phase_kubelet-finalize.md\" />}} {{< tab name=\"kublet-finalize-all\" include=\"generated/kubeadm_init_phase_kubelet-finalize_all.md\" />}} {{< tab name=\"kublet-finalize-cert-rotation\" include=\"generated/kubeadm_init_phase_kubelet-finalize_experimental-cert-rotation.md\" />}} {{< /tabs >}} </ins> ## kubeadm init phase addon {#cmd-phase-addon}"}
{"_id":"q-en-website-2d33b3b17748227bc97bdf475e443f48a2212cfafea41b7df878994703ac9415","text":"```shell kubectl get -f myapp.yaml ``` <ins> 実行結果は下記のようになります。 </ins> ``` NAME        READY     STATUS     RESTARTS   AGE myapp-pod   0/1       Init:0/2   0          6m"}
{"_id":"q-en-website-2d4ba3fe1272f449fd8febc84bfa24ecde412fcc5370c7261587b115dcfcc0a6","text":"## {{% heading \"prerequisites\" %}} <del> {{< include \"task-tutorial-prereqs.md\" >}} {{< version-check >}} </del> <ins> {{< include \"task-tutorial-prereqs-node-upgrade.md\" >}} {{< version-check >}} </ins> * Familiarize yourself with [the process for upgrading the rest of your kubeadm cluster](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade). You will want to upgrade the control plane nodes before upgrading your Windows nodes."}
{"_id":"q-en-website-2fc8dbbaf61e6eeef4b0b239b038d93c40e71e1064a063cb727e5aa52a814247","text":"### Weave Net from Weaveworks <del> [Weave Net](https://www.weave.works/products/weave-net/) is a </del> <ins> [Weave Net](https://www.weave.works/oss/net/) is a </ins> resilient and simple to use network for Kubernetes and its hosted applications. Weave Net runs as a [CNI plug-in](https://www.weave.works/docs/net/latest/cni-plugin/) or stand-alone.  In either version, it doesn't require any configuration or extra code"}
{"_id":"q-en-website-32d569d82780a5d083ac97950547930168ab3c01f4c0e721d5f38d5748ea399b","text":"<ins> --- layout: blog title: \"确保准入控制器的安全\" date: 2022-01-19 slug: secure-your-admission-controllers-and-webhooks --- <!-- layout: blog title: \"Securing Admission Controllers\" date: 2022-01-19 slug: secure-your-admission-controllers-and-webhooks --> <!-- **Author:** Rory McCune (Aqua Security) --> **作者:** Rory McCune (Aqua Security) <!-- [Admission control](/docs/reference/access-authn-authz/admission-controllers/) is a key part of Kubernetes security, alongside authentication and authorization. Webhook admission controllers are extensively used to help improve the security of Kubernetes clusters in a variety of ways including restricting the privileges of workloads and ensuring that images deployed to the cluster meet organization’s security requirements. --> [准入控制](/zh/docs/reference/access-authn-authz/admission-controllers/)和认证、授权都是 Kubernetes 安全性的关键部分。 Webhook 准入控制器被广泛用于以多种方式帮助提高 Kubernetes 集群的安全性， 包括限制工作负载权限和确保部署到集群的镜像满足组织安全要求。 <!-- However, as with any additional component added to a cluster, security risks can present themselves. A security risk example is if the deployment and management of the admission controller are not handled correctly. To help admission controller users and designers manage these risks appropriately, the [security documentation](https://github.com/kubernetes/community/tree/master/sig-security#security-docs) subgroup of SIG Security has spent some time developing a [threat model for admission controllers](https://github.com/kubernetes/sig-security/tree/main/sig-security-docs/papers/admission-control). This threat model looks at likely risks which may arise from the incorrect use of admission controllers, which could allow security policies to be bypassed, or even allow an attacker to get unauthorised access to the cluster. --> 然而，与添加到集群中的任何其他组件一样，安全风险也会随之出现。 一个安全风险示例是没有正确处理准入控制器的部署和管理。 为了帮助准入控制器用户和设计人员适当地管理这些风险， SIG Security 的[安全文档](https://github.com/kubernetes/community/tree/master/sig-security#security-docs)小组 花费了一些时间来开发一个[准入控制器威胁模型](https://github.com/kubernetes/sig-security/tree/main/sig-security-docs/papers/admission-control)。 这种威胁模型着眼于由于不正确使用准入控制器而产生的可能的风险，可能允许绕过安全策略，甚至允许攻击者未经授权访问集群。 <!-- From the threat model, we developed a set of security best practices that should be adopted to ensure that cluster operators can get the security benefits of admission controllers whilst avoiding any risks from using them. --> 基于这个威胁模型，我们开发了一套安全最佳实践。 你应该采用这些实践来确保集群操作员可以获得准入控制器带来的安全优势，同时避免使用它们带来的任何风险。 <!-- ## Admission controllers and good practices for security --> ## 准入控制器和安全的良好做法 <!-- From the threat model, a couple of themes emerged around how to ensure the security of admission controllers. --> 基于这个威胁模型，围绕着如何确保准入控制器的安全性出现了几个主题。 <!-- ### Secure webhook configuration --> ### 安全的 webhook 配置 <!-- It’s important to ensure that any security component in a cluster is well configured and admission controllers are no different here. There are a couple of security best practices to consider when using admission controllers --> 确保集群中的任何安全组件都配置良好是很重要的，在这里准入控制器也并不例外。 使用准入控制器时需要考虑几个安全最佳实践： <!-- * **Correctly configured TLS for all webhook traffic**. Communications between the API server and the admission controller webhook should be authenticated and encrypted to ensure that attackers who may be in a network position to view or modify this traffic cannot do so. To achieve this access the API server and webhook must be using certificates from a trusted certificate authority so that they can validate their mutual identities --> * **为所有 webhook 流量正确配置了 TLS**。 API 服务器和准入控制器 webhook 之间的通信应该经过身份验证和加密，以确保处于网络中查看或修改此流量的攻击者无法查看或修改。 要实现此访问，API 服务器和 webhook 必须使用来自受信任的证书颁发机构的证书，以便它们可以验证相互的身份。 <!-- * **Only authenticated access allowed**. If an attacker can send an admission controller large numbers of requests, they may be able to overwhelm the service causing it to fail. Ensuring all access requires strong authentication should mitigate that risk. --> * **只允许经过身份验证的访问**。 如果攻击者可以向准入控制器发送大量请求，他们可能会压垮服务导致其失败。 确保所有访问都需要强身份验证可以降低这种风险。 <!-- * **Admission controller fails closed**. This is a security practice that has a tradeoff, so whether a cluster operator wants to configure it will depend on the cluster’s threat model. If an admission controller fails closed, when the API server can’t get a response from it, all deployments will fail. This stops attackers bypassing the admission controller by disabling it, but, can disrupt the cluster’s operation. As clusters can have multiple webhooks, one approach to hit a middle ground might be to have critical controls on a fail closed setups and less critical controls allowed to fail open. --> * **准入控制器关闭失败**。 这是一种需要权衡的安全实践，集群操作员是否要对其进行配置取决于集群的威胁模型。 如果一个准入控制器关闭失败，当 API 服务器无法从它得到响应时，所有的部署都会失败。 这可以阻止攻击者通过禁用准入控制器绕过准入控制器，但可能会破坏集群的运行。 由于集群可以有多个 webhook，因此一种折中的方法是对关键控制允许故障关闭， 并允许不太关键的控制进行故障打开。 <!-- * **Regular reviews of webhook configuration**. Configuration mistakes can lead to security issues, so it’s important that the admission controller webhook configuration is checked to make sure the settings are correct. This kind of review could be done automatically by an Infrastructure As Code scanner or manually by an administrator. --> * **定期审查 webhook 配置**。 配置错误可能导致安全问题，因此检查准入控制器 webhook 配置以确保设置正确非常重要。 这种审查可以由基础设施即代码扫描程序自动完成，也可以由管理员手动完成。 <!-- ### Secure cluster configuration for admission control --> ### 为准入控制保护集群配置 <!-- In most cases, the admission controller webhook used by a cluster will be installed as a workload in the cluster. As a result, it’s important to ensure that Kubernetes' security features that could impact its operation are well configured. --> 在大多数情况下，集群使用的准入控制器 webhook 将作为工作负载安装在集群中。 因此，确保正确配置了可能影响其操作的 Kubernetes 安全特性非常重要。 <!-- * **Restrict [RBAC](/docs/reference/access-authn-authz/rbac/) rights**. Any user who has rights which would allow them to modify the configuration of the webhook objects or the workload that the admission controller uses could disrupt its operation. So it’s important to make sure that only cluster administrators have those rights. --> * **限制 [RBAC](/zh/docs/reference/access-authn-authz/rbac/) 权限**。 任何有权修改 webhook 对象的配置或准入控制器使用的工作负载的用户都可以破坏其运行。 因此，确保只有集群管理员拥有这些权限非常重要。 <!-- * **Prevent privileged workloads**. One of the realities of container systems is that if a workload is given certain privileges, it will be possible to break out to the underlying cluster node and impact other containers on that node. Where admission controller services run in the cluster they’re protecting, it’s important to ensure that any requirement for privileged workloads is carefully reviewed and restricted as much as possible. --> * **防止特权工作负载**。 容器系统的一个现实是，如果工作负载被赋予某些特权， 则有可能逃逸到下层的集群节点并影响该节点上的其他容器。 如果准入控制器服务在它们所保护的集群上运行， 一定要确保对特权工作负载的所有请求都要经过仔细审查并尽可能地加以限制。 <!-- * **Strictly control external system access**. As a security service in a cluster admission controller systems will have access to sensitive information like credentials. To reduce the risk of this information being sent outside the cluster, [network policies](/docs/concepts/services-networking/network-policies/) should be used to restrict the admission controller services access to external networks. --> * **严格控制外部系统访问**。 作为集群中的安全服务，准入控制器系统将有权访问敏感信息，如凭证。 为了降低此信息被发送到集群外的风险， 应使用[网络策略](/zh/docs/concepts/services-networking/network-policies/) 来限制准入控制器服务对外部网络的访问。 <!-- * **Each cluster has a dedicated webhook**. Whilst it may be possible to have admission controller webhooks that serve multiple clusters, there is a risk when using that model that an attack on the webhook service would have a larger impact where it’s shared. Also where multiple clusters use an admission controller there will be increased complexity and access requirements, making it harder to secure. --> * **每个集群都有一个专用的 webhook**。 虽然可能让准入控制器 webhook 服务于多个集群的， 但在使用该模型时存在对 webhook 服务的攻击会对共享它的地方产生更大影响的风险。 此外，在多个集群使用准入控制器的情况下，复杂性和访问要求也会增加，从而更难保护其安全。 <!-- ### Admission controller rules --> ### 准入控制器规则 <!-- A key element of any admission controller used for Kubernetes security is the rulebase it uses. The rules need to be able to accurately meet their goals avoiding false positive and false negative results. --> 对于用于 Kubernetes 安全的所有准入控制器而言，一个关键元素是它使用的规则库。 规则需要能够准确地满足其目标，避免假阳性和假阴性结果。 <!-- * **Regularly test and review rules**. Admission controller rules need to be tested to ensure their accuracy. They also need to be regularly reviewed as the Kubernetes API will change with each new version, and rules need to be assessed with each Kubernetes release to understand any changes that may be required to keep them up to date. --> * **定期测试和审查规则**。 需要测试准入控制器规则以确保其准确性。 还需要定期审查，因为 Kubernetes API 会随着每个新版本而改变， 并且需要在每个 Kubernetes 版本中评估规则，以了解使他们保持最新版本所需要做的任何改变。 </ins>  No newline at end of file"}
{"_id":"q-en-website-32f98857ace0affa5292646b0169ac5d25825bb52a7637d028694f190cca91e4","text":"from the community. Please try it out and give us feedback! {{< /caution >}} <ins> ## kubeadm alpha certs {#cmd-certs} A collection of operations for operating Kubernetes certificates. {{< tabs name=\"tab-certs\" >}} {{< tab name=\"overview\" include=\"generated/kubeadm_alpha_certs.md\" />}} {{< /tabs >}} </ins> ## kubeadm alpha certs renew {#cmd-certs-renew} You can renew all Kubernetes certificates using the `all` subcommand or renew them selectively."}
{"_id":"q-en-website-3308fe535b661c0bede75d6ea644ffc6edd5aaa0c817bce38a96ba8be372e2ef","text":"known endpoints. To use different container runtime or if there are more than one installed on the provisioned node, specify the `--cri-socket` argument to `kubeadm`. See [Installing a runtime](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#installing-runtime). <del> 1. (Optional) Unless otherwise specified, `kubeadm` uses the network interface associated with the default gateway to set the advertise address for this particular control-plane node's API server. To use a different network interface, specify the `--apiserver-advertise-address=<ip-address>` argument to `kubeadm init`. To deploy an IPv6 Kubernetes cluster using IPv6 addressing, you must specify an IPv6 address, for example `--apiserver-advertise-address=2001:db8::101` </del> To initialize the control-plane node run:"}
{"_id":"q-en-website-3392ca316c0f6f68db2cfee0574d87ac95592509c2130da527ca6d2dc38a1058","text":"### rbd `rbd` 볼륨을 사용하면 <del> [Rados Block Device](https://ceph.com/docs/master/rbd/rbd/)(RBD) 볼륨을 파드에 마운트할 수 </del> <ins> [Rados Block Device](https://docs.ceph.com/en/latest/rbd/)(RBD) 볼륨을 파드에 마운트할 수 </ins> 있다. 파드를 제거할 때 지워지는 `emptyDir` 와는 다르게 `rbd` 볼륨의 내용은 유지되고, 볼륨은 마운트 해제만 된다. 이 의미는 RBD 볼륨에 데이터를 미리 채울 수 있으며, 데이터를"}
{"_id":"q-en-website-3500ef8a6c375aea5b8dc123332bcf0cc92b11081422d751bde6d9f1addfd28c","text":"The Kubernetes project uses an automation tool called prow for automation related to GitHub issues and pull requests. The [Kubernetes website repository](https://github.com/kubernetes/website) uses <del> two [prow plugins](https://github.com/kubernetes/test-infra/tree/master/prow/plugins): </del> <ins> two [prow plugins](https://github.com/kubernetes-sigs/prow/tree/main/pkg/plugins): </ins> - blunderbuss - approve"}
{"_id":"q-en-website-3510a97367a8958ee100dc8ba16d785775de68f4657beb5477babac0749f318f","text":"--- title: Service Accounts description: > <del> Learn about the Kubernetes ServiceAccount object. </del> <ins> Learn about ServiceAccount objects in Kubernetes. </ins> content_type: concept weight: 10 ---"}
{"_id":"q-en-website-35354c9e05afb4d42662d0575327f179e0fe4a08f6e86eb93abe1eae956d6abf","text":"* `TYPE`: Specifies the [resource type](#resource-types). Resource types are case-insensitive and you can specify the singular, plural, or abbreviated forms. For example, the following commands produce the same output: <del> ```shell kubectl get pod pod1 kubectl get pods pod1 kubectl get po pod1 ``` </del> <ins> ```shell kubectl get pod pod1 kubectl get pods pod1 kubectl get po pod1 ``` </ins> * `NAME`: Specifies the name of the resource. Names are case-sensitive. If the name is omitted, details for all resources are displayed, for example `kubectl get pods`."}
{"_id":"q-en-website-37702b65234a003ceb838beb23b946080752b4e0188ca34c3d8cf19c43b6b1e6","text":"<ins> --- title: \"macOS 系统上的 bash 自动补全\" description: \"在 macOS 上实现 Bash 自动补全的一些可选配置。\" headless: true --- <!-- --- title: \"bash auto-completion on macOS\" description: \"Some optional configuration for bash auto-completion on macOS.\" headless: true --- --> <!-- ### Introduction --> ### 简介 <!-- The kubectl completion script for Bash can be generated with `kubectl completion bash`. Sourcing this script in your shell enables kubectl completion. However, the kubectl completion script depends on [**bash-completion**](https://github.com/scop/bash-completion) which you thus have to previously install. --> kubectl 的 Bash 补全脚本可以通过 `kubectl completion bash` 命令生成。 在你的 shell 中导入（Sourcing）这个脚本即可启用补全功能。 此外，kubectl 补全脚本依赖于工具 [**bash-completion**](https://github.com/scop/bash-completion)， 所以你必须先安装它。 {{< warning>}} <!-- There are two versions of bash-completion, v1 and v2. V1 is for Bash 3.2 (which is the default on macOS), and v2 is for Bash 4.1+. The kubectl completion script **doesn't work** correctly with bash-completion v1 and Bash 3.2. It requires **bash-completion v2** and **Bash 4.1+**. Thus, to be able to correctly use kubectl completion on macOS, you have to install and use Bash 4.1+ ([*instructions*](https://itnext.io/upgrading-bash-on-macos-7138bd1066ba)). The following instructions assume that you use Bash 4.1+ (that is, any Bash version of 4.1 or newer). --> bash-completion 有两个版本：v1 和 v2。v1 对应 Bash3.2（也是 macOS 的默认安装版本），v2 对应 Bash 4.1+。 kubectl 的补全脚本**无法适配** bash-completion v1 和 Bash 3.2。 必须为它配备  **bash-completion v2** 和 **Bash 4.1+**。 有鉴于此，为了在 macOS 上使用 kubectl 补全功能，你必须要安装和使用 Bash 4.1+ ([*说明*](https://itnext.io/upgrading-bash-on-macos-7138bd1066ba))。 后续说明假定你用的是 Bash 4.1+（也就是 Bash 4.1 或更新的版本） {{< /warning >}} <!-- ### Upgrade Bash --> ### 升级 Bash <!-- The instructions here assume you use Bash 4.1+. You can check your Bash's version by running: --> 后续说明假定你已使用 Bash 4.1+。你可以运行以下命令检查 Bash 版本： ```bash echo $BASH_VERSION ``` <!-- If it is too old, you can install/upgrade it using Homebrew: --> 如果版本太旧，可以用 Homebrew 安装/升级： ```bash brew install bash ``` <!-- Reload your shell and verify that the desired version is being used: --> 重新加载 shell，并验证所需的版本已经生效： ```bash echo $BASH_VERSION $SHELL ``` <!-- Homebrew usually installs it at `/usr/local/bin/bash`. --> Homebrew 通常把它安装为 `/usr/local/bin/bash`。 <!-- ### Install bash-completion --> ### 安装 bash-completion {{< note >}} <!-- As mentioned, these instructions assume you use Bash 4.1+, which means you will install bash-completion v2 (in contrast to Bash 3.2 and bash-completion v1, in which case kubectl completion won't work). --> 如前所述，本说明假定你使用的 Bash 版本为 4.1+，这意味着你要安装 bash-completion v2 （不同于 Bash 3.2 和 bash-completion v1，kubectl 的补全功能在该场景下无法工作）。 {{< /note >}} <!-- You can test if you have bash-completion v2 already installed with `type _init_completion`. If not, you can install it with Homebrew: --> 你可以用命令 `type _init_completion` 测试 bash-completion v2 是否已经安装。 如未安装，用 Homebrew 来安装它： ```bash brew install bash-completion@2 ``` <!-- As stated in the output of this command, add the following to your `~/.bash_profile` file: --> 如命令的输出信息所显示的，将如下内容添加到文件 `~/.bash_profile` 中： ```bash export BASH_COMPLETION_COMPAT_DIR=\"/usr/local/etc/bash_completion.d\" [[ -r \"/usr/local/etc/profile.d/bash_completion.sh\" ]] && . \"/usr/local/etc/profile.d/bash_completion.sh\" ``` <!-- Reload your shell and verify that bash-completion v2 is correctly installed with `type _init_completion`. --> 重新加载 shell，并用命令 `type _init_completion` 验证 bash-completion v2 已经恰当的安装。 <!-- ### Enable kubectl autocompletion --> ### 启用 kubectl 自动补全功能 <!-- You now have to ensure that the kubectl completion script gets sourced in all your shell sessions. There are multiple ways to achieve this: - Source the completion script in your `~/.bash_profile` file: --> 你现在需要确保在所有的 shell 环境中均已导入（sourced） kubectl 的补全脚本， 有若干种方法可以实现这一点： - 在文件 `~/.bash_profile` 中导入（Source）补全脚本： ```bash echo 'source <(kubectl completion bash)' >>~/.bash_profile ``` <!-- - Add the completion script to the `/usr/local/etc/bash_completion.d` directory: --> - 将补全脚本添加到目录 `/usr/local/etc/bash_completion.d` 中： ```bash kubectl completion bash >/usr/local/etc/bash_completion.d/kubectl ``` <!-- - If you have an alias for kubectl, you can extend shell completion to work with that alias: --> - 如果你为 kubectl 定义了别名，则可以扩展 shell 补全来兼容该别名： ```bash echo 'alias k=kubectl' >>~/.bash_profile echo 'complete -F __start_kubectl k' >>~/.bash_profile ``` <!-- - If you installed kubectl with Homebrew (as explained [above](#install-with-homebrew-on-macos)), then the kubectl completion script should already be in `/usr/local/etc/bash_completion.d/kubectl`. In that case, you don't need to do anything. --> - 如果你是用 Homebrew 安装的 kubectl（[如上所述](#install-with-homebrew-on-macos)）， 那么 kubectl 补全脚本应该已经安装到目录 `/usr/local/etc/bash_completion.d/kubectl` 中了。 这种情况下，你什么都不需要做。 {{< note >}} <!-- The Homebrew installation of bash-completion v2 sources all the files in the `BASH_COMPLETION_COMPAT_DIR` directory, that's why the latter two methods work. --> 用 Hommbrew 安装的 bash-completion v2 会初始化 目录 `BASH_COMPLETION_COMPAT_DIR` 中的所有文件，这就是后两种方法能正常工作的原因。 {{< /note >}} <!-- In any case, after reloading your shell, kubectl completion should be working. --> 总之，重新加载 shell 之后，kubectl 补全功能将立即生效。 </ins>"}
{"_id":"q-en-website-37e76407529bbfedcf8b3bbc2c9d7a7704f723a65ef5b19a2f6e349cf1676f18","text":"[plugin](/docs/concepts/storage/volumes/#types-of-volumes). The following broad classes of Kubernetes volume plugins are supported on Windows: <del> * [`FlexVolume plugins`](/docs/concepts/storage/volumes/#flexvolume-deprecated) </del> <ins> * [`FlexVolume plugins`](/docs/concepts/storage/volumes/#flexvolume) </ins> * Please note that FlexVolumes have been deprecated as of 1.23 * [`CSI Plugins`](/docs/concepts/storage/volumes/#csi)"}
{"_id":"q-en-website-3863da7166b07bbc93e8e2d322792353b854dcf594d995d2d4bbd90bbbad526e","text":"**only do this in a test cluster**. ```shell <del> kubectl drain <node-name> --force --delete-local-data --ignore-daemonsets </del> <ins> kubectl drain <node-name> --force --delete-emptydir-data --ignore-daemonsets </ins> ``` Now you can watch as the Pod reschedules on a different Node:"}
{"_id":"q-en-website-38fbbe4e41a661735453e6ae6ce887ca774d3d9f0353eebec8cb8fc2167a2026","text":"</h4> {{ end }} <p>{{ .message | markdownify }}</p> <ins> {{- if eq .dismissParameters.dismissible true -}} <button  id=\"banner-dismiss\" class=\"button\" style=\"display: none;\" data-ttl={{ .dismiss_params.showDismissedAnnouncementAfterDays }}>{{ T \"banner_acknowledgement\" }}</button> <!-- Only JS enabled users will see this button --> {{- end -}} </ins> </div> </aside> </div>"}
{"_id":"q-en-website-39b5d388fb2ac51998e82fdbd58f0d18fea7e66fa1a3402ae814537726f420a8","text":"<ins> --- title: Secret id: secret date: 2018-04-12 full_link: /ja/docs/concepts/configuration/secret/ short_description: > パスワードやOAuthトークン、SSHキーのような機密の情報を保持します。 aka: tags: - core-object - security --- パスワードやOAuthトークン、SSHキーのような機密の情報を保持します。 <!--more--> 機密情報の取り扱い方法を細かく制御することができ、保存時には[暗号化](/ja/docs/tasks/administer-cluster/encrypt-data/#ensure-all-secrets-are-encrypted)するなど、誤って公開してしまうリスクを減らすことができます。{{< glossary_tooltip text=\"Pod\" term_id=\"pod\" >}}は、ボリュームマウントされたファイルとして、またはPodのイメージをPullするkubeletによって、Secretを参照します。Secretは機密情報を扱うのに最適で、機密でない情報には[ConfigMap](/ja/docs/tasks/configure-pod-container/configure-pod-configmap/)が適しています。 </ins>"}
{"_id":"q-en-website-3a77b7d32d2f266fa3c16e6e5bf28d02b349e1ac138fac0a4d45dd6ce7470f44","text":"title: Extending the Kubernetes API weight: 30 --- <ins> Custom resources are extensions of the Kubernetes API. Kubernetes provides two ways to add custom resources to your cluster: - The [CustomResourceDefinition](/docs/concepts/extend-kubernetes/api-extension/custom-resources/) (CRD) mechanism allows you to declaratively define a new custom API with an API group, kind, and schema that you specify. The Kubernetes control plane serves and handles the storage of your custom resource. CRDs allow you to create new types of resources for your cluster without writing and running a custom API server. - The [aggregation layer](/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/) sits behind the primary API server, which acts as a proxy. This arrangement is called API Aggregation (AA), which allows you to provide specialized implementations for your custom resources by writing and deploying your own API server. The main API server delegates requests to your API server for the custom APIs that you specify, making them available to all of its clients. </ins>"}
{"_id":"q-en-website-3b5f0d195ffc236ff2a763672a36c8bd3f345448ff145d483e5a70fad78b40ff","text":"<del> --- title: Pod 拓扑分布约束 content_type: concept weight: 40 --- <!-- title: Pod Topology Spread Constraints content_type: concept weight: 40 --> <!-- overview --> <!-- You can use _topology spread constraints_ to control how {{< glossary_tooltip text=\"Pods\" term_id=\"Pod\" >}} are spread across your cluster among failure-domains such as regions, zones, nodes, and other user-defined topology domains. This can help to achieve high availability as well as efficient resource utilization. --> 你可以使用 _拓扑分布约束（Topology Spread Constraints）_ 来控制 {{< glossary_tooltip text=\"Pod\" term_id=\"Pod\" >}} 在集群内故障域之间的分布， 例如区域（Region）、可用区（Zone）、节点和其他用户自定义拓扑域。 这样做有助于实现高可用并提升资源利用率。 <!-- body --> <!-- ## Prerequisites ### Node Labels --> ## 先决条件   {#prerequisites} ### 节点标签   {#node-labels} <!-- Topology spread constraints rely on node labels to identify the topology domain(s) that each Node is in. For example, a Node might have labels: `node=node1,zone=us-east-1a,region=us-east-1` --> 拓扑分布约束依赖于节点标签来标识每个节点所在的拓扑域。 例如，某节点可能具有标签：`node=node1,zone=us-east-1a,region=us-east-1` <!-- Suppose you have a 4-node cluster with the following labels: --> 假设你拥有具有以下标签的一个 4 节点集群： ``` NAME    STATUS   ROLES    AGE     VERSION   LABELS node1   Ready    <none>   4m26s   v1.16.0   node=node1,zone=zoneA node2   Ready    <none>   3m58s   v1.16.0   node=node2,zone=zoneA node3   Ready    <none>   3m17s   v1.16.0   node=node3,zone=zoneB node4   Ready    <none>   2m43s   v1.16.0   node=node4,zone=zoneB ``` <!-- Then the cluster is logically viewed as below: --> 那么，从逻辑上看集群如下： {{<mermaid>}} graph TB subgraph \"zoneB\" n3(Node3) n4(Node4) end subgraph \"zoneA\" n1(Node1) n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4 k8s; class zoneA,zoneB cluster; {{< /mermaid >}} <!-- Instead of manually applying labels, you can also reuse the [well-known labels](/docs/reference/labels-annotations-taints/) that are created and populated automatically on most clusters. --> 你可以复用在大多数集群上自动创建和填充的[常用标签](/zh-cn/docs/reference/labels-annotations-taints/)， 而不是手动添加标签。 <!-- ## Spread Constraints for Pods --> ## Pod 的分布约束    {#spread-constraints-for-pods} ### API <!-- The API field `pod.spec.topologySpreadConstraints` is defined as below: --> `pod.spec.topologySpreadConstraints` 字段定义如下所示： ```yaml apiVersion: v1 kind: Pod metadata: name: mypod spec: topologySpreadConstraints: - maxSkew: <integer> topologyKey: <string> whenUnsatisfiable: <string> labelSelector: <object> ``` <!-- You can define one or multiple `topologySpreadConstraint` to instruct the kube-scheduler how to place each incoming Pod in relation to the existing Pods across your cluster. The fields are: --> 你可以定义一个或多个 `topologySpreadConstraint` 来指示 kube-scheduler 如何根据与现有的 Pod 的关联关系将每个传入的 Pod 部署到集群中。字段包括： <!-- - **maxSkew** describes the degree to which Pods may be unevenly distributed. It's the maximum permitted difference between the number of matching Pods in any two topology domains of a given topology type. It must be greater than zero. Its semantics differs according to the value of `whenUnsatisfiable`: - when `whenUnsatisfiable` equals to \"DoNotSchedule\", `maxSkew` is the maximum permitted difference between the number of matching pods in the target topology and the global minimum. (the minimum number of pods that match the label selector in a topology domain. For example, if you have 3 zones with 0, 2 and 3 matching pods respectively, The global minimum is 0). - when `whenUnsatisfiable` equals to \"ScheduleAnyway\", scheduler gives higher precedence to topologies that would help reduce the skew. --> - **maxSkew** 描述 Pod 分布不均的程度。这是给定拓扑类型中任意两个拓扑域中匹配的 Pod 之间的最大允许差值。它必须大于零。取决于 `whenUnsatisfiable` 的取值， 其语义会有不同。 - 当 `whenUnsatisfiable` 等于 \"DoNotSchedule\" 时，`maxSkew` 是目标拓扑域中匹配的 Pod 数与全局最小值（一个拓扑域中与标签选择器匹配的 Pod 的最小数量。例如，如果你有 3 个区域，分别具有 0 个、2 个 和 3 个匹配的 Pod，则全局最小值为 0。）之间可存在的差异。 - 当 `whenUnsatisfiable` 等于 \"ScheduleAnyway\" 时，调度器会更为偏向能够降低偏差值的拓扑域。 <!-- - **minDomains** indicates a minimum number of eligible domains. A domain is a particular instance of a topology. An eligible domain is a domain whose nodes match the node selector. - The value of `minDomains` must be greater than 0, when specified. - When the number of eligible domains with match topology keys is less than `minDomains`, Pod topology spread treats \"global minimum\" as 0, and then the calculation of `skew` is performed. The \"global minimum\" is the minimum number of matching Pods in an eligible domain, or zero if the number of eligible domains is less than `minDomains`. - When the number of eligible domains with matching topology keys equals or is greater than `minDomains`, this value has no effect on scheduling. - When `minDomains` is nil, the constraint behaves as if `minDomains` is 1. - When `minDomains` is not nil, the value of `whenUnsatisfiable` must be \"`DoNotSchedule`\". --> - **minDomains** 表示符合条件的域的最小数量。域是拓扑的一个特定实例。 符合条件的域是其节点与节点选择器匹配的域。 - 指定的 `minDomains` 的值必须大于 0。 - 当符合条件的、拓扑键匹配的域的数量小于 `minDomains` 时，Pod 拓扑分布将“全局最小值” （global minimum）设为 0，然后进行 `skew` 计算。“全局最小值”是一个符合条件的域中匹配 Pod 的最小数量，如果符合条件的域的数量小于 `minDomains`，则全局最小值为零。 - 当符合条件的拓扑键匹配域的个数等于或大于 `minDomains` 时，该值对调度没有影响。 - 当 `minDomains` 为 nil 时，约束的行为等于 `minDomains` 为 1。 - 当 `minDomains` 不为 nil 时，`whenUnsatisfiable` 的值必须为 \"`DoNotSchedule`\" 。 {{< note >}} <!-- The `minDomains` field is an alpha field added in 1.24. You have to enable the `MinDomainsInPodToplogySpread` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) in order to use it. --> `minDomains` 字段是在 1.24 版本中新增的 alpha 字段。你必须启用 `MinDomainsInPodToplogySpread` [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)才能使用它。 {{< /note >}} <!-- - **topologyKey** is the key of node labels. If two Nodes are labelled with this key and have identical values for that label, the scheduler treats both Nodes as being in the same topology. The scheduler tries to place a balanced number of Pods into each topology domain. - **whenUnsatisfiable** indicates how to deal with a Pod if it doesn't satisfy the spread constraint: - `DoNotSchedule` (default) tells the scheduler not to schedule it. - `ScheduleAnyway` tells the scheduler to still schedule it while prioritizing nodes that minimize the skew. - **labelSelector** is used to find matching Pods. Pods that match this label selector are counted to determine the number of Pods in their corresponding topology domain. See [Label Selectors](/docs/concepts/overview/working-with-objects/labels/#label-selectors) for more details. --> - **topologyKey** 是节点标签的键。如果两个节点使用此键标记并且具有相同的标签值， 则调度器会将这两个节点视为处于同一拓扑域中。调度器试图在每个拓扑域中放置数量均衡的 Pod。 - **whenUnsatisfiable** 指示如果 Pod 不满足分布约束时如何处理： - `DoNotSchedule`（默认）告诉调度器不要调度。 - `ScheduleAnyway` 告诉调度器仍然继续调度，只是根据如何能将偏差最小化来对节点进行排序。 - **labelSelector** 用于查找匹配的 Pod。匹配此标签的 Pod 将被统计， 以确定相应拓扑域中 Pod 的数量。 有关详细信息，请参考[标签选择算符](/zh-cn/docs/concepts/overview/working-with-objects/labels/#label-selectors)。 <!-- When a Pod defines more than one `topologySpreadConstraint`, those constraints are ANDed: The kube-scheduler looks for a node for the incoming Pod that satisfies all the constraints. --> 当 Pod 定义了不止一个 `topologySpreadConstraint`，这些约束之间是逻辑与的关系。 kube-scheduler 会为新的 Pod 寻找一个能够满足所有约束的节点。 <!-- You can read more about this field by running `kubectl explain Pod.spec.topologySpreadConstraints`. --> 你可以执行 `kubectl explain Pod.spec.topologySpreadConstraints` 命令以了解关于 topologySpreadConstraints 的更多信息。 <!-- ### Example: One TopologySpreadConstraint Suppose you have a 4-node cluster where 3 Pods labeled `foo:bar` are located in node1, node2 and node3 respectively: --> ### 例子：单个 TopologySpreadConstraint 假设你拥有一个 4 节点集群，其中标记为 `foo:bar` 的 3 个 Pod 分别位于 node1、node2 和 node3 中： {{<mermaid>}} graph BT subgraph \"zoneB\" p3(Pod) --> n3(Node3) n4(Node4) end subgraph \"zoneA\" p1(Pod) --> n1(Node1) p2(Pod) --> n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4,p1,p2,p3 k8s; class zoneA,zoneB cluster; {{< /mermaid >}} <!-- If we want an incoming Pod to be evenly spread with existing Pods across zones, the spec can be given as: --> 如果希望新来的 Pod 均匀分布在现有的可用区域，则可以按如下设置其规约： {{< codenew file=\"pods/topology-spread-constraints/one-constraint.yaml\" >}} <!-- `topologyKey: zone` implies the even distribution will only be applied to the nodes which have label pair \"zone:&lt;any value&gt;\" present. `whenUnsatisfiable: DoNotSchedule` tells the scheduler to let it stay pending if the incoming Pod can’t satisfy the constraint. --> `topologyKey: zone` 意味着均匀分布将只应用于存在标签键值对为 \"zone:&lt;任何值&gt;\" 的节点。 `whenUnsatisfiable: DoNotSchedule` 告诉调度器如果新的 Pod 不满足约束， 则让它保持悬决状态。 <!-- If the scheduler placed this incoming Pod into \"zoneA\", the Pods distribution would become [3, 1], hence the actual skew is 2 (3 - 1) - which violates `maxSkew: 1`. In this example, the incoming Pod can only be placed onto \"zoneB\": --> 如果调度器将新的 Pod 放入 \"zoneA\"，Pods 分布将变为 [3, 1]，因此实际的偏差为 2（3 - 1）。这违反了 `maxSkew: 1` 的约定。此示例中，新 Pod 只能放置在 \"zoneB\" 上： {{<mermaid>}} graph BT subgraph \"zoneB\" p3(Pod) --> n3(Node3) p4(mypod) --> n4(Node4) end subgraph \"zoneA\" p1(Pod) --> n1(Node1) p2(Pod) --> n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4,p1,p2,p3 k8s; class p4 plain; class zoneA,zoneB cluster; {{< /mermaid >}} 或者 {{<mermaid>}} graph BT subgraph \"zoneB\" p3(Pod) --> n3(Node3) p4(mypod) --> n3 n4(Node4) end subgraph \"zoneA\" p1(Pod) --> n1(Node1) p2(Pod) --> n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4,p1,p2,p3 k8s; class p4 plain; class zoneA,zoneB cluster; {{< /mermaid >}} <!-- You can tweak the Pod spec to meet various kinds of requirements: --> 你可以调整 Pod 规约以满足各种要求： <!-- - Change `maxSkew` to a bigger value like \"2\" so that the incoming Pod can be placed onto \"zoneA\" as well. - Change `topologyKey` to \"node\" so as to distribute the Pods evenly across nodes instead of zones. In the above example, if `maxSkew` remains \"1\", the incoming Pod can only be placed onto \"node4\". - Change `whenUnsatisfiable: DoNotSchedule` to `whenUnsatisfiable: ScheduleAnyway` to ensure the incoming Pod to be always schedulable (suppose other scheduling APIs are satisfied). However, it’s preferred to be placed onto the topology domain which has fewer matching Pods. (Be aware that this preferability is jointly normalized with other internal scheduling priorities like resource usage ratio, etc.) --> - 将 `maxSkew` 更改为更大的值，比如 \"2\"，这样新的 Pod 也可以放在 \"zoneA\" 上。 - 将 `topologyKey` 更改为 \"node\"，以便将 Pod 均匀分布在节点上而不是区域中。 在上面的例子中，如果 `maxSkew` 保持为 \"1\"，那么传入的 Pod 只能放在 \"node4\" 上。 - 将 `whenUnsatisfiable: DoNotSchedule` 更改为 `whenUnsatisfiable: ScheduleAnyway`， 以确保新的 Pod 始终可以被调度（假设满足其他的调度 API）。 但是，最好将其放置在匹配 Pod 数量较少的拓扑域中。 （请注意，这一优先判定会与其他内部调度优先级（如资源使用率等）排序准则一起进行标准化。） <!-- ### Example: Multiple TopologySpreadConstraints --> ### 例子：多个 TopologySpreadConstraints <!-- This builds upon the previous example. Suppose you have a 4-node cluster where 3 Pods labeled `foo:bar` are located in node1, node2 and node3 respectively (`P` represents Pod): --> 下面的例子建立在前面例子的基础上。假设你拥有一个 4 节点集群，其中 3 个标记为 `foo:bar` 的 Pod 分别位于 node1、node2 和 node3 上： {{<mermaid>}} graph BT subgraph \"zoneB\" p3(Pod) --> n3(Node3) n4(Node4) end subgraph \"zoneA\" p1(Pod) --> n1(Node1) p2(Pod) --> n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4,p1,p2,p3 k8s; class p4 plain; class zoneA,zoneB cluster; {{< /mermaid >}} <!-- You can use 2 TopologySpreadConstraints to control the Pods spreading on both zone and node: --> 可以使用 2 个 TopologySpreadConstraint 来控制 Pod 在 区域和节点两个维度上的分布： {{< codenew file=\"pods/topology-spread-constraints/two-constraints.yaml\" >}} <!-- In this case, to match the first constraint, the incoming Pod can only be placed onto \"zoneB\"; while in terms of the second constraint, the incoming Pod can only be placed onto \"node4\". Then the results of 2 constraints are ANDed, so the only viable option is to place on \"node4\". --> 在这种情况下，为了匹配第一个约束，新的 Pod 只能放置在 \"zoneB\" 中；而在第二个约束中， 新的 Pod 只能放置在 \"node4\" 上。最后两个约束的结果加在一起，唯一可行的选择是放置在 \"node4\" 上。 <!-- Multiple constraints can lead to conflicts. Suppose you have a 3-node cluster across 2 zones: --> 多个约束之间可能存在冲突。假设有一个跨越 2 个区域的 3 节点集群： {{<mermaid>}} graph BT subgraph \"zoneB\" p4(Pod) --> n3(Node3) p5(Pod) --> n3 end subgraph \"zoneA\" p1(Pod) --> n1(Node1) p2(Pod) --> n1 p3(Pod) --> n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4,p1,p2,p3,p4,p5 k8s; class zoneA,zoneB cluster; {{< /mermaid >}} <!-- If you apply \"two-constraints.yaml\" to this cluster, you will notice \"mypod\" stays in `Pending` state. This is because: to satisfy the first constraint, \"mypod\" can only be put to \"zoneB\"; while in terms of the second constraint, \"mypod\" can only put onto \"node2\". Then a joint result of \"zoneB\" and \"node2\" returns nothing. --> 如果对集群应用 \"two-constraints.yaml\"，会发现 \"mypod\" 处于 `Pending` 状态。 这是因为：为了满足第一个约束，\"mypod\" 只能放在 \"zoneB\" 中，而第二个约束要求 \"mypod\" 只能放在 \"node2\" 上。Pod 调度无法满足两种约束。 <!-- To overcome this situation, you can either increase the `maxSkew` or modify one of the constraints to use `whenUnsatisfiable: ScheduleAnyway`. --> 为了克服这种情况，你可以增加 `maxSkew` 或修改其中一个约束，让其使用 `whenUnsatisfiable: ScheduleAnyway`。 <!-- ### Interaction With Node Affinity and Node Selectors The scheduler will skip the non-matching nodes from the skew calculations if the incoming Pod has `spec.nodeSelector` or `spec.affinity.nodeAffinity` defined. --> ### 节点亲和性与节点选择器的相互作用   {#interaction-with-node-affinity-and-node-selectors} 如果 Pod 定义了 `spec.nodeSelector` 或 `spec.affinity.nodeAffinity`， 调度器将在偏差计算中跳过不匹配的节点。 <!-- ### Example: TopologySpreadConstraints with NodeAffinity Suppose you have a 5-node cluster ranging from zoneA to zoneC: --> ### 示例：TopologySpreadConstraints 与 NodeAffinity 假设你有一个跨越 zoneA 到 zoneC 的 5 节点集群： {{<mermaid>}} graph BT subgraph \"zoneB\" p3(Pod) --> n3(Node3) n4(Node4) end subgraph \"zoneA\" p1(Pod) --> n1(Node1) p2(Pod) --> n2(Node2) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n1,n2,n3,n4,p1,p2,p3 k8s; class p4 plain; class zoneA,zoneB cluster; {{< /mermaid >}} {{<mermaid>}} graph BT subgraph \"zoneC\" n5(Node5) end classDef plain fill:#ddd,stroke:#fff,stroke-width:4px,color:#000; classDef k8s fill:#326ce5,stroke:#fff,stroke-width:4px,color:#fff; classDef cluster fill:#fff,stroke:#bbb,stroke-width:2px,color:#326ce5; class n5 k8s; class zoneC cluster; {{< /mermaid >}} <!-- and you know that \"zoneC\" must be excluded. In this case, you can compose the yaml as below, so that \"mypod\" will be placed into \"zoneB\" instead of \"zoneC\". Similarly `spec.nodeSelector` is also respected. --> 而且你知道 \"zoneC\" 必须被排除在外。在这种情况下，可以按如下方式编写 YAML， 以便将 \"mypod\" 放置在 \"zoneB\" 上，而不是 \"zoneC\" 上。同样，`spec.nodeSelector` 也要一样处理。 {{< codenew file=\"pods/topology-spread-constraints/one-constraint-with-nodeaffinity.yaml\" >}} <!-- The scheduler doesn't have prior knowledge of all the zones or other topology domains that a cluster has. They are determined from the existing nodes in the cluster. This could lead to a problem in autoscaled clusters, when a node pool (or node group) is scaled to zero nodes and the user is expecting them to scale up, because, in this case, those topology domains won't be considered until there is at least one node in them. --> 调度器不会预先知道集群拥有的所有区域和其他拓扑域。拓扑域由集群中存在的节点确定。 在自动伸缩的集群中，如果一个节点池（或节点组）的节点数量为零， 而用户正期望其扩容时，可能会导致调度出现问题。 因为在这种情况下，调度器不会考虑这些拓扑域信息，因为它们是空的，没有节点。 <!-- ### Other Noticeable Semantics There are some implicit conventions worth noting here: --> ### 其他值得注意的语义   {#other-noticeable-semantics} 这里有一些值得注意的隐式约定： <!-- - Only the Pods holding the same namespace as the incoming Pod can be matching candidates. - The scheduler will bypass the nodes without `topologySpreadConstraints[*].topologyKey` present. This implies that: 1. the Pods located on those nodes do not impact `maxSkew` calculation - in the above example, suppose \"node1\" does not have label \"zone\", then the 2 Pods will be disregarded, hence the incoming Pod will be scheduled into \"zoneA\". 2. the incoming Pod has no chances to be scheduled onto such nodes - in the above example, suppose a \"node5\" carrying label `{zone-typo: zoneC}` joins the cluster, it will be bypassed due to the absence of label key \"zone\". --> - 只有与新的 Pod 具有相同命名空间的 Pod 才能作为匹配候选者。 - 调度器会忽略没有 `topologySpreadConstraints[*].topologyKey` 的节点。这意味着： 1. 位于这些节点上的 Pod 不影响 `maxSkew` 的计算。 在上面的例子中，假设 \"node1\" 没有标签 \"zone\"，那么 2 个 Pod 将被忽略， 因此传入的 Pod 将被调度到 \"zoneA\" 中。 2. 新的 Pod 没有机会被调度到这类节点上。 在上面的例子中，假设一个带有标签 `{zone-typo: zoneC}` 的 \"node5\" 加入到集群， 它将由于没有标签键 \"zone\" 而被忽略。 <!-- - Be aware of what will happen if the incomingPod’s `topologySpreadConstraints[*].labelSelector` doesn’t match its own labels. In the above example, if we remove the incoming Pod’s labels, it can still be placed onto \"zoneB\" since the constraints are still satisfied. However, after the placement, the degree of imbalance of the cluster remains unchanged - it’s still zoneA having 2 Pods which hold label {foo:bar}, and zoneB having 1 Pod which holds label {foo:bar}. So if this is not what you expect, we recommend the workload’s `topologySpreadConstraints[*].labelSelector` to match its own labels. --> - 注意，如果新 Pod 的 `topologySpreadConstraints[*].labelSelector` 与自身的标签不匹配，将会发生什么。 在上面的例子中，如果移除新 Pod 上的标签，Pod 仍然可以调度到 \"zoneB\"，因为约束仍然满足。 然而，在调度之后，集群的不平衡程度保持不变。zoneA 仍然有 2 个带有 {foo:bar} 标签的 Pod， zoneB 有 1 个带有 {foo:bar} 标签的 Pod。 因此，如果这不是你所期望的，建议工作负载的 `topologySpreadConstraints[*].labelSelector` 与其自身的标签匹配。 <!-- ### Cluster-level default constraints It is possible to set default topology spread constraints for a cluster. Default topology spread constraints are applied to a Pod if, and only if: - It doesn't define any constraints in its `.spec.topologySpreadConstraints`. - It belongs to a service, replication controller, replica set or stateful set. --> ### 集群级别的默认约束   {#cluster-level-default-constraints} 为集群设置默认的拓扑分布约束也是可能的。 默认拓扑分布约束在且仅在以下条件满足时才会被应用到 Pod 上： - Pod 没有在其 `.spec.topologySpreadConstraints` 设置任何约束； - Pod 隶属于某个服务、副本控制器、ReplicaSet 或 StatefulSet。 <!-- Default constraints can be set as part of the `PodTopologySpread` plugin args in a [scheduling profile](/docs/reference/scheduling/config/#profiles). The constraints are specified with the same [API above](#api), except that `labelSelector` must be empty. The selectors are calculated from the services, replication controllers, replica sets or stateful sets that the Pod belongs to. An example configuration might look like follows: --> 你可以在 [调度方案（Scheduling Profile）](/zh-cn/docs/reference/scheduling/config/#profiles) 中将默认约束作为 `PodTopologySpread` 插件参数的一部分来设置。 约束的设置采用[如前所述的 API](#api)，只是 `labelSelector` 必须为空。 选择算符是根据 Pod 所属的服务、副本控制器、ReplicaSet 或 StatefulSet 来设置的。 配置的示例可能看起来像下面这个样子： ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta3 kind: KubeSchedulerConfiguration profiles: - schedulerName: default-scheduler pluginConfig: - name: PodTopologySpread args: defaultConstraints: - maxSkew: 1 topologyKey: topology.kubernetes.io/zone whenUnsatisfiable: ScheduleAnyway defaultingType: List ``` {{< note >}} <!-- [`SelectorSpread` plugin](/docs/reference/scheduling/config/#scheduling-plugins) is disabled by default. It's recommended to use `PodTopologySpread` to achieve similar behavior. --> [`SelectorSpread` 插件](/zh-cn/docs/reference/scheduling/config/#scheduling-plugins)默认是被禁用的。 建议使用 `PodTopologySpread` 来实现类似的行为。 {{< /note >}} <!-- #### Internal default constraints --> #### 内部默认约束    {#internal-default-constraints} {{< feature-state for_k8s_version=\"v1.24\" state=\"stable\" >}} <!-- If you don't configure any cluster-level default constraints for pod topology spreading, then kube-scheduler acts as if you specified the following default topology constraints: --> 如果你没有为 Pod 拓扑分布配置任何集群级别的默认约束， kube-scheduler 的行为就像你指定了以下默认拓扑约束一样： ```yaml defaultConstraints: - maxSkew: 3 topologyKey: \"kubernetes.io/hostname\" whenUnsatisfiable: ScheduleAnyway - maxSkew: 5 topologyKey: \"topology.kubernetes.io/zone\" whenUnsatisfiable: ScheduleAnyway ``` <!-- Also, the legacy `SelectorSpread` plugin, which provides an equivalent behavior, is disabled by default. --> 此外，原来用于提供等同行为的 `SelectorSpread` 插件默认被禁用。 {{< note >}} <!-- The `PodTopologySpread` plugin does not score the nodes that don't have the topology keys specified in the spreading constraints. This might result in a different default behavior compared to the legacy `SelectorSpread` plugin when using the default topology constraints. --> 对于分布约束中所指定的拓扑键而言，`PodTopologySpread` 插件不会为不包含这些主键的节点评分。 这可能导致在使用默认拓扑约束时，其行为与原来的 `SelectorSpread` 插件的默认行为不同， <!-- If your nodes are not expected to have **both** `kubernetes.io/hostname` and `topology.kubernetes.io/zone` labels set, define your own constraints instead of using the Kubernetes defaults. --> 如果你的节点不会 **同时** 设置 `kubernetes.io/hostname` 和 `topology.kubernetes.io/zone` 标签，你应该定义自己的约束而不是使用 Kubernetes 的默认约束。 {{< /note >}} <!-- If you don't want to use the default Pod spreading constraints for your cluster, you can disable those defaults by setting `defaultingType` to `List` and leaving empty `defaultConstraints` in the `PodTopologySpread` plugin configuration: --> 如果你不想为集群使用默认的 Pod 分布约束，你可以通过设置 `defaultingType` 参数为 `List` 并将 `PodTopologySpread` 插件配置中的 `defaultConstraints` 参数置空来禁用默认 Pod 分布约束。 ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta3 kind: KubeSchedulerConfiguration profiles: - schedulerName: default-scheduler pluginConfig: - name: PodTopologySpread args: defaultConstraints: [] defaultingType: List ``` <!-- ## Comparison with PodAffinity/PodAntiAffinity In Kubernetes, directives related to \"Affinity\" control how Pods are scheduled - more packed or more scattered. --> ## 与 PodAffinity/PodAntiAffinity 相比较 在 Kubernetes 中，与“亲和性”相关的指令控制 Pod 的调度方式（更密集或更分散）。 <!-- - For `PodAffinity`, you can try to pack any number of Pods into qualifying topology domain(s) - For `PodAntiAffinity`, only one Pod can be scheduled into a single topology domain. --> - 对于 `PodAffinity`，你可以尝试将任意数量的 Pod 集中到符合条件的拓扑域中。 - 对于 `PodAntiAffinity`，只能将一个 Pod 调度到某个拓扑域中。 <!-- For finer control, you can specify topology spread constraints to distribute Pods across different topology domains - to achieve either high availability or cost-saving. This can also help on rolling update workloads and scaling out replicas smoothly. See [Motivation](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/895-pod-topology-spread#motivation) for more details. --> 要实现更细粒度的控制，你可以设置拓扑分布约束来将 Pod 分布到不同的拓扑域下， 从而实现高可用性或节省成本。这也有助于工作负载的滚动更新和平稳地扩展副本规模。 有关详细信息，请参考 [动机](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/20190221-pod-topology-spread.md#motivation)文档。 <!-- ## Known Limitations - There's no guarantee that the constraints remain satisfied when Pods are removed. For example, scaling down a Deployment may result in imbalanced Pods distribution. You can use [Descheduler](https://github.com/kubernetes-sigs/descheduler) to rebalance the Pods distribution. - Pods matched on tainted nodes are respected. See [Issue 80921](https://github.com/kubernetes/kubernetes/issues/80921) --> ## 已知局限性 - 当 Pod 被移除时，无法保证约束仍被满足。例如，缩减某 Deployment 的规模时， Pod 的分布可能不再均衡。 你可以使用 [Descheduler](https://github.com/kubernetes-sigs/descheduler) 来重新实现 Pod 分布的均衡。 - 具有污点的节点上匹配的 Pods 也会被统计。 参考 [Issue 80921](https://github.com/kubernetes/kubernetes/issues/80921)。 ## {{% heading \"whatsnext\" %}} <!-- - [Blog: Introducing PodTopologySpread](https://kubernetes.io/blog/2020/05/introducing-podtopologyspread/) explains `maxSkew` in details, as well as bringing up some advanced usage examples. --> - [博客: PodTopologySpread介绍](https://kubernetes.io/blog/2020/05/introducing-podtopologyspread/) 详细解释了 `maxSkew`，并给出了一些高级的使用示例。 </del>"}
{"_id":"q-en-website-3c47b16bfd45e1c4407a4bcec606c6c8ddb51cb2aa6d8940648b92e135e0af16","text":"<del> „--- </del> <ins> --- </ins> title: I componenti di Kubernetes content_type: concept weight: 20"}
{"_id":"q-en-website-3c4ee72794137b585d201e4b134ba0cf78b4f8f80841220c5f9c01e5a5be5c1c","text":"Initコンテナの順序と実行を考えるとき、リソースの使用に関して下記のルールが適用されます。 <del> * 全てのInitコンテナの中で定義された最も高いリソースリクエストとリソースリミットが、*有効なinitリクエスト／リミット* になります。 </del> <ins> * 全てのInitコンテナの中で定義された最も高いリソースリクエストとリソースリミットが、*有効なinitリクエスト／リミット* になります。いずれかのリソースでリミットが設定されていない場合、これが最上級のリミットとみなされます。 </ins> * Podのリソースの*有効なリクエスト／リミット* は、下記の2つの中のどちらか高い方となります。 * リソースに対する全てのアプリケーションコンテナのリクエスト／リミットの合計 * リソースに対する有効なinitリクエスト／リミット"}
{"_id":"q-en-website-3d616ae2ce953284a60f6524a350b7c3629fbb4d7613247f594135cc5d4aabf9","text":"object named `default` for every namespace in your cluster. The `default` service accounts in each namespace get no permissions by default other than the [default API discovery permissions](/docs/reference/access-authn-authz/rbac/#default-roles-and-role-bindings) <del> that Kubernetes grants to all authenticated principals if role-based access control (RBAC) is enabled. If you delete the `default` ServiceAccount object in a namespace, the {{<glossary_tooltip text=\"control plane\" term_id=\"control-plane\">}} </del> <ins> that Kubernetes grants to all authenticated principals if role-based access control (RBAC) is enabled. If you delete the `default` ServiceAccount object in a namespace, the {{< glossary_tooltip text=\"control plane\" term_id=\"control-plane\" >}} </ins> replaces it with a new one. If you deploy a Pod in a namespace, and you don't"}
{"_id":"q-en-website-3e822568e9a8e83b3749f53ad9b4093deaa78dedc2291d0644cff066f359f4e9","text":"<del> --- reviewers: - rickypai - thockin title: Adding entries to Pod /etc/hosts with HostAliases content_type: concept weight: 60 min-kubernetes-server-version: 1.7 --- <!-- overview --> Adding entries to a Pod's `/etc/hosts` file provides Pod-level override of hostname resolution when DNS and other options are not applicable. You can add these custom entries with the HostAliases field in PodSpec. Modification not using HostAliases is not suggested because the file is managed by the kubelet and can be overwritten on during Pod creation/restart. <!-- body --> ## Default hosts file content Start an Nginx Pod which is assigned a Pod IP: ```shell kubectl run nginx --image nginx ``` ``` pod/nginx created ``` Examine a Pod IP: ```shell kubectl get pods --output=wide ``` ``` NAME     READY     STATUS    RESTARTS   AGE    IP           NODE nginx    1/1       Running   0          13s    10.200.0.4   worker0 ``` The hosts file content would look like this: ```shell kubectl exec nginx -- cat /etc/hosts ``` ``` # Kubernetes-managed hosts file. 127.0.0.1\tlocalhost ::1\tlocalhost ip6-localhost ip6-loopback fe00::0\tip6-localnet fe00::0\tip6-mcastprefix fe00::1\tip6-allnodes fe00::2\tip6-allrouters 10.200.0.4\tnginx ``` By default, the `hosts` file only includes IPv4 and IPv6 boilerplates like `localhost` and its own hostname. ## Adding additional entries with hostAliases In addition to the default boilerplate, you can add additional entries to the `hosts` file. For example: to resolve `foo.local`, `bar.local` to `127.0.0.1` and `foo.remote`, `bar.remote` to `10.1.2.3`, you can configure HostAliases for a Pod under `.spec.hostAliases`: {{< codenew file=\"service/networking/hostaliases-pod.yaml\" >}} You can start a Pod with that configuration by running: ```shell kubectl apply -f https://k8s.io/examples/service/networking/hostaliases-pod.yaml ``` ``` pod/hostaliases-pod created ``` Examine a Pod's details to see its IPv4 address and its status: ```shell kubectl get pod --output=wide ``` ``` NAME                           READY     STATUS      RESTARTS   AGE       IP              NODE hostaliases-pod                0/1       Completed   0          6s        10.200.0.5      worker0 ``` The `hosts` file content looks like this: ```shell kubectl logs hostaliases-pod ``` ``` # Kubernetes-managed hosts file. 127.0.0.1\tlocalhost ::1\tlocalhost ip6-localhost ip6-loopback fe00::0\tip6-localnet fe00::0\tip6-mcastprefix fe00::1\tip6-allnodes fe00::2\tip6-allrouters 10.200.0.5\thostaliases-pod # Entries added by HostAliases. 127.0.0.1\tfoo.local\tbar.local 10.1.2.3\tfoo.remote\tbar.remote ``` with the additional entries specified at the bottom. ## Why does the kubelet manage the hosts file? {#why-does-kubelet-manage-the-hosts-file} The kubelet [manages](https://github.com/kubernetes/kubernetes/issues/14633) the `hosts` file for each container of the Pod to prevent Docker from [modifying](https://github.com/moby/moby/issues/17190) the file after the containers have already been started. {{< caution >}} Avoid making manual changes to the hosts file inside a container. If you make manual changes to the hosts file, those changes are lost when the container exits. {{< /caution >}} </del>"}
{"_id":"q-en-website-3f21ae3973e6d21ea34e3bf86052b2e94cabd01ce29db48b79f306b5acc3772d","text":"</td> </tr> <tr><td><code>userInfo</code> <B>[Required]</B><br/> <del> <a href=\"https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#userinfo-v1-authentication\"><code>authentication/v1.UserInfo</code></a> </del> <ins> <a href=\"https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#userinfo-v1-authentication-k8s-io\"><code>authentication/v1.UserInfo</code></a> </ins> </td> <td> <p>UserInfo is information about the requesting user</p>"}
{"_id":"q-en-website-3fcd630daea04592ed39c0c549fd6fd5ec138b82b2a1f8b5f5f01a9cb37a12d9","text":"<!-- overview --> <del> KubernetesのSecretはパスワード、OAuthトークン、SSHキーのような機密情報を保存し、管理できるようにします。 Secretに機密情報を保存することは、それらを{{< glossary_tooltip text=\"Pod\" term_id=\"pod\" >}}の定義や{{< glossary_tooltip text=\"コンテナイメージ\" term_id=\"image\" >}}に直接記載するより、安全で柔軟です。 詳しくは[Secretの設計文書](https://git.k8s.io/community/contributors/design-proposals/auth/secrets.md)を参照してください。 Secretはパスワード、トークン、キーのような小容量の機密データを含むオブジェクトです。 他の方法としては、そのような情報はPodの定義やイメージに含めることができます。 ユーザーはSecretを作ることができ、またシステムが作るSecretもあります。 </del> <ins> Secretとは、パスワードやトークン、キーなどの少量の機密データを含むオブジェクトのことです。 このような情報は、Secretを用いないと{{< glossary_tooltip term_id=\"pod\" >}}の定義や{{< glossary_tooltip text=\"コンテナイメージ\" term_id=\"image\" >}}に直接記載することになってしまうかもしれません。 Secretを使用すれば、アプリケーションコードに機密データを含める必要がなくなります。 なぜなら、Secretは、それを使用するPodとは独立して作成することができ、 Podの作成、閲覧、編集といったワークフローの中でSecret(およびそのデータ)が漏洩する危険性が低くなるためです。 また、Kubernetesやクラスター内で動作するアプリケーションは、不揮発性ストレージに機密データを書き込まないようにするなど、Secretで追加の予防措置を取ることができます。 Secretsは、{{< glossary_tooltip text=\"ConfigMaps\" term_id=\"configmap\" >}}に似ていますが、機密データを保持するために用います。 {{< caution >}} KubernetesのSecretは、デフォルトでは、APIサーバーの基礎となるデータストア(etcd)に暗号化されずに保存されます。APIにアクセスできる人は誰でもSecretを取得または変更でき、etcdにアクセスできる人も同様です。 さらに、名前空間でPodを作成する権限を持つ人は、そのアクセスを使用して、その名前空間のあらゆるSecretを読むことができます。これには、Deploymentを作成する能力などの間接的なアクセスも含まれます。 Secretsを安全に使用するには、以下の手順を推奨します。 1. Secretsを[安全に暗号化する](/docs/tasks/administer-cluster/encrypt-data/) 2. Secretsのデータの読み取りを制限する[RBACルール](/docs/reference/access-authn-authz/authorization/)の有効化または設定 3. 適切な場合には、RBACなどのメカニズムを使用して、どの原則が新しいSecretの作成や既存のSecretの置き換えを許可されるかを制限します。 {{< /caution >}} </ins> <!-- body -->"}
{"_id":"q-en-website-40e0c1ee42717b2deca8662aa195e5cf3dabcb13c5d1b71df4f36c8aa81bfd84","text":"| `ProbeTerminationGracePeriod` | `false` | Alpha | 1.21 | | | `ProcMountType` | `false` | Alpha | 1.12 | | | `QOSReserved` | `false` | Alpha | 1.11 | | <del> | `RemainingItemCount` | `false` | Alpha | 1.15 | | </del> <ins> | `RemainingItemCount` | `false` | Alpha | 1.15 | 1.15 | | `RemainingItemCount` | `true` | Beta | 1.16 | | </ins> | `RemoveSelfLink` | `false` | Alpha | 1.16 | 1.19 | | `RemoveSelfLink` | `true` | Beta | 1.20 | | | `RotateKubeletServerCertificate` | `false` | Alpha | 1.7 | 1.11 |"}
{"_id":"q-en-website-4150a9f64638a4fa97a488c5d32ed35107ebc6a821f9912a00cabd3401b3afe3","text":"<ins> --- title: Conceitos main_menu: true content_type: concept weight: 40 --- <!-- overview --> A seção de Conceitos irá te ajudar a aprender mais sobre as partes do ecossistema Kubernetes e as abstrações que o Kubernetes usa para representar seu {{< glossary_tooltip text=\"cluster\" term_id=\"cluster\" length=\"all\" >}}. Ela irá lhe ajudar a obter um entendimento mais profundo sobre como o Kubernetes funciona. <!-- body --> </ins>"}
{"_id":"q-en-website-41e441254509f93a77abc94d8cdbaf62af126c9345e2b6e658f8500c30152ed7","text":"{{- if or (eq .endTime nil ) (gt ( time .endTime ) now ) -}} {{- if not $announcementShown -}} {{- $announcementShown = true -}} <del> <div lang=\"en\" id=\"announcement\" style=\"background-color: #3371e3; color: #fff; {{ .style | safeCSS }}\"> </del> <ins> <div lang=\"en\" id=\"announcement\" data-announcement-name=\"{{ .name }}\" style=\"background-color: #3371e3; color: #fff; {{ .style | safeCSS }}\"> </ins> <aside> <div class=\"announcement-main\" data-nosnippet> {{ if .title }}"}
{"_id":"q-en-website-4246e8c9a4015739ba284e05463caef78f149b8eba255451bc08835835b0313d","text":"with static, long-lived credentials. In Kubernetes v1.24 and later, the [LegacyServiceAccountTokenNoAutoGeneration feature gate](/docs/reference/command-line-tools-reference/feature-gates/#feature-gates-for-graduated-or-deprecated-features) prevents Kubernetes from automatically creating these tokens for <del> ServiceAccounts. </del> <ins> ServiceAccounts. `LegacyServiceAccountTokenNoAutoGeneration` is enabled by default; in other words, Kubernetes does not create these tokens. </ins> ## Authenticating service account credentials {#authenticating-credentials}"}
{"_id":"q-en-website-42b3eddb87f4219a4491ff6a15dc7121eab18d583800f20ccfce92b9c253ee6a","text":"* 使用证书配置的 Nginx 服务器 * 使证书可以访问 Pod 的 [Secret](/zh/docs/concepts/configuration/secret/) <del> 你可以从 [Nginx https 示例](https://github.com/kubernetes/kubernetes/tree/{{< param \"githubbranch\" >}}/staging/https-nginx/) </del> <ins> 你可以从 [Nginx https 示例](https://github.com/kubernetes/examples/tree/{{< param \"githubbranch\" >}}/staging/https-nginx/) </ins> 获取所有上述内容。你需要安装 go 和 make 工具。如果你不想安装这些软件，可以按照 后文所述的手动执行步骤执行操作。简要过程如下："}
{"_id":"q-en-website-42e22e5e64b1e08cffcedcaac2bd7ce5b5dc4da8dddc27f914c0ce938c14040c","text":"[cAdvisor](https://github.com/google/cadvisor) that runs within the kubelet. If you enable the `PodAndContainerStatsFromCRI` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) in your cluster, and you use a container runtime that supports statistics access via <del> {{< glossary_tooltip term_id=\"cri\" text=\"Container Runtime Interface\">}} (CRI), then </del> <ins> {{< glossary_tooltip term_id=\"container-runtime-interface\" text=\"Container Runtime Interface\">}} (CRI), then </ins> the kubelet [fetches Pod- and container-level metric data using CRI](/docs/reference/instrumentation/cri-pod-container-metrics), and not via cAdvisor. ## {{% heading \"whatsnext\" %}}"}
{"_id":"q-en-website-433efe7806cef70a191f4b6c25e16f2e62b7e58a58baa9405d7f4750acc72934","text":"FLANNEL_IPMASQ=true ``` <del> 1. My Windows node cannot access my services using the service IP </del> <ins> 1. WindowsノードがService IPを使用してServiceにアクセスできない </ins> <del> This is a known limitation of the current networking stack on Windows. Windows Pods are able to access the service IP however. </del> <ins> これは、Windows上の現在のネットワークスタックの既知の制限です。ただし、Windows PodはService IPにアクセスできます。 </ins> <del> 1. No network adapter is found when starting kubelet </del> <ins> 1. kubeletの起動時にネットワークアダプターが見つかりません </ins> <del> The Windows networking stack needs a virtual adapter for Kubernetes networking to work. If the following commands return no results (in an admin shell), virtual network creation — a necessary prerequisite for Kubelet to work — has failed: </del> <ins> WindowsネットワーキングスタックがKubernetesネットワーキングを動かすには、仮想アダプターが必要です。次のコマンドを実行しても結果が返されない場合（管理シェルで）、仮想ネットワークの作成（Kubeletが機能するために必要な前提条件）に失敗したことになります。: </ins> ```powershell Get-HnsNetwork | ? Name -ieq \"cbr0\" Get-NetAdapter | ? Name -Like \"vEthernet (Ethernet*\" ``` <del> Often it is worthwhile to modify the [InterfaceName](https://github.com/microsoft/SDN/blob/master/Kubernetes/flannel/start.ps1#L6) parameter of the start.ps1 script, in cases where the host's network adapter isn't \"Ethernet\". Otherwise, consult the output of the `start-kubelet.ps1` script to see if there are errors during virtual network creation. </del> <ins> ホストのネットワークアダプターが「イーサネット」ではない場合、多くの場合、start.ps1スクリプトの[InterfaceName](https://github.com/microsoft/SDN/blob/master/Kubernetes/flannel/start.ps1#L6)パラメーターを修正する価値があります。そうでない場合は`start-kubelet.ps1`スクリプトの出力結果を調べて、仮想ネットワークの作成中にエラーがないか確認します。 </ins> <del> 1. My Pods are stuck at \"Container Creating\" or restarting over and over </del> <ins> 1. Podが「Container Creating」と表示されたまま動かなくなったり、何度も再起動を繰り返します </ins> <del> Check that your pause image is compatible with your OS version. The [instructions](https://docs.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/deploying-resources) assume that both the OS and the containers are version 1803. If you have a later version of Windows, such as an Insider build, you need to adjust the images accordingly. Please refer to the Microsoft's [Docker repository](https://hub.docker.com/u/microsoft/) for images. Regardless, both the pause image Dockerfile and the sample service expect the image to be tagged as :latest. </del> <ins> PauseイメージがOSバージョンと互換性があることを確認してください。[説明](https://docs.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/deploying-resources)では、OSとコンテナの両方がバージョン1803であると想定しています。それ以降のバージョンのWindowsを使用している場合は、Insiderビルドなどでは、それに応じてイメージを調整する必要があります。イメージについては、Microsoftの[Dockerレジストリ](https://hub.docker.com/u/microsoft/)を参照してください。いずれにしても、PauseイメージのDockerfileとサンプルサービスの両方で、イメージに:latestのタグが付けられていると想定しています。 </ins> <del> Starting with Kubernetes v1.14, Microsoft releases the pause infrastructure container at `mcr.microsoft.com/k8s/core/pause:1.2.0`. For more information search for \"pause\" in the [Guide for adding Windows Nodes in Kubernetes](../user-guide-windows-nodes). </del> <ins> Kubernetes v1.14以降、MicrosoftはPauseインフラストラクチャコンテナを`mcr.microsoft.com/k8s/core/pause:1.2.0`でリリースしています。詳細については、[KubernetesにWindowsノードを追加するためのガイド](../user-guide-windows-nodes)で「Pause」を検索してください。 </ins> <del> 1. DNS resolution is not properly working </del> <ins> 1. DNS名前解決が正しく機能していない </ins> <del> Check the DNS limitations for Windows in this [section](#dns-limitations). </del> <ins> この[セクション](#dns-limitations)でDNSの制限を確認してください。 </ins> <del> 1. `kubectl port-forward` fails with \"unable to do port forwarding: wincat not found\" </del> <ins> 1. `kubectl port-forward`が「ポート転送を実行できません:wincatが見つかりません」で失敗します </ins> <del> This was implemented in Kubernetes 1.15, and the pause infrastructure container `mcr.microsoft.com/k8s/core/pause:1.2.0`. Be sure to use these versions or newer ones. If you would like to build your own pause infrastructure container, be sure to include [wincat](https://github.com/kubernetes-sigs/sig-windows-tools/tree/master/cmd/wincat) </del> <ins> これはKubernetes 1.15、およびPauseインフラストラクチャコンテナ`mcr.microsoft.com/k8s/core/pause:1.2.0`で実装されました。必ずこれらのバージョン以降を使用してください。 独自のPauseインフラストラクチャコンテナを構築する場合は、必ず[wincat](https://github.com/kubernetes-sigs/sig-windows-tools/tree/master/cmd/wincat)を含めてください。 </ins> <del> 1. My Kubernetes installation is failing because my Windows Server node is behind a proxy </del> <ins> 1. Windows Serverノードがプロキシの背後にあるため、Kubernetesのインストールが失敗します </ins> <del> If you are behind a proxy, the following PowerShell environment variables must be defined: </del> <ins> プロキシの背後にある場合は、次のPowerShell環境変数を定義する必要があります。: </ins> ```PowerShell [Environment]::SetEnvironmentVariable(\"HTTP_PROXY\", \"http://proxy.example.com:80/\", [EnvironmentVariableTarget]::Machine) [Environment]::SetEnvironmentVariable(\"HTTPS_PROXY\", \"http://proxy.example.com:443/\", [EnvironmentVariableTarget]::Machine) ``` <del> 1. What is a `pause` container? </del> <ins> 1. `pause`コンテナとは何ですか </ins> <del> In a Kubernetes Pod, an infrastructure or \"pause\" container is first created to host the container endpoint. Containers that belong to the same pod, including infrastructure and worker containers, share a common network namespace and endpoint (same IP and port space). Pause containers are needed to accommodate worker containers crashing or restarting without losing any of the networking configuration. </del> <ins> Kubernetes Podでは、インフラストラクチャまたは「pause」コンテナが最初に作成され、コンテナエンドポイントをホストします。インフラストラクチャやワーカーコンテナなど、同じPodに属するコンテナは、共通のネットワークネームスペースとエンドポイント（同じIPとポートスペース）を共有します。Pauseコンテナは、ネットワーク構成を失うことなくクラッシュまたは再起動するワーカーコンテナに対応するために必要です。 </ins> <del> The \"pause\" (infrastructure) image is hosted on Microsoft Container Registry (MCR). You can access it using `docker pull mcr.microsoft.com/k8s/core/pause:1.2.0`. For more details, see the [DOCKERFILE](https://github.com/kubernetes-sigs/sig-windows-tools/tree/master/cmd/wincat). </del> <ins> 「pause」（インフラストラクチャ）イメージは、Microsoft Container Registry（MCR）でホストされています。`docker pull mcr.microsoft.com/k8s/core/pause:1.2.0`を使用してアクセスできます。詳細については、[DOCKERFILE](https://github.com/kubernetes-sigs/sig-windows-tools/tree/master/cmd/wincat)をご覧ください。 </ins> <del> ### Further investigation </del> <ins> ### さらなる調査 </ins> <del> If these steps don't resolve your problem, you can get help running Windows containers on Windows nodes in Kubernetes through: </del> <ins> これらの手順で問題が解決しない場合は、次の方法で、KubernetesのWindowsノードでWindowsコンテナを実行する際のヘルプを利用できます。: </ins> <del> * StackOverflow [Windows Server Container](https://stackoverflow.com/questions/tagged/windows-server-container) topic * Kubernetes Official Forum [discuss.kubernetes.io](https://discuss.kubernetes.io/) </del> <ins> * StackOverflow [Windows Server Container](https://stackoverflow.com/questions/tagged/windows-server-container)トピック * Kubernetesオフィシャルフォーラム [discuss.kubernetes.io](https://discuss.kubernetes.io/) </ins> * Kubernetes Slack [#SIG-Windows Channel](https://kubernetes.slack.com/messages/sig-windows) <del> ## Reporting Issues and Feature Requests </del> <ins> ## IssueとFeatureリクエストの報告 </ins> <del> If you have what looks like a bug, or you would like to make a feature request, please use the [GitHub issue tracking system](https://github.com/kubernetes/kubernetes/issues). You can open issues on [GitHub](https://github.com/kubernetes/kubernetes/issues/new/choose) and assign them to SIG-Windows. You should first search the list of issues in case it was reported previously and comment with your experience on the issue and add additional logs. SIG-Windows Slack is also a great avenue to get some initial support and troubleshooting ideas prior to creating a ticket. </del> <ins> バグのようなものがある場合、またはFeatureリクエストを行う場合は、[GitHubのIssueシステム](https://github.com/kubernetes/kubernetes/issues)を使用してください。[GitHub](https://github.com/kubernetes/kubernetes/issues/new/choose)でIssueを開いて、SIG-Windowsに割り当てることができます。以前に報告された場合は、まずIssueリストを検索し、Issueについての経験をコメントして、追加のログを加える必要があります。SIG-Windows Slackは、チケットを作成する前に、初期サポートとトラブルシューティングのアイデアを得るための素晴らしい手段でもあります。 </ins> <del> If filing a bug, please include detailed information about how to reproduce the problem, such as: </del> <ins> バグを報告する場合は、問題の再現方法に関する次のような詳細情報を含めてください。: </ins> <del> * Kubernetes version: kubectl version * Environment details: Cloud provider, OS distro, networking choice and configuration, and Docker version * Detailed steps to reproduce the problem * [Relevant logs](https://github.com/kubernetes/community/blob/master/sig-windows/CONTRIBUTING.md#gathering-logs) * Tag the issue sig/windows by commenting on the issue with `/sig windows` to bring it to a SIG-Windows member's attention </del> <ins> * Kubernetesのバージョン: kubectlのバージョン * 環境の詳細: クラウドプロバイダー、OSのディストリビューション、選択したネットワーキングと構成、およびDockerのバージョン * 問題を再現するための詳細な手順 * [関連するログ](https://github.com/kubernetes/community/blob/master/sig-windows/CONTRIBUTING.md#gathering-logs) * `/sig windows`でIssueにコメントして、Issueにsig/windowsのタグを付けて、SIG-Windowsメンバーが気付くようにします </ins> ## {{% heading \"whatsnext\" %}} <del> We have a lot of features in our roadmap. An abbreviated high level list is included below, but we encourage you to view our [roadmap project](https://github.com/orgs/kubernetes/projects/8) and help us make Windows support better by [contributing](https://github.com/kubernetes/community/blob/master/sig-windows/). </del> <ins> ロードマップには多くの機能があります。高レベルの簡略リストを以下に示しますが、[ロードマッププロジェクト](https://github.com/orgs/kubernetes/projects/8)を見て、[貢献すること](https://github.com/kubernetes/community/blob/master/sig-windows/)によってWindowsサポートを改善することをお勧めします。 </ins> ### CRI-ContainerD <del> {{< glossary_tooltip term_id=\"containerd\" >}} is another OCI-compliant runtime that recently graduated as a {{< glossary_tooltip text=\"CNCF\" term_id=\"cncf\" >}} project. It's currently tested on Linux, but 1.3 will bring support for Windows and Hyper-V. [[reference](https://blog.docker.com/2019/02/containerd-graduates-within-the-cncf/)] </del> <ins> {{< glossary_tooltip term_id=\"containerd\" >}}は、最近{{< glossary_tooltip text=\"CNCF\" term_id=\"cncf\" >}}プロジェクトとして卒業した、もう1つのOCI準拠ランタイムです。現在Linuxでテストされていますが、1.3はWindowsとHyper-Vをサポートします。[[リファレンス](https://blog.docker.com/2019/02/containerd-graduates-within-the-cncf/)] </ins> <del> The CRI-ContainerD interface will be able to manage sandboxes based on Hyper-V. This provides a foundation where RuntimeClass could be implemented for new use cases including: </del> <ins> CRI-ContainerDインターフェイスは、Hyper-Vに基づいてサンドボックスを管理できるようになります。これにより、RuntimeClassを次のような新しいユースケースに実装できる基盤が提供されます: </ins> <del> * Hypervisor-based isolation between pods for additional security * Backwards compatibility allowing a node to run a newer Windows Server version without requiring containers to be rebuilt * Specific CPU/NUMA settings for a pod * Memory isolation and reservations </del> <ins> * Pod間のハイパーバイザーベースの分離により、セキュリティを強化 * 下位互換性により、コンテナの再構築を必要とせずにノードで新しいWindows Serverバージョンを実行 * Podの特定のCPU/NUMA設定 * メモリの分離と予約 </ins> <del> ### Hyper-V isolation </del> <ins> ### Hyper-V分離 </ins> <del> The existing Hyper-V isolation support, an experimental feature as of v1.10, will be deprecated in the future in favor of the CRI-ContainerD and RuntimeClass features mentioned above. To use the current features and create a Hyper-V isolated container, the kubelet should be started with feature gates `HyperVContainer=true` and the Pod should include the annotation `experimental.windows.kubernetes.io/isolation-type=hyperv`. In the experiemental release, this feature is limited to 1 container per Pod. </del> <ins> 既存のHyper-V分離サポートは、v1.10の試験的な機能であり、上記のCRI-ContainerD機能とRuntimeClass機能を優先して将来廃止される予定です。現在の機能を使用してHyper-V分離コンテナを作成するには、kubeletのフィーチャーゲートを`HyperVContainer=true`で開始し、Podにアノテーション`experimental.windows.kubernetes.io/isolation-type=hyperv`を含める必要があります。実験的リリースでは、この機能はPodごとに1つのコンテナに制限されています。 </ins> ```yaml apiVersion: apps/v1"}
{"_id":"q-en-website-441191e60dcd7321753e2b91c1ee2bbd65bc28778e494c7ce0b1c84e60db5dc7","text":"* Provider support for dual-stack networking (Cloud provider or otherwise must be able to provide Kubernetes nodes with routable IPv4/IPv6 network interfaces) * A [network plugin](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/) that supports dual-stack (such as Kubenet or Calico) <del> * Kube-proxy running in mode IPVS </del> * [Dual-stack enabled](/docs/concepts/services-networking/dual-stack/) cluster {{< version-check >}}"}
{"_id":"q-en-website-448f1bde9b6d1d08549c072860f1c1932c2d492be14752ffd8283bdd1a24f5e7","text":"For further documentation refer to the authorization.v1beta1 API objects and [webhook.go](https://github.com/kubernetes/kubernetes/blob/{{< param \"githubbranch\" >}}/staging/src/k8s.io/apiserver/plugin/pkg/authorizer/webhook/webhook.go)."}
{"_id":"q-en-website-44978bcd7182b82a8d3795f95108f80a4c785059d670b75ad1c441d515609fae","text":"* `apiserver_flowcontrol_dispatched_requests_total` is a counter vector (cumulative since server start) of requests that began <del> executing, broken down by the labels `flowSchema` (indicating the one that matched the request) and `priorityLevel` (indicating the </del> <ins> executing, broken down by the labels `flow_schema` (indicating the one that matched the request) and `priority_level` (indicating the </ins> one to which the request was assigned). * `apiserver_current_inqueue_requests` is a gauge vector of recent"}
{"_id":"q-en-website-44ccedc4f7df7cb562fb3b83a089536e09d43679eb7c690091fadd14ec39a280","text":"<ins> --- title: Scheduling weight: 70 toc-hide: true --- </ins>"}
{"_id":"q-en-website-44d914294be8a74e126214dacd248f673424a31893ae89ad860f91fd31d967bf","text":"kubectl create secret docker-registry secret-tiger-docker  --docker-username=tiger  --docker-password=pass113  <del> --docker-email=tiger@acme.com </del> <ins> --docker-email=tiger@acme.com  --docker-server=my-registry.example:5000 </ins> ``` このコマンドは、`kubernetes.io/dockerconfigjson`型のSecretを作成します。"}
{"_id":"q-en-website-45360eac8815254d4f687531b77a01901bcbf2271e919484cc14a2f697e1c85f","text":"--> [HostAliases](/docs/reference/generated/kubernetes-api/{{< param \"version\" >}}/#hostalias-v1-core) 是一个包含主机名和 IP 地址的可选列表，配置后将被注入到 Pod 内的 hosts 文件中。 <del> 该选项仅适用于没有配置 hostNetwork 的 Pod. </del> <ins> 该选项仅适用于没有配置 hostNetwork 的 Pod。 </ins>"}
{"_id":"q-en-website-4682809bdcb920102c94c746abe29b8916bbdf22a039171ca936e1cf573d417b","text":"release in order to get access to the packages of the desired Kubernetes minor version. <del> {{< tabs name=\"k8s_install_versions\" >}} </del> <ins> {{< tabs name=\"k8s_upgrade_versions\" >}} </ins> {{% tab name=\"Ubuntu, Debian or HypriotOS\" %}} 1. Open the file that defines the Kubernetes `apt` repository using a text editor of your choice:"}
{"_id":"q-en-website-4759fab2c6647a572f79a5486fec6e34a171d7c10c3433fb343bd0f3275a8244","text":"1. Validate the binary (optional) <del> Download the kubectl checksum file: </del> <ins> Download the `kubectl` checksum file: </ins> ```powershell curl -LO \"https://dl.k8s.io/{{< param \"fullversion\" >}}/bin/windows/amd64/kubectl.exe.sha256\" ``` <del> Validate the kubectl binary against the checksum file: </del> <ins> Validate the `kubectl` binary against the checksum file: </ins> - Using Command Prompt to manually compare `CertUtil`'s output to the checksum file downloaded:"}
{"_id":"q-en-website-47ffeaf7ab78293ce6b6bfda85144e8c7b171f30a2fb4c5069bd6f7ce645d673","text":"the YAML: `192.0.2.42:9376` (TCP). {{< note >}} <del> The Kubernetes API server does not allow proxying to endpoints that are not mapped to pods. Actions such as `kubectl proxy <service-name>` where the service has no selector will fail due to this constraint. This prevents the Kubernetes API server from being used as a proxy to endpoints the caller may not be authorized to access. </del> <ins> The Kubernetes API server does not allow proxying to endpoints that are not mapped to pods. Actions such as `kubectl proxy <service-name>` where the service has no selector will fail due to this constraint. This prevents the Kubernetes API server from being used as a proxy to endpoints the caller may not be authorized to access. </ins> {{< /note >}} An ExternalName Service is a special case of Service that does not have"}
{"_id":"q-en-website-48b1050c1aa4825d8cb94c4a449e432b2cfa1b0b5300e74d53f2a0085efa9deb","text":"<ins> --- title: kubectlを使用してSecretを管理する content_type: task weight: 10 description: kubectlコマンドラインを使用してSecretを作成する --- <!-- overview --> ## {{% heading \"prerequisites\" %}} {{< include \"task-tutorial-prereqs.md\" >}} <!-- steps --> ## Secretを作成する `Secret`はデータベースにアクセスするためにPodが必要とするユーザー資格情報を含めることができます。 たとえば、データベース接続文字列はユーザー名とパスワードで構成されます。 ユーザー名はローカルマシンの`./username.txt`に、パスワードは`./password.txt`に保存します。 ```shell echo -n 'admin' > ./username.txt echo -n '1f2d1e2e67df' > ./password.txt ``` 上記の2つのコマンドの`-n`フラグは、生成されたファイルにテキスト末尾の余分な改行文字が含まれないようにします。 `kubectl`がファイルを読み取り、内容をbase64文字列にエンコードすると、余分な改行文字もエンコードされるため、これは重要です。 `kubectl create secret`コマンドはこれらのファイルをSecretにパッケージ化し、APIサーバー上にオブジェクトを作成します。 ```shell kubectl create secret generic db-user-pass  --from-file=./username.txt  --from-file=./password.txt ``` 出力は次のようになります: ``` secret/db-user-pass created ``` ファイル名がデフォルトのキー名になります。オプションで`--from-file=[key=]source`を使用してキー名を設定できます。たとえば: ```shell kubectl create secret generic db-user-pass  --from-file=username=./username.txt  --from-file=password=./password.txt ``` `--from-file`に指定したファイルに含まれるパスワードの特殊文字をエスケープする必要はありません。 また、`--from-literal=<key>=<value>`タグを使用してSecretデータを提供することもできます。 このタグは、複数のキーと値のペアを提供するために複数回指定することができます。 `$`、``、`*`、`=`、`!`などの特殊文字は[シェル](https://en.wikipedia.org/wiki/Shell_(computing))によって解釈されるため、エスケープを必要とすることに注意してください。 ほとんどのシェルでは、パスワードをエスケープする最も簡単な方法は、シングルクォート(`'`)で囲むことです。 たとえば、実際のパスワードが`S!B*d$zDsb=`の場合、次のようにコマンドを実行します: ```shell kubectl create secret generic dev-db-secret  --from-literal=username=devuser  --from-literal=password='S!B*d$zDsb=' ``` ## Secretを検証する Secretが作成されたことを確認できます: ```shell kubectl get secrets ``` 出力は次のようになります: ``` NAME                  TYPE                                  DATA      AGE db-user-pass          Opaque                                2         51s ``` `Secret`の説明を参照できます: ```shell kubectl describe secrets/db-user-pass ``` 出力は次のようになります: ``` Name:            db-user-pass Namespace:       default Labels:          <none> Annotations:     <none> Type:            Opaque Data ==== password:    12 bytes username:    5 bytes ``` `kubectl get`と`kubectl describe`コマンドはデフォルトでは`Secret`の内容を表示しません。 これは、`Secret`が不用意に他人にさらされたり、ターミナルログに保存されたりしないようにするためです。 ## Secretをデコードする  {#decoding-secret} 先ほど作成したSecretの内容を見るには、以下のコマンドを実行します: ```shell kubectl get secret db-user-pass -o jsonpath='{.data}' ``` 出力は次のようになります: ```json {\"password.txt\":\"MWYyZDFlMmU2N2Rm\",\"username.txt\":\"YWRtaW4=\"} ``` `password.txt`のデータをデコードします: ```shell echo 'MWYyZDFlMmU2N2Rm' | base64 --decode ``` 出力は次のようになります: ``` 1f2d1e2e67df ``` ## クリーンアップ 作成したSecretを削除するには次のコマンドを実行します: ```shell kubectl delete secret db-user-pass ``` <!-- discussion --> ## {{% heading \"whatsnext\" %}} - [Secretのコンセプト](/ja/docs/concepts/configuration/secret/)を読む - [設定ファイルを使用してSecretを管理する](/docs/tasks/configmap-secret/managing-secret-using-config-file/)方法を知る - [kustomizeを使用してSecretを管理する](/docs/tasks/configmap-secret/managing-secret-using-kustomize/)方法を知る </ins>"}
{"_id":"q-en-website-4a12fd7fd13af4ab625fee2d2d928f8277b80c986ad454f5c32022875ec6c750","text":"/usr/local/bin/kubectl-foo /usr/local/bin/kubectl-bar ``` <del> ``` </del> <ins> ```shell </ins> # this command can also warn us about plugins that are # not executable, or that are overshadowed by other # plugins, for example"}
{"_id":"q-en-website-4b82eee99d3f40e27a30b17a2cbab8641291fc5453f332c25e44ef3624e6dec1","text":"_Nothing has changed._ ### Changed <del> - github.com/Azure/azure-sdk-for-go: [v40.2.0+incompatible → v43.0.0+incompatible](https://github.com/Azure/azure-sdk-for-go/compare/v40.2.0...v43.0.0) - github.com/coredns/corefile-migration: [v1.0.6 → v1.0.8](https://github.com/coredns/corefile-migration/compare/v1.0.6...v1.0.8) - k8s.io/klog/v2: v2.0.0 → v2.1.0 </del> <ins> _Nothing has changed._ </ins> ### Removed _Nothing has changed._ <del> # v1.19.0-beta.1 </del> <ins> # v1.20.0-alpha.2 </ins> <del> ## Downloads for v1.19.0-beta.1 </del> <ins> ## Downloads for v1.20.0-alpha.2 </ins> ### Source Code filename | sha512 hash -------- | ----------- <del> [kubernetes.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes.tar.gz) | c4ab79e987790fbda842310525abecee60861e44374c414159e60d74e85b4dd36d9d49253b8e7f08aec36a031726f9517d0a401fb748e41835ae2dc86aee069d [kubernetes-src.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-src.tar.gz) | 08d1aadb8a31b35f3bc39f44d8f97b7e98951f833bb87f485f318c6acfdb53539851fbb2d4565036e00b6f620c5b1882c6f9620759c3b36833da1d6b2b0610f2 </del> <ins> [kubernetes.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes.tar.gz) | 45089a4d26d56a5d613ecbea64e356869ac738eca3cc71d16b74ea8ae1b4527bcc32f1dc35ff7aa8927e138083c7936603faf063121d965a2f0f8ba28fa128d8 [kubernetes-src.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-src.tar.gz) | 646edd890d6df5858b90aaf68cc6e1b4589b8db09396ae921b5c400f2188234999e6c9633906692add08c6e8b4b09f12b2099132b0a7533443fb2a01cfc2bf81 </ins> ### Client binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-client-darwin-386.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-client-darwin-386.tar.gz) | 55eb230fdb4e60ded6c456ec6e03363c6d55e145a956aa5eff0c2b38d8ecfe848b4a404169def45d392e747e4d04ee71fe3182ab1e6426110901ccfb2e1bc17f [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-client-darwin-amd64.tar.gz) | ddc03644081928bd352c40077f2a075961c90a7159964be072b3e05ec170a17d6d78182d90210c18d24d61e75b45eae3d1b1486626db9e28f692dfb33196615c [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-client-linux-386.tar.gz) | 6e1e00a53289bd9a4d74a61fce4665786051aafe8fef8d1d42de88ba987911bfb7fd5f4a2c3771ae830819546cf9f4badd94fd90c50ca74367c1ace748e8eafd [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-client-linux-amd64.tar.gz) | 2c4db87c61bc4a528eb2af9246648fc7a015741fe52f551951fda786c252eca1dc48a4325be70e6f80f1560f773b763242334ad4fe06657af290e610f10bc231 [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-client-linux-arm.tar.gz) | 8a2bebf67cbd8f91ba38edc36a239aa50d3e58187827763eb5778a5ca0d9d35be97e193b794bff415e8f5de071e47659033dc0420e038d78cc32e841a417a62a [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-client-linux-arm64.tar.gz) | f2d0029efc03bf17554c01c11e77b161b8956d9da4b17962ca878378169cbdee04722bbda87279f4b7431c91db0e92bfede45dcc6d971f34d3fe891339b7c47b [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-client-linux-ppc64le.tar.gz) | 45eb3fe40951ba152f05aa0fe41b7c17ffb91ee3cecb12ec19d2d9cdb467267c1eb5696660687852da314eb8a14a9ebf5f5da21eca252e1c2e3b18dca151ad0d [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-client-linux-s390x.tar.gz) | 2097ac5d593dd0951a34df9bdf7883b5c228da262042904ee3a2ccfd1f9c955ff6a3a59961850053e41646bce8fc70a023efe9e9fe49f14f9a6276c8da22f907 [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-client-windows-386.tar.gz) | c38b034e8ac3a5972a01f36b184fe1a195f6a422a3c6564f1f3faff858b1220173b6ab934e7b7ec200931fd7d9456e947572620d82d02e7b05fc61a7fb67ec70 [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-client-windows-amd64.tar.gz) | 0501694734381914882836e067dc177e8bccd48a4826e286017dc5f858f27cdef348edbb664dda59162f6cd3ac14a9e491e314a3ea032dec43bc77610ce8c8bc </del> <ins> [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-client-darwin-amd64.tar.gz) | c136273883e24a2a50b5093b9654f01cdfe57b97461d34885af4a68c2c4d108c07583c02b1cdf7f57f82e91306e542ce8f3bddb12fcce72b744458bc4796f8eb [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-client-linux-386.tar.gz) | 6ec59f1ed30569fa64ddb2d0de32b1ae04cda4ffe13f339050a7c9d7c63d425ee6f6d963dcf82c17281c4474da3eaf32c08117669052872a8c81bdce2c8a5415 [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-client-linux-amd64.tar.gz) | 7b40a4c087e2ea7f8d055f297fcd39a3f1cb6c866e7a3981a9408c3c3eb5363c648613491aad11bc7d44d5530b20832f8f96f6ceff43deede911fb74aafad35f [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-client-linux-arm.tar.gz) | cda9955feebea5acb8f2b5b87895d24894bbbbde47041453b1f926ebdf47a258ce0496aa27d06bcbf365b5615ce68a20d659b64410c54227216726e2ee432fca [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-client-linux-arm64.tar.gz) | f65bd9241c7eb88a4886a285330f732448570aea4ededaebeabcf70d17ea185f51bf8a7218f146ee09fb1adceca7ee71fb3c3683834f2c415163add820fba96e [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-client-linux-ppc64le.tar.gz) | 1e377599af100a81d027d9199365fb8208d443a8e0a97affff1a79dc18796e14b78cb53d6e245c1c1e8defd0e050e37bf5f2a23c8a3ff45a6d18d03619709bf5 [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-client-linux-s390x.tar.gz) | 1cdee81478246aa7e7b80ae4efc7f070a5b058083ae278f59fad088b75a8052761b0e15ab261a6e667ddafd6a69fb424fc307072ed47941cad89a85af7aee93d [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-client-windows-386.tar.gz) | d8774167c87b6844c348aa15e92d5033c528d6ab9e95d08a7cb22da68bafd8e46d442cf57a5f6affad62f674c10ae6947d524b94108b5e450ca78f92656d63c0 [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-client-windows-amd64.tar.gz) | f664b47d8daa6036f8154c1dc1f881bfe683bf57c39d9b491de3848c03d051c50c6644d681baf7f9685eae45f9ce62e4c6dfea2853763cfe8256a61bdd59d894 </ins> ### Server binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-server-linux-amd64.tar.gz) | 0dd2058889eabbf0b05b6fafd593997ff9911467f0fc567c142583adf0474f4d0e2f4024b4906ff9ee4264d1cbbfde66596ccb8c73b3d5bb79f67e5eb4b3258a [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-server-linux-arm.tar.gz) | 9c3a33d7c198116386178a4f8ee7d4df82e810d6f26833f19f93eff112c29f9f89e5ee790013ad1d497856ecb2662ee95a49fc6a41f0d33cc67e431d06135b88 [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-server-linux-arm64.tar.gz) | 11f83132f729bec4a4d84fc1983dbd5ddd1643d000dc74c6e05f35637de21533834a572692fc1281c7b0bd29ee93e721fb00e276983e36c327a1950266b17f6d [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-server-linux-ppc64le.tar.gz) | 949334065d968f10207089db6175dcc4bf9432b3b48b120f689cd39c56562a0f4f60d774c95a20a5391d0467140a4c3cb6b2a2dfedccfda6c20f333a63ebcf81 [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-server-linux-s390x.tar.gz) | 29e8f6a22969d8ab99bf6d272215f53d8f7a125d0c5c20981dcfe960ed440369f831c71a94bb61974b486421e4e9ed936a9421a1be6f02a40e456daab4995663 </del> <ins> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-server-linux-amd64.tar.gz) | d6fcb4600be0beb9de222a8da64c35fe22798a0da82d41401d34d0f0fc7e2817512169524c281423d8f4a007cd77452d966317d5a1b67d2717a05ff346e8aa7d [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-server-linux-arm.tar.gz) | 022a76cf10801f8afbabb509572479b68fdb4e683526fa0799cdbd9bab4d3f6ecb76d1d63d0eafee93e3edf6c12892d84b9c771ef2325663b95347728fa3d6c0 [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-server-linux-arm64.tar.gz) | 0679aadd60bbf6f607e5befad74b5267eb2d4c1b55985cc25a97e0f4c5efb7acbb3ede91bfa6a5a5713dae4d7a302f6faaf678fd6b359284c33d9a6aca2a08bb [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-server-linux-ppc64le.tar.gz) | 9f2cfeed543b515eafb60d9765a3afff4f3d323c0a5c8a0d75e3de25985b2627817bfcbe59a9a61d969e026e2b861adb974a09eae75b58372ed736ceaaed2a82 [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-server-linux-s390x.tar.gz) | 937258704d7b9dcd91f35f2d34ee9dd38c18d9d4e867408c05281bfbbb919ad012c95880bee84d2674761aa44cc617fb2fae1124cf63b689289286d6eac1c407 </ins> ### Node binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-node-linux-amd64.tar.gz) | 3d9767e97a40b501f29bbfc652c8fd841eae1dee22a97fdc20115e670081de7fa8e84f6e1be7bbf2376b59c5eef15fb5291415ae2e24ce4c9c5e141faa38c47c [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-node-linux-arm.tar.gz) | 8ccf401e0bd0c59403af49046b49cf556ff164fca12c5233169a80e18cc4367f404fd7edd236bb862bff9fd25b687d48a8d57d5567809b89fd2727549d0dc48f [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-node-linux-arm64.tar.gz) | 3e1fa2bde05a4baec6ddd43cd1994d155a143b9c825ab5dafe766efc305cb1aad92d6026c41c05e9da114a04226361fb6b0510b98e3b05c3ed510da23db403b3 [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-node-linux-ppc64le.tar.gz) | 01df4be687f5634afa0ab5ef06f8cee17079264aa452f00a45eccb8ace654c9acc6582f4c74e8242e6ca7715bc48bf2a7d2c4d3d1eef69106f99c8208bc245c4 [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-node-linux-s390x.tar.gz) | 5523b0b53c30b478b1a9e1df991607886acdcde8605e1b44ef91c94993ca2256c74f6e38fbdd24918d7dbf7afd5cd73d24a3f7ff911e9762819776cc19935363 [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.1/kubernetes-node-windows-amd64.tar.gz) | 8e7ebf000bc8dec1079a775576807c0a11764d20a59e16f89d93c948532ba5e6864efd3e08c3e8cc5bd7e7f97bb65baefbf2f01cb226897abd5e01997a4c4f75 </del> <ins> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-node-linux-amd64.tar.gz) | 076165d745d47879de68f4404eaf432920884be48277eb409e84bf2c61759633bf3575f46b0995f1fc693023d76c0921ed22a01432e756d7f8d9e246a243b126 [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-node-linux-arm.tar.gz) | 1ff2e2e3e43af41118cdfb70c778e15035bbb1aca833ffd2db83c4bcd44f55693e956deb9e65017ebf3c553f2820ad5cd05f5baa33f3d63f3e00ed980ea4dfed [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-node-linux-arm64.tar.gz) | b232c7359b8c635126899beee76998078eec7a1ef6758d92bcdebe8013b0b1e4d7b33ecbf35e3f82824fe29493400845257e70ed63c1635bfa36c8b3b4969f6f [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-node-linux-ppc64le.tar.gz) | 51d415a068f554840f4c78d11a4fedebd7cb03c686b0ec864509b24f7a8667ebf54bb0a25debcf2b70f38be1e345e743f520695b11806539a55a3620ce21946f [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-node-linux-s390x.tar.gz) | b51c082d8af358233a088b632cf2f6c8cfe5421471c27f5dc9ba4839ae6ea75df25d84298f2042770097554c01742bb7686694b331ad9bafc93c86317b867728 [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.2/kubernetes-node-windows-amd64.tar.gz) | 91b9d26620a2dde67a0edead0039814efccbdfd54594dda3597aaced6d89140dc92612ed0727bc21d63468efeef77c845e640153b09e39d8b736062e6eee0c76 </ins> <del> ## Changelog since v1.19.0-alpha.3 </del> <ins> ## Changelog since v1.20.0-alpha.1 </ins> <del> ## Urgent Upgrade Notes </del> <ins> ## Changes by Kind </ins> <del> ### (No, really, you MUST read this before you upgrade) </del> <ins> ### Deprecation </ins> <del> - ACTION REQUIRED : Switch core master base images (kube-controller-manager) from debian to distroless. If you need Flex Volumes support using scripts, please build your own image with required packages (like bash) ([#91329](https://github.com/kubernetes/kubernetes/pull/91329), [@dims](https://github.com/dims)) [SIG Cloud Provider, Release, Storage and Testing] - Kubeadm: Move the \"kubeadm init\" phase \"kubelet-start\" later in the init workflow, after the \"kubeconfig\" phase. This makes kubeadm start the kubelet only after the KubeletConfiguration component config file (/var/lib/kubelet/config.yaml) is generated and solves a problem where init systems like OpenRC cannot crashloop the kubelet service. ([#90892](https://github.com/kubernetes/kubernetes/pull/90892), [@xphoniex](https://github.com/xphoniex)) [SIG Cluster Lifecycle] ## Changes by Kind </del> <ins> - Action-required: kubeadm: graduate the \"kubeadm alpha certs\" command to a parent command \"kubeadm certs\". The command \"kubeadm alpha certs\" is deprecated and will be removed in a future release. Please migrate. ([#94938](https://github.com/kubernetes/kubernetes/pull/94938), [@yagonobre](https://github.com/yagonobre)) [SIG Cluster Lifecycle] - Action-required: kubeadm: remove the deprecated feature --experimental-kustomize from kubeadm commands. The feature was replaced with --experimental-patches in 1.19. To migrate see the --help description for the --experimental-patches flag. ([#94871](https://github.com/kubernetes/kubernetes/pull/94871), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: deprecate self-hosting support. The experimental command \"kubeadm alpha self-hosting\" is now deprecated and will be removed in a future release. ([#95125](https://github.com/kubernetes/kubernetes/pull/95125), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Removes deprecated scheduler metrics DeprecatedSchedulingDuration, DeprecatedSchedulingAlgorithmPredicateEvaluationSecondsDuration, DeprecatedSchedulingAlgorithmPriorityEvaluationSecondsDuration ([#94884](https://github.com/kubernetes/kubernetes/pull/94884), [@arghya88](https://github.com/arghya88)) [SIG Instrumentation and Scheduling] - Scheduler alpha metrics binding_duration_seconds and scheduling_algorithm_preemption_evaluation_seconds are deprecated, Both of those metrics are now covered as part of framework_extension_point_duration_seconds, the former as a PostFilter the latter and a Bind plugin. The plan is to remove both in 1.21 ([#95001](https://github.com/kubernetes/kubernetes/pull/95001), [@arghya88](https://github.com/arghya88)) [SIG Instrumentation and Scheduling] </ins> ### API Change <del> - CertificateSigningRequest API conditions were updated: - a `status` field was added; this field defaults to `True`, and may only be set to `True` for `Approved`, `Denied`, and `Failed` conditions - a `lastTransitionTime` field was added - a `Failed` condition type was added to allow signers to indicate permanent failure; this condition can be added via the `certificatesigningrequests/status` subresource. - `Approved` and `Denied` conditions are mutually exclusive - `Approved`, `Denied`, and `Failed` conditions can no longer be removed from a CSR ([#90191](https://github.com/kubernetes/kubernetes/pull/90191), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Apps, Auth, CLI and Node] - EnvVarSource api doc bug fixes ([#91194](https://github.com/kubernetes/kubernetes/pull/91194), [@wawa0210](https://github.com/wawa0210)) [SIG Apps] - Fixed: log timestamps now include trailing zeros to maintain a fixed width ([#91207](https://github.com/kubernetes/kubernetes/pull/91207), [@iamchuckss](https://github.com/iamchuckss)) [SIG Apps and Node] - The Kubelet's --node-status-max-images option is now available via the Kubelet config file field nodeStatusMaxImage ([#91275](https://github.com/kubernetes/kubernetes/pull/91275), [@knabben](https://github.com/knabben)) [SIG Node] - The Kubelet's --seccomp-profile-root option is now available via the Kubelet config file field seccompProfileRoot. ([#91182](https://github.com/kubernetes/kubernetes/pull/91182), [@knabben](https://github.com/knabben)) [SIG Node] - The Kubelet's `--enable-server` and `--provider-id` option is now available via the Kubelet config file field `enableServer` and `providerID` respectively. ([#90494](https://github.com/kubernetes/kubernetes/pull/90494), [@knabben](https://github.com/knabben)) [SIG Node] - The Kubelet's `--really-crash-for-testing` and  `--chaos-chance` options are now marked as deprecated. ([#90499](https://github.com/kubernetes/kubernetes/pull/90499), [@knabben](https://github.com/knabben)) [SIG Node] - The alpha `DynamicAuditing` feature gate and `auditregistration.k8s.io/v1alpha1` API have been removed and are no longer supported. ([#91502](https://github.com/kubernetes/kubernetes/pull/91502), [@deads2k](https://github.com/deads2k)) [SIG API Machinery, Auth and Testing] - `NodeResourcesLeastAllocated` and `NodeResourcesMostAllocated` plugins now support customized weight on the CPU and memory. ([#90544](https://github.com/kubernetes/kubernetes/pull/90544), [@chendave](https://github.com/chendave)) [SIG Scheduling] - `PostFilter` type is added to scheduler component config API on version v1beta1. ([#91547](https://github.com/kubernetes/kubernetes/pull/91547), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling] - `kubescheduler.config.k8s.io` is now beta ([#91420](https://github.com/kubernetes/kubernetes/pull/91420), [@pancernik](https://github.com/pancernik)) [SIG Scheduling] </del> <ins> - GPU metrics provided by kubelet are now disabled by default ([#95184](https://github.com/kubernetes/kubernetes/pull/95184), [@RenaudWasTaken](https://github.com/RenaudWasTaken)) [SIG Node] - New parameter `defaultingType` for `PodTopologySpread` plugin allows to use k8s defined or user provided default constraints ([#95048](https://github.com/kubernetes/kubernetes/pull/95048), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - Server Side Apply now treats LabelSelector fields as atomic (meaning the entire selector is managed by a single writer and updated together), since they contain interrelated and inseparable fields that do not merge in intuitive ways. ([#93901](https://github.com/kubernetes/kubernetes/pull/93901), [@jpbetz](https://github.com/jpbetz)) [SIG API Machinery, Auth, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Network, Node, Storage and Testing] - Status of v1beta1 CRDs without \"preserveUnknownFields:false\" will show violation \"spec.preserveUnknownFields: Invalid value: true: must be false\" ([#93078](https://github.com/kubernetes/kubernetes/pull/93078), [@vareti](https://github.com/vareti)) [SIG API Machinery] </ins> ### Feature <del> - Add --logging-format flag for component-base. Defaults to \"text\" using unchanged klog. ([#89683](https://github.com/kubernetes/kubernetes/pull/89683), [@yuzhiquan](https://github.com/yuzhiquan)) [SIG Instrumentation] - Add --port flag to kubectl create deployment ([#91113](https://github.com/kubernetes/kubernetes/pull/91113), [@soltysh](https://github.com/soltysh)) [SIG CLI and Testing] - Add .import-restrictions file to cmd/cloud-controller-manager. ([#90630](https://github.com/kubernetes/kubernetes/pull/90630), [@nilo19](https://github.com/nilo19)) [SIG API Machinery and Cloud Provider] - Add Annotations to CRI-API ImageSpec objects. ([#90061](https://github.com/kubernetes/kubernetes/pull/90061), [@marosset](https://github.com/marosset)) [SIG Node and Windows] - Added feature support to Windows for configuring session affinity of Kubernetes services. required: [Windows Server vNext Insider Preview Build 19551](https://blogs.windows.com/windowsexperience/2020/01/28/announcing-windows-server-vnext-insider-preview-build-19551/) (or higher) ([#91701](https://github.com/kubernetes/kubernetes/pull/91701), [@elweb9858](https://github.com/elweb9858)) [SIG Network and Windows] - Added service.beta.kubernetes.io/aws-load-balancer-target-node-labels annotation to target nodes in AWS LoadBalancer Services ([#90943](https://github.com/kubernetes/kubernetes/pull/90943), [@foobarfran](https://github.com/foobarfran)) [SIG Cloud Provider] - Feat: azure disk migration go beta in 1.19 ([#90896](https://github.com/kubernetes/kubernetes/pull/90896), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Kube-addon-manager has been updated to v9.1.1 to allow overriding the default list of whitelisted resources (https://github.com/kubernetes/kubernetes/pull/91018) ([#91240](https://github.com/kubernetes/kubernetes/pull/91240), [@tosi3k](https://github.com/tosi3k)) [SIG Cloud Provider, Scalability and Testing] - Kubeadm now distinguishes between generated and user supplied component configs, regenerating the former ones if a config upgrade is required ([#86070](https://github.com/kubernetes/kubernetes/pull/86070), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - Kubeadm: add startup probes for static Pods to protect slow starting containers ([#91179](https://github.com/kubernetes/kubernetes/pull/91179), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle] - Kubelets configured to rotate client certificates now publish a `certificate_manager_server_ttl_seconds` gauge metric indicating the remaining seconds until certificate expiration. ([#91148](https://github.com/kubernetes/kubernetes/pull/91148), [@liggitt](https://github.com/liggitt)) [SIG Auth and Node] - Local-up-cluster.sh installs CSI snapshotter by default now, can be disabled with ENABLE_CSI_SNAPSHOTTER=false. ([#91504](https://github.com/kubernetes/kubernetes/pull/91504), [@pohly](https://github.com/pohly)) [SIG Storage] - Rest.Config now supports a flag to override proxy configuration that was previously only configurable through environment variables. ([#81443](https://github.com/kubernetes/kubernetes/pull/81443), [@mikedanese](https://github.com/mikedanese)) [SIG API Machinery and Node] - Scores from PodTopologySpreading have reduced differentiation as maxSkew increases. ([#90820](https://github.com/kubernetes/kubernetes/pull/90820), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - Service controller: only sync LB node pools when relevant fields in Node changes ([#90769](https://github.com/kubernetes/kubernetes/pull/90769), [@andrewsykim](https://github.com/andrewsykim)) [SIG Apps and Network] - Switch core master base images (kube-apiserver, kube-scheduler) from debian to distroless ([#90674](https://github.com/kubernetes/kubernetes/pull/90674), [@dims](https://github.com/dims)) [SIG Cloud Provider, Release and Scalability] - Switch etcd image (with migration scripts) from debian to distroless ([#91171](https://github.com/kubernetes/kubernetes/pull/91171), [@dims](https://github.com/dims)) [SIG API Machinery and Cloud Provider] - The `certificatesigningrequests/approval` subresource now supports patch API requests ([#91558](https://github.com/kubernetes/kubernetes/pull/91558), [@liggitt](https://github.com/liggitt)) [SIG Auth and Testing] - Update cri-tools to v1.18.0 ([#89720](https://github.com/kubernetes/kubernetes/pull/89720), [@saschagrunert](https://github.com/saschagrunert)) [SIG Cloud Provider, Cluster Lifecycle, Release and Scalability] - Weight of PodTopologySpread scheduling Score is doubled. ([#91258](https://github.com/kubernetes/kubernetes/pull/91258), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - `maxThreshold` of `ImageLocality` plugin is now scaled by the number of images in the pod, which helps to distinguish the node priorities for pod with several images. ([#91138](https://github.com/kubernetes/kubernetes/pull/91138), [@chendave](https://github.com/chendave)) [SIG Scheduling] </del> <ins> - Added `get-users` and `delete-user` to the `kubectl config` subcommand ([#89840](https://github.com/kubernetes/kubernetes/pull/89840), [@eddiezane](https://github.com/eddiezane)) [SIG CLI] - Added counter metric \"apiserver_request_self\" to count API server self-requests with labels for verb, resource, and subresource. ([#94288](https://github.com/kubernetes/kubernetes/pull/94288), [@LogicalShark](https://github.com/LogicalShark)) [SIG API Machinery, Auth, Instrumentation and Scheduling] - Added new k8s.io/component-helpers repository providing shared helper code for (core) components. ([#92507](https://github.com/kubernetes/kubernetes/pull/92507), [@ingvagabund](https://github.com/ingvagabund)) [SIG Apps, Node, Release and Scheduling] - Adds `create ingress` command to `kubectl` ([#78153](https://github.com/kubernetes/kubernetes/pull/78153), [@amimof](https://github.com/amimof)) [SIG CLI and Network] - Allow configuring AWS LoadBalancer health check protocol via service annotations ([#94546](https://github.com/kubernetes/kubernetes/pull/94546), [@kishorj](https://github.com/kishorj)) [SIG Cloud Provider] - Azure: Support multiple services sharing one IP address ([#94991](https://github.com/kubernetes/kubernetes/pull/94991), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - Ephemeral containers now apply the same API defaults as initContainers and containers ([#94896](https://github.com/kubernetes/kubernetes/pull/94896), [@wawa0210](https://github.com/wawa0210)) [SIG Apps and CLI] - In dual-stack bare-metal clusters, you can now pass dual-stack IPs to `kubelet --node-ip`. eg: `kubelet --node-ip 10.1.0.5,fd01::0005`. This is not yet supported for non-bare-metal clusters. In dual-stack clusters where nodes have dual-stack addresses, hostNetwork pods will now get dual-stack PodIPs. ([#95239](https://github.com/kubernetes/kubernetes/pull/95239), [@danwinship](https://github.com/danwinship)) [SIG Network and Node] - Introduces a new GCE specific cluster creation variable KUBE_PROXY_DISABLE. When set to true, this will skip over the creation of kube-proxy (whether the daemonset or static pod). This can be used to control the lifecycle of kube-proxy separately from the lifecycle of the nodes. ([#91977](https://github.com/kubernetes/kubernetes/pull/91977), [@varunmar](https://github.com/varunmar)) [SIG Cloud Provider] - Kubeadm: do not throw errors if the current system time is outside of the NotBefore and NotAfter bounds of a loaded certificate. Print warnings instead. ([#94504](https://github.com/kubernetes/kubernetes/pull/94504), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: make the command \"kubeadm alpha kubeconfig user\" accept a \"--config\" flag and remove the following flags: - apiserver-advertise-address / apiserver-bind-port: use either localAPIEndpoint from InitConfiguration or controlPlaneEndpoint from ClusterConfiguration. - cluster-name: use clusterName from ClusterConfiguration - cert-dir: use certificatesDir from ClusterConfiguration ([#94879](https://github.com/kubernetes/kubernetes/pull/94879), [@knight42](https://github.com/knight42)) [SIG Cluster Lifecycle] - Kubectl rollout history sts/sts-name --revision=some-revision will start showing the detailed view of  the sts on that specified revision ([#86506](https://github.com/kubernetes/kubernetes/pull/86506), [@dineshba](https://github.com/dineshba)) [SIG CLI] - Scheduling Framework: expose Run[Pre]ScorePlugins functions to PreemptionHandle which can be used in PostFilter extention point. ([#93534](https://github.com/kubernetes/kubernetes/pull/93534), [@everpeace](https://github.com/everpeace)) [SIG Scheduling and Testing] - Send gce node startup scripts logs to console and journal ([#95311](https://github.com/kubernetes/kubernetes/pull/95311), [@karan](https://github.com/karan)) [SIG Cloud Provider and Node] - Support kubectl delete orphan/foreground/background options ([#93384](https://github.com/kubernetes/kubernetes/pull/93384), [@zhouya0](https://github.com/zhouya0)) [SIG CLI and Testing] </ins> ### Bug or Regression <del> - Add support for TLS 1.3 ciphers: TLS_AES_128_GCM_SHA256, TLS_CHACHA20_POLY1305_SHA256 and TLS_AES_256_GCM_SHA384. ([#90843](https://github.com/kubernetes/kubernetes/pull/90843), [@pjbgf](https://github.com/pjbgf)) [SIG API Machinery, Auth and Cluster Lifecycle] - Base-images: Update to kube-cross:v1.13.9-5 ([#90963](https://github.com/kubernetes/kubernetes/pull/90963), [@justaugustus](https://github.com/justaugustus)) [SIG Release and Testing] - CloudNodeLifecycleController will check node existence status before shutdown status when monitoring nodes. ([#90737](https://github.com/kubernetes/kubernetes/pull/90737), [@jiahuif](https://github.com/jiahuif)) [SIG Apps and Cloud Provider] - First pod with required affinity terms can schedule only on nodes with matching topology keys. ([#91168](https://github.com/kubernetes/kubernetes/pull/91168), [@ahg-g](https://github.com/ahg-g)) [SIG Scheduling] - Fix VirtualMachineScaleSets.virtualMachines.GET not allowed issues when customers have set VMSS orchestrationMode. ([#91097](https://github.com/kubernetes/kubernetes/pull/91097), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Fix a racing issue that scheduler may perform unnecessary scheduling attempt. ([#90660](https://github.com/kubernetes/kubernetes/pull/90660), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling and Testing] - Fix kubectl create --dryrun client ignore namespace ([#90502](https://github.com/kubernetes/kubernetes/pull/90502), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - Fix kubectl create secret docker-registry --from-file not usable ([#90960](https://github.com/kubernetes/kubernetes/pull/90960), [@zhouya0](https://github.com/zhouya0)) [SIG CLI and Testing] - Fix kubectl describe node for users not having access to lease information. ([#90469](https://github.com/kubernetes/kubernetes/pull/90469), [@uthark](https://github.com/uthark)) [SIG CLI] - Fix kubectl run  --dry-run client  ignore namespace ([#90785](https://github.com/kubernetes/kubernetes/pull/90785), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - Fix public IP not shown issues after assigning public IP to Azure VMs ([#90886](https://github.com/kubernetes/kubernetes/pull/90886), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Fix: add azure file migration support on annotation support ([#91093](https://github.com/kubernetes/kubernetes/pull/91093), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Node] - Fix: azure disk dangling attach issue which would cause API throttling ([#90749](https://github.com/kubernetes/kubernetes/pull/90749), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix: fix topology issue in azure disk storage class migration ([#91196](https://github.com/kubernetes/kubernetes/pull/91196), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix: support removal of nodes backed by deleted non VMSS instances on Azure ([#91184](https://github.com/kubernetes/kubernetes/pull/91184), [@bpineau](https://github.com/bpineau)) [SIG Cloud Provider] - Fixed a regression preventing garbage collection of RBAC role and binding objects ([#90534](https://github.com/kubernetes/kubernetes/pull/90534), [@apelisse](https://github.com/apelisse)) [SIG Auth] - For external storage e2e test suite, update external driver, to pick snapshot provisioner from VolumeSnapshotClass, when a VolumeSnapshotClass is explicitly provided as an input. ([#90878](https://github.com/kubernetes/kubernetes/pull/90878), [@saikat-royc](https://github.com/saikat-royc)) [SIG Storage and Testing] - Get-kube.sh: fix order to get the binaries from the right bucket ([#91635](https://github.com/kubernetes/kubernetes/pull/91635), [@cpanato](https://github.com/cpanato)) [SIG Release] - In a HA env, during the period a standby scheduler lost connection to API server, if a Pod is deleted and recreated, and the standby scheduler becomes master afterwards, there could be a scheduler cache corruption. This PR fixes this issue. ([#91126](https://github.com/kubernetes/kubernetes/pull/91126), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling] - Kubeadm: during \"reset\" do not remove the only remaining stacked etcd member from the cluster and just proceed with the cleanup of the local etcd storage. ([#91145](https://github.com/kubernetes/kubernetes/pull/91145), [@tnqn](https://github.com/tnqn)) [SIG Cluster Lifecycle] - Kubeadm: increase robustness for \"kubeadm join\" when adding etcd members on slower setups ([#90645](https://github.com/kubernetes/kubernetes/pull/90645), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Pod Conditions updates are skipped for re-scheduling attempts ([#91252](https://github.com/kubernetes/kubernetes/pull/91252), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - Prevent PVC requested size overflow when expanding or creating a volume ([#90907](https://github.com/kubernetes/kubernetes/pull/90907), [@gnufied](https://github.com/gnufied)) [SIG Cloud Provider and Storage] - Resolves an issue using `kubectl certificate approve/deny` against a server serving the v1 CSR API ([#91691](https://github.com/kubernetes/kubernetes/pull/91691), [@liggitt](https://github.com/liggitt)) [SIG Auth and CLI] - Scheduling failures due to no nodes available are now reported as unschedulable under ```schedule_attempts_total``` metric. ([#90989](https://github.com/kubernetes/kubernetes/pull/90989), [@ahg-g](https://github.com/ahg-g)) [SIG Scheduling] - The following components that do not expect non-empty, non-flag arguments will now print an error message and exit if an argument is specified: cloud-controller-manager, kube-apiserver, kube-controller-manager, kube-proxy, kubeadm {alpha|config|token|version}, kubemark. Flags should be prefixed with a single dash \"-\" (0x45) for short form or double dash \"--\" for long form. Before this change, malformed flags (for example, starting with a non-ascii dash character such as 0x8211: \"–\") would have been silently treated as positional arguments and ignored. ([#91349](https://github.com/kubernetes/kubernetes/pull/91349), [@neolit123](https://github.com/neolit123)) [SIG API Machinery, Cloud Provider, Cluster Lifecycle, Network and Scheduling] - When evicting, Pods in Pending state are removed without checking PDBs. ([#83906](https://github.com/kubernetes/kubernetes/pull/83906), [@michaelgugino](https://github.com/michaelgugino)) [SIG API Machinery, Apps, Node and Scheduling] </del> <ins> - Change the mount way from systemd to normal mount except ceph and glusterfs intree-volume. ([#94916](https://github.com/kubernetes/kubernetes/pull/94916), [@smileusd](https://github.com/smileusd)) [SIG Apps, Cloud Provider, Network, Node, Storage and Testing] - Cloud node controller: handle empty providerID from getProviderID ([#95342](https://github.com/kubernetes/kubernetes/pull/95342), [@nicolehanjing](https://github.com/nicolehanjing)) [SIG Cloud Provider] - Fix a bug where the endpoint slice controller was not mirroring the parent service labels to its corresponding endpoint slices ([#94443](https://github.com/kubernetes/kubernetes/pull/94443), [@aojea](https://github.com/aojea)) [SIG Apps and Network] - Fix azure disk attach failure for disk size bigger than 4TB ([#95463](https://github.com/kubernetes/kubernetes/pull/95463), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix azure disk data loss issue on Windows when unmount disk ([#95456](https://github.com/kubernetes/kubernetes/pull/95456), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Fix detach azure disk issue when vm not exist ([#95177](https://github.com/kubernetes/kubernetes/pull/95177), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix network_programming_latency metric reporting for Endpoints/EndpointSlice deletions, where we don't have correct timestamp ([#95363](https://github.com/kubernetes/kubernetes/pull/95363), [@wojtek-t](https://github.com/wojtek-t)) [SIG Network and Scalability] - Fix scheduler cache snapshot when a Node is deleted before its Pods ([#95130](https://github.com/kubernetes/kubernetes/pull/95130), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - Fix vsphere detach failure for static PVs ([#95447](https://github.com/kubernetes/kubernetes/pull/95447), [@gnufied](https://github.com/gnufied)) [SIG Cloud Provider and Storage] - Fixed a bug that prevents the use of ephemeral containers in the presence of a validating admission webhook. ([#94685](https://github.com/kubernetes/kubernetes/pull/94685), [@verb](https://github.com/verb)) [SIG Node and Testing] - Gracefully delete nodes when their parent scale set went missing ([#95289](https://github.com/kubernetes/kubernetes/pull/95289), [@bpineau](https://github.com/bpineau)) [SIG Cloud Provider] - In dual-stack clusters, kubelet will now set up both IPv4 and IPv6 iptables rules, which may fix some problems, eg with HostPorts. ([#94474](https://github.com/kubernetes/kubernetes/pull/94474), [@danwinship](https://github.com/danwinship)) [SIG Network and Node] - Kubeadm: for Docker as the container runtime, make the \"kubeadm reset\" command stop containers before removing them ([#94586](https://github.com/kubernetes/kubernetes/pull/94586), [@BedivereZero](https://github.com/BedivereZero)) [SIG Cluster Lifecycle] - Kubeadm: warn but do not error out on missing \"ca.key\" files for root CA, front-proxy CA and etcd CA, during \"kubeadm join --control-plane\" if the user has provided all certificates, keys and kubeconfig files which require signing with the given CA keys. ([#94988](https://github.com/kubernetes/kubernetes/pull/94988), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Port mapping allows to map the same `containerPort` to multiple `hostPort` without naming the mapping explicitly. ([#94494](https://github.com/kubernetes/kubernetes/pull/94494), [@SergeyKanzhelev](https://github.com/SergeyKanzhelev)) [SIG Network and Node] - Warn instead of fail when creating Roles and ClusterRoles with custom verbs via kubectl ([#92492](https://github.com/kubernetes/kubernetes/pull/92492), [@eddiezane](https://github.com/eddiezane)) [SIG CLI] </ins> ### Other (Cleanup or Flake) <del> - Adds additional testing to ensure that udp pods conntrack are cleaned up ([#90180](https://github.com/kubernetes/kubernetes/pull/90180), [@JacobTanenbaum](https://github.com/JacobTanenbaum)) [SIG Architecture, Network and Testing] - Adjusts the fsType for cinder values to be `ext4` if no fsType is specified. ([#90608](https://github.com/kubernetes/kubernetes/pull/90608), [@huffmanca](https://github.com/huffmanca)) [SIG Storage] - Change beta.kubernetes.io/os to kubernetes.io/os ([#89461](https://github.com/kubernetes/kubernetes/pull/89461), [@wawa0210](https://github.com/wawa0210)) [SIG Cloud Provider and Cluster Lifecycle] - Content-type and verb for request metrics are now bounded to a known set. ([#89451](https://github.com/kubernetes/kubernetes/pull/89451), [@logicalhan](https://github.com/logicalhan)) [SIG API Machinery and Instrumentation] - Emit `WaitingForPodScheduled` event if the unbound PVC is in delay binding mode but used by a pod ([#91455](https://github.com/kubernetes/kubernetes/pull/91455), [@cofyc](https://github.com/cofyc)) [SIG Storage] - Improve server-side apply conflict errors by setting dedicated kubectl subcommand field managers ([#88885](https://github.com/kubernetes/kubernetes/pull/88885), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG CLI and Testing] - It is now possible to use the service annotation `cloud.google.com/network-tier: Standard` to configure the Network Tier of the GCE Loadbalancer ([#88532](https://github.com/kubernetes/kubernetes/pull/88532), [@zioproto](https://github.com/zioproto)) [SIG Cloud Provider, Network and Testing] - Kube-scheduler: The metric name `scheduler_total_preemption_attempts` has been renamed to `scheduler_preemption_attempts_total`. ([#91448](https://github.com/kubernetes/kubernetes/pull/91448), [@RainbowMango](https://github.com/RainbowMango)) [SIG API Machinery, Cluster Lifecycle, Instrumentation and Scheduling] - Kubeadm now forwards the IPv6DualStack feature gate using the kubelet component config, instead of the kubelet command line ([#90840](https://github.com/kubernetes/kubernetes/pull/90840), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - Kubeadm: do not use a DaemonSet for the pre-pull of control-plane images during \"kubeadm upgrade apply\". Individual node upgrades now pull the required images using a preflight check. The flag \"--image-pull-timeout\" for \"kubeadm upgrade apply\" is now deprecated and will be removed in a future release following a GA deprecation policy. ([#90788](https://github.com/kubernetes/kubernetes/pull/90788), [@xlgao-zju](https://github.com/xlgao-zju)) [SIG Cluster Lifecycle] - Kubeadm: use two separate checks on /livez and /readyz for the kube-apiserver static Pod instead of using /healthz ([#90970](https://github.com/kubernetes/kubernetes/pull/90970), [@johscheuer](https://github.com/johscheuer)) [SIG Cluster Lifecycle] - NONE ([#91597](https://github.com/kubernetes/kubernetes/pull/91597), [@elmiko](https://github.com/elmiko)) [SIG Autoscaling and Testing] - Remove deprecated --server-dry-run flag from kubectl apply ([#91308](https://github.com/kubernetes/kubernetes/pull/91308), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG CLI and Testing] - The \"HostPath should give a volume the correct mode\" is no longer a conformance test ([#90861](https://github.com/kubernetes/kubernetes/pull/90861), [@dims](https://github.com/dims)) [SIG Architecture and Testing] - The Kubelet's --experimental-mounter-path and --experimental-check-node-capabilities-before-mount options are now marked as deprecated. ([#91373](https://github.com/kubernetes/kubernetes/pull/91373), [@knabben](https://github.com/knabben)) [SIG Node] - The kube-apiserver `--kubelet-https` flag is deprecated. kube-apiserver connections to kubelets now unconditionally use `https` (kubelets have unconditionally used `https` to serve the endpoints the apiserver communicates with since before v1.0). ([#91630](https://github.com/kubernetes/kubernetes/pull/91630), [@liggitt](https://github.com/liggitt)) [SIG API Machinery and Node] - Update CNI to v0.8.6 ([#91370](https://github.com/kubernetes/kubernetes/pull/91370), [@justaugustus](https://github.com/justaugustus)) [SIG Cloud Provider, Network, Release and Testing] - `beta.kubernetes.io/os` and `beta.kubernetes.io/arch` node labels are deprecated. Update node selectors to use `kubernetes.io/os` and `kubernetes.io/arch`. ([#91046](https://github.com/kubernetes/kubernetes/pull/91046), [@wawa0210](https://github.com/wawa0210)) [SIG Apps and Node] - base-images: Use debian-base:v2.1.0 ([#90697](https://github.com/kubernetes/kubernetes/pull/90697), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery and Release] - base-images: Use debian-iptables:v12.1.0 ([#90782](https://github.com/kubernetes/kubernetes/pull/90782), [@justaugustus](https://github.com/justaugustus)) [SIG Release] </del> <ins> - Added fine grained debugging to the intra-pod conformance test for helping easily resolve networking issues for nodes that might be unhealthy when running conformance or sonobuoy tests. ([#93837](https://github.com/kubernetes/kubernetes/pull/93837), [@jayunit100](https://github.com/jayunit100)) [SIG Network and Testing] - AdmissionReview objects sent for the creation of Namespace API objects now populate the `namespace` attribute consistently (previously the `namespace` attribute was empty for Namespace creation via POST requests, and populated for Namespace creation via server-side-apply PATCH requests) ([#95012](https://github.com/kubernetes/kubernetes/pull/95012), [@nodo](https://github.com/nodo)) [SIG API Machinery and Testing] - Client-go header logging (at verbosity levels >= 9) now masks `Authorization` header contents ([#95316](https://github.com/kubernetes/kubernetes/pull/95316), [@sfowl](https://github.com/sfowl)) [SIG API Machinery] - Enhance log information of verifyRunAsNonRoot, add pod, container information ([#94911](https://github.com/kubernetes/kubernetes/pull/94911), [@wawa0210](https://github.com/wawa0210)) [SIG Node] - Errors from staticcheck: vendor/k8s.io/client-go/discovery/cached/memory/memcache_test.go:94:2: this value of g is never used (SA4006) ([#95098](https://github.com/kubernetes/kubernetes/pull/95098), [@phunziker](https://github.com/phunziker)) [SIG API Machinery] - Kubeadm: update the default pause image version to 1.4.0 on Windows. With this update the image supports Windows versions 1809 (2019LTS), 1903, 1909, 2004 ([#95419](https://github.com/kubernetes/kubernetes/pull/95419), [@jsturtevant](https://github.com/jsturtevant)) [SIG Cluster Lifecycle and Windows] - Masks ceph RBD adminSecrets in logs when logLevel >= 4 ([#95245](https://github.com/kubernetes/kubernetes/pull/95245), [@sfowl](https://github.com/sfowl)) [SIG Storage] - Upgrade snapshot controller to 3.0.0 ([#95412](https://github.com/kubernetes/kubernetes/pull/95412), [@saikat-royc](https://github.com/saikat-royc)) [SIG Cloud Provider] - Remove offensive words from kubectl cluster-info command ([#95202](https://github.com/kubernetes/kubernetes/pull/95202), [@rikatz](https://github.com/rikatz)) [SIG Architecture, CLI and Testing] - The following new metrics are available. - network_plugin_operations_total - network_plugin_operations_errors_total ([#93066](https://github.com/kubernetes/kubernetes/pull/93066), [@AnishShah](https://github.com/AnishShah)) [SIG Instrumentation, Network and Node] - Vsphere: improve logging message on node cache refresh event ([#95236](https://github.com/kubernetes/kubernetes/pull/95236), [@andrewsykim](https://github.com/andrewsykim)) [SIG Cloud Provider] - `kubectl api-resources` now prints the API version (as 'API group/version', same as output of `kubectl api-versions`). The column APIGROUP is now APIVERSION ([#95253](https://github.com/kubernetes/kubernetes/pull/95253), [@sallyom](https://github.com/sallyom)) [SIG CLI] </ins> ## Dependencies ### Added <del> - cloud.google.com/go/bigquery: v1.0.1 - cloud.google.com/go/datastore: v1.0.0 - cloud.google.com/go/pubsub: v1.0.1 - cloud.google.com/go/storage: v1.0.0 - dmitri.shuralyov.com/gpu/mtl: 666a987 - github.com/cespare/xxhash/v2: [v2.1.1](https://github.com/cespare/xxhash/v2/tree/v2.1.1) - github.com/chzyer/logex: [v1.1.10](https://github.com/chzyer/logex/tree/v1.1.10) - github.com/chzyer/readline: [2972be2](https://github.com/chzyer/readline/tree/2972be2) - github.com/chzyer/test: [a1ea475](https://github.com/chzyer/test/tree/a1ea475) - github.com/containerd/cgroups: [bf292b2](https://github.com/containerd/cgroups/tree/bf292b2) - github.com/containerd/continuity: [aaeac12](https://github.com/containerd/continuity/tree/aaeac12) - github.com/containerd/fifo: [a9fb20d](https://github.com/containerd/fifo/tree/a9fb20d) - github.com/containerd/go-runc: [5a6d9f3](https://github.com/containerd/go-runc/tree/5a6d9f3) - github.com/coreos/bbolt: [v1.3.2](https://github.com/coreos/bbolt/tree/v1.3.2) - github.com/cpuguy83/go-md2man/v2: [v2.0.0](https://github.com/cpuguy83/go-md2man/v2/tree/v2.0.0) - github.com/go-gl/glfw/v3.3/glfw: [12ad95a](https://github.com/go-gl/glfw/v3.3/glfw/tree/12ad95a) - github.com/google/renameio: [v0.1.0](https://github.com/google/renameio/tree/v0.1.0) - github.com/ianlancetaylor/demangle: [5e5cf60](https://github.com/ianlancetaylor/demangle/tree/5e5cf60) - github.com/rogpeppe/go-internal: [v1.3.0](https://github.com/rogpeppe/go-internal/tree/v1.3.0) - github.com/russross/blackfriday/v2: [v2.0.1](https://github.com/russross/blackfriday/v2/tree/v2.0.1) - github.com/shurcooL/sanitized_anchor_name: [v1.0.0](https://github.com/shurcooL/sanitized_anchor_name/tree/v1.0.0) - github.com/ugorji/go: [v1.1.4](https://github.com/ugorji/go/tree/v1.1.4) - golang.org/x/mod: v0.1.0 - google.golang.org/protobuf: v1.23.0 - gopkg.in/errgo.v2: v2.1.0 - k8s.io/klog/v2: v2.0.0 </del> <ins> - github.com/jmespath/go-jmespath/internal/testify: [v1.5.1](https://github.com/jmespath/go-jmespath/internal/testify/tree/v1.5.1) </ins> ### Changed <del> - cloud.google.com/go: v0.38.0 → v0.51.0 - github.com/GoogleCloudPlatform/k8s-cloud-provider: [27a4ced → 7901bc8](https://github.com/GoogleCloudPlatform/k8s-cloud-provider/compare/27a4ced...7901bc8) - github.com/Microsoft/hcsshim: [672e52e → v0.8.9](https://github.com/Microsoft/hcsshim/compare/672e52e...v0.8.9) - github.com/alecthomas/template: [a0175ee → fb15b89](https://github.com/alecthomas/template/compare/a0175ee...fb15b89) - github.com/alecthomas/units: [2efee85 → c3de453](https://github.com/alecthomas/units/compare/2efee85...c3de453) - github.com/beorn7/perks: [v1.0.0 → v1.0.1](https://github.com/beorn7/perks/compare/v1.0.0...v1.0.1) - github.com/coreos/pkg: [97fdf19 → 399ea9e](https://github.com/coreos/pkg/compare/97fdf19...399ea9e) - github.com/go-kit/kit: [v0.8.0 → v0.9.0](https://github.com/go-kit/kit/compare/v0.8.0...v0.9.0) - github.com/go-logfmt/logfmt: [v0.3.0 → v0.4.0](https://github.com/go-logfmt/logfmt/compare/v0.3.0...v0.4.0) - github.com/golang/groupcache: [02826c3 → 215e871](https://github.com/golang/groupcache/compare/02826c3...215e871) - github.com/golang/protobuf: [v1.3.3 → v1.4.2](https://github.com/golang/protobuf/compare/v1.3.3...v1.4.2) - github.com/google/cadvisor: [8af10c6 → 6a8d614](https://github.com/google/cadvisor/compare/8af10c6...6a8d614) - github.com/google/pprof: [3ea8567 → d4f498a](https://github.com/google/pprof/compare/3ea8567...d4f498a) - github.com/googleapis/gax-go/v2: [v2.0.4 → v2.0.5](https://github.com/googleapis/gax-go/v2/compare/v2.0.4...v2.0.5) - github.com/json-iterator/go: [v1.1.8 → v1.1.9](https://github.com/json-iterator/go/compare/v1.1.8...v1.1.9) - github.com/jstemmer/go-junit-report: [af01ea7 → v0.9.1](https://github.com/jstemmer/go-junit-report/compare/af01ea7...v0.9.1) - github.com/prometheus/client_golang: [v1.0.0 → v1.6.0](https://github.com/prometheus/client_golang/compare/v1.0.0...v1.6.0) - github.com/prometheus/common: [v0.4.1 → v0.9.1](https://github.com/prometheus/common/compare/v0.4.1...v0.9.1) - github.com/prometheus/procfs: [v0.0.5 → v0.0.11](https://github.com/prometheus/procfs/compare/v0.0.5...v0.0.11) - github.com/spf13/cobra: [v0.0.5 → v1.0.0](https://github.com/spf13/cobra/compare/v0.0.5...v1.0.0) - github.com/spf13/viper: [v1.3.2 → v1.4.0](https://github.com/spf13/viper/compare/v1.3.2...v1.4.0) - github.com/tmc/grpc-websocket-proxy: [89b8d40 → 0ad062e](https://github.com/tmc/grpc-websocket-proxy/compare/89b8d40...0ad062e) - go.opencensus.io: v0.21.0 → v0.22.2 - go.uber.org/atomic: v1.3.2 → v1.4.0 - golang.org/x/exp: 4b39c73 → da58074 - golang.org/x/image: 0694c2d → cff245a - golang.org/x/lint: 959b441 → fdd1cda - golang.org/x/mobile: d3739f8 → d2bd2a2 - golang.org/x/oauth2: 0f29369 → 858c2ad - google.golang.org/api: 5213b80 → v0.15.1 - google.golang.org/appengine: v1.5.0 → v1.6.5 - google.golang.org/genproto: f3c370f → ca5a221 - honnef.co/go/tools: e561f67 → v0.0.1-2019.2.3 - k8s.io/gengo: e0e292d → 8167cfd - k8s.io/kube-openapi: e1beb1b → 656914f - k8s.io/utils: a9aa75a → 2df71eb - sigs.k8s.io/apiserver-network-proxy/konnectivity-client: v0.0.7 → 33b9978 </del> <ins> - github.com/aws/aws-sdk-go: [v1.28.2 → v1.35.5](https://github.com/aws/aws-sdk-go/compare/v1.28.2...v1.35.5) - github.com/jmespath/go-jmespath: [c2b33e8 → v0.4.0](https://github.com/jmespath/go-jmespath/compare/c2b33e8...v0.4.0) - k8s.io/kube-openapi: 6aeccd4 → 8b50664 - sigs.k8s.io/apiserver-network-proxy/konnectivity-client: v0.0.9 → v0.0.12 - sigs.k8s.io/structured-merge-diff/v4: v4.0.1 → b3cf1e8 </ins> ### Removed <del> - github.com/coreos/go-etcd: [v2.0.0+incompatible](https://github.com/coreos/go-etcd/tree/v2.0.0) - github.com/ugorji/go/codec: [d75b2dc](https://github.com/ugorji/go/codec/tree/d75b2dc) - k8s.io/klog: v1.0.0 </del> <ins> _Nothing has changed._ </ins> <del> # v1.19.0-beta.0 </del> <ins> # v1.20.0-alpha.1 </ins> <del> ## Downloads for v1.19.0-beta.0 </del> <ins> ## Downloads for v1.20.0-alpha.1 </ins> ### Source Code filename | sha512 hash -------- | ----------- <del> [kubernetes.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes.tar.gz) | 8c7e820b8bd7a8f742b7560cafe6ae1acc4c9836ae23d1b10d987b4de6a690826be75c68b8f76ec027097e8dfd861afb1d229b3687f0b82afcfe7b4d6481242e [kubernetes-src.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-src.tar.gz) | 543e9d36fd8b2de3e19631d3295d3a7706e6e88bbd3adb2d558b27b3179a3961455f4f04f0d4a5adcff1466779e1b08023fe64dc2ab39813b37adfbbc779dec7 </del> <ins> [kubernetes.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes.tar.gz) | e7daed6502ea07816274f2371f96fe1a446d0d7917df4454b722d9eb3b5ff6163bfbbd5b92dfe7a0c1d07328b8c09c4ae966e482310d6b36de8813aaf87380b5 [kubernetes-src.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-src.tar.gz) | e91213a0919647a1215d4691a63b12d89a3e74055463a8ebd71dc1a4cabf4006b3660881067af0189960c8dab74f4a7faf86f594df69021901213ee5b56550ea </ins> ### Client binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-client-darwin-386.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-client-darwin-386.tar.gz) | 3ef37ef367a8d9803f023f6994d73ff217865654a69778c1ea3f58c88afbf25ff5d8d6bec9c608ac647c2654978228c4e63f30eec2a89d16d60f4a1c5f333b22 [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-client-darwin-amd64.tar.gz) | edb02b0b8d6a1c2167fbce4a85d84fb413566d3a76839fd366801414ca8ad2d55a5417b39b4cac6b65fddf13c1b3259791a607703773241ca22a67945ecb0014 [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-client-linux-386.tar.gz) | dafe93489df7328ae23f4bdf0a9d2e234e18effe7e042b217fe2dd1355e527a54bab3fb664696ed606a8ebedce57da4ee12647ec1befa2755bd4c43d9d016063 [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-client-linux-amd64.tar.gz) | d8e2bf8c9dd665410c2e7ceaa98bc4fc4f966753b7ade91dcef3b5eff45e0dda63bd634610c8761392a7804deb96c6b030c292280bf236b8b29f63b7f1af3737 [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-client-linux-arm.tar.gz) | d590d3d07d0ebbb562bce480c7cbe4e60b99feba24376c216fe73d8b99a246e2cd2acb72abe1427bde3e541d94d55b7688daf9e6961e4cbc6b875ac4eeea6e62 [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-client-linux-arm64.tar.gz) | f9647a99a566c9febd348c1c4a8e5c05326058eab076292a8bb5d3a2b882ee49287903f8e0e036b40af294aa3571edd23e65f3de91330ac9af0c10350b02583d [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-client-linux-ppc64le.tar.gz) | 662f009bc393734a89203d7956942d849bad29e28448e7baa017d1ac2ec2d26d7290da4a44bccb99ed960b2e336d9d98908c98f8a3d9fe1c54df2d134c799cad [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-client-linux-s390x.tar.gz) | 61fdf4aff78dcdb721b82a3602bf5bc94d44d51ab6607b255a9c2218bb3e4b57f6e656c2ee0dd68586fb53acbeff800d6fd03e4642dded49735a93356e7c5703 [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-client-windows-386.tar.gz) | 20d1e803b10b3bee09a7a206473ba320cc5f1120278d8f6e0136c388b2720da7264b917cd4738488b1d0a9aa922eb581c1f540715a6c2042c4dd7b217b6a9a0a [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-client-windows-amd64.tar.gz) | b85d729ec269f6aad0b6d2f95f3648fbea84330d2fbfde2267a519bc08c42d70d7b658b0e41c3b0d5f665702a8f1bbb37652753de34708ae3a03e45175c8b92c </del> <ins> [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-client-darwin-amd64.tar.gz) | 1f3add5f826fa989820d715ca38e8864b66f30b59c1abeacbb4bfb96b4e9c694eac6b3f4c1c81e0ee3451082d44828cb7515315d91ad68116959a5efbdaef1e1 [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-client-linux-386.tar.gz) | c62acdc8993b0a950d4b0ce0b45473bf96373d501ce61c88adf4007afb15c1d53da8d53b778a7eccac6c1624f7fdda322be9f3a8bc2d80aaad7b4237c39f5eaf [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-client-linux-amd64.tar.gz) | 1203ababfe00f9bc5be5c059324c17160a96530c1379a152db33564bbe644ccdb94b30eea15a0655bd652efb17895a46c31bbba19d4f5f473c2a0ff62f6e551f [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-client-linux-arm.tar.gz) | 31860088596e12d739c7aed94556c2d1e217971699b950c8417a3cea1bed4e78c9ff1717b9f3943354b75b4641d4b906cd910890dbf4278287c0d224837d9a7d [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-client-linux-arm64.tar.gz) | 8d469f37fe20d6e15b5debc13cce4c22e8b7a4f6a4ac787006b96507a85ce761f63b28140d692c54b5f7deb08697f8d5ddb9bbfa8f5ac0d9241fc7de3a3fe3cd [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-client-linux-ppc64le.tar.gz) | 0d62ee1729cd5884946b6c73701ad3a570fa4d642190ca0fe5c1db0fb0cba9da3ac86a948788d915b9432d28ab8cc499e28aadc64530b7d549ee752a6ed93ec1 [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-client-linux-s390x.tar.gz) | 0fc0420e134ec0b8e0ab2654e1e102cebec47b48179703f1e1b79d51ee0d6da55a4e7304d8773d3cf830341ac2fe3cede1e6b0460fd88f7595534e0730422d5a [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-client-windows-386.tar.gz) | 3fb53b5260f4888c77c0e4ff602bbcf6bf38c364d2769850afe2b8d8e8b95f7024807c15e2b0d5603e787c46af8ac53492be9e88c530f578b8a389e3bd50c099 [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-client-windows-amd64.tar.gz) | 2f44c93463d6b5244ce0c82f147e7f32ec2233d0e29c64c3c5759e23533aebd12671bf63e986c0861e9736f9b5259bb8d138574a7c8c8efc822e35cd637416c0 </ins> ### Server binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-server-linux-amd64.tar.gz) | c3641bdb0a8d8eff5086d24b71c6547131092b21f976b080dc48129f91de3da560fed6edf880eab1d205017ad74be716a5b970e4bbc00d753c005e5932b3d319 [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-server-linux-arm.tar.gz) | 7c29b8e33ade23a787330d28da22bf056610dae4d3e15574c56c46340afe5e0fdb00126ae3fd64fd70a26d1a87019f47e401682b88fa1167368c7edbecc72ccf [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-server-linux-arm64.tar.gz) | 27cd6042425eb94bb468431599782467ed818bcc51d75e8cb251c287a806b60a5cce50d4ae7525348c5446eaa45f849bc3fe3e6ac7248b54f3ebae8bf6553c3f [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-server-linux-ppc64le.tar.gz) | ede896424eb12ec07dd3756cbe808ca3915f51227e7b927795402943d81a99bb61654fd8f485a838c2faf199d4a55071af5bd8e69e85669a7f4a0b0e84a093cc [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-server-linux-s390x.tar.gz) | 4e48d4f5afd22f0ae6ade7da4877238fd2a5c10ae3dea2ae721c39ac454b0b295e1d7501e26bddee4bc0289e79e33dadca255a52a645bee98cf81acf937db0ef </del> <ins> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-server-linux-amd64.tar.gz) | ae82d14b1214e4100f0cc2c988308b3e1edd040a65267d0eddb9082409f79644e55387889e3c0904a12c710f91206e9383edf510990bee8c9ea2e297b6472551 [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-server-linux-arm.tar.gz) | 9a2a5828b7d1ddb16cc19d573e99a4af642f84129408e6203eeeb0558e7b8db77f3269593b5770b6a976fe9df4a64240ed27ad05a4bd43719e55fce1db0abf58 [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-server-linux-arm64.tar.gz) | ed700dd226c999354ce05b73927388d36d08474c15333ae689427de15de27c84feb6b23c463afd9dd81993315f31eb8265938cfc7ecf6f750247aa42b9b33fa9 [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-server-linux-ppc64le.tar.gz) | abb7a9d726538be3ccf5057a0c63ff9732b616e213c6ebb81363f0c49f1e168ce8068b870061ad7cba7ba1d49252f94cf00a5f68cec0f38dc8fce4e24edc5ca6 [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-server-linux-s390x.tar.gz) | 3a51888af1bfdd2d5b0101d173ee589c1f39240e4428165f5f85c610344db219625faa42f00a49a83ce943fb079be873b1a114a62003fae2f328f9bf9d1227a4 </ins> ### Node binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-node-linux-amd64.tar.gz) | 8025bd8deb9586487fcf268bdaf99e8fd9f9433d9e7221c29363d1d66c4cbd55a2c44e6c89bc8133828c6a1aa0c42c2359b74846dfb71765c9ae8f21b8170625 [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-node-linux-arm.tar.gz) | 25787d47c8cc1e9445218d3a947b443d261266033187f8b7bc6141ae353a6806503fe72e3626f058236d4cd7f284348d2cc8ccb7a0219b9ddd7c6a336dae360b [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-node-linux-arm64.tar.gz) | ff737a7310057bdfd603f2853b15f79dc2b54a3cbbbd7a8ffd4d9756720fa5a02637ffc10a381eeee58bef61024ff348a49f3044a6dfa0ba99645fda8d08e2da [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-node-linux-ppc64le.tar.gz) | 2b1144c9ae116306a2c3214b02361083a60a349afc804909f95ea85db3660de5025de69a1860e8fc9e7e92ded335c93b74ecbbb20e1f6266078842d4adaf4161 [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-node-linux-s390x.tar.gz) | 822ec64aef3d65faa668a91177aa7f5d0c78a83cc1284c5e30629eda448ee4b2874cf4cfa6f3d68ad8eb8029dd035bf9fe15f68cc5aa4b644513f054ed7910ae [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.0/kubernetes-node-windows-amd64.tar.gz) | 3957cae43211df050c5a9991a48e23ac27d20aec117c580c53fc7edf47caf79ed1e2effa969b5b972968a83e9bdba0b20c46705caca0c35571713041481c1966 ## Changelog since v1.19.0-alpha.3 ## Changes by Kind ### API Change - EnvVarSource api doc bug fixes ([#91194](https://github.com/kubernetes/kubernetes/pull/91194), [@wawa0210](https://github.com/wawa0210)) [SIG Apps] - The Kubelet's `--really-crash-for-testing` and  `--chaos-chance` options are now marked as deprecated. ([#90499](https://github.com/kubernetes/kubernetes/pull/90499), [@knabben](https://github.com/knabben)) [SIG Node] - `NodeResourcesLeastAllocated` and `NodeResourcesMostAllocated` plugins now support customized weight on the CPU and memory. ([#90544](https://github.com/kubernetes/kubernetes/pull/90544), [@chendave](https://github.com/chendave)) [SIG Scheduling] ### Feature - Add .import-restrictions file to cmd/cloud-controller-manager. ([#90630](https://github.com/kubernetes/kubernetes/pull/90630), [@nilo19](https://github.com/nilo19)) [SIG API Machinery and Cloud Provider] - Add Annotations to CRI-API ImageSpec objects. ([#90061](https://github.com/kubernetes/kubernetes/pull/90061), [@marosset](https://github.com/marosset)) [SIG Node and Windows] - Kubelets configured to rotate client certificates now publish a `certificate_manager_server_ttl_seconds` gauge metric indicating the remaining seconds until certificate expiration. ([#91148](https://github.com/kubernetes/kubernetes/pull/91148), [@liggitt](https://github.com/liggitt)) [SIG Auth and Node] - Rest.Config now supports a flag to override proxy configuration that was previously only configurable through environment variables. ([#81443](https://github.com/kubernetes/kubernetes/pull/81443), [@mikedanese](https://github.com/mikedanese)) [SIG API Machinery and Node] - Scores from PodTopologySpreading have reduced differentiation as maxSkew increases. ([#90820](https://github.com/kubernetes/kubernetes/pull/90820), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - Service controller: only sync LB node pools when relevant fields in Node changes ([#90769](https://github.com/kubernetes/kubernetes/pull/90769), [@andrewsykim](https://github.com/andrewsykim)) [SIG Apps and Network] - Switch core master base images (kube-apiserver, kube-scheduler) from debian to distroless ([#90674](https://github.com/kubernetes/kubernetes/pull/90674), [@dims](https://github.com/dims)) [SIG Cloud Provider, Release and Scalability] - Update cri-tools to v1.18.0 ([#89720](https://github.com/kubernetes/kubernetes/pull/89720), [@saschagrunert](https://github.com/saschagrunert)) [SIG Cloud Provider, Cluster Lifecycle, Release and Scalability] ### Bug or Regression - Add support for TLS 1.3 ciphers: TLS_AES_128_GCM_SHA256, TLS_CHACHA20_POLY1305_SHA256 and TLS_AES_256_GCM_SHA384. ([#90843](https://github.com/kubernetes/kubernetes/pull/90843), [@pjbgf](https://github.com/pjbgf)) [SIG API Machinery, Auth and Cluster Lifecycle] - Base-images: Update to kube-cross:v1.13.9-5 ([#90963](https://github.com/kubernetes/kubernetes/pull/90963), [@justaugustus](https://github.com/justaugustus)) [SIG Release and Testing] - CloudNodeLifecycleController will check node existence status before shutdown status when monitoring nodes. ([#90737](https://github.com/kubernetes/kubernetes/pull/90737), [@jiahuif](https://github.com/jiahuif)) [SIG Apps and Cloud Provider] - First pod with required affinity terms can schedule only on nodes with matching topology keys. ([#91168](https://github.com/kubernetes/kubernetes/pull/91168), [@ahg-g](https://github.com/ahg-g)) [SIG Scheduling] - Fix VirtualMachineScaleSets.virtualMachines.GET not allowed issues when customers have set VMSS orchestrationMode. ([#91097](https://github.com/kubernetes/kubernetes/pull/91097), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Fix a racing issue that scheduler may perform unnecessary scheduling attempt. ([#90660](https://github.com/kubernetes/kubernetes/pull/90660), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling and Testing] - Fix kubectl run  --dry-run client  ignore namespace ([#90785](https://github.com/kubernetes/kubernetes/pull/90785), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - Fix public IP not shown issues after assigning public IP to Azure VMs ([#90886](https://github.com/kubernetes/kubernetes/pull/90886), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Fix: azure disk dangling attach issue which would cause API throttling ([#90749](https://github.com/kubernetes/kubernetes/pull/90749), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix: support removal of nodes backed by deleted non VMSS instances on Azure ([#91184](https://github.com/kubernetes/kubernetes/pull/91184), [@bpineau](https://github.com/bpineau)) [SIG Cloud Provider] - Fixed a regression preventing garbage collection of RBAC role and binding objects ([#90534](https://github.com/kubernetes/kubernetes/pull/90534), [@apelisse](https://github.com/apelisse)) [SIG Auth] - For external storage e2e test suite, update external driver, to pick snapshot provisioner from VolumeSnapshotClass, when a VolumeSnapshotClass is explicitly provided as an input. ([#90878](https://github.com/kubernetes/kubernetes/pull/90878), [@saikat-royc](https://github.com/saikat-royc)) [SIG Storage and Testing] - In a HA env, during the period a standby scheduler lost connection to API server, if a Pod is deleted and recreated, and the standby scheduler becomes master afterwards, there could be a scheduler cache corruption. This PR fixes this issue. ([#91126](https://github.com/kubernetes/kubernetes/pull/91126), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling] - Kubeadm: increase robustness for \"kubeadm join\" when adding etcd members on slower setups ([#90645](https://github.com/kubernetes/kubernetes/pull/90645), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Prevent PVC requested size overflow when expanding or creating a volume ([#90907](https://github.com/kubernetes/kubernetes/pull/90907), [@gnufied](https://github.com/gnufied)) [SIG Cloud Provider and Storage] - Scheduling failures due to no nodes available are now reported as unschedulable under ```schedule_attempts_total``` metric. ([#90989](https://github.com/kubernetes/kubernetes/pull/90989), [@ahg-g](https://github.com/ahg-g)) [SIG Scheduling] ### Other (Cleanup or Flake) - Adds additional testing to ensure that udp pods conntrack are cleaned up ([#90180](https://github.com/kubernetes/kubernetes/pull/90180), [@JacobTanenbaum](https://github.com/JacobTanenbaum)) [SIG Architecture, Network and Testing] - Adjusts the fsType for cinder values to be `ext4` if no fsType is specified. ([#90608](https://github.com/kubernetes/kubernetes/pull/90608), [@huffmanca](https://github.com/huffmanca)) [SIG Storage] - Change beta.kubernetes.io/os to kubernetes.io/os ([#89461](https://github.com/kubernetes/kubernetes/pull/89461), [@wawa0210](https://github.com/wawa0210)) [SIG Cloud Provider and Cluster Lifecycle] - Improve server-side apply conflict errors by setting dedicated kubectl subcommand field managers ([#88885](https://github.com/kubernetes/kubernetes/pull/88885), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG CLI and Testing] - It is now possible to use the service annotation `cloud.google.com/network-tier: Standard` to configure the Network Tier of the GCE Loadbalancer ([#88532](https://github.com/kubernetes/kubernetes/pull/88532), [@zioproto](https://github.com/zioproto)) [SIG Cloud Provider, Network and Testing] - Kubeadm now forwards the IPv6DualStack feature gate using the kubelet component config, instead of the kubelet command line ([#90840](https://github.com/kubernetes/kubernetes/pull/90840), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - Kubeadm: do not use a DaemonSet for the pre-pull of control-plane images during \"kubeadm upgrade apply\". Individual node upgrades now pull the required images using a preflight check. The flag \"--image-pull-timeout\" for \"kubeadm upgrade apply\" is now deprecated and will be removed in a future release following a GA deprecation policy. ([#90788](https://github.com/kubernetes/kubernetes/pull/90788), [@xlgao-zju](https://github.com/xlgao-zju)) [SIG Cluster Lifecycle] - Kubeadm: use two separate checks on /livez and /readyz for the kube-apiserver static Pod instead of using /healthz ([#90970](https://github.com/kubernetes/kubernetes/pull/90970), [@johscheuer](https://github.com/johscheuer)) [SIG Cluster Lifecycle] - The \"HostPath should give a volume the correct mode\" is no longer a conformance test ([#90861](https://github.com/kubernetes/kubernetes/pull/90861), [@dims](https://github.com/dims)) [SIG Architecture and Testing] - `beta.kubernetes.io/os` and `beta.kubernetes.io/arch` node labels are deprecated. Update node selectors to use `kubernetes.io/os` and `kubernetes.io/arch`. ([#91046](https://github.com/kubernetes/kubernetes/pull/91046), [@wawa0210](https://github.com/wawa0210)) [SIG Apps and Node] - base-images: Use debian-base:v2.1.0 ([#90697](https://github.com/kubernetes/kubernetes/pull/90697), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery and Release] - base-images: Use debian-iptables:v12.1.0 ([#90782](https://github.com/kubernetes/kubernetes/pull/90782), [@justaugustus](https://github.com/justaugustus)) [SIG Release] ## Dependencies ### Added - cloud.google.com/go/bigquery: v1.0.1 - cloud.google.com/go/datastore: v1.0.0 - cloud.google.com/go/pubsub: v1.0.1 - cloud.google.com/go/storage: v1.0.0 - dmitri.shuralyov.com/gpu/mtl: 666a987 - github.com/cespare/xxhash/v2: [v2.1.1](https://github.com/cespare/xxhash/v2/tree/v2.1.1) - github.com/chzyer/logex: [v1.1.10](https://github.com/chzyer/logex/tree/v1.1.10) - github.com/chzyer/readline: [2972be2](https://github.com/chzyer/readline/tree/2972be2) - github.com/chzyer/test: [a1ea475](https://github.com/chzyer/test/tree/a1ea475) - github.com/coreos/bbolt: [v1.3.2](https://github.com/coreos/bbolt/tree/v1.3.2) - github.com/cpuguy83/go-md2man/v2: [v2.0.0](https://github.com/cpuguy83/go-md2man/v2/tree/v2.0.0) - github.com/go-gl/glfw/v3.3/glfw: [12ad95a](https://github.com/go-gl/glfw/v3.3/glfw/tree/12ad95a) - github.com/google/renameio: [v0.1.0](https://github.com/google/renameio/tree/v0.1.0) - github.com/ianlancetaylor/demangle: [5e5cf60](https://github.com/ianlancetaylor/demangle/tree/5e5cf60) - github.com/rogpeppe/go-internal: [v1.3.0](https://github.com/rogpeppe/go-internal/tree/v1.3.0) - github.com/russross/blackfriday/v2: [v2.0.1](https://github.com/russross/blackfriday/v2/tree/v2.0.1) - github.com/shurcooL/sanitized_anchor_name: [v1.0.0](https://github.com/shurcooL/sanitized_anchor_name/tree/v1.0.0) - github.com/ugorji/go: [v1.1.4](https://github.com/ugorji/go/tree/v1.1.4) - golang.org/x/mod: v0.1.0 - google.golang.org/protobuf: v1.23.0 - gopkg.in/errgo.v2: v2.1.0 - k8s.io/klog/v2: v2.0.0 ### Changed - cloud.google.com/go: v0.38.0 → v0.51.0 - github.com/GoogleCloudPlatform/k8s-cloud-provider: [27a4ced → 7901bc8](https://github.com/GoogleCloudPlatform/k8s-cloud-provider/compare/27a4ced...7901bc8) - github.com/alecthomas/template: [a0175ee → fb15b89](https://github.com/alecthomas/template/compare/a0175ee...fb15b89) - github.com/alecthomas/units: [2efee85 → c3de453](https://github.com/alecthomas/units/compare/2efee85...c3de453) - github.com/beorn7/perks: [v1.0.0 → v1.0.1](https://github.com/beorn7/perks/compare/v1.0.0...v1.0.1) - github.com/coreos/pkg: [97fdf19 → 399ea9e](https://github.com/coreos/pkg/compare/97fdf19...399ea9e) - github.com/go-kit/kit: [v0.8.0 → v0.9.0](https://github.com/go-kit/kit/compare/v0.8.0...v0.9.0) - github.com/go-logfmt/logfmt: [v0.3.0 → v0.4.0](https://github.com/go-logfmt/logfmt/compare/v0.3.0...v0.4.0) - github.com/golang/groupcache: [02826c3 → 215e871](https://github.com/golang/groupcache/compare/02826c3...215e871) - github.com/golang/protobuf: [v1.3.3 → v1.4.2](https://github.com/golang/protobuf/compare/v1.3.3...v1.4.2) - github.com/google/cadvisor: [8af10c6 → 6a8d614](https://github.com/google/cadvisor/compare/8af10c6...6a8d614) - github.com/google/pprof: [3ea8567 → d4f498a](https://github.com/google/pprof/compare/3ea8567...d4f498a) - github.com/googleapis/gax-go/v2: [v2.0.4 → v2.0.5](https://github.com/googleapis/gax-go/v2/compare/v2.0.4...v2.0.5) - github.com/json-iterator/go: [v1.1.8 → v1.1.9](https://github.com/json-iterator/go/compare/v1.1.8...v1.1.9) - github.com/jstemmer/go-junit-report: [af01ea7 → v0.9.1](https://github.com/jstemmer/go-junit-report/compare/af01ea7...v0.9.1) - github.com/prometheus/client_golang: [v1.0.0 → v1.6.0](https://github.com/prometheus/client_golang/compare/v1.0.0...v1.6.0) - github.com/prometheus/common: [v0.4.1 → v0.9.1](https://github.com/prometheus/common/compare/v0.4.1...v0.9.1) - github.com/prometheus/procfs: [v0.0.5 → v0.0.11](https://github.com/prometheus/procfs/compare/v0.0.5...v0.0.11) - github.com/spf13/cobra: [v0.0.5 → v1.0.0](https://github.com/spf13/cobra/compare/v0.0.5...v1.0.0) - github.com/spf13/viper: [v1.3.2 → v1.4.0](https://github.com/spf13/viper/compare/v1.3.2...v1.4.0) - github.com/tmc/grpc-websocket-proxy: [89b8d40 → 0ad062e](https://github.com/tmc/grpc-websocket-proxy/compare/89b8d40...0ad062e) - go.opencensus.io: v0.21.0 → v0.22.2 - go.uber.org/atomic: v1.3.2 → v1.4.0 - golang.org/x/exp: 4b39c73 → da58074 - golang.org/x/image: 0694c2d → cff245a - golang.org/x/lint: 959b441 → fdd1cda - golang.org/x/mobile: d3739f8 → d2bd2a2 - golang.org/x/oauth2: 0f29369 → 858c2ad - google.golang.org/api: 5213b80 → v0.15.1 - google.golang.org/appengine: v1.5.0 → v1.6.5 - google.golang.org/genproto: f3c370f → ca5a221 - honnef.co/go/tools: e561f67 → v0.0.1-2019.2.3 - k8s.io/gengo: e0e292d → 8167cfd - k8s.io/kube-openapi: e1beb1b → 656914f - k8s.io/utils: a9aa75a → 2df71eb - sigs.k8s.io/apiserver-network-proxy/konnectivity-client: v0.0.7 → 33b9978 ### Removed - github.com/coreos/go-etcd: [v2.0.0+incompatible](https://github.com/coreos/go-etcd/tree/v2.0.0) - github.com/ugorji/go/codec: [d75b2dc](https://github.com/ugorji/go/codec/tree/d75b2dc) - k8s.io/klog: v1.0.0 # v1.19.0-alpha.3 [Documentation](https://docs.k8s.io) ## Downloads for v1.19.0-alpha.3 filename | sha512 hash -------- | ----------- [kubernetes.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes.tar.gz) | `49df3a77453b759d3262be6883dd9018426666b4261313725017eed42da1bc8dd1af037ec6c11357a6360c0c32c2486490036e9e132c9026f491325ce353c84b` [kubernetes-src.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-src.tar.gz) | `ddbb0baaf77516dc885c41017f4a8d91d0ff33eeab14009168a1e4d975939ccc6a053a682c2af14346c67fe7b142aa2c1ba32e86a30f2433cefa423764c5332d` </del> <ins> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-node-linux-amd64.tar.gz) | d0f28e3c38ca59a7ff1bfecb48a1ce97116520355d9286afdca1200d346c10018f5bbdf890f130a388654635a2e83e908b263ed45f8a88defca52a7c1d0a7984 [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-node-linux-arm.tar.gz) | ed9d3f13028beb3be39bce980c966f82c4b39dc73beaae38cc075fea5be30b0309e555cb2af8196014f2cc9f0df823354213c314b4d6545ff6e30dd2d00ec90e [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-node-linux-arm64.tar.gz) | ad5b3268db365dcdded9a9a4bffc90c7df0f844000349accdf2b8fb5f1081e553de9b9e9fb25d5e8a4ef7252d51fa94ef94d36d2ab31d157854e164136f662c2 [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-node-linux-ppc64le.tar.gz) | c4de2524e513996def5eeba7b83f7b406f17eaf89d4d557833a93bd035348c81fa9375dcd5c27cfcc55d73995449fc8ee504be1b3bd7b9f108b0b2f153cb05ae [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-node-linux-s390x.tar.gz) | 9157b44e3e7bd5478af9f72014e54d1afa5cd19b984b4cd8b348b312c385016bb77f29db47f44aea08b58abf47d8a396b92a2d0e03f2fe8acdd30f4f9466cbdb [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.1/kubernetes-node-windows-amd64.tar.gz) | 8b40a43c5e6447379ad2ee8aac06e8028555e1b370a995f6001018a62411abe5fbbca6060b3d1682c5cadc07a27d49edd3204e797af46368800d55f4ca8aa1de </ins> <del> ### Client Binaries filename | sha512 hash -------- | ----------- [kubernetes-client-darwin-386.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-client-darwin-386.tar.gz) | `c0fb1afb5b22f6e29cf3e5121299d3a5244a33b7663e041209bcc674a0009842b35b9ebdafa5bd6b91a1e1b67fa891e768627b97ea5258390d95250f07c2defc` [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-client-darwin-amd64.tar.gz) | `f32596863fed32bc8e3f032ef1e4f9f232898ed506624cb1b4877ce2ced2a0821d70b15599258422aa13181ab0e54f38837399ca611ab86cbf3feec03ede8b95` [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-client-linux-386.tar.gz) | `37290244cee54ff05662c2b14b69445eee674d385e6b05ca0b8c8b410ba047cf054033229c78af91670ca1370807753103c25dbb711507edc1c6beca87bd0988` [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-client-linux-amd64.tar.gz) | `3753eb28b9d68a47ef91fff3e91215015c28bce12828f81c0bbddbde118fd2cf4d580e474e54b1e8176fa547829e2ed08a4df36bbf83b912c831a459821bd581` [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-client-linux-arm.tar.gz) | `86b1cdb59a6b4e9de4496e5aa817b1ae7687ac6a93f8b8259cdeb356020773711d360a2ea35f7a8dc1bdd6d31c95e6491abf976afaff3392eb7d2df1008e192c` [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-client-linux-arm64.tar.gz) | `fbf324e92b93cd8048073b2a627ddc8866020bc4f086604d82bf4733d463411a534d8c8f72565976eb1b32be64aecae8858cd140ef8b7a3c96fcbbf92ca54689` [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-client-linux-ppc64le.tar.gz) | `7a6551eca17d29efb5d818e360b53ab2f0284e1091cc537e0a7ce39843d0b77579f26eb14bdeca9aa9e0aa0ef92ce1ccde34bdce84b4a5c1e090206979afb0ea` [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-client-linux-s390x.tar.gz) | `46352be54882cf3edb949b355e71daea839c9b1955ccfe1085590b81326665d81cabde192327d82e56d6a157e224caefdcfbec3364b9f8b18b5da0cfcb97fc0c` [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-client-windows-386.tar.gz) | `d049bf5f27e5e646ea4aa657aa0a694de57394b0dc60eadf1f7516d1ca6a6db39fc89d34bb6bba0a82f0c140113c2a91c41ad409e0ab41118a104f47eddcb9d2` [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-client-windows-amd64.tar.gz) | `2e585f6f97b86443a6e3a847c8dfaa29c6323f8d5bbfdb86dc7bf5465ba54f64b35ee55a6d38e9be105a67fff39057ad16db3f3b1c3b9c909578517f4da7e51e` ### Server Binaries filename | sha512 hash -------- | ----------- [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-server-linux-amd64.tar.gz) | `8c41c6abf32ba7040c2cc654765d443e615d96891eacf6bcec24146a8aaf79b9206d13358518958e5ec04eb911ade108d4522ebd8603b88b3e3d95e7d5b24e60` [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-server-linux-arm.tar.gz) | `7e54c60bf724e2e3e2cff1197512ead0f73030788877f2f92a7e0deeeabd86e75ce8120eb815bf63909f8a110e647a5fcfddd510efffbd9c339bd0f90caa6706` [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-server-linux-arm64.tar.gz) | `7c57fd80b18be6dd6b6e17558d12ec0c07c06ce248e99837737fdd39b7f5d752597679748dc6294563f30def986ed712a8f469f3ea1c3a4cbe5d63c44f1d41dc` [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-server-linux-ppc64le.tar.gz) | `d22b1d4d8ccf9e9df8f90d35b8d2a1e7916f8d809806743cddc00b15d8ace095c54c61d7c9affd6609a316ee14ba43bf760bfec4276aee8273203aab3e7ac3c1` [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-server-linux-s390x.tar.gz) | `3177c9a2d6bd116d614fa69ff9cb16b822bee4e36e38f93ece6aeb5d118ae67dbe61546c7f628258ad719e763c127ca32437ded70279ea869cfe4869e06cbdde` ### Node Binaries filename | sha512 hash -------- | ----------- [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-node-linux-amd64.tar.gz) | `543248e35c57454bfc4b6f3cf313402d7cf81606b9821a5dd95c6758d55d5b9a42e283a7fb0d45322ad1014e3382aafaee69879111c0799dac31d5c4ad1b8041` [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-node-linux-arm.tar.gz) | `c94bed3861376d3fd41cb7bc93b5a849612bc7346ed918f6b5b634449cd3acef69ff63ca0b6da29f45df68402f64f3d290d7688bc50f46dac07e889219dac30c` [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-node-linux-arm64.tar.gz) | `3649dbca59d08c3922830b7acd8176e8d2f622fbf6379288f3a70045763d5d72c944d241f8a2c57306f23e6e44f7cc3b912554442f77e0f90e9f876f240114a8` [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-node-linux-ppc64le.tar.gz) | `5655d1d48a1ae97352af2d703954c7a28c2d1c644319c4eb24fe19ccc5fb546c30b34cc86d8910f26c88feee88d7583bc085ebfe58916054f73dcf372a824fd9` [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-node-linux-s390x.tar.gz) | `55190804357a687c37d1abb489d5aef7cea209d1c03778548f0aa4dab57a0b98b710fda09ff5c46d0963f2bb674726301d544b359f673df8f57226cafa831ce3` [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.3/kubernetes-node-windows-amd64.tar.gz) | `d8ffbe8dc9a0b0b55db357afa6ef94e6145f9142b1bc505897cac9ee7c950ef527a189397a8e61296e66ce76b020eccb276668256927d2273d6079b9ffebef24` ## Changelog since v1.19.0-alpha.2 </del> <ins> ## Changelog since v1.20.0-alpha.0 </ins> ## Urgent Upgrade Notes ### (No, really, you MUST read this before you upgrade) <del> - Kubeadm does not set the deprecated '--cgroup-driver' flag in /var/lib/kubelet/kubeadm-flags.env, it will be set in the kubelet config.yaml. If you have this flag in /var/lib/kubelet/kubeadm-flags.env or /etc/default/kubelet (/etc/sysconfig/kubelet for RPMs) please remove it and set the value using KubeletConfiguration ([#90513](https://github.com/kubernetes/kubernetes/pull/90513), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle] - Kubeadm respects resolvConf value set by user even if systemd-resolved service is active. kubeadm no longer sets the flag in '--resolv-conf' in /var/lib/kubelet/kubeadm-flags.env. If you have this flag in /var/lib/kubelet/kubeadm-flags.env or /etc/default/kubelet (/etc/sysconfig/kubelet for RPMs) please remove it and set the value using KubeletConfiguration ([#90394](https://github.com/kubernetes/kubernetes/pull/90394), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle] </del> <ins> - Azure blob disk feature(`kind`: `Shared`, `Dedicated`) has been deprecated, you should use `kind`: `Managed` in `kubernetes.io/azure-disk` storage class. ([#92905](https://github.com/kubernetes/kubernetes/pull/92905), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - CVE-2020-8559 (Medium): Privilege escalation from compromised node to cluster. See https://github.com/kubernetes/kubernetes/issues/92914 for more details. The API Server will no longer proxy non-101 responses for upgrade requests. This could break proxied backends (such as an extension API server) that respond to upgrade requests with a non-101 response code. ([#92941](https://github.com/kubernetes/kubernetes/pull/92941), [@tallclair](https://github.com/tallclair)) [SIG API Machinery] </ins> ## Changes by Kind ### Deprecation <del> - Apiextensions.k8s.io/v1beta1 is deprecated in favor of apiextensions.k8s.io/v1 ([#90673](https://github.com/kubernetes/kubernetes/pull/90673), [@deads2k](https://github.com/deads2k)) [SIG API Machinery] - Apiregistration.k8s.io/v1beta1 is deprecated in favor of apiregistration.k8s.io/v1 ([#90672](https://github.com/kubernetes/kubernetes/pull/90672), [@deads2k](https://github.com/deads2k)) [SIG API Machinery] - Authentication.k8s.io/v1beta1 and authorization.k8s.io/v1beta1 are deprecated in 1.19 in favor of v1 levels and will be removed in 1.22 ([#90458](https://github.com/kubernetes/kubernetes/pull/90458), [@deads2k](https://github.com/deads2k)) [SIG API Machinery and Auth] - Autoscaling/v2beta1 is deprecated in favor of autoscaling/v2beta2 ([#90463](https://github.com/kubernetes/kubernetes/pull/90463), [@deads2k](https://github.com/deads2k)) [SIG Autoscaling] - Coordination.k8s.io/v1beta1 is deprecated in 1.19, targeted for removal in 1.22, use v1 instead. ([#90559](https://github.com/kubernetes/kubernetes/pull/90559), [@deads2k](https://github.com/deads2k)) [SIG Scalability] - Storage.k8s.io/v1beta1 is deprecated in favor of storage.k8s.io/v1 ([#90671](https://github.com/kubernetes/kubernetes/pull/90671), [@deads2k](https://github.com/deads2k)) [SIG Storage] </del> <ins> - Kube-apiserver: the componentstatus API is deprecated. This API provided status of etcd, kube-scheduler, and kube-controller-manager components, but only worked when those components were local to the API server, and when kube-scheduler and kube-controller-manager exposed unsecured health endpoints. Instead of this API, etcd health is included in the kube-apiserver health check and kube-scheduler/kube-controller-manager health checks can be made directly against those components' health endpoints. ([#93570](https://github.com/kubernetes/kubernetes/pull/93570), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Apps and Cluster Lifecycle] - Kubeadm: deprecate the \"kubeadm alpha kubelet config enable-dynamic\" command. To continue using the feature please defer to the guide for \"Dynamic Kubelet Configuration\" at k8s.io. ([#92881](https://github.com/kubernetes/kubernetes/pull/92881), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: remove the deprecated \"kubeadm alpha kubelet config enable-dynamic\" command. To continue using the feature please defer to the guide for \"Dynamic Kubelet Configuration\" at k8s.io. This change also removes the parent command \"kubeadm alpha kubelet\" as there are no more sub-commands under it for the time being. ([#94668](https://github.com/kubernetes/kubernetes/pull/94668), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: remove the deprecated --kubelet-config flag for the command \"kubeadm upgrade node\" ([#94869](https://github.com/kubernetes/kubernetes/pull/94869), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubelet's deprecated endpoint `metrics/resource/v1alpha1` has been removed, please adopt to `metrics/resource`. ([#94272](https://github.com/kubernetes/kubernetes/pull/94272), [@RainbowMango](https://github.com/RainbowMango)) [SIG Instrumentation and Node] - The v1alpha1 PodPreset API and admission plugin has been removed with no built-in replacement. Admission webhooks can be used to modify pods on creation. ([#94090](https://github.com/kubernetes/kubernetes/pull/94090), [@deads2k](https://github.com/deads2k)) [SIG API Machinery, Apps, CLI, Cloud Provider, Scalability and Testing] </ins> ### API Change <del> - K8s.io/apimachinery - scheme.Convert() now uses only explicitly registered conversions - default reflection based conversion is no longer available. `+k8s:conversion-gen` tags can be used with the `k8s.io/code-generator` component to generate conversions. ([#90018](https://github.com/kubernetes/kubernetes/pull/90018), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery, Apps and Testing] - Kubelet's --runonce option is now also available in Kubelet's config file as `runOnce`. ([#89128](https://github.com/kubernetes/kubernetes/pull/89128), [@vincent178](https://github.com/vincent178)) [SIG Node] - Promote Immutable Secrets/ConfigMaps feature to Beta and enable the feature by default. This allows to set `Immutable` field in Secrets or ConfigMap object to mark their contents as immutable. ([#89594](https://github.com/kubernetes/kubernetes/pull/89594), [@wojtek-t](https://github.com/wojtek-t)) [SIG Apps and Testing] - The unused `series.state` field, deprecated since v1.14, is removed from the `events.k8s.io/v1beta1` and `v1` Event types. ([#90449](https://github.com/kubernetes/kubernetes/pull/90449), [@wojtek-t](https://github.com/wojtek-t)) [SIG Apps] </del> <ins> - A new `nofuzz` go build tag now disables gofuzz support. Release binaries enable this. ([#92491](https://github.com/kubernetes/kubernetes/pull/92491), [@BenTheElder](https://github.com/BenTheElder)) [SIG API Machinery] - A new alpha-level field, `SupportsFsGroup`, has been introduced for CSIDrivers to allow them to specify whether they support volume ownership and permission modifications. The `CSIVolumeSupportFSGroup` feature gate must be enabled to allow this field to be used. ([#92001](https://github.com/kubernetes/kubernetes/pull/92001), [@huffmanca](https://github.com/huffmanca)) [SIG API Machinery, CLI and Storage] - Added pod version skew strategy for seccomp profile to synchronize the deprecated annotations with the new API Server fields. Please see the corresponding section [in the KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/20190717-seccomp-ga.md&#35;version-skew-strategy) for more detailed explanations. ([#91408](https://github.com/kubernetes/kubernetes/pull/91408), [@saschagrunert](https://github.com/saschagrunert)) [SIG Apps, Auth, CLI and Node] - Adds the ability to disable Accelerator/GPU metrics collected by Kubelet ([#91930](https://github.com/kubernetes/kubernetes/pull/91930), [@RenaudWasTaken](https://github.com/RenaudWasTaken)) [SIG Node] - Custom Endpoints are now mirrored to EndpointSlices by a new EndpointSliceMirroring controller. ([#91637](https://github.com/kubernetes/kubernetes/pull/91637), [@robscott](https://github.com/robscott)) [SIG API Machinery, Apps, Auth, Cloud Provider, Instrumentation, Network and Testing] - External facing API podresources is now available under k8s.io/kubelet/pkg/apis/ ([#92632](https://github.com/kubernetes/kubernetes/pull/92632), [@RenaudWasTaken](https://github.com/RenaudWasTaken)) [SIG Node and Testing] - Fix conversions for custom metrics. ([#94481](https://github.com/kubernetes/kubernetes/pull/94481), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery and Instrumentation] - Generic ephemeral volumes, a new alpha feature under the `GenericEphemeralVolume` feature gate, provide a more flexible alternative to `EmptyDir` volumes: as with `EmptyDir`, volumes are created and deleted for each pod automatically by Kubernetes. But because the normal provisioning process is used (`PersistentVolumeClaim`), storage can be provided by third-party storage vendors and all of the usual volume features work. Volumes don't need to be empt; for example, restoring from snapshot is supported. ([#92784](https://github.com/kubernetes/kubernetes/pull/92784), [@pohly](https://github.com/pohly)) [SIG API Machinery, Apps, Auth, CLI, Instrumentation, Node, Scheduling, Storage and Testing] - Kube-controller-manager: volume plugins can be restricted from contacting local and loopback addresses by setting `--volume-host-allow-local-loopback=false`, or from contacting specific CIDR ranges by setting `--volume-host-cidr-denylist` (for example, `--volume-host-cidr-denylist=127.0.0.1/28,feed::/16`) ([#91785](https://github.com/kubernetes/kubernetes/pull/91785), [@mattcary](https://github.com/mattcary)) [SIG API Machinery, Apps, Auth, CLI, Network, Node, Storage and Testing] - Kubernetes is now built with golang 1.15.0-rc.1. - The deprecated, legacy behavior of treating the CommonName field on X.509 serving certificates as a host name when no Subject Alternative Names are present is now disabled by default. It can be temporarily re-enabled by adding the value x509ignoreCN=0 to the GODEBUG environment variable. ([#93264](https://github.com/kubernetes/kubernetes/pull/93264), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery, Auth, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Network, Node, Release, Scalability, Storage and Testing] - Migrate scheduler, controller-manager and cloud-controller-manager to use LeaseLock ([#94603](https://github.com/kubernetes/kubernetes/pull/94603), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery, Apps, Cloud Provider and Scheduling] - Modify DNS-1123 error messages to indicate that RFC 1123 is not followed exactly ([#94182](https://github.com/kubernetes/kubernetes/pull/94182), [@mattfenwick](https://github.com/mattfenwick)) [SIG API Machinery, Apps, Auth, Network and Node] - The ServiceAccountIssuerDiscovery feature gate is now Beta and enabled by default. ([#91921](https://github.com/kubernetes/kubernetes/pull/91921), [@mtaufen](https://github.com/mtaufen)) [SIG Auth] - The kube-controller-manager managed signers can now have distinct signing certificates and keys.  See the help about `--cluster-signing-[signer-name]-{cert,key}-file`.  `--cluster-signing-{cert,key}-file` is still the default. ([#90822](https://github.com/kubernetes/kubernetes/pull/90822), [@deads2k](https://github.com/deads2k)) [SIG API Machinery, Apps and Auth] - When creating a networking.k8s.io/v1 Ingress API object, `spec.tls[*].secretName` values are required to pass validation rules for Secret API object names. ([#93929](https://github.com/kubernetes/kubernetes/pull/93929), [@liggitt](https://github.com/liggitt)) [SIG Network] - WinOverlay feature graduated to beta ([#94807](https://github.com/kubernetes/kubernetes/pull/94807), [@ksubrmnn](https://github.com/ksubrmnn)) [SIG Windows] </ins> ### Feature <del> - Kube-apiserver: The NodeRestriction admission plugin now restricts Node labels kubelets are permitted to set when creating a new Node to the `--node-labels` parameters accepted by kubelets in 1.16+. ([#90307](https://github.com/kubernetes/kubernetes/pull/90307), [@liggitt](https://github.com/liggitt)) [SIG Auth and Node] - Kubectl supports taint no without specifying(without having to type the full resource name) ([#88723](https://github.com/kubernetes/kubernetes/pull/88723), [@wawa0210](https://github.com/wawa0210)) [SIG CLI] - New scoring for PodTopologySpreading that yields better spreading ([#90475](https://github.com/kubernetes/kubernetes/pull/90475), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - No ([#89549](https://github.com/kubernetes/kubernetes/pull/89549), [@happinesstaker](https://github.com/happinesstaker)) [SIG API Machinery, Auth, Instrumentation and Testing] - Try to send watch bookmarks (if requested) periodically in addition to sending them right before timeout ([#90560](https://github.com/kubernetes/kubernetes/pull/90560), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery] ### Bug or Regression - Avoid GCE API calls when initializing GCE CloudProvider for Kubelets. ([#90218](https://github.com/kubernetes/kubernetes/pull/90218), [@wojtek-t](https://github.com/wojtek-t)) [SIG Cloud Provider and Scalability] - Avoid unnecessary scheduling churn when annotations are updated while Pods are being scheduled. ([#90373](https://github.com/kubernetes/kubernetes/pull/90373), [@fabiokung](https://github.com/fabiokung)) [SIG Scheduling] - Fix a bug where ExternalTrafficPolicy is not applied to service ExternalIPs. ([#90537](https://github.com/kubernetes/kubernetes/pull/90537), [@freehan](https://github.com/freehan)) [SIG Network] - Fixed a regression in wait.Forever that skips the backoff period on the first repeat ([#90476](https://github.com/kubernetes/kubernetes/pull/90476), [@zhan849](https://github.com/zhan849)) [SIG API Machinery] - Fixes a bug that non directory hostpath type can be recognized as HostPathFile and adds e2e tests for HostPathType ([#64829](https://github.com/kubernetes/kubernetes/pull/64829), [@dixudx](https://github.com/dixudx)) [SIG Apps, Storage and Testing] - Fixes a regression in 1.17 that dropped cache-control headers on API requests ([#90468](https://github.com/kubernetes/kubernetes/pull/90468), [@liggitt](https://github.com/liggitt)) [SIG API Machinery and Testing] - Fixes regression in CPUManager that caused freeing of exclusive CPUs at incorrect times ([#90377](https://github.com/kubernetes/kubernetes/pull/90377), [@cbf123](https://github.com/cbf123)) [SIG Cloud Provider and Node] - Fixes regression in CPUManager that had the (rare) possibility to release exclusive CPUs in app containers inherited from init containers. ([#90419](https://github.com/kubernetes/kubernetes/pull/90419), [@klueska](https://github.com/klueska)) [SIG Node] - Jsonpath support in kubectl / client-go serializes complex types (maps / slices / structs) as json instead of Go-syntax. ([#89660](https://github.com/kubernetes/kubernetes/pull/89660), [@pjferrell](https://github.com/pjferrell)) [SIG API Machinery, CLI and Cluster Lifecycle] - Kubeadm: ensure `image-pull-timeout` flag is respected during upgrade phase ([#90328](https://github.com/kubernetes/kubernetes/pull/90328), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle] - Kubeadm: fix misleading warning for the kube-apiserver authz modes during \"kubeadm init\" ([#90064](https://github.com/kubernetes/kubernetes/pull/90064), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Provides a fix to allow a cluster in a private Azure cloud to authenticate to ACR in the same cloud. ([#90425](https://github.com/kubernetes/kubernetes/pull/90425), [@DavidParks8](https://github.com/DavidParks8)) [SIG Cloud Provider] - Update github.com/moby/ipvs to v1.0.1 to fix IPVS compatiblity issue with older kernels ([#90555](https://github.com/kubernetes/kubernetes/pull/90555), [@andrewsykim](https://github.com/andrewsykim)) [SIG Network] - Updates to pod status via the status subresource now validate that `status.podIP` and `status.podIPs` fields are well-formed. ([#90628](https://github.com/kubernetes/kubernetes/pull/90628), [@liggitt](https://github.com/liggitt)) [SIG Apps and Node] ### Other (Cleanup or Flake) - Drop some conformance tests that rely on Kubelet API directly ([#90615](https://github.com/kubernetes/kubernetes/pull/90615), [@dims](https://github.com/dims)) [SIG Architecture, Network, Release and Testing] - Kube-proxy exposes a new metric, `kubeproxy_sync_proxy_rules_last_queued_timestamp_seconds`, that indicates the last time a change for kube-proxy was queued to be applied. ([#90175](https://github.com/kubernetes/kubernetes/pull/90175), [@squeed](https://github.com/squeed)) [SIG Instrumentation and Network] - Kubeadm: fix badly formatted error message for small service CIDRs ([#90411](https://github.com/kubernetes/kubernetes/pull/90411), [@johscheuer](https://github.com/johscheuer)) [SIG Cluster Lifecycle] - None. ([#90484](https://github.com/kubernetes/kubernetes/pull/90484), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - Remove the repeated calculation of nodeName and hostname during kubelet startup, these parameters are all calculated in the `RunKubelet` method ([#90284](https://github.com/kubernetes/kubernetes/pull/90284), [@wawa0210](https://github.com/wawa0210)) [SIG Node] - UI change ([#87743](https://github.com/kubernetes/kubernetes/pull/87743), [@u2takey](https://github.com/u2takey)) [SIG Apps and Node] - Update opencontainers/runtime-spec dependency to v1.0.2 ([#89644](https://github.com/kubernetes/kubernetes/pull/89644), [@saschagrunert](https://github.com/saschagrunert)) [SIG Node] # v1.19.0-alpha.2 [Documentation](https://docs.k8s.io) ## Downloads for v1.19.0-alpha.2 filename | sha512 hash -------- | ----------- [kubernetes.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes.tar.gz) | `a1106309d18a5d73882650f8a5cbd1f287436a0dc527136808e5e882f5e98d6b0d80029ff53abc0c06ac240f6b879167437f15906e5309248d536ec1675ed909` [kubernetes-src.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-src.tar.gz) | `c24c0b2a99ad0d834e0f017d7436fa84c6de8f30e8768ee59b1a418eb66a9b34ed4bcc25e03c04b19ea17366564f4ee6fe55a520fa4d0837e86c0a72fc7328c1` ### Client Binaries filename | sha512 hash -------- | ----------- [kubernetes-client-darwin-386.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-client-darwin-386.tar.gz) | `51ede026b0f8338f7fd293fb096772a67f88f23411c3280dff2f9efdd3ad7be7917d5c32ba764162c1a82b14218a90f624271c3cd8f386c8e41e4a9eac28751f` [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-client-darwin-amd64.tar.gz) | `4ed4358cabbecf724d974207746303638c7f23d422ece9c322104128c245c8485e37d6ffdd9d17e13bb1d8110e870c0fe17dcc1c9e556b69a4df7d34b6ff66d5` [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-client-linux-386.tar.gz) | `a57b10f146083828f18d809dbe07938b72216fa21083e7dbb9acce7dbcc3e8c51b8287d3bf89e81c8e1af4dd139075c675cc0f6ae7866ef69a3813db09309b97` [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-client-linux-amd64.tar.gz) | `099247419dd34dc78131f24f1890cc5c6a739e887c88fae96419d980c529456bfd45c4e451ba5b6425320ddc764245a2eab1bd5e2b5121d9a2774bdb5df9438b` [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-client-linux-arm.tar.gz) | `d12704bc6c821d3afcd206234fbd32e57cefcb5a5d15a40434b6b0ef4781d7fa77080e490678005225f24b116540ff51e436274debf66a6eb2247cd1dc833e6c` [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-client-linux-arm64.tar.gz) | `da0d110751fa9adac69ed2166eb82b8634989a32b65981eff014c84449047abfb94fe015e2d2e22665d57ff19f673e2c9f6549c578ad1b1e2f18b39871b50b81` [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-client-linux-ppc64le.tar.gz) | `7ac2b85bba9485dd38aed21895d627d34beb9e3b238e0684a9864f4ce2cfa67d7b3b7c04babc2ede7144d05beacdbe11c28c7d53a5b0041004700b2854b68042` [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-client-linux-s390x.tar.gz) | `ac447eabc5002a059e614b481d25e668735a7858134f8ad49feb388bb9f9191ff03b65da57bb49811119983e8744c8fdc7d19c184d9232bd6d038fae9eeec7c6` [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-client-windows-386.tar.gz) | `7c7dac7af329e4515302e7c35d3a19035352b4211942f254a4bb94c582a89d740b214d236ba6e35b9e78945a06b7e6fe8d70da669ecc19a40b7a9e8eaa2c0a28` [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-client-windows-amd64.tar.gz) | `0c89b70a25551123ffdd7c5d3cc499832454745508c5f539f13b4ea0bf6eea1afd16e316560da9cf68e5178ae69d91ccfe6c02d7054588db3fac15c30ed96f4b` ### Server Binaries filename | sha512 hash -------- | ----------- [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-server-linux-amd64.tar.gz) | `3396e6e0516a09999ec26631e305cf0fb1eb0109ca1490837550b7635eb051dd92443de8f4321971fc2b4030ea2d8da4bfe8b85887505dec96e2a136b6a46617` [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-server-linux-arm.tar.gz) | `cdea122a2d8d602ec0c89c1135ecfc27c47662982afc5b94edf4a6db7d759f27d6fe8d8b727bddf798bfec214a50e8d8a6d8eb0bca2ad5b1f72eb3768afd37f1` [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-server-linux-arm64.tar.gz) | `6543186a3f4437fb475fbc6a5f537640ab00afb2a22678c468c3699b3f7493f8b35fb6ca14694406ffc90ff8faad17a1d9d9d45732baa976cb69f4b27281295a` [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-server-linux-ppc64le.tar.gz) | `fde8dfeb9a0b243c8bef5127a9c63bf685429e2ff7e486ac8bae373882b87a4bd1b28a12955e3cce1c04eb0e6a67aabba43567952f9deef943a75fcb157a949c` [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-server-linux-s390x.tar.gz) | `399d004ee4db5d367f37a1fa9ace63b5db4522bd25eeb32225019f3df9b70c715d2159f6556015ddffe8f49aa0f72a1f095f742244637105ddbed3fb09570d0d` ### Node Binaries filename | sha512 hash -------- | ----------- [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-node-linux-amd64.tar.gz) | `fd865c2fcc71796d73c90982f90c789a44a921cf1d56aee692bd00efaa122dcc903b0448f285a06b0a903e809f8310546764b742823fb8d10690d36ec9e27cbd` [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-node-linux-arm.tar.gz) | `63aeb35222241e2a9285aeee4190b4b49c49995666db5cdb142016ca87872e7fdafc9723bc5de1797a45cc7e950230ed27be93ac165b8cda23ca2a9f9233c27a` [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-node-linux-arm64.tar.gz) | `3532574d9babfc064ce90099b514eadfc2a4ce69091f92d9c1a554ead91444373416d1506a35ef557438606a96cf0e5168a83ddd56c92593ea4adaa15b0b56a8` [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-node-linux-ppc64le.tar.gz) | `de59d91e5b0e4549e9a97f3a0243236e97babaed08c70f1a17273abf1966e6127db7546e1f91c3d66e933ce6eeb70bc65632ab473aa2c1be2a853da026c9d725` [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-node-linux-s390x.tar.gz) | `0cb8cf6f8dffd63122376a2f3e8986a2db155494a45430beea7cb5d1180417072428dabebd1af566ea13a4f079d46368c8b549be4b8a6c0f62a974290fd2fdb0` [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.2/kubernetes-node-windows-amd64.tar.gz) | `f1faf695f9f6fded681653f958b48779a2fecf50803af49787acba192441790c38b2b611ec8e238971508c56e67bb078fb423e8f6d9bddb392c199b5ee47937c` ## Changelog since v1.19.0-alpha.1 ## Urgent Upgrade Notes </del> <ins> - ACTION REQUIRED : In CoreDNS v1.7.0, [metrics names have been changed](https://github.com/coredns/coredns/blob/master/notes/coredns-1.7.0.md&#35;metric-changes) which will be backward incompatible with existing reporting formulas that use the old metrics' names. Adjust your formulas to the new names before upgrading. </ins> <del> ### (No, really, you MUST read this before you upgrade) - Kubeadm now respects user specified etcd versions in the ClusterConfiguration and properly uses them. If users do not want to stick to the version specified in the ClusterConfiguration, they should edit the kubeadm-config config map and delete it. ([#89588](https://github.com/kubernetes/kubernetes/pull/89588), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] </del> <ins> Kubeadm now includes CoreDNS version v1.7.0. Some of the major changes include: -  Fixed a bug that could cause CoreDNS to stop updating service records. -  Fixed a bug in the forward plugin where only the first upstream server is always selected no matter which policy is set. -  Remove already deprecated options `resyncperiod` and `upstream` in the Kubernetes plugin. -  Includes Prometheus metrics name changes (to bring them in line with standard Prometheus metrics naming convention). They will be backward incompatible with existing reporting formulas that use the old metrics' names. -  The federation plugin (allows for v1 Kubernetes federation) has been removed. More details are available in https://coredns.io/2020/06/15/coredns-1.7.0-release/ ([#92651](https://github.com/kubernetes/kubernetes/pull/92651), [@rajansandeep](https://github.com/rajansandeep)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle and Instrumentation] - Add metrics for azure service operations (route and loadbalancer). ([#94124](https://github.com/kubernetes/kubernetes/pull/94124), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider and Instrumentation] - Add network rule support in Azure account creation ([#94239](https://github.com/kubernetes/kubernetes/pull/94239), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Add tags support for Azure File Driver ([#92825](https://github.com/kubernetes/kubernetes/pull/92825), [@ZeroMagic](https://github.com/ZeroMagic)) [SIG Cloud Provider and Storage] - Added kube-apiserver metrics: apiserver_current_inflight_request_measures and, when API Priority and Fairness is enable, windowed_request_stats. ([#91177](https://github.com/kubernetes/kubernetes/pull/91177), [@MikeSpreitzer](https://github.com/MikeSpreitzer)) [SIG API Machinery, Instrumentation and Testing] - Audit events for API requests to deprecated API versions now include a `\"k8s.io/deprecated\": \"true\"` audit annotation. If a target removal release is identified, the audit event includes a `\"k8s.io/removal-release\": \"<majorVersion>.<minorVersion>\"` audit annotation as well. ([#92842](https://github.com/kubernetes/kubernetes/pull/92842), [@liggitt](https://github.com/liggitt)) [SIG API Machinery and Instrumentation] - Cloud node-controller use InstancesV2 ([#91319](https://github.com/kubernetes/kubernetes/pull/91319), [@gongguan](https://github.com/gongguan)) [SIG Apps, Cloud Provider, Scalability and Storage] - Kubeadm: Add a preflight check that the control-plane node has at least 1700MB of RAM ([#93275](https://github.com/kubernetes/kubernetes/pull/93275), [@xlgao-zju](https://github.com/xlgao-zju)) [SIG Cluster Lifecycle] - Kubeadm: add the \"--cluster-name\" flag to the \"kubeadm alpha kubeconfig user\" to allow configuring the cluster name in the generated kubeconfig file ([#93992](https://github.com/kubernetes/kubernetes/pull/93992), [@prabhu43](https://github.com/prabhu43)) [SIG Cluster Lifecycle] - Kubeadm: add the \"--kubeconfig\" flag to the \"kubeadm init phase upload-certs\" command to allow users to pass a custom location for a kubeconfig file. ([#94765](https://github.com/kubernetes/kubernetes/pull/94765), [@zhanw15](https://github.com/zhanw15)) [SIG Cluster Lifecycle] - Kubeadm: deprecate the \"--csr-only\" and \"--csr-dir\" flags of the \"kubeadm init phase certs\" subcommands. Please use \"kubeadm alpha certs generate-csr\" instead. This new command allows you to generate new private keys and certificate signing requests for all the control-plane components, so that the certificates can be signed by an external CA. ([#92183](https://github.com/kubernetes/kubernetes/pull/92183), [@wallrj](https://github.com/wallrj)) [SIG Cluster Lifecycle] - Kubeadm: make etcd pod request 100m CPU, 100Mi memory and 100Mi ephemeral_storage by default ([#94479](https://github.com/kubernetes/kubernetes/pull/94479), [@knight42](https://github.com/knight42)) [SIG Cluster Lifecycle] - Kubemark now supports both real and hollow nodes in a single cluster. ([#93201](https://github.com/kubernetes/kubernetes/pull/93201), [@ellistarn](https://github.com/ellistarn)) [SIG Scalability] - Kubernetes is now built using go1.15.2 - build: Update to k/repo-infra@v0.1.1 (supports go1.15.2) - build: Use go-runner:buster-v2.0.1 (built using go1.15.1) - bazel: Replace --features with Starlark build settings flag - hack/lib/util.sh: some bash cleanups - switched one spot to use kube::logging - make kube::util::find-binary return an error when it doesn't find anything so that hack scripts fail fast instead of with '' binary not found errors. - this required deleting some genfeddoc stuff. the binary no longer exists in k/k repo since we removed federation/, and I don't see it in https://github.com/kubernetes-sigs/kubefed/ either. I'm assuming that it's gone for good now. - bazel: output go_binary rule directly from go_binary_conditional_pure From: @mikedanese: Instead of aliasing. Aliases are annoying in a number of ways. This is specifically bugging me now because they make the action graph harder to analyze programmatically. By using aliases here, we would need to handle potentially aliased go_binary targets and dereference to the effective target. The comment references an issue with `pure = select(...)` which appears to be resolved considering this now builds. - make kube::util::find-binary not dependent on bazel-out/ structure Implement an aspect that outputs go_build_mode metadata for go binaries, and use that during binary selection. ([#94449](https://github.com/kubernetes/kubernetes/pull/94449), [@justaugustus](https://github.com/justaugustus)) [SIG Architecture, CLI, Cluster Lifecycle, Node, Release and Testing] - Only update Azure data disks when attach/detach ([#94265](https://github.com/kubernetes/kubernetes/pull/94265), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Promote SupportNodePidsLimit to GA to provide node to pod pid isolation Promote SupportPodPidsLimit to GA to provide ability to limit pids per pod ([#94140](https://github.com/kubernetes/kubernetes/pull/94140), [@derekwaynecarr](https://github.com/derekwaynecarr)) [SIG Node and Testing] - Rename pod_preemption_metrics to preemption_metrics. ([#93256](https://github.com/kubernetes/kubernetes/pull/93256), [@ahg-g](https://github.com/ahg-g)) [SIG Instrumentation and Scheduling] - Server-side apply behavior has been regularized in the case where a field is removed from the applied configuration. Removed fields which have no other owners are deleted from the live object, or reset to their default value if they have one. Safe ownership transfers, such as the transfer of a `replicas` field from a user to an HPA without resetting to the default value are documented in [Transferring Ownership](https://kubernetes.io/docs/reference/using-api/api-concepts/&#35;transferring-ownership) ([#92661](https://github.com/kubernetes/kubernetes/pull/92661), [@jpbetz](https://github.com/jpbetz)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation and Testing] - Set CSIMigrationvSphere feature gates to beta. Users should enable CSIMigration + CSIMigrationvSphere features and install the vSphere CSI Driver (https://github.com/kubernetes-sigs/vsphere-csi-driver) to move workload from the in-tree vSphere plugin \"kubernetes.io/vsphere-volume\" to vSphere CSI Driver. </ins> <del> ## Changes by Kind </del> <ins> Requires: vSphere vCenter/ESXi Version: 7.0u1, HW Version: VM version 15 ([#92816](https://github.com/kubernetes/kubernetes/pull/92816), [@divyenpatel](https://github.com/divyenpatel)) [SIG Cloud Provider and Storage] - Support [service.beta.kubernetes.io/azure-pip-ip-tags] annotations to allow customers to specify ip-tags to influence public-ip creation in Azure [Tag1=Value1, Tag2=Value2, etc.] ([#94114](https://github.com/kubernetes/kubernetes/pull/94114), [@MarcPow](https://github.com/MarcPow)) [SIG Cloud Provider] - Support a smooth upgrade from client-side apply to server-side apply without conflicts, as well as support the corresponding downgrade. ([#90187](https://github.com/kubernetes/kubernetes/pull/90187), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG API Machinery and Testing] - Trace output in apiserver logs is more organized and comprehensive. Traces are nested, and for all non-long running request endpoints, the entire filter chain is instrumented (e.g. authentication check is included). ([#88936](https://github.com/kubernetes/kubernetes/pull/88936), [@jpbetz](https://github.com/jpbetz)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation and Scheduling] - `kubectl alpha debug` now supports debugging nodes by creating a debugging container running in the node's host namespaces. ([#92310](https://github.com/kubernetes/kubernetes/pull/92310), [@verb](https://github.com/verb)) [SIG CLI] </ins> <del> ### API Change </del> <ins> ### Documentation </ins> <del> - Kube-proxy: add `--bind-address-hard-fail` flag to treat failure to bind to a port as fatal ([#89350](https://github.com/kubernetes/kubernetes/pull/89350), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle and Network] - Remove kubescheduler.config.k8s.io/v1alpha1 ([#89298](https://github.com/kubernetes/kubernetes/pull/89298), [@gavinfish](https://github.com/gavinfish)) [SIG Scheduling] - ServiceAppProtocol feature gate is now beta and enabled by default, adding new AppProtocol field to Services and Endpoints. ([#90023](https://github.com/kubernetes/kubernetes/pull/90023), [@robscott](https://github.com/robscott)) [SIG Apps and Network] - The Kubelet's `--volume-plugin-dir` option is now available via the Kubelet config file field `VolumePluginDir`. ([#88480](https://github.com/kubernetes/kubernetes/pull/88480), [@savitharaghunathan](https://github.com/savitharaghunathan)) [SIG Node] </del> <ins> - Kubelet: remove alpha warnings for CNI flags. ([#94508](https://github.com/kubernetes/kubernetes/pull/94508), [@andrewsykim](https://github.com/andrewsykim)) [SIG Network and Node] </ins> <del> ### Feature </del> <ins> ### Failing Test </ins> <del> - Add client-side and server-side dry-run support to kubectl scale ([#89666](https://github.com/kubernetes/kubernetes/pull/89666), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG CLI and Testing] - Add support for cgroups v2 node validation ([#89901](https://github.com/kubernetes/kubernetes/pull/89901), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle and Node] - Detailed scheduler scoring result can be printed at verbose level 10. ([#89384](https://github.com/kubernetes/kubernetes/pull/89384), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling] - E2e.test can print the list of conformance tests that need to pass for the cluster to be conformant. ([#88924](https://github.com/kubernetes/kubernetes/pull/88924), [@dims](https://github.com/dims)) [SIG Architecture and Testing] - Feat: add azure shared disk support ([#89511](https://github.com/kubernetes/kubernetes/pull/89511), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Kube-apiserver backed by etcd3 exports metric showing the database file size. ([#89151](https://github.com/kubernetes/kubernetes/pull/89151), [@jingyih](https://github.com/jingyih)) [SIG API Machinery] - Kube-apiserver: The NodeRestriction admission plugin now restricts Node labels kubelets are permitted to set when creating a new Node to the `--node-labels` parameters accepted by kubelets in 1.16+. ([#90307](https://github.com/kubernetes/kubernetes/pull/90307), [@liggitt](https://github.com/liggitt)) [SIG Auth and Node] - Kubeadm: during 'upgrade apply', if the kube-proxy ConfigMap is missing, assume that kube-proxy should not be upgraded. Same applies to a missing kube-dns/coredns ConfigMap for the DNS server addon. Note that this is a temporary workaround until 'upgrade apply' supports phases. Once phases are supported the kube-proxy/dns upgrade should be skipped manually. ([#89593](https://github.com/kubernetes/kubernetes/pull/89593), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: switch control-plane static Pods to the \"system-node-critical\" priority class ([#90063](https://github.com/kubernetes/kubernetes/pull/90063), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Support for running on a host that uses cgroups v2 unified mode ([#85218](https://github.com/kubernetes/kubernetes/pull/85218), [@giuseppe](https://github.com/giuseppe)) [SIG Node] - Update etcd client side to v3.4.7 ([#89822](https://github.com/kubernetes/kubernetes/pull/89822), [@jingyih](https://github.com/jingyih)) [SIG API Machinery and Cloud Provider] </del> <ins> - Kube-proxy iptables min-sync-period defaults to 1 sec. Previously, it was 0. ([#92836](https://github.com/kubernetes/kubernetes/pull/92836), [@aojea](https://github.com/aojea)) [SIG Network] </ins> ### Bug or Regression <del> - An issue preventing GCP cloud-controller-manager running out-of-cluster to initialize new Nodes is now fixed. ([#90057](https://github.com/kubernetes/kubernetes/pull/90057), [@ialidzhikov](https://github.com/ialidzhikov)) [SIG Apps and Cloud Provider] - Avoid unnecessary GCE API calls when adding IP alises or reflecting them in Node object in GCE cloud provider. ([#90242](https://github.com/kubernetes/kubernetes/pull/90242), [@wojtek-t](https://github.com/wojtek-t)) [SIG Apps, Cloud Provider and Network] - Azure: fix concurreny issue in lb creation ([#89604](https://github.com/kubernetes/kubernetes/pull/89604), [@aramase](https://github.com/aramase)) [SIG Cloud Provider] - Bug fix for AWS NLB service when nodePort for existing servicePort changed manually. ([#89562](https://github.com/kubernetes/kubernetes/pull/89562), [@M00nF1sh](https://github.com/M00nF1sh)) [SIG Cloud Provider] - CSINode initialization does not crash kubelet on startup when APIServer is not reachable or kubelet has not the right credentials yet. ([#89589](https://github.com/kubernetes/kubernetes/pull/89589), [@jsafrane](https://github.com/jsafrane)) [SIG Storage] - Client-go: resolves an issue with informers falling back to full list requests when timeouts are encountered, rather than re-establishing a watch. ([#89652](https://github.com/kubernetes/kubernetes/pull/89652), [@liggitt](https://github.com/liggitt)) [SIG API Machinery and Testing] - Dual-stack: fix the bug that Service clusterIP does not respect specified ipFamily ([#89612](https://github.com/kubernetes/kubernetes/pull/89612), [@SataQiu](https://github.com/SataQiu)) [SIG Network] - Ensure Azure availability zone is always in lower cases. ([#89722](https://github.com/kubernetes/kubernetes/pull/89722), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Explain CRDs whose resource name are the same as builtin objects ([#89505](https://github.com/kubernetes/kubernetes/pull/89505), [@knight42](https://github.com/knight42)) [SIG API Machinery, CLI and Testing] - Fix flaws in Azure File CSI translation ([#90162](https://github.com/kubernetes/kubernetes/pull/90162), [@rfranzke](https://github.com/rfranzke)) [SIG Release and Storage] - Fix kubectl describe CSINode nil pointer error ([#89646](https://github.com/kubernetes/kubernetes/pull/89646), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - Fix kubectl diff so it doesn't actually persist patches ([#89795](https://github.com/kubernetes/kubernetes/pull/89795), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG CLI and Testing] - Fix kubectl version should print version info without config file ([#89913](https://github.com/kubernetes/kubernetes/pull/89913), [@zhouya0](https://github.com/zhouya0)) [SIG API Machinery and CLI] - Fix missing `-c` shorthand for `--container` flag of `kubectl alpha debug` ([#89674](https://github.com/kubernetes/kubernetes/pull/89674), [@superbrothers](https://github.com/superbrothers)) [SIG CLI] - Fix printers ignoring object average value ([#89142](https://github.com/kubernetes/kubernetes/pull/89142), [@zhouya0](https://github.com/zhouya0)) [SIG API Machinery] - Fix scheduler crash when removing node before its pods ([#89908](https://github.com/kubernetes/kubernetes/pull/89908), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - Fix: get attach disk error due to missing item in max count table ([#89768](https://github.com/kubernetes/kubernetes/pull/89768), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Fixed a bug where executing a kubectl command with a jsonpath output expression that has a nested range would ignore expressions following the nested range. ([#88464](https://github.com/kubernetes/kubernetes/pull/88464), [@brianpursley](https://github.com/brianpursley)) [SIG API Machinery] - Fixed a regression running kubectl commands with  --local or --dry-run flags when no kubeconfig file is present ([#90243](https://github.com/kubernetes/kubernetes/pull/90243), [@soltysh](https://github.com/soltysh)) [SIG API Machinery, CLI and Testing] - Fixed an issue mounting credentials for service accounts whose name contains `.` characters ([#89696](https://github.com/kubernetes/kubernetes/pull/89696), [@nabokihms](https://github.com/nabokihms)) [SIG Auth] - Fixed mountOptions in iSCSI and FibreChannel volume plugins. ([#89172](https://github.com/kubernetes/kubernetes/pull/89172), [@jsafrane](https://github.com/jsafrane)) [SIG Storage] - Fixed the EndpointSlice controller to run without error on a cluster with the OwnerReferencesPermissionEnforcement validating admission plugin enabled. ([#89741](https://github.com/kubernetes/kubernetes/pull/89741), [@marun](https://github.com/marun)) [SIG Auth and Network] - Fixes a bug defining a default value for a replicas field in a custom resource definition that has the scale subresource enabled ([#89833](https://github.com/kubernetes/kubernetes/pull/89833), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle and Instrumentation] - Fixes conversion error for HorizontalPodAutoscaler objects with invalid annotations ([#89963](https://github.com/kubernetes/kubernetes/pull/89963), [@liggitt](https://github.com/liggitt)) [SIG Autoscaling] - Fixes kubectl to apply all validly built objects, instead of stopping on error. ([#89848](https://github.com/kubernetes/kubernetes/pull/89848), [@seans3](https://github.com/seans3)) [SIG CLI and Testing] - For GCE cluster provider, fix bug of not being able to create internal type load balancer for clusters with more than 1000 nodes in a single zone. ([#89902](https://github.com/kubernetes/kubernetes/pull/89902), [@wojtek-t](https://github.com/wojtek-t)) [SIG Cloud Provider, Network and Scalability] - If firstTimestamp is not set use eventTime when printing event ([#89999](https://github.com/kubernetes/kubernetes/pull/89999), [@soltysh](https://github.com/soltysh)) [SIG CLI] - If we set parameter cgroupPerQos=false and cgroupRoot=/docker，this function will retrun  nodeAllocatableRoot=/docker/kubepods, it is not right, the correct return should be /docker. cm.NodeAllocatableRoot(s.CgroupRoot, s.CgroupDriver) kubeDeps.CAdvisorInterface, err = cadvisor.New(imageFsInfoProvider, s.RootDirectory, cgroupRoots, cadvisor.UsingLegacyCadvisorStats(s.ContainerRuntime, s.RemoteRuntimeEndpoint)) the above funtion，as we use cgroupRoots to create cadvisor interface，the wrong parameter cgroupRoots will lead eviction manager not  to collect metric from /docker, then kubelet frequently print those error： E0303 17:25:03.436781 63839 summary_sys_containers.go:47] Failed to get system container stats for \"/docker\": failed to get cgroup stats for \"/docker\": failed to get container info for \"/docker\": unknown container \"/docker\" E0303 17:25:03.436809 63839 helpers.go:680] eviction manager: failed to construct signal: \"allocatableMemory.available\" error: system container \"pods\" not found in metrics ([#88970](https://github.com/kubernetes/kubernetes/pull/88970), [@mysunshine92](https://github.com/mysunshine92)) [SIG Node] - In the kubelet resource metrics endpoint at /metrics/resource, change the names of the following metrics: - node_cpu_usage_seconds --> node_cpu_usage_seconds_total - container_cpu_usage_seconds --> container_cpu_usage_seconds_total This is a partial revert of &#35;86282, which was added in 1.18.0, and initially removed the _total suffix ([#89540](https://github.com/kubernetes/kubernetes/pull/89540), [@dashpole](https://github.com/dashpole)) [SIG Instrumentation and Node] - Kube-apiserver: multiple comma-separated protocols in a single X-Stream-Protocol-Version header are now recognized, in addition to multiple headers, complying with RFC2616 ([#89857](https://github.com/kubernetes/kubernetes/pull/89857), [@tedyu](https://github.com/tedyu)) [SIG API Machinery] - Kubeadm increased to 5 minutes its timeout for the TLS bootstrapping process to complete upon join ([#89735](https://github.com/kubernetes/kubernetes/pull/89735), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - Kubeadm: during join when a check is performed that a Node with the same name already exists in the cluster, make sure the NodeReady condition is properly validated ([#89602](https://github.com/kubernetes/kubernetes/pull/89602), [@kvaps](https://github.com/kvaps)) [SIG Cluster Lifecycle] - Kubeadm: fix a bug where post upgrade to 1.18.x, nodes cannot join the cluster due to missing RBAC ([#89537](https://github.com/kubernetes/kubernetes/pull/89537), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: fix misleading warning about passing control-plane related flags on 'kubeadm join' ([#89596](https://github.com/kubernetes/kubernetes/pull/89596), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubectl azure authentication: fixed a regression in 1.18.0 where \"spn:\" prefix was unexpectedly added to the `apiserver-id` configuration in the kubeconfig file ([#89706](https://github.com/kubernetes/kubernetes/pull/89706), [@weinong](https://github.com/weinong)) [SIG API Machinery and Auth] - Restore the ability to `kubectl apply --prune` without --namespace flag.  Since 1.17, `kubectl apply --prune` only prunes resources in the default namespace (or from kubeconfig) or explicitly specified in command line flag.  But this is s breaking change from kubectl 1.16, which can prune resources in all namespace in config file.  This patch restores the kubectl 1.16 behaviour. ([#89551](https://github.com/kubernetes/kubernetes/pull/89551), [@tatsuhiro-t](https://github.com/tatsuhiro-t)) [SIG CLI and Testing] - Restores priority of static control plane pods in the cluster/gce/manifests control-plane manifests ([#89970](https://github.com/kubernetes/kubernetes/pull/89970), [@liggitt](https://github.com/liggitt)) [SIG Cluster Lifecycle and Node] - Service account tokens bound to pods can now be used during the pod deletion grace period. ([#89583](https://github.com/kubernetes/kubernetes/pull/89583), [@liggitt](https://github.com/liggitt)) [SIG Auth] - Sync LB backend nodes for Service Type=LoadBalancer on Add/Delete node events. ([#81185](https://github.com/kubernetes/kubernetes/pull/81185), [@andrewsykim](https://github.com/andrewsykim)) [SIG Apps and Network] ### Other (Cleanup or Flake) - Change beta.kubernetes.io/os  to kubernetes.io/os ([#89460](https://github.com/kubernetes/kubernetes/pull/89460), [@wawa0210](https://github.com/wawa0210)) [SIG Testing and Windows] - Changes not found message when using `kubectl get` to retrieve not namespaced resources ([#89861](https://github.com/kubernetes/kubernetes/pull/89861), [@rccrdpccl](https://github.com/rccrdpccl)) [SIG CLI] - Node ([#76443](https://github.com/kubernetes/kubernetes/pull/76443), [@mgdevstack](https://github.com/mgdevstack)) [SIG Architecture, Network, Node, Testing and Windows] - None. ([#90273](https://github.com/kubernetes/kubernetes/pull/90273), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - Reduce event spam during a volume operation error. ([#89794](https://github.com/kubernetes/kubernetes/pull/89794), [@msau42](https://github.com/msau42)) [SIG Storage] - The PR adds functionality to generate events when a PV or PVC processing encounters certain failures. The events help users to know the reason for the failure so they can take necessary recovery actions. ([#89845](https://github.com/kubernetes/kubernetes/pull/89845), [@yuga711](https://github.com/yuga711)) [SIG Apps] - The PodShareProcessNamespace feature gate has been removed, and the PodShareProcessNamespace is unconditionally enabled. ([#90099](https://github.com/kubernetes/kubernetes/pull/90099), [@tanjunchen](https://github.com/tanjunchen)) [SIG Node] - Update default etcd server version to 3.4.4 ([#89214](https://github.com/kubernetes/kubernetes/pull/89214), [@jingyih](https://github.com/jingyih)) [SIG API Machinery, Cluster Lifecycle and Testing] - Update default etcd server version to 3.4.7 ([#89895](https://github.com/kubernetes/kubernetes/pull/89895), [@jingyih](https://github.com/jingyih)) [SIG API Machinery, Cluster Lifecycle and Testing] # v1.19.0-alpha.1 [Documentation](https://docs.k8s.io) ## Downloads for v1.19.0-alpha.1 filename | sha512 hash -------- | ----------- [kubernetes.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes.tar.gz) | `d5930e62f98948e3ae2bc0a91b2cb93c2009202657b9e798e43fcbf92149f50d991af34a49049b2640db729efc635d643d008f4b3dd6c093cac4426ee3d5d147` [kubernetes-src.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-src.tar.gz) | `5d92125ec3ca26b6b0af95c6bb3289bb7cf60a4bad4e120ccdad06ffa523c239ca8e608015b7b5a1eb789bfdfcedbe0281518793da82a7959081fb04cf53c174` ### Client Binaries filename | sha512 hash -------- | ----------- [kubernetes-client-darwin-386.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-client-darwin-386.tar.gz) | `08d307dafdd8e1aa27721f97f038210b33261d1777ea173cc9ed4b373c451801988a7109566425fce32d38df70bdf0be6b8cfff69da768fbd3c303abd6dc13a5` [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-client-darwin-amd64.tar.gz) | `08c3b722a62577d051e300ebc3c413ead1bd3e79555598a207c704064116087323215fb402bae7584b9ffd08590f36fa8a35f13f8fea1ce92e8f144e3eae3384` [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-client-linux-386.tar.gz) | `0735978b4d4cb0601171eae3cc5603393c00f032998f51d79d3b11e4020f4decc9559905e9b02ddcb0b6c3f4caf78f779940ebc97996e3b96b98ba378fbe189d` [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-client-linux-amd64.tar.gz) | `ca55fc431d59c1a0bf1f1c248da7eab65215e438fcac223d4fc3a57fae0205869e1727b2475dfe9b165921417d68ac380a6e42bf7ea6732a34937ba2590931ce` [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-client-linux-arm.tar.gz) | `4e1aa9e640d7cf0ccaad19377e4c3ca9a60203daa2ce0437d1d40fdea0e43759ef38797e948cdc3c676836b01e83f1bfde51effc0579bf832f6f062518f03f06` [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-client-linux-arm64.tar.gz) | `fca5df8c2919a9b3d99248120af627d9a1b5ddf177d9a10f04eb4e486c14d4e3ddb72e3abc4733b5078e0d27204a51e2f714424923fb92a5351137f82d87d6ea` [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-client-linux-ppc64le.tar.gz) | `6a98a4f99aa8b72ec815397c5062b90d5c023092da28fa7bca1cdadf406e2d86e2fd3a0eeab28574064959c6926007423c413d9781461e433705452087430d57` [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-client-linux-s390x.tar.gz) | `94724c17985ae2dbd3888e6896f300f95fec8dc2bf08e768849e98b05affc4381b322d802f41792b8e6da4708ce1ead2edcb8f4d5299be6267f6559b0d49e484` [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-client-windows-386.tar.gz) | `5a076bf3a5926939c170a501f8292a38003552848c45c1f148a97605b7ac9843fb660ef81a46abe6d139f4c5eaa342d4b834a799ee7055d5a548d189b31d7124` [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-client-windows-amd64.tar.gz) | `4b395894bfd9cfa0976512d1d58c0056a80bacefc798de294db6d3f363bd5581fd3ce2e4bdc1b902d46c8ce2ac87a98ced56b6b29544c86e8444fb8e9465faea` ### Server Binaries filename | sha512 hash -------- | ----------- [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-server-linux-amd64.tar.gz) | `6720d1b826dc20e56b0314e580403cd967430ff25bdbe08e8bf453fed339557d2a4ace114c2f524e6b6814ec9341ccdea870f784ebb53a52056ca3ab22e5cc36` [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-server-linux-arm.tar.gz) | `f09b295f5a95cc72494eb1c0e9706b237a8523eacda182778e9afdb469704c7eacd29614aff6d3d7aff3bc1783fb277d52ad56a1417f1bd973eeb9bdc8086695` [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-server-linux-arm64.tar.gz) | `24787767abd1d67a4d0234433e1693ea3e1e906364265ee03e58ba203b66583b75d4ce0c4185756fc529997eb9a842d65841962cd228df9c182a469dbd72493d` [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-server-linux-ppc64le.tar.gz) | `a117e609729263d7bd58aac156efa33941f0f9aa651892d1abf32cfa0a984aa495fccd3be8385cae083415bfa8f81942648d5978f72e950103e42184fd0d7527` [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-server-linux-s390x.tar.gz) | `19280a6dc20f019d23344934f8f1ec6aa17c3374b9c569d4c173535a8cd9e298b8afcabe06d232a146c9c7cb4bfe7d1d0e10aa2ab9184ace0b7987e36973aaef` ### Node Binaries filename | sha512 hash -------- | ----------- [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-node-linux-amd64.tar.gz) | `c4b23f113ed13edb91b59a498d15de8b62ff1005243f2d6654a11468511c9d0ebaebb6dc02d2fa505f18df446c9221e77d7fc3147fa6704cde9bec5d6d80b5a3` [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-node-linux-arm.tar.gz) | `8dcf5531a5809576049c455d3c5194f09ddf3b87995df1e8ca4543deff3ffd90a572539daff9aa887e22efafedfcada2e28035da8573e3733c21778e4440677a` [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-node-linux-arm64.tar.gz) | `4b3f4dfee2034ce7d01fef57b8766851fe141fc72da0f9edeb39aca4c7a937e2dccd2c198a83fbb92db7911d81e50a98bd0a17b909645adbeb26e420197db2cd` [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-node-linux-ppc64le.tar.gz) | `df0e87f5e42056db2bbc7ef5f08ecda95d66afc3f4d0bc57f6efcc05834118c39ab53d68595d8f2bb278829e33b9204c5cce718d8bf841ce6cccbb86d0d20730` [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-node-linux-s390x.tar.gz) | `3a6499b008a68da52f8ae12eb694885d9e10a8f805d98f28fc5f7beafea72a8e180df48b5ca31097b2d4779c61ff67216e516c14c2c812163e678518d95f22d6` [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-alpha.1/kubernetes-node-windows-amd64.tar.gz) | `c311373506cbfa0244ac92a709fbb9bddb46cbeb130733bdb689641ecee6b21a7a7f020eae4856a3f04a3845839dc5e0914cddc3478d55cd3d5af3d7804aa5ba` ## Changelog since v1.19.0-alpha.0 ## Urgent Upgrade Notes </del> <ins> - A panic in the apiserver caused by the `informer-sync` health checker is now fixed. ([#93600](https://github.com/kubernetes/kubernetes/pull/93600), [@ialidzhikov](https://github.com/ialidzhikov)) [SIG API Machinery] - Add kubectl wait  --ignore-not-found flag ([#90969](https://github.com/kubernetes/kubernetes/pull/90969), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - Adding fix to the statefulset controller to wait for pvc deletion before creating pods. ([#93457](https://github.com/kubernetes/kubernetes/pull/93457), [@ymmt2005](https://github.com/ymmt2005)) [SIG Apps] - Azure ARM client: don't segfault on empty response and http error ([#94078](https://github.com/kubernetes/kubernetes/pull/94078), [@bpineau](https://github.com/bpineau)) [SIG Cloud Provider] - Azure: fix a bug that kube-controller-manager would panic if wrong Azure VMSS name is configured ([#94306](https://github.com/kubernetes/kubernetes/pull/94306), [@knight42](https://github.com/knight42)) [SIG Cloud Provider] - Azure: per VMSS VMSS VMs cache to prevent throttling on clusters having many attached VMSS ([#93107](https://github.com/kubernetes/kubernetes/pull/93107), [@bpineau](https://github.com/bpineau)) [SIG Cloud Provider] - Both apiserver_request_duration_seconds metrics and RequestReceivedTimestamp field of an audit event take into account the time a request spends in the apiserver request filters. ([#94903](https://github.com/kubernetes/kubernetes/pull/94903), [@tkashem](https://github.com/tkashem)) [SIG API Machinery, Auth and Instrumentation] - Build/lib/release: Explicitly use '--platform' in building server images </ins> <del> ### (No, really, you MUST read this before you upgrade) </del> <ins> When we switched to go-runner for building the apiserver, controller-manager, and scheduler server components, we no longer reference the individual architectures in the image names, specifically in the 'FROM' directive of the server image Dockerfiles. </ins> <del> - The StreamingProxyRedirects feature and `--redirect-container-streaming` flag are deprecated, and will be removed in a future release. The default behavior (proxy streaming requests through the kubelet) will be the only supported option. If you are setting `--redirect-container-streaming=true`, then you must migrate off this configuration. The flag will no longer be able to be enabled starting in v1.20. If you are not setting the flag, no action is necessary. ([#88290](https://github.com/kubernetes/kubernetes/pull/88290), [@tallclair](https://github.com/tallclair)) [SIG API Machinery and Node] </del> <ins> As a result, server images for non-amd64 images copy in the go-runner amd64 binary instead of the go-runner that matches that architecture. </ins> <del> - `kubectl` no longer defaults to `http://localhost:8080`.  If you own one of these legacy clusters, you are *strongly- encouraged to secure your server.   If you cannot secure your server, you can set `KUBERNETES_MASTER` if you were relying on that behavior and you're client-go user. Set `--server`, `--kubeconfig` or `KUBECONFIG` to make it work in `kubectl`. ([#86173](https://github.com/kubernetes/kubernetes/pull/86173), [@soltysh](https://github.com/soltysh)) [SIG API Machinery, CLI and Testing] </del> <ins> This commit explicitly sets the '--platform=linux/${arch}' to ensure we're pulling the correct go-runner arch from the manifest list. </ins> <del> ## Changes by Kind </del> <ins> Before: `FROM ${base_image}` </ins> <del> ### Deprecation </del> <ins> After: `FROM --platform=linux/${arch} ${base_image}` ([#94552](https://github.com/kubernetes/kubernetes/pull/94552), [@justaugustus](https://github.com/justaugustus)) [SIG Release] - CSIDriver object can be deployed during volume attachment. ([#93710](https://github.com/kubernetes/kubernetes/pull/93710), [@Jiawei0227](https://github.com/Jiawei0227)) [SIG Apps, Node, Storage and Testing] - CVE-2020-8557 (Medium): Node-local denial of service via container /etc/hosts file. See https://github.com/kubernetes/kubernetes/issues/93032 for more details. ([#92916](https://github.com/kubernetes/kubernetes/pull/92916), [@joelsmith](https://github.com/joelsmith)) [SIG Node] - Do not add nodes labeled with kubernetes.azure.com/managed=false to backend pool of load balancer. ([#93034](https://github.com/kubernetes/kubernetes/pull/93034), [@matthias50](https://github.com/matthias50)) [SIG Cloud Provider] - Do not fail sorting empty elements. ([#94666](https://github.com/kubernetes/kubernetes/pull/94666), [@soltysh](https://github.com/soltysh)) [SIG CLI] - Do not retry volume expansion if CSI driver returns FailedPrecondition error ([#92986](https://github.com/kubernetes/kubernetes/pull/92986), [@gnufied](https://github.com/gnufied)) [SIG Node and Storage] - Dockershim security: pod sandbox now always run with `no-new-privileges` and `runtime/default` seccomp profile dockershim seccomp: custom profiles can now have smaller seccomp profiles when set at pod level ([#90948](https://github.com/kubernetes/kubernetes/pull/90948), [@pjbgf](https://github.com/pjbgf)) [SIG Node] - Dual-stack: make nodeipam compatible with existing single-stack clusters when dual-stack feature gate become enabled by default ([#90439](https://github.com/kubernetes/kubernetes/pull/90439), [@SataQiu](https://github.com/SataQiu)) [SIG API Machinery] - Endpoint controller requeues service after an endpoint deletion event occurs to confirm that deleted endpoints are undesired to mitigate the effects of an out of sync endpoint cache. ([#93030](https://github.com/kubernetes/kubernetes/pull/93030), [@swetharepakula](https://github.com/swetharepakula)) [SIG Apps and Network] - EndpointSlice controllers now return immediately if they encounter an error creating, updating, or deleting resources. ([#93908](https://github.com/kubernetes/kubernetes/pull/93908), [@robscott](https://github.com/robscott)) [SIG Apps and Network] - EndpointSliceMirroring controller now copies labels from Endpoints to EndpointSlices. ([#93442](https://github.com/kubernetes/kubernetes/pull/93442), [@robscott](https://github.com/robscott)) [SIG Apps and Network] - EndpointSliceMirroring controller now mirrors Endpoints that do not have a Service associated with them. ([#94171](https://github.com/kubernetes/kubernetes/pull/94171), [@robscott](https://github.com/robscott)) [SIG Apps, Network and Testing] - Ensure backoff step is set to 1 for Azure armclient. ([#94180](https://github.com/kubernetes/kubernetes/pull/94180), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Ensure getPrimaryInterfaceID not panic when network interfaces for Azure VMSS are null ([#94355](https://github.com/kubernetes/kubernetes/pull/94355), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Eviction requests for pods that have a non-zero DeletionTimestamp will always succeed ([#91342](https://github.com/kubernetes/kubernetes/pull/91342), [@michaelgugino](https://github.com/michaelgugino)) [SIG Apps] - Extended DSR loadbalancer feature in winkernel kube-proxy to HNS versions 9.3-9.max, 10.2+ ([#93080](https://github.com/kubernetes/kubernetes/pull/93080), [@elweb9858](https://github.com/elweb9858)) [SIG Network] - Fix HandleCrash order ([#93108](https://github.com/kubernetes/kubernetes/pull/93108), [@lixiaobing1](https://github.com/lixiaobing1)) [SIG API Machinery] - Fix a concurrent map writes error in kubelet ([#93773](https://github.com/kubernetes/kubernetes/pull/93773), [@knight42](https://github.com/knight42)) [SIG Node] - Fix a regression where kubeadm bails out with a fatal error when an optional version command line argument is supplied to the \"kubeadm upgrade plan\" command ([#94421](https://github.com/kubernetes/kubernetes/pull/94421), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - Fix azure file migration panic ([#94853](https://github.com/kubernetes/kubernetes/pull/94853), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix bug where loadbalancer deletion gets stuck because of missing resource group &#35;75198 ([#93962](https://github.com/kubernetes/kubernetes/pull/93962), [@phiphi282](https://github.com/phiphi282)) [SIG Cloud Provider] - Fix calling AttachDisk on a previously attached EBS volume ([#93567](https://github.com/kubernetes/kubernetes/pull/93567), [@gnufied](https://github.com/gnufied)) [SIG Cloud Provider, Storage and Testing] - Fix detection of image filesystem, disk metrics for devicemapper, detection of OOM Kills on 5.0+ linux kernels. ([#92919](https://github.com/kubernetes/kubernetes/pull/92919), [@dashpole](https://github.com/dashpole)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation and Node] - Fix etcd_object_counts metric reported by kube-apiserver ([#94773](https://github.com/kubernetes/kubernetes/pull/94773), [@tkashem](https://github.com/tkashem)) [SIG API Machinery] - Fix incorrectly reported verbs for kube-apiserver metrics for CRD objects ([#93523](https://github.com/kubernetes/kubernetes/pull/93523), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery and Instrumentation] - Fix instance not found issues when an Azure Node is recreated in a short time ([#93316](https://github.com/kubernetes/kubernetes/pull/93316), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Fix kube-apiserver /readyz to contain \"informer-sync\" check ensuring that internal informers are synced. ([#93670](https://github.com/kubernetes/kubernetes/pull/93670), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery and Testing] - Fix kubectl SchemaError on CRDs with schema using x-kubernetes-preserve-unknown-fields on array types. ([#94888](https://github.com/kubernetes/kubernetes/pull/94888), [@sttts](https://github.com/sttts)) [SIG API Machinery] - Fix memory leak in EndpointSliceTracker for EndpointSliceMirroring controller. ([#93441](https://github.com/kubernetes/kubernetes/pull/93441), [@robscott](https://github.com/robscott)) [SIG Apps and Network] - Fix missing csi annotations on node during parallel csinode update. ([#94389](https://github.com/kubernetes/kubernetes/pull/94389), [@pacoxu](https://github.com/pacoxu)) [SIG Storage] - Fix the `cloudprovider_azure_api_request_duration_seconds` metric buckets to correctly capture the latency metrics. Previously, the majority of the calls would fall in the \"+Inf\" bucket. ([#94873](https://github.com/kubernetes/kubernetes/pull/94873), [@marwanad](https://github.com/marwanad)) [SIG Cloud Provider and Instrumentation] - Fix: azure disk resize error if source does not exist ([#93011](https://github.com/kubernetes/kubernetes/pull/93011), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix: detach azure disk broken on Azure Stack ([#94885](https://github.com/kubernetes/kubernetes/pull/94885), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix: determine the correct ip config based on ip family ([#93043](https://github.com/kubernetes/kubernetes/pull/93043), [@aramase](https://github.com/aramase)) [SIG Cloud Provider] - Fix: initial delay in mounting azure disk & file ([#93052](https://github.com/kubernetes/kubernetes/pull/93052), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Fix: use sensitiveOptions on Windows mount ([#94126](https://github.com/kubernetes/kubernetes/pull/94126), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Fixed Ceph RBD volume expansion when no ceph.conf exists ([#92027](https://github.com/kubernetes/kubernetes/pull/92027), [@juliantaylor](https://github.com/juliantaylor)) [SIG Storage] - Fixed a bug where improper storage and comparison of endpoints led to excessive API traffic from the endpoints controller ([#94112](https://github.com/kubernetes/kubernetes/pull/94112), [@damemi](https://github.com/damemi)) [SIG Apps, Network and Testing] - Fixed a bug whereby the allocation of reusable CPUs and devices was not being honored when the TopologyManager was enabled ([#93189](https://github.com/kubernetes/kubernetes/pull/93189), [@klueska](https://github.com/klueska)) [SIG Node] - Fixed a panic in kubectl debug when pod has multiple init containers or ephemeral containers ([#94580](https://github.com/kubernetes/kubernetes/pull/94580), [@kiyoshim55](https://github.com/kiyoshim55)) [SIG CLI] - Fixed a regression that sometimes prevented `kubectl portforward` to work when TCP and UDP services were configured on the same port ([#94728](https://github.com/kubernetes/kubernetes/pull/94728), [@amorenoz](https://github.com/amorenoz)) [SIG CLI] - Fixed bug in reflector that couldn't recover from \"Too large resource version\" errors with API servers 1.17.0-1.18.5 ([#94316](https://github.com/kubernetes/kubernetes/pull/94316), [@janeczku](https://github.com/janeczku)) [SIG API Machinery] - Fixed bug where kubectl top pod output is not sorted when --sort-by and --containers flags are used together ([#93692](https://github.com/kubernetes/kubernetes/pull/93692), [@brianpursley](https://github.com/brianpursley)) [SIG CLI] - Fixed kubelet creating extra sandbox for pods with RestartPolicyOnFailure after all containers succeeded ([#92614](https://github.com/kubernetes/kubernetes/pull/92614), [@tnqn](https://github.com/tnqn)) [SIG Node and Testing] - Fixed memory leak in endpointSliceTracker ([#92838](https://github.com/kubernetes/kubernetes/pull/92838), [@tnqn](https://github.com/tnqn)) [SIG Apps and Network] - Fixed node data lost in kube-scheduler for clusters with imbalance on number of nodes across zones ([#93355](https://github.com/kubernetes/kubernetes/pull/93355), [@maelk](https://github.com/maelk)) [SIG Scheduling] - Fixed the EndpointSliceController to correctly create endpoints for IPv6-only pods. </ins> <del> - AlgorithmSource is removed from v1alpha2 Scheduler ComponentConfig ([#87999](https://github.com/kubernetes/kubernetes/pull/87999), [@damemi](https://github.com/damemi)) [SIG Scheduling] - Azure service annotation service.beta.kubernetes.io/azure-load-balancer-disable-tcp-reset has been deprecated. Its support would be removed in a future release. ([#88462](https://github.com/kubernetes/kubernetes/pull/88462), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Kube-proxy: deprecate `--healthz-port` and `--metrics-port` flag, please use `--healthz-bind-address` and `--metrics-bind-address` instead ([#88512](https://github.com/kubernetes/kubernetes/pull/88512), [@SataQiu](https://github.com/SataQiu)) [SIG Network] - Kubeadm: deprecate the usage of the experimental flag '--use-api' under the 'kubeadm alpha certs renew' command. ([#88827](https://github.com/kubernetes/kubernetes/pull/88827), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubernetes no longer supports building hyperkube images ([#88676](https://github.com/kubernetes/kubernetes/pull/88676), [@dims](https://github.com/dims)) [SIG Cluster Lifecycle and Release] </del> <ins> Fixed the EndpointController to allow IPv6 headless services, if the IPv6DualStack feature gate is enabled, by specifying `ipFamily: IPv6` on the service. (This already worked with the EndpointSliceController.) ([#91399](https://github.com/kubernetes/kubernetes/pull/91399), [@danwinship](https://github.com/danwinship)) [SIG Apps and Network] - Fixes a bug evicting pods after a taint with a limited tolerationSeconds toleration is removed from a node ([#93722](https://github.com/kubernetes/kubernetes/pull/93722), [@liggitt](https://github.com/liggitt)) [SIG Apps and Node] - Fixes a bug where EndpointSlices would not be recreated after rapid Service recreation. ([#94730](https://github.com/kubernetes/kubernetes/pull/94730), [@robscott](https://github.com/robscott)) [SIG Apps, Network and Testing] - Fixes a race condition in kubelet pod handling ([#94751](https://github.com/kubernetes/kubernetes/pull/94751), [@auxten](https://github.com/auxten)) [SIG Node] - Fixes an issue proxying to ipv6 pods without specifying a port ([#94834](https://github.com/kubernetes/kubernetes/pull/94834), [@liggitt](https://github.com/liggitt)) [SIG API Machinery and Network] - Fixes an issue that can result in namespaced custom resources being orphaned when their namespace is deleted, if the CRD defining the custom resource is removed concurrently with namespaces being deleted, then recreated. ([#93790](https://github.com/kubernetes/kubernetes/pull/93790), [@liggitt](https://github.com/liggitt)) [SIG API Machinery and Apps] - Ignore root user check when windows pod starts ([#92355](https://github.com/kubernetes/kubernetes/pull/92355), [@wawa0210](https://github.com/wawa0210)) [SIG Node and Windows] - Increased maximum IOPS of AWS EBS io1 volumes to 64,000 (current AWS maximum). ([#90014](https://github.com/kubernetes/kubernetes/pull/90014), [@jacobmarble](https://github.com/jacobmarble)) [SIG Cloud Provider and Storage] - K8s.io/apimachinery: runtime.DefaultUnstructuredConverter.FromUnstructured now handles converting integer fields to typed float values ([#93250](https://github.com/kubernetes/kubernetes/pull/93250), [@liggitt](https://github.com/liggitt)) [SIG API Machinery] - Kube-aggregator certificates are dynamically loaded on change from disk ([#92791](https://github.com/kubernetes/kubernetes/pull/92791), [@p0lyn0mial](https://github.com/p0lyn0mial)) [SIG API Machinery] - Kube-apiserver: fixed a bug returning inconsistent results from list requests which set a field or label selector and set a paging limit ([#94002](https://github.com/kubernetes/kubernetes/pull/94002), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery] - Kube-apiserver: jsonpath expressions with consecutive recursive descent operators are no longer evaluated for custom resource printer columns ([#93408](https://github.com/kubernetes/kubernetes/pull/93408), [@joelsmith](https://github.com/joelsmith)) [SIG API Machinery] - Kube-proxy now trims extra spaces found in loadBalancerSourceRanges to match Service validation. ([#94107](https://github.com/kubernetes/kubernetes/pull/94107), [@robscott](https://github.com/robscott)) [SIG Network] - Kube-up now includes CoreDNS version v1.7.0. Some of the major changes include: -  Fixed a bug that could cause CoreDNS to stop updating service records. -  Fixed a bug in the forward plugin where only the first upstream server is always selected no matter which policy is set. -  Remove already deprecated options `resyncperiod` and `upstream` in the Kubernetes plugin. -  Includes Prometheus metrics name changes (to bring them in line with standard Prometheus metrics naming convention). They will be backward incompatible with existing reporting formulas that use the old metrics' names. -  The federation plugin (allows for v1 Kubernetes federation) has been removed. More details are available in https://coredns.io/2020/06/15/coredns-1.7.0-release/ ([#92718](https://github.com/kubernetes/kubernetes/pull/92718), [@rajansandeep](https://github.com/rajansandeep)) [SIG Cloud Provider] - Kubeadm now makes sure the etcd manifest is regenerated upon upgrade even when no etcd version change takes place ([#94395](https://github.com/kubernetes/kubernetes/pull/94395), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - Kubeadm: avoid a panic when determining if the running version of CoreDNS is supported during upgrades ([#94299](https://github.com/kubernetes/kubernetes/pull/94299), [@zouyee](https://github.com/zouyee)) [SIG Cluster Lifecycle] - Kubeadm: ensure \"kubeadm reset\" does not unmount the root \"/var/lib/kubelet\" directory if it is mounted by the user ([#93702](https://github.com/kubernetes/kubernetes/pull/93702), [@thtanaka](https://github.com/thtanaka)) [SIG Cluster Lifecycle] - Kubeadm: ensure the etcd data directory is created with 0700 permissions during control-plane init and join ([#94102](https://github.com/kubernetes/kubernetes/pull/94102), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: fix the bug that kubeadm tries to call 'docker info' even if the CRI socket was for another CR ([#94555](https://github.com/kubernetes/kubernetes/pull/94555), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle] - Kubeadm: make the kubeconfig files for the kube-controller-manager and kube-scheduler use the LocalAPIEndpoint instead of the ControlPlaneEndpoint. This makes kubeadm clusters more reseliant to version skew problems during immutable upgrades: https://kubernetes.io/docs/setup/release/version-skew-policy/#kube-controller-manager-kube-scheduler-and-cloud-controller-manager ([#94398](https://github.com/kubernetes/kubernetes/pull/94398), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: relax the validation of kubeconfig server URLs. Allow the user to define custom kubeconfig server URLs without erroring out during validation of existing kubeconfig files (e.g. when using external CA mode). ([#94816](https://github.com/kubernetes/kubernetes/pull/94816), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: remove duplicate DNS names and IP addresses from generated certificates ([#92753](https://github.com/kubernetes/kubernetes/pull/92753), [@QianChenglong](https://github.com/QianChenglong)) [SIG Cluster Lifecycle] - Kubelet: assume that swap is disabled when `/proc/swaps` does not exist ([#93931](https://github.com/kubernetes/kubernetes/pull/93931), [@SataQiu](https://github.com/SataQiu)) [SIG Node] - Kubelet: fix race condition in pluginWatcher ([#93622](https://github.com/kubernetes/kubernetes/pull/93622), [@knight42](https://github.com/knight42)) [SIG Node] - Kuberuntime security: pod sandbox now always runs with `runtime/default` seccomp profile kuberuntime seccomp: custom profiles can now have smaller seccomp profiles when set at pod level ([#90949](https://github.com/kubernetes/kubernetes/pull/90949), [@pjbgf](https://github.com/pjbgf)) [SIG Node] - NONE ([#71269](https://github.com/kubernetes/kubernetes/pull/71269), [@DeliangFan](https://github.com/DeliangFan)) [SIG Node] - New Azure instance types do now have correct max data disk count information. ([#94340](https://github.com/kubernetes/kubernetes/pull/94340), [@ialidzhikov](https://github.com/ialidzhikov)) [SIG Cloud Provider and Storage] - Pods with invalid Affinity/AntiAffinity LabelSelectors will now fail scheduling when these plugins are enabled ([#93660](https://github.com/kubernetes/kubernetes/pull/93660), [@damemi](https://github.com/damemi)) [SIG Scheduling] - Require feature flag CustomCPUCFSQuotaPeriod if setting a non-default cpuCFSQuotaPeriod in kubelet config. ([#94687](https://github.com/kubernetes/kubernetes/pull/94687), [@karan](https://github.com/karan)) [SIG Node] - Reverted devicemanager for Windows node added in 1.19rc1. ([#93263](https://github.com/kubernetes/kubernetes/pull/93263), [@liggitt](https://github.com/liggitt)) [SIG Node and Windows] - Scheduler bugfix: Scheduler doesn't lose pod information when nodes are quickly recreated. This could happen when nodes are restarted or quickly recreated reusing a nodename. ([#93938](https://github.com/kubernetes/kubernetes/pull/93938), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scalability, Scheduling and Testing] - The EndpointSlice controller now waits for EndpointSlice and Node caches to be synced before starting. ([#94086](https://github.com/kubernetes/kubernetes/pull/94086), [@robscott](https://github.com/robscott)) [SIG Apps and Network] - The `/debug/api_priority_and_fairness/dump_requests` path at an apiserver will no longer return a phantom line for each exempt priority level. ([#93406](https://github.com/kubernetes/kubernetes/pull/93406), [@MikeSpreitzer](https://github.com/MikeSpreitzer)) [SIG API Machinery] - The kubelet recognizes the --containerd-namespace flag to configure the namespace used by cadvisor. ([#87054](https://github.com/kubernetes/kubernetes/pull/87054), [@changyaowei](https://github.com/changyaowei)) [SIG Node] - The terminationGracePeriodSeconds from pod spec is respected for the mirror pod. ([#92442](https://github.com/kubernetes/kubernetes/pull/92442), [@tedyu](https://github.com/tedyu)) [SIG Node and Testing] - Update Calico to v3.15.2 ([#94241](https://github.com/kubernetes/kubernetes/pull/94241), [@lmm](https://github.com/lmm)) [SIG Cloud Provider] - Update default etcd server version to 3.4.13 ([#94287](https://github.com/kubernetes/kubernetes/pull/94287), [@jingyih](https://github.com/jingyih)) [SIG API Machinery, Cloud Provider, Cluster Lifecycle and Testing] - Updated Cluster Autoscaler to 1.19.0; ([#93577](https://github.com/kubernetes/kubernetes/pull/93577), [@vivekbagade](https://github.com/vivekbagade)) [SIG Autoscaling and Cloud Provider] - Use NLB Subnet CIDRs instead of VPC CIDRs in Health Check SG Rules ([#93515](https://github.com/kubernetes/kubernetes/pull/93515), [@t0rr3sp3dr0](https://github.com/t0rr3sp3dr0)) [SIG Cloud Provider] - Users will see increase in time for deletion of pods and also guarantee that removal of pod from api server  would mean deletion of all the resources from container runtime. ([#92817](https://github.com/kubernetes/kubernetes/pull/92817), [@kmala](https://github.com/kmala)) [SIG Node] - Very large patches may now be specified to `kubectl patch` with the `--patch-file` flag instead of including them directly on the command line. The `--patch` and `--patch-file` flags are mutually exclusive. ([#93548](https://github.com/kubernetes/kubernetes/pull/93548), [@smarterclayton](https://github.com/smarterclayton)) [SIG CLI] - When creating a networking.k8s.io/v1 Ingress API object, `spec.rules[*].http` values are now validated consistently when the `host` field contains a wildcard. ([#93954](https://github.com/kubernetes/kubernetes/pull/93954), [@Miciah](https://github.com/Miciah)) [SIG CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Network, Storage and Testing] </ins> <del> ### API Change </del> <ins> ### Other (Cleanup or Flake) </ins> <del> - A new IngressClass resource has been added to enable better Ingress configuration. ([#88509](https://github.com/kubernetes/kubernetes/pull/88509), [@robscott](https://github.com/robscott)) [SIG API Machinery, Apps, CLI, Network, Node and Testing] - API additions to apiserver types ([#87179](https://github.com/kubernetes/kubernetes/pull/87179), [@Jefftree](https://github.com/Jefftree)) [SIG API Machinery, Cloud Provider and Cluster Lifecycle] - Add Scheduling Profiles to kubescheduler.config.k8s.io/v1alpha2 ([#88087](https://github.com/kubernetes/kubernetes/pull/88087), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling and Testing] - Added GenericPVCDataSource feature gate to enable using arbitrary custom resources as the data source for a PVC. ([#88636](https://github.com/kubernetes/kubernetes/pull/88636), [@bswartz](https://github.com/bswartz)) [SIG Apps and Storage] - Added support for multiple sizes huge pages on a container level ([#84051](https://github.com/kubernetes/kubernetes/pull/84051), [@bart0sh](https://github.com/bart0sh)) [SIG Apps, Node and Storage] - Allow user to specify fsgroup permission change policy for pods ([#88488](https://github.com/kubernetes/kubernetes/pull/88488), [@gnufied](https://github.com/gnufied)) [SIG Apps and Storage] - AppProtocol is a new field on Service and Endpoints resources, enabled with the ServiceAppProtocol feature gate. ([#88503](https://github.com/kubernetes/kubernetes/pull/88503), [@robscott](https://github.com/robscott)) [SIG Apps and Network] - BlockVolume and CSIBlockVolume features are now GA. ([#88673](https://github.com/kubernetes/kubernetes/pull/88673), [@jsafrane](https://github.com/jsafrane)) [SIG Apps, Node and Storage] - Consumers of the 'certificatesigningrequests/approval' API must now grant permission to 'approve' CSRs for the 'signerName' specified on the CSR. More information on the new signerName field can be found at https://github.com/kubernetes/enhancements/blob/master/keps/sig-auth/20190607-certificates-api.md&#35;signers ([#88246](https://github.com/kubernetes/kubernetes/pull/88246), [@munnerz](https://github.com/munnerz)) [SIG API Machinery, Apps, Auth, CLI, Node and Testing] - CustomResourceDefinition schemas that use `x-kubernetes-list-map-keys` to specify properties that uniquely identify list items must make those properties required or have a default value, to ensure those properties are present for all list items. See https://kubernetes.io/docs/reference/using-api/api-concepts/&#35;merge-strategy for details. ([#88076](https://github.com/kubernetes/kubernetes/pull/88076), [@eloyekunle](https://github.com/eloyekunle)) [SIG API Machinery and Testing] - Fixed missing validation of uniqueness of list items in lists with `x-kubernetes-list-type: map` or x-kubernetes-list-type: set` in CustomResources. ([#84920](https://github.com/kubernetes/kubernetes/pull/84920), [@sttts](https://github.com/sttts)) [SIG API Machinery] - Fixes a regression with clients prior to 1.15 not being able to update podIP in pod status, or podCIDR in node spec, against >= 1.16 API servers ([#88505](https://github.com/kubernetes/kubernetes/pull/88505), [@liggitt](https://github.com/liggitt)) [SIG Apps and Network] - Ingress: Add Exact and Prefix maching to Ingress PathTypes ([#88587](https://github.com/kubernetes/kubernetes/pull/88587), [@cmluciano](https://github.com/cmluciano)) [SIG Apps, Cluster Lifecycle and Network] - Ingress: Add alternate backends via TypedLocalObjectReference ([#88775](https://github.com/kubernetes/kubernetes/pull/88775), [@cmluciano](https://github.com/cmluciano)) [SIG Apps and Network] - Ingress: allow wildcard hosts in IngressRule ([#88858](https://github.com/kubernetes/kubernetes/pull/88858), [@cmluciano](https://github.com/cmluciano)) [SIG Network] - Introduces optional --detect-local flag to kube-proxy. Currently the only supported value is \"cluster-cidr\", which is the default if not specified. ([#87748](https://github.com/kubernetes/kubernetes/pull/87748), [@satyasm](https://github.com/satyasm)) [SIG Cluster Lifecycle, Network and Scheduling] - Kube-controller-manager and kube-scheduler expose profiling by default to match the kube-apiserver.  Use `--enable-profiling=false` to disable. ([#88663](https://github.com/kubernetes/kubernetes/pull/88663), [@deads2k](https://github.com/deads2k)) [SIG API Machinery, Cloud Provider and Scheduling] - Kube-scheduler can run more than one scheduling profile. Given a pod, the profile is selected by using its `.spec.SchedulerName`. ([#88285](https://github.com/kubernetes/kubernetes/pull/88285), [@alculquicondor](https://github.com/alculquicondor)) [SIG Apps, Scheduling and Testing] - Move TaintBasedEvictions feature gates to GA ([#87487](https://github.com/kubernetes/kubernetes/pull/87487), [@skilxn-go](https://github.com/skilxn-go)) [SIG API Machinery, Apps, Node, Scheduling and Testing] - Moving Windows RunAsUserName feature to GA ([#87790](https://github.com/kubernetes/kubernetes/pull/87790), [@marosset](https://github.com/marosset)) [SIG Apps and Windows] - New flag --endpointslice-updates-batch-period in kube-controller-manager can be used to reduce number of endpointslice updates generated by pod changes. ([#88745](https://github.com/kubernetes/kubernetes/pull/88745), [@mborsz](https://github.com/mborsz)) [SIG API Machinery, Apps and Network] - New flag `--show-hidden-metrics-for-version` in kubelet can be used to show all hidden metrics that deprecated in the previous minor release. ([#85282](https://github.com/kubernetes/kubernetes/pull/85282), [@serathius](https://github.com/serathius)) [SIG Node] - Removes ConfigMap as suggestion for IngressClass parameters ([#89093](https://github.com/kubernetes/kubernetes/pull/89093), [@robscott](https://github.com/robscott)) [SIG Network] - Scheduler Extenders can now be configured in the v1alpha2 component config ([#88768](https://github.com/kubernetes/kubernetes/pull/88768), [@damemi](https://github.com/damemi)) [SIG Release, Scheduling and Testing] - The apiserver/v1alph1&#35;EgressSelectorConfiguration API is now beta. ([#88502](https://github.com/kubernetes/kubernetes/pull/88502), [@caesarxuchao](https://github.com/caesarxuchao)) [SIG API Machinery] - The storage.k8s.io/CSIDriver has moved to GA, and is now available for use. ([#84814](https://github.com/kubernetes/kubernetes/pull/84814), [@huffmanca](https://github.com/huffmanca)) [SIG API Machinery, Apps, Auth, Node, Scheduling, Storage and Testing] - VolumePVCDataSource moves to GA in 1.18 release ([#88686](https://github.com/kubernetes/kubernetes/pull/88686), [@j-griffith](https://github.com/j-griffith)) [SIG Apps, CLI and Cluster Lifecycle] </del> <ins> - --cache-dir sets cache directory for both http and discovery, defaults to $HOME/.kube/cache ([#92910](https://github.com/kubernetes/kubernetes/pull/92910), [@soltysh](https://github.com/soltysh)) [SIG API Machinery and CLI] - Adds a bootstrapping ClusterRole, ClusterRoleBinding and group for /metrics, /livez/*, /readyz/*, & /healthz/- endpoints. ([#93311](https://github.com/kubernetes/kubernetes/pull/93311), [@logicalhan](https://github.com/logicalhan)) [SIG API Machinery, Auth, Cloud Provider and Instrumentation] - Base-images: Update to debian-iptables:buster-v1.3.0 - Uses iptables 1.8.5 - base-images: Update to debian-base:buster-v1.2.0 - cluster/images/etcd: Build etcd:3.4.13-1 image - Uses debian-base:buster-v1.2.0 ([#94733](https://github.com/kubernetes/kubernetes/pull/94733), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery, Release and Testing] - Build: Update to debian-base@v2.1.2 and debian-iptables@v12.1.1 ([#93667](https://github.com/kubernetes/kubernetes/pull/93667), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery, Release and Testing] - Build: Update to debian-base@v2.1.3 and debian-iptables@v12.1.2 ([#93916](https://github.com/kubernetes/kubernetes/pull/93916), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery, Release and Testing] - Build: Update to go-runner:buster-v2.0.0 ([#94167](https://github.com/kubernetes/kubernetes/pull/94167), [@justaugustus](https://github.com/justaugustus)) [SIG Release] - Fix kubelet to properly log when a container is started. Before, sometimes the log said that a container is dead and was restarted when it was started for the first time. This only happened when using pods with initContainers and regular containers. ([#91469](https://github.com/kubernetes/kubernetes/pull/91469), [@rata](https://github.com/rata)) [SIG Node] - Fix: license issue in blob disk feature ([#92824](https://github.com/kubernetes/kubernetes/pull/92824), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fixes the flooding warning messages about setting volume ownership for configmap/secret volumes ([#92878](https://github.com/kubernetes/kubernetes/pull/92878), [@jvanz](https://github.com/jvanz)) [SIG Instrumentation, Node and Storage] - Fixes the message about no auth for metrics in scheduler. ([#94035](https://github.com/kubernetes/kubernetes/pull/94035), [@zhouya0](https://github.com/zhouya0)) [SIG Scheduling] - Kube-up: defaults to limiting critical pods to the kube-system namespace to match behavior prior to 1.17 ([#93121](https://github.com/kubernetes/kubernetes/pull/93121), [@liggitt](https://github.com/liggitt)) [SIG Cloud Provider and Scheduling] - Kubeadm: Separate argument key/value in log msg ([#94016](https://github.com/kubernetes/kubernetes/pull/94016), [@mrueg](https://github.com/mrueg)) [SIG Cluster Lifecycle] - Kubeadm: remove support for the \"ci/k8s-master\" version label. This label has been removed in the Kubernetes CI release process and would no longer work in kubeadm. You can use the \"ci/latest\" version label instead. See kubernetes/test-infra&#35;18517 ([#93626](https://github.com/kubernetes/kubernetes/pull/93626), [@vikkyomkar](https://github.com/vikkyomkar)) [SIG Cluster Lifecycle] - Kubeadm: remove the CoreDNS check for known image digests when applying the addon ([#94506](https://github.com/kubernetes/kubernetes/pull/94506), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubernetes is now built with go1.15.0 ([#93939](https://github.com/kubernetes/kubernetes/pull/93939), [@justaugustus](https://github.com/justaugustus)) [SIG Release and Testing] - Kubernetes is now built with go1.15.0-rc.2 ([#93827](https://github.com/kubernetes/kubernetes/pull/93827), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Node, Release and Testing] - Lock ExternalPolicyForExternalIP to default, this feature gate will be removed in 1.22. ([#94581](https://github.com/kubernetes/kubernetes/pull/94581), [@knabben](https://github.com/knabben)) [SIG Network] - Service.beta.kubernetes.io/azure-load-balancer-disable-tcp-reset is removed.  All Standard load balancers will always enable tcp resets. ([#94297](https://github.com/kubernetes/kubernetes/pull/94297), [@MarcPow](https://github.com/MarcPow)) [SIG Cloud Provider] - Stop propagating SelfLink (deprecated in 1.16) in kube-apiserver ([#94397](https://github.com/kubernetes/kubernetes/pull/94397), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery and Testing] - Strip unnecessary security contexts on Windows ([#93475](https://github.com/kubernetes/kubernetes/pull/93475), [@ravisantoshgudimetla](https://github.com/ravisantoshgudimetla)) [SIG Node, Testing and Windows] - To ensure the code be strong,  add unit test for GetAddressAndDialer ([#93180](https://github.com/kubernetes/kubernetes/pull/93180), [@FreeZhang61](https://github.com/FreeZhang61)) [SIG Node] - Update CNI plugins to v0.8.7 ([#94367](https://github.com/kubernetes/kubernetes/pull/94367), [@justaugustus](https://github.com/justaugustus)) [SIG Cloud Provider, Network, Node, Release and Testing] - Update Golang to v1.14.5 - Update repo-infra to 0.0.7 (to support go1.14.5 and go1.13.13) - Includes: - bazelbuild/bazel-toolchains@3.3.2 - bazelbuild/rules_go@v0.22.7 ([#93088](https://github.com/kubernetes/kubernetes/pull/93088), [@justaugustus](https://github.com/justaugustus)) [SIG Release and Testing] - Update Golang to v1.14.6 - Update repo-infra to 0.0.8 (to support go1.14.6 and go1.13.14) - Includes: - bazelbuild/bazel-toolchains@3.4.0 - bazelbuild/rules_go@v0.22.8 ([#93198](https://github.com/kubernetes/kubernetes/pull/93198), [@justaugustus](https://github.com/justaugustus)) [SIG Release and Testing] - Update cri-tools to [v1.19.0](https://github.com/kubernetes-sigs/cri-tools/releases/tag/v1.19.0) ([#94307](https://github.com/kubernetes/kubernetes/pull/94307), [@xmudrii](https://github.com/xmudrii)) [SIG Cloud Provider] - Update default etcd server version to 3.4.9 ([#92349](https://github.com/kubernetes/kubernetes/pull/92349), [@jingyih](https://github.com/jingyih)) [SIG API Machinery, Cloud Provider, Cluster Lifecycle and Testing] - Update etcd client side to v3.4.13 ([#94259](https://github.com/kubernetes/kubernetes/pull/94259), [@jingyih](https://github.com/jingyih)) [SIG API Machinery and Cloud Provider] - `kubectl get ingress` now prefers the `networking.k8s.io/v1` over `extensions/v1beta1` (deprecated since v1.14). To explicitly request the deprecated version, use `kubectl get ingress.v1beta1.extensions`. ([#94309](https://github.com/kubernetes/kubernetes/pull/94309), [@liggitt](https://github.com/liggitt)) [SIG API Machinery and CLI] </ins> <del> ### Feature </del> <ins> ## Dependencies </ins> <del> - deps: Update to Golang 1.13.9 - build: Remove kube-cross image building ([#89275](https://github.com/kubernetes/kubernetes/pull/89275), [@justaugustus](https://github.com/justaugustus)) [SIG Release and Testing] - Add --dry-run to kubectl delete, taint, replace ([#88292](https://github.com/kubernetes/kubernetes/pull/88292), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG CLI and Testing] - Add `rest_client_rate_limiter_duration_seconds` metric to component-base to track client side rate limiter latency in seconds. Broken down by verb and URL. ([#88134](https://github.com/kubernetes/kubernetes/pull/88134), [@jennybuckley](https://github.com/jennybuckley)) [SIG API Machinery, Cluster Lifecycle and Instrumentation] - Add huge page stats to Allocated resources in \"kubectl describe node\" ([#80605](https://github.com/kubernetes/kubernetes/pull/80605), [@odinuge](https://github.com/odinuge)) [SIG CLI] - Add support for pre allocated huge pages with different sizes, on node level ([#89252](https://github.com/kubernetes/kubernetes/pull/89252), [@odinuge](https://github.com/odinuge)) [SIG Apps and Node] - Adds support for NodeCIDR as an argument to --detect-local-mode ([#88935](https://github.com/kubernetes/kubernetes/pull/88935), [@satyasm](https://github.com/satyasm)) [SIG Network] - Allow user to specify resource using --filename flag when invoking kubectl exec ([#88460](https://github.com/kubernetes/kubernetes/pull/88460), [@soltysh](https://github.com/soltysh)) [SIG CLI and Testing] - Apiserver add a new flag --goaway-chance which is the fraction of requests that will be closed gracefully(GOAWAY) to prevent HTTP/2 clients from getting stuck on a single apiserver. After the connection closed(received GOAWAY), the client's other in-flight requests won't be affected, and the client will reconnect. The flag min value is 0 (off), max is .02 (1/50 requests); .001 (1/1000) is a recommended starting point. Clusters with single apiservers, or which don't use a load balancer, should NOT enable this. ([#88567](https://github.com/kubernetes/kubernetes/pull/88567), [@answer1991](https://github.com/answer1991)) [SIG API Machinery] - Azure Cloud Provider now supports using Azure network resources (Virtual Network, Load Balancer, Public IP, Route Table, Network Security Group, etc.) in different AAD Tenant and Subscription than those for the Kubernetes cluster. To use the feature, please reference https://github.com/kubernetes-sigs/cloud-provider-azure/blob/master/docs/cloud-provider-config.md&#35;host-network-resources-in-different-aad-tenant-and-subscription. ([#88384](https://github.com/kubernetes/kubernetes/pull/88384), [@bowen5](https://github.com/bowen5)) [SIG Cloud Provider] - Azure: add support for single stack IPv6 ([#88448](https://github.com/kubernetes/kubernetes/pull/88448), [@aramase](https://github.com/aramase)) [SIG Cloud Provider] - DefaultConstraints can be specified for the PodTopologySpread plugin in the component config ([#88671](https://github.com/kubernetes/kubernetes/pull/88671), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - EndpointSlice controller waits longer to retry failed sync. ([#89438](https://github.com/kubernetes/kubernetes/pull/89438), [@robscott](https://github.com/robscott)) [SIG Apps and Network] - Feat: change azure disk api-version ([#89250](https://github.com/kubernetes/kubernetes/pull/89250), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Feat: support [Azure shared disk](https://docs.microsoft.com/en-us/azure/virtual-machines/windows/disks-shared-enable), added a new field(`maxShares`) in azure disk storage class: kind: StorageClass apiVersion: storage.k8s.io/v1 metadata: name: shared-disk provisioner: kubernetes.io/azure-disk parameters: skuname: Premium_LRS  &#35; Currently only available with premium SSDs. cachingMode: None  &#35; ReadOnly host caching is not available for premium SSDs with maxShares>1 maxShares: 2 ([#89328](https://github.com/kubernetes/kubernetes/pull/89328), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Kube-apiserver, kube-scheduler and kube-controller manager now use SO_REUSEPORT socket option when listening on address defined by --bind-address and --secure-port flags, when running on Unix systems (Windows is NOT supported). This allows to run multiple instances of those processes on a single host with the same configuration, which allows to update/restart them in a graceful way, without causing downtime. ([#88893](https://github.com/kubernetes/kubernetes/pull/88893), [@invidian](https://github.com/invidian)) [SIG API Machinery, Scheduling and Testing] - Kubeadm: The ClusterStatus struct present in the kubeadm-config ConfigMap is deprecated and will be removed on a future version. It is going to be maintained by kubeadm until it gets removed. The same information can be found on `etcd` and `kube-apiserver` pod annotations, `kubeadm.kubernetes.io/etcd.advertise-client-urls` and `kubeadm.kubernetes.io/kube-apiserver.advertise-address.endpoint` respectively. ([#87656](https://github.com/kubernetes/kubernetes/pull/87656), [@ereslibre](https://github.com/ereslibre)) [SIG Cluster Lifecycle] - Kubeadm: add the experimental feature gate PublicKeysECDSA that can be used to create a cluster with ECDSA certificates from \"kubeadm init\". Renewal of existing ECDSA certificates is also supported using \"kubeadm alpha certs renew\", but not switching between the RSA and ECDSA algorithms on the fly or during upgrades. ([#86953](https://github.com/kubernetes/kubernetes/pull/86953), [@rojkov](https://github.com/rojkov)) [SIG API Machinery, Auth and Cluster Lifecycle] - Kubeadm: on kubeconfig certificate renewal, keep the embedded CA in sync with the one on disk ([#88052](https://github.com/kubernetes/kubernetes/pull/88052), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: support Windows specific kubelet flags in kubeadm-flags.env ([#88287](https://github.com/kubernetes/kubernetes/pull/88287), [@gab-satchi](https://github.com/gab-satchi)) [SIG Cluster Lifecycle and Windows] - Kubeadm: upgrade supports fallback to the nearest known etcd version if an unknown k8s version is passed ([#88373](https://github.com/kubernetes/kubernetes/pull/88373), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle] - Kubectl cluster-info dump changed to only display a message telling you the location where the output was written when the output is not standard output. ([#88765](https://github.com/kubernetes/kubernetes/pull/88765), [@brianpursley](https://github.com/brianpursley)) [SIG CLI] - New flag `--show-hidden-metrics-for-version` in kube-scheduler can be used to show all hidden metrics that deprecated in the previous minor release. ([#84913](https://github.com/kubernetes/kubernetes/pull/84913), [@serathius](https://github.com/serathius)) [SIG Instrumentation and Scheduling] - Print NotReady when pod is not ready based on its conditions. ([#88240](https://github.com/kubernetes/kubernetes/pull/88240), [@soltysh](https://github.com/soltysh)) [SIG CLI] - Scheduler Extender API is now located under k8s.io/kube-scheduler/extender ([#88540](https://github.com/kubernetes/kubernetes/pull/88540), [@damemi](https://github.com/damemi)) [SIG Release, Scheduling and Testing] - Scheduler framework permit plugins now run at the end of the scheduling cycle, after reserve plugins. Waiting on permit will remain in the beginning of the binding cycle. ([#88199](https://github.com/kubernetes/kubernetes/pull/88199), [@mateuszlitwin](https://github.com/mateuszlitwin)) [SIG Scheduling] - Signatures on scale client methods have been modified to accept `context.Context` as a first argument. Signatures of Get, Update, and Patch methods have been updated to accept GetOptions, UpdateOptions and PatchOptions respectively. ([#88599](https://github.com/kubernetes/kubernetes/pull/88599), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG API Machinery, Apps, Autoscaling and CLI] - Signatures on the dynamic client methods have been modified to accept `context.Context` as a first argument. Signatures of Delete and DeleteCollection methods now accept DeleteOptions by value instead of by reference. ([#88906](https://github.com/kubernetes/kubernetes/pull/88906), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Apps, CLI, Cluster Lifecycle, Storage and Testing] - Signatures on the metadata client methods have been modified to accept `context.Context` as a first argument. Signatures of Delete and DeleteCollection methods now accept DeleteOptions by value instead of by reference. ([#88910](https://github.com/kubernetes/kubernetes/pull/88910), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Apps and Testing] - Support create or update VMSS asynchronously. ([#89248](https://github.com/kubernetes/kubernetes/pull/89248), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - The kubelet and the default docker runtime now support running ephemeral containers in the Linux process namespace of a target container. Other container runtimes must implement this feature before it will be available in that runtime. ([#84731](https://github.com/kubernetes/kubernetes/pull/84731), [@verb](https://github.com/verb)) [SIG Node] - Update etcd client side to v3.4.4 ([#89169](https://github.com/kubernetes/kubernetes/pull/89169), [@jingyih](https://github.com/jingyih)) [SIG API Machinery and Cloud Provider] - Upgrade to azure-sdk v40.2.0 ([#89105](https://github.com/kubernetes/kubernetes/pull/89105), [@andyzhangx](https://github.com/andyzhangx)) [SIG CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Storage and Testing] - Webhooks will have alpha support for network proxy ([#85870](https://github.com/kubernetes/kubernetes/pull/85870), [@Jefftree](https://github.com/Jefftree)) [SIG API Machinery, Auth and Testing] - When client certificate files are provided, reload files for new connections, and close connections when a certificate changes. ([#79083](https://github.com/kubernetes/kubernetes/pull/79083), [@jackkleeman](https://github.com/jackkleeman)) [SIG API Machinery, Auth, Node and Testing] - When deleting objects using kubectl with the --force flag, you are no longer required to also specify --grace-period=0. ([#87776](https://github.com/kubernetes/kubernetes/pull/87776), [@brianpursley](https://github.com/brianpursley)) [SIG CLI] - `kubectl` now contains a `kubectl alpha debug` command. This command allows attaching an ephemeral container to a running pod for the purposes of debugging. ([#88004](https://github.com/kubernetes/kubernetes/pull/88004), [@verb](https://github.com/verb)) [SIG CLI] </del> <ins> ### Added - github.com/Azure/go-autorest: [v14.2.0+incompatible](https://github.com/Azure/go-autorest/tree/v14.2.0) - github.com/fvbommel/sortorder: [v1.0.1](https://github.com/fvbommel/sortorder/tree/v1.0.1) - github.com/yuin/goldmark: [v1.1.27](https://github.com/yuin/goldmark/tree/v1.1.27) - sigs.k8s.io/structured-merge-diff/v4: v4.0.1 </ins> <del> ### Documentation </del> <ins> ### Changed - github.com/Azure/go-autorest/autorest/adal: [v0.8.2 → v0.9.0](https://github.com/Azure/go-autorest/autorest/adal/compare/v0.8.2...v0.9.0) - github.com/Azure/go-autorest/autorest/date: [v0.2.0 → v0.3.0](https://github.com/Azure/go-autorest/autorest/date/compare/v0.2.0...v0.3.0) - github.com/Azure/go-autorest/autorest/mocks: [v0.3.0 → v0.4.0](https://github.com/Azure/go-autorest/autorest/mocks/compare/v0.3.0...v0.4.0) - github.com/Azure/go-autorest/autorest: [v0.9.6 → v0.11.1](https://github.com/Azure/go-autorest/autorest/compare/v0.9.6...v0.11.1) - github.com/Azure/go-autorest/logger: [v0.1.0 → v0.2.0](https://github.com/Azure/go-autorest/logger/compare/v0.1.0...v0.2.0) - github.com/Azure/go-autorest/tracing: [v0.5.0 → v0.6.0](https://github.com/Azure/go-autorest/tracing/compare/v0.5.0...v0.6.0) - github.com/Microsoft/hcsshim: [v0.8.9 → 5eafd15](https://github.com/Microsoft/hcsshim/compare/v0.8.9...5eafd15) - github.com/cilium/ebpf: [9f1617e → 1c8d4c9](https://github.com/cilium/ebpf/compare/9f1617e...1c8d4c9) - github.com/containerd/cgroups: [bf292b2 → 0dbf7f0](https://github.com/containerd/cgroups/compare/bf292b2...0dbf7f0) - github.com/coredns/corefile-migration: [v1.0.8 → v1.0.10](https://github.com/coredns/corefile-migration/compare/v1.0.8...v1.0.10) - github.com/evanphx/json-patch: [e83c0a1 → v4.9.0+incompatible](https://github.com/evanphx/json-patch/compare/e83c0a1...v4.9.0) - github.com/google/cadvisor: [8450c56 → v0.37.0](https://github.com/google/cadvisor/compare/8450c56...v0.37.0) - github.com/json-iterator/go: [v1.1.9 → v1.1.10](https://github.com/json-iterator/go/compare/v1.1.9...v1.1.10) - github.com/opencontainers/go-digest: [v1.0.0-rc1 → v1.0.0](https://github.com/opencontainers/go-digest/compare/v1.0.0-rc1...v1.0.0) - github.com/opencontainers/runc: [1b94395 → 819fcc6](https://github.com/opencontainers/runc/compare/1b94395...819fcc6) - github.com/prometheus/client_golang: [v1.6.0 → v1.7.1](https://github.com/prometheus/client_golang/compare/v1.6.0...v1.7.1) - github.com/prometheus/common: [v0.9.1 → v0.10.0](https://github.com/prometheus/common/compare/v0.9.1...v0.10.0) - github.com/prometheus/procfs: [v0.0.11 → v0.1.3](https://github.com/prometheus/procfs/compare/v0.0.11...v0.1.3) - github.com/rubiojr/go-vhd: [0bfd3b3 → 02e2102](https://github.com/rubiojr/go-vhd/compare/0bfd3b3...02e2102) - github.com/storageos/go-api: [343b3ef → v2.2.0+incompatible](https://github.com/storageos/go-api/compare/343b3ef...v2.2.0) - github.com/urfave/cli: [v1.22.1 → v1.22.2](https://github.com/urfave/cli/compare/v1.22.1...v1.22.2) - go.etcd.io/etcd: 54ba958 → dd1b699 - golang.org/x/crypto: bac4c82 → 75b2880 - golang.org/x/mod: v0.1.0 → v0.3.0 - golang.org/x/net: d3edc99 → ab34263 - golang.org/x/tools: c00d67e → c1934b7 - k8s.io/kube-openapi: 656914f → 6aeccd4 - k8s.io/system-validators: v1.1.2 → v1.2.0 - k8s.io/utils: 6e3d28b → d5654de </ins> <del> - Improved error message for incorrect auth field. ([#82829](https://github.com/kubernetes/kubernetes/pull/82829), [@martin-schibsted](https://github.com/martin-schibsted)) [SIG Auth] - Update Japanese translation for kubectl help ([#86837](https://github.com/kubernetes/kubernetes/pull/86837), [@inductor](https://github.com/inductor)) [SIG CLI and Docs] - Updated the instructions for deploying the sample app. ([#82785](https://github.com/kubernetes/kubernetes/pull/82785), [@ashish-billore](https://github.com/ashish-billore)) [SIG API Machinery] - `kubectl plugin` now prints a note how to install krew ([#88577](https://github.com/kubernetes/kubernetes/pull/88577), [@corneliusweig](https://github.com/corneliusweig)) [SIG CLI] ### Other (Bug, Cleanup or Flake) - A PV set from in-tree source will have ordered requirement values in NodeAffinity when converted to CSIPersistentVolumeSource ([#88987](https://github.com/kubernetes/kubernetes/pull/88987), [@jiahuif](https://github.com/jiahuif)) [SIG Storage] - Add delays between goroutines for vm instance update ([#88094](https://github.com/kubernetes/kubernetes/pull/88094), [@aramase](https://github.com/aramase)) [SIG Cloud Provider] - Add init containers log to cluster dump info. ([#88324](https://github.com/kubernetes/kubernetes/pull/88324), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - Azure VMSS LoadBalancerBackendAddressPools updating has been improved with squential-sync + concurrent-async requests. ([#88699](https://github.com/kubernetes/kubernetes/pull/88699), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Azure auth module for kubectl now requests login after refresh token expires. ([#86481](https://github.com/kubernetes/kubernetes/pull/86481), [@tdihp](https://github.com/tdihp)) [SIG API Machinery and Auth] - AzureFile and CephFS use new Mount library that prevents logging of sensitive mount options. ([#88684](https://github.com/kubernetes/kubernetes/pull/88684), [@saad-ali](https://github.com/saad-ali)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation and Storage] - Beta.kubernetes.io/arch is already deprecated since v1.14, are targeted for removal in v1.18 ([#89462](https://github.com/kubernetes/kubernetes/pull/89462), [@wawa0210](https://github.com/wawa0210)) [SIG Testing] - Build: Enable kube-cross image-building on K8s Infra ([#88562](https://github.com/kubernetes/kubernetes/pull/88562), [@justaugustus](https://github.com/justaugustus)) [SIG Release and Testing] - CPU limits are now respected for Windows containers. If a node is over-provisioned, no weighting is used - only limits are respected. ([#86101](https://github.com/kubernetes/kubernetes/pull/86101), [@PatrickLang](https://github.com/PatrickLang)) [SIG Node, Testing and Windows] - Client-go certificate manager rotation gained the ability to preserve optional intermediate chains accompanying issued certificates ([#88744](https://github.com/kubernetes/kubernetes/pull/88744), [@jackkleeman](https://github.com/jackkleeman)) [SIG API Machinery and Auth] - Cloud provider config CloudProviderBackoffMode has been removed since it won't be used anymore. ([#88463](https://github.com/kubernetes/kubernetes/pull/88463), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Conformance image now depends on stretch-slim instead of debian-hyperkube-base as that image is being deprecated and removed. ([#88702](https://github.com/kubernetes/kubernetes/pull/88702), [@dims](https://github.com/dims)) [SIG Cluster Lifecycle, Release and Testing] - Deprecate --generator flag from kubectl create commands ([#88655](https://github.com/kubernetes/kubernetes/pull/88655), [@soltysh](https://github.com/soltysh)) [SIG CLI] - Deprecate kubectl top flags related to heapster Drop support of heapster in kubectl top ([#87498](https://github.com/kubernetes/kubernetes/pull/87498), [@serathius](https://github.com/serathius)) [SIG CLI] - EndpointSlice should not contain endpoints for terminating pods ([#89056](https://github.com/kubernetes/kubernetes/pull/89056), [@andrewsykim](https://github.com/andrewsykim)) [SIG Apps and Network] - Evictions due to pods breaching their ephemeral storage limits are now recorded by the `kubelet_evictions` metric and can be alerted on. ([#87906](https://github.com/kubernetes/kubernetes/pull/87906), [@smarterclayton](https://github.com/smarterclayton)) [SIG Node] - FIX: prevent apiserver from panicking when failing to load audit webhook config file ([#88879](https://github.com/kubernetes/kubernetes/pull/88879), [@JoshVanL](https://github.com/JoshVanL)) [SIG API Machinery and Auth] - Fix /readyz to return error immediately after a shutdown is initiated, before the --shutdown-delay-duration has elapsed. ([#88911](https://github.com/kubernetes/kubernetes/pull/88911), [@tkashem](https://github.com/tkashem)) [SIG API Machinery] - Fix a bug that didn't allow to use IPv6 addresses with leading zeros ([#89341](https://github.com/kubernetes/kubernetes/pull/89341), [@aojea](https://github.com/aojea)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle and Instrumentation] - Fix a bug where ExternalTrafficPolicy is not applied to service ExternalIPs. ([#88786](https://github.com/kubernetes/kubernetes/pull/88786), [@freehan](https://github.com/freehan)) [SIG Network] - Fix a bug where kubenet fails to parse the tc output. ([#83572](https://github.com/kubernetes/kubernetes/pull/83572), [@chendotjs](https://github.com/chendotjs)) [SIG Network] - Fix bug with xfs_repair from stopping xfs mount ([#89444](https://github.com/kubernetes/kubernetes/pull/89444), [@gnufied](https://github.com/gnufied)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation and Storage] - Fix describe ingress annotations not sorted. ([#88394](https://github.com/kubernetes/kubernetes/pull/88394), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - Fix detection of SystemOOMs in which the victim is a container. ([#88871](https://github.com/kubernetes/kubernetes/pull/88871), [@dashpole](https://github.com/dashpole)) [SIG Node] - Fix handling of aws-load-balancer-security-groups annotation. Security-Groups assigned with this annotation are no longer modified by kubernetes which is the expected behaviour of most users. Also no unnecessary Security-Groups are created anymore if this annotation is used. ([#83446](https://github.com/kubernetes/kubernetes/pull/83446), [@Elias481](https://github.com/Elias481)) [SIG Cloud Provider] - Fix invalid VMSS updates due to incorrect cache ([#89002](https://github.com/kubernetes/kubernetes/pull/89002), [@ArchangelSDY](https://github.com/ArchangelSDY)) [SIG Cloud Provider] - Fix isCurrentInstance for Windows by removing the dependency of hostname. ([#89138](https://github.com/kubernetes/kubernetes/pull/89138), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Fix kube-apiserver startup to wait for APIServices to be installed into the HTTP handler before reporting readiness. ([#89147](https://github.com/kubernetes/kubernetes/pull/89147), [@sttts](https://github.com/sttts)) [SIG API Machinery] - Fix kubectl create deployment image name ([#86636](https://github.com/kubernetes/kubernetes/pull/86636), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - Fix missing \"apiVersion\" for \"involvedObject\" in Events for Nodes. ([#87537](https://github.com/kubernetes/kubernetes/pull/87537), [@uthark](https://github.com/uthark)) [SIG Apps and Node] - Fix that prevents repeated fetching of PVC/PV objects by kubelet when processing of pod volumes fails. While this prevents hammering API server in these error scenarios, it means that some errors in processing volume(s) for a pod could now take up to 2-3 minutes before retry. ([#88141](https://github.com/kubernetes/kubernetes/pull/88141), [@tedyu](https://github.com/tedyu)) [SIG Node and Storage] - Fix the VMSS name and resource group name when updating Azure VMSS for LoadBalancer backendPools ([#89337](https://github.com/kubernetes/kubernetes/pull/89337), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Fix: add remediation in azure disk attach/detach ([#88444](https://github.com/kubernetes/kubernetes/pull/88444), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix: azure file mount timeout issue ([#88610](https://github.com/kubernetes/kubernetes/pull/88610), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Fix: check disk status before delete azure disk ([#88360](https://github.com/kubernetes/kubernetes/pull/88360), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix: corrupted mount point in csi driver ([#88569](https://github.com/kubernetes/kubernetes/pull/88569), [@andyzhangx](https://github.com/andyzhangx)) [SIG Storage] - Fixed a bug in the TopologyManager. Previously, the TopologyManager would only guarantee alignment if container creation was serialized in some way. Alignment is now guaranteed under all scenarios of container creation. ([#87759](https://github.com/kubernetes/kubernetes/pull/87759), [@klueska](https://github.com/klueska)) [SIG Node] - Fixed a data race in kubelet image manager that can cause static pod workers to silently stop working. ([#88915](https://github.com/kubernetes/kubernetes/pull/88915), [@roycaihw](https://github.com/roycaihw)) [SIG Node] - Fixed an issue that could cause the kubelet to incorrectly run concurrent pod reconciliation loops and crash. ([#89055](https://github.com/kubernetes/kubernetes/pull/89055), [@tedyu](https://github.com/tedyu)) [SIG Node] - Fixed block CSI volume cleanup after timeouts. ([#88660](https://github.com/kubernetes/kubernetes/pull/88660), [@jsafrane](https://github.com/jsafrane)) [SIG Node and Storage] - Fixed bug where a nonzero exit code was returned when initializing zsh completion even though zsh completion was successfully initialized ([#88165](https://github.com/kubernetes/kubernetes/pull/88165), [@brianpursley](https://github.com/brianpursley)) [SIG CLI] - Fixed cleaning of CSI raw block volumes. ([#87978](https://github.com/kubernetes/kubernetes/pull/87978), [@jsafrane](https://github.com/jsafrane)) [SIG Storage] - Fixes conversion error in multi-version custom resources that could cause metadata.generation to increment on no-op patches or updates of a custom resource. ([#88995](https://github.com/kubernetes/kubernetes/pull/88995), [@liggitt](https://github.com/liggitt)) [SIG API Machinery] - Fixes issue where you can't attach more than 15 GCE Persistent Disks to c2, n2, m1, m2 machine types. ([#88602](https://github.com/kubernetes/kubernetes/pull/88602), [@yuga711](https://github.com/yuga711)) [SIG Storage] - Fixes v1.18.0-rc.1 regression in `kubectl port-forward` when specifying a local and remote port ([#89401](https://github.com/kubernetes/kubernetes/pull/89401), [@liggitt](https://github.com/liggitt)) [SIG CLI] - For volumes that allow attaches across multiple nodes, attach and detach operations across different nodes are now executed in parallel. ([#88678](https://github.com/kubernetes/kubernetes/pull/88678), [@verult](https://github.com/verult)) [SIG Apps, Node and Storage] - Get-kube.sh uses the gcloud's current local GCP service account for auth when the provider is GCE or GKE instead of the metadata server default ([#88383](https://github.com/kubernetes/kubernetes/pull/88383), [@BenTheElder](https://github.com/BenTheElder)) [SIG Cluster Lifecycle] - Golang/x/net has been updated to bring in fixes for CVE-2020-9283 ([#88381](https://github.com/kubernetes/kubernetes/pull/88381), [@BenTheElder](https://github.com/BenTheElder)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle and Instrumentation] - Hide kubectl.kubernetes.io/last-applied-configuration in describe command ([#88758](https://github.com/kubernetes/kubernetes/pull/88758), [@soltysh](https://github.com/soltysh)) [SIG Auth and CLI] - In GKE alpha clusters it will be possible to use the service annotation `cloud.google.com/network-tier: Standard` ([#88487](https://github.com/kubernetes/kubernetes/pull/88487), [@zioproto](https://github.com/zioproto)) [SIG Cloud Provider] - Ipvs: only attempt setting of sysctlconnreuse on supported kernels ([#88541](https://github.com/kubernetes/kubernetes/pull/88541), [@cmluciano](https://github.com/cmluciano)) [SIG Network] - Kube-proxy: on dual-stack mode, if it is not able to get the IP Family of an endpoint, logs it with level InfoV(4) instead of Warning, avoiding flooding the logs for endpoints without addresses ([#88934](https://github.com/kubernetes/kubernetes/pull/88934), [@aojea](https://github.com/aojea)) [SIG Network] - Kubeadm now includes CoreDNS version 1.6.7 ([#86260](https://github.com/kubernetes/kubernetes/pull/86260), [@rajansandeep](https://github.com/rajansandeep)) [SIG Cluster Lifecycle] - Kubeadm: fix the bug that 'kubeadm upgrade' hangs in single node cluster ([#88434](https://github.com/kubernetes/kubernetes/pull/88434), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle] - Kubelet: fix the bug that kubelet help information can not show the right type of flags ([#88515](https://github.com/kubernetes/kubernetes/pull/88515), [@SataQiu](https://github.com/SataQiu)) [SIG Docs and Node] - Kubelets perform fewer unnecessary pod status update operations on the API server. ([#88591](https://github.com/kubernetes/kubernetes/pull/88591), [@smarterclayton](https://github.com/smarterclayton)) [SIG Node and Scalability] - Optimize kubectl version help info ([#88313](https://github.com/kubernetes/kubernetes/pull/88313), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - Plugin/PluginConfig and Policy APIs are mutually exclusive when running the scheduler ([#88864](https://github.com/kubernetes/kubernetes/pull/88864), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - Removes the deprecated command `kubectl rolling-update` ([#88057](https://github.com/kubernetes/kubernetes/pull/88057), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG Architecture, CLI and Testing] - Resolved a regression in v1.18.0-rc.1 mounting windows volumes ([#89319](https://github.com/kubernetes/kubernetes/pull/89319), [@mboersma](https://github.com/mboersma)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation and Storage] - Scheduler PreScore plugins are not executed if there is one filtered node or less. ([#89370](https://github.com/kubernetes/kubernetes/pull/89370), [@ahg-g](https://github.com/ahg-g)) [SIG Scheduling] - Specifying PluginConfig for the same plugin more than once fails scheduler startup. Specifying extenders and configuring .ignoredResources for the NodeResourcesFit plugin fails ([#88870](https://github.com/kubernetes/kubernetes/pull/88870), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - Support TLS Server Name overrides in kubeconfig file and via --tls-server-name in kubectl ([#88769](https://github.com/kubernetes/kubernetes/pull/88769), [@deads2k](https://github.com/deads2k)) [SIG API Machinery, Auth and CLI] - Terminating a restartPolicy=Never pod no longer has a chance to report the pod succeeded when it actually failed. ([#88440](https://github.com/kubernetes/kubernetes/pull/88440), [@smarterclayton](https://github.com/smarterclayton)) [SIG Node and Testing] - The EventRecorder from k8s.io/client-go/tools/events will now create events in the default namespace (instead of kube-system) when the related object does not have it set. ([#88815](https://github.com/kubernetes/kubernetes/pull/88815), [@enj](https://github.com/enj)) [SIG API Machinery] - The audit event sourceIPs list will now always end with the IP that sent the request directly to the API server. ([#87167](https://github.com/kubernetes/kubernetes/pull/87167), [@tallclair](https://github.com/tallclair)) [SIG API Machinery and Auth] - Update Cluster Autoscaler to 1.18.0; changelog: https://github.com/kubernetes/autoscaler/releases/tag/cluster-autoscaler-1.18.0 ([#89095](https://github.com/kubernetes/kubernetes/pull/89095), [@losipiuk](https://github.com/losipiuk)) [SIG Autoscaling and Cluster Lifecycle] - Update to use golang 1.13.8 ([#87648](https://github.com/kubernetes/kubernetes/pull/87648), [@ialidzhikov](https://github.com/ialidzhikov)) [SIG Release and Testing] - Validate kube-proxy flags --ipvs-tcp-timeout, --ipvs-tcpfin-timeout, --ipvs-udp-timeout ([#88657](https://github.com/kubernetes/kubernetes/pull/88657), [@chendotjs](https://github.com/chendotjs)) [SIG Network] - Wait for all CRDs to show up in discovery endpoint before reporting readiness. ([#89145](https://github.com/kubernetes/kubernetes/pull/89145), [@sttts](https://github.com/sttts)) [SIG API Machinery] - `kubectl config view` now redacts bearer tokens by default, similar to client certificates. The `--raw` flag can still be used to output full content. ([#88985](https://github.com/kubernetes/kubernetes/pull/88985), [@brianpursley](https://github.com/brianpursley)) [SIG API Machinery and CLI] </del> <ins> ### Removed - github.com/godbus/dbus: [ade71ed](https://github.com/godbus/dbus/tree/ade71ed) - github.com/xlab/handysort: [fb3537e](https://github.com/xlab/handysort/tree/fb3537e) - sigs.k8s.io/structured-merge-diff/v3: v3.0.0 - vbom.ml/util: db5cfe1 </ins>"}
{"_id":"q-en-website-4ca0aa72938bffbf7d44421e3048eb4422c72221dc6d1eb3ce52ef3141b2ad00","text":"アルファリリースでは、静的にプロビジョニングされたボリュームのみがサポートされます。管理者は、rawブロックデバイスを使用する場合、これらの値を考慮するように注意する必要があります。 {{< /note >}} <del> ## ボリュームのスナップショットとスナップショットからのボリュームの復元のサポート </del> <ins> ## ボリュームのスナップショットとスナップショットからのボリュームの復元のサポート {#volume-snapshot-and-restore-volume-from-snapshot-support} </ins> {{< feature-state for_k8s_version=\"v1.17\" state=\"beta\" >}}"}
{"_id":"q-en-website-4d540edb9453dd5ae0415d43652be3ad9988252d1455975866d701f4e61f8ff6","text":"```json { <del> \"auths\": { \"https://index.docker.io/v1/\": { \"username\": \"tiger\", \"password\": \"pass113\", \"email\": \"tiger@acme.com\", \"auth\": \"dGlnZXI6cGFzczExMw==\" } } </del> <ins> \"apiVersion\": \"v1\", \"data\": { \".dockerconfigjson\": \"eyJhdXRocyI6eyJteS1yZWdpc3RyeTo1MDAwIjp7InVzZXJuYW1lIjoidGlnZXIiLCJwYXNzd29yZCI6InBhc3MxMTMiLCJlbWFpbCI6InRpZ2VyQGFjbWUuY29tIiwiYXV0aCI6ImRHbG5aWEk2Y0dGemN6RXhNdz09In19fQ==\" }, \"kind\": \"Secret\", \"metadata\": { \"creationTimestamp\": \"2021-07-01T07:30:59Z\", \"name\": \"secret-tiger-docker\", \"namespace\": \"default\", \"resourceVersion\": \"566718\", \"uid\": \"e15c1d7b-9071-4100-8681-f3a7a2ce89ca\" }, \"type\": \"kubernetes.io/dockerconfigjson\" </ins> } ``` ### Basic authentication Secret"}
{"_id":"q-en-website-4dd5de1d649862dbf6fc61aa14f0f1abbe56f1da1c522866dff550303e8db0e1","text":"| Language | Client Library | Sample Programs | |----------|----------------|-----------------| <ins> | dotnet   | [github.com/kubernetes-client/csharp](https://github.com/kubernetes-client/csharp) | [browse](https://github.com/kubernetes-client/csharp/tree/master/examples/simple) </ins> | Go       | [github.com/kubernetes/client-go/](https://github.com/kubernetes/client-go/) | [browse](https://github.com/kubernetes/client-go/tree/master/examples) <del> | Python       | [github.com/kubernetes-client/python/](https://github.com/kubernetes-client/python/) | [browse](https://github.com/kubernetes-client/python/tree/master/examples) </del> <ins> | Haskell  | [github.com/kubernetes-client/haskell](https://github.com/kubernetes-client/haskell) | [browse](https://github.com/kubernetes-client/haskell/tree/master/kubernetes-client/example) </ins> | Java     | [github.com/kubernetes-client/java](https://github.com/kubernetes-client/java/) | [browse](https://github.com/kubernetes-client/java#installation) <del> | dotnet   | [github.com/kubernetes-client/csharp](https://github.com/kubernetes-client/csharp) | [browse](https://github.com/kubernetes-client/csharp/tree/master/examples/simple) </del> | JavaScript   | [github.com/kubernetes-client/javascript](https://github.com/kubernetes-client/javascript) | [browse](https://github.com/kubernetes-client/javascript/tree/master/examples) <del> | Haskell  | [github.com/kubernetes-client/haskell](https://github.com/kubernetes-client/haskell) | [browse](https://github.com/kubernetes-client/haskell/tree/master/kubernetes-client/example) </del> <ins> | Python   | [github.com/kubernetes-client/python/](https://github.com/kubernetes-client/python/) | [browse](https://github.com/kubernetes-client/python/tree/master/examples) </ins> ## Community-maintained client libraries"}
{"_id":"q-en-website-4eafb358d65c458fbd0451258dce56fe926ef577a2459a4a5183cfaf6d844281","text":"* `apiserver_flowcontrol_request_execution_seconds` is a histogram vector of how long requests took to actually execute, broken down by <del> the labels `flowSchema` (indicating which one matched the request) and `priorityLevel` (indicating the one to which the request was </del> <ins> the labels `flow_schema` (indicating which one matched the request) and `priority_level` (indicating the one to which the request was </ins> assigned). ### Debug endpoints"}
{"_id":"q-en-website-4fbe732a4717726b009e0c50a2cdce617b0516a45cda2da34e50b0064404eebe","text":"[blog_post_show_more] other = \"Show More Posts...\" <ins> [banner_acknowledgement] other = \"Hide this notice\" </ins> [caution] other = \"Caution:\""}
{"_id":"q-en-website-501028be07832af2106911f9aa9c168041272f6343c6ba05b87e40d7bce0e2d2","text":"There are a few options for tuning DNS horizontal autoscaling. Which option to use depends on different conditions. <del> ### Option 1: Scale down the dns-autoscaler deployment to 0 replicas </del> <ins> ### Option 1: Scale down the kube-dns-autoscaler deployment to 0 replicas </ins> This option works for all situations. Enter this command: ```shell <del> kubectl scale deployment --replicas=0 dns-autoscaler --namespace=kube-system </del> <ins> kubectl scale deployment --replicas=0 kube-dns-autoscaler --namespace=kube-system </ins> ``` The output is: <del> deployment.apps/dns-autoscaler scaled </del> <ins> deployment.apps/kube-dns-autoscaler scaled </ins> Verify that the replica count is zero:"}
{"_id":"q-en-website-50446d14dec6c99fea7a8e5b368d603ea0bab82a3ad15b410b22a733bb4928f1","text":"- [Slack](https://kubernetes.slack.com/messages/kubernetes-docs-ja) - [メーリングリスト](https://groups.google.com/forum/#!forum/kubernetes-sig-docs) <del> ## ドキュメントに貢献する </del> <ins> ## ドキュメントに貢献する {#contributing-to-the-docs} </ins> GitHubの画面右上にある**Fork**ボタンをクリックすると、お使いのGitHubアカウントに紐付いた本リポジトリのコピーが作成され、このコピーのことを*フォーク*と呼びます。フォークリポジトリの中ではお好きなように変更を加えていただいて構いません。加えた変更をこのリポジトリに追加したい任意のタイミングにて、フォークリポジトリからPull Reqeustを作成してください。"}
{"_id":"q-en-website-510e052d702c41cb628028e018e48e586e05f65dc553894237046c403f24b079","text":"## References <del> - [Docs for the DNS cluster addon](http://releases.k8s.io/{{page.githubbranch}}/build-tools/kube-dns/README.md) </del> <ins> - [Docs for the DNS cluster addon](http://releases.k8s.io/{{page.githubbranch}}/build/kube-dns/README.md) </ins> ## What's next - [Autoscaling the DNS Service in a Cluster](/docs/tasks/administer-cluster/dns-horizontal-autoscaling/)."}
{"_id":"q-en-website-53e4b6f7e967b97791e5ecf58ef5b78ce1dd410026f54bbed08348b52074381f","text":"### Configuring nodes to authenticate to a private registry <del> If you run Docker on your nodes, you can configure the Docker container runtime to authenticate to a private container registry. </del> <ins> Specific instructions for setting credentials depends on the container runtime and registry you chose to use. You should refer to your solution's documentation for the most accurate information. </ins> <del> This approach is suitable if you can control node configuration. {{< note >}} Default Kubernetes only supports the `auths` and `HttpHeaders` section in Docker configuration. Docker credential helpers (`credHelpers` or `credsStore`) are not supported. {{< /note >}} Docker stores keys for private registries in the `$HOME/.dockercfg` or `$HOME/.docker/config.json` file.  If you put the same file in the search paths list below, kubelet uses it as the credential provider when pulling images. * `{--root-dir:-/var/lib/kubelet}/config.json` * `{cwd of kubelet}/config.json` * `${HOME}/.docker/config.json` * `/.docker/config.json` * `{--root-dir:-/var/lib/kubelet}/.dockercfg` * `{cwd of kubelet}/.dockercfg` * `${HOME}/.dockercfg` * `/.dockercfg` {{< note >}} You may have to set `HOME=/root` explicitly in the environment of the kubelet process. {{< /note >}} Here are the recommended steps to configuring your nodes to use a private registry.  In this example, run these on your desktop/laptop: 1. Run `docker login [server]` for each set of credentials you want to use.  This updates `$HOME/.docker/config.json` on your PC. 1. View `$HOME/.docker/config.json` in an editor to ensure it contains only the credentials you want to use. 1. Get a list of your nodes; for example: - if you want the names: `nodes=$( kubectl get nodes -o jsonpath='{range.items[*].metadata}{.name} {end}' )` - if you want to get the IP addresses: `nodes=$( kubectl get nodes -o jsonpath='{range .items[*].status.addresses[?(@.type==\"ExternalIP\")]}{.address} {end}' )` 1. Copy your local `.docker/config.json` to one of the search paths list above. - for example, to test this out: `for n in $nodes; do scp ~/.docker/config.json root@\"$n\":/var/lib/kubelet/config.json; done` {{< note >}} For production clusters, use a configuration management tool so that you can apply this setting to all the nodes where you need it. {{< /note >}} Verify by creating a Pod that uses a private image; for example: ```shell kubectl apply -f - <<EOF apiVersion: v1 kind: Pod metadata: name: private-image-test-1 spec: containers: - name: uses-private-image image: $PRIVATE_IMAGE_NAME imagePullPolicy: Always command: [ \"echo\", \"SUCCESS\" ] EOF ``` ``` pod/private-image-test-1 created ``` If everything is working, then, after a few moments, you can run: ```shell kubectl logs private-image-test-1 ``` and see that the command outputs: ``` SUCCESS ``` If you suspect that the command failed, you can run: ```shell kubectl describe pods/private-image-test-1 | grep 'Failed' ``` In case of failure, the output is similar to: ``` Fri, 26 Jun 2015 15:36:13 -0700    Fri, 26 Jun 2015 15:39:13 -0700    19    {kubelet node-i2hq}    spec.containers{uses-private-image}    failed        Failed to pull image \"user/privaterepo:v1\": Error: image user/privaterepo:v1 not found ``` You must ensure all nodes in the cluster have the same `.docker/config.json`.  Otherwise, pods will run on some nodes and fail to run on others.  For example, if you use node autoscaling, then each instance template needs to include the `.docker/config.json` or mount a drive that contains it. All pods will have read access to images in any private registry once private registry keys are added to the `.docker/config.json`. </del> <ins> For an example of configuring a private container image registry, see the [Pull an Image from a Private Registry](/docs/tasks/configure-pod-container/pull-image-private-registry) task. That example uses a private registry in Docker Hub. </ins> ### Interpretation of config.json {#config-json}"}
{"_id":"q-en-website-5410a4b30fdf837ddcb85edca5baf107633b86cce771318b60a29f348c5d7437","text":"* [ドキュメントのスタイルガイド](https://kubernetes.io/docs/contribute/style/style-guide/) * [Kubernetesドキュメントの翻訳方法](https://kubernetes.io/docs/contribute/localization/) <del> ## 翻訳された`README.md`一覧 </del> <ins> ### New Contributor Ambassadors コントリビュートする時に何か助けが必要なら、[New Contributor Ambassadors](https://kubernetes.io/docs/contribute/advanced/#serve-as-a-new-contributor-ambassador)に聞いてみると良いでしょう。彼らはSIG Docsのapproverで、最初の数回のPull Requestを通して新しいコントリビューターを指導し助けることを責務としています。New Contributors Ambassadorsにコンタクトするには、[Kubernetes Slack](https://slack.k8s.io)が最適な場所です。現在のSIG DocsのNew Contributor Ambassadorは次の通りです: | 名前                       | Slack                      | GitHub                     | | -------------------------- | -------------------------- | -------------------------- | | Arsh Sharma                | @arsh                      | @RinkiyaKeDad              | ## 翻訳された`README.md`一覧 {#localization-readmemds} </ins> | Language  | Language | |---|---|"}
{"_id":"q-en-website-5419d6b2686e914176ec73d3091f68bf22c5a6e97374d464f1307aa40b3a440c","text":"<ins> --- title: Event id: event date: 2022-01-16 full_link: /docs/reference/kubernetes-api/cluster-resources/event-v1/ short_description: > A report of an event somewhere in the cluster. It generally denotes some state change in the system. aka: tags: - core-object - fundamental --- Each Event is a report of an event somewhere in the {{< glossary_tooltip text=\"cluster\" term_id=\"cluster\" >}}. It generally denotes some state change in the system. <!--more--> Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given reason reflecting a consistent underlying trigger, or the continued existence of events with that reason. Events should be treated as informative, best-effort, supplemental data. In Kubernetes, [auditing](/docs/tasks/debug-application-cluster/audit/) generates a different kind of Event record (API group `audit.k8s.io`). </ins>"}
{"_id":"q-en-website-5476819631721be2bc1ea4813369eab84c623692058dbe2cfbe0144649d48007","text":"to be pulled, then the kubelet will try to download them from both authentication sources if one of them fails. ### Pre-pulled images {{< note >}}"}
{"_id":"q-en-website-54e92d6524afedbc3b1c7b605f5b49fbda4a6c2c5395a43796e7930ed8d1a6b8","text":"The {{< api-reference page=\"workload-resources/pod-v1\" >}} object definition describes the object in detail. * [The Distributed System Toolkit: Patterns for Composite Containers](/blog/2015/06/the-distributed-system-toolkit-patterns/) explains common layouts for Pods with more than one container. <del> * Read about [Pod topology spread constraints](/docs/concepts/workloads/pods/pod-topology-spread-constraints/). </del> <ins> * Read about [Pod topology spread constraints](/docs/concepts/scheduling-eviction/topology-spread-constraints//). </ins> --> * 了解 [Pod 生命周期](/zh-cn/docs/concepts/workloads/pods/pod-lifecycle/)。 * 了解 [RuntimeClass](/zh-cn/docs/concepts/containers/runtime-class/)，以及如何使用它"}
{"_id":"q-en-website-55c3087a9cf5f44297108be430dd881195df193c445f3cfc63b7e0d74525b37a","text":"(and the default interval is 15 seconds). Once during each period, the controller manager queries the resource utilization against the <del> metrics specified in each HorizontalPodAutoscaler definition.  The controller manager obtains the metrics from either the resource metrics API (for per-pod resource metrics), </del> <ins> metrics specified in each HorizontalPodAutoscaler definition.  The controller manager finds the target resource defined by the `scaleTargetRef`, then selects the pods based on the target resource's `.spec.selector` labels, and obtains the metrics from either the resource metrics API (for per-pod resource metrics), </ins> or the custom metrics API (for all other metrics). * For per-pod resource metrics (like CPU), the controller fetches the metrics"}
{"_id":"q-en-website-5699a4f9c13dafc8e62a4ddf8d5336a48ff950d9af8fa8bb86bb3ea1712fff6f","text":"--- <del> title: Node </del> <ins> title: Nó </ins> id: node date: 2020-04-19 full_link: /docs/concepts/architecture/nodes/ short_description: > <del> Um Node é uma máquina de trabalho no Kubernetes. </del> <ins> Um Nó é uma máquina de trabalho no Kubernetes. </ins> aka: tags: - fundamental --- <del> Um Node é uma máquina de trabalho no Kubernetes. </del> <ins> Um Nó é uma máquina de trabalho no Kubernetes. </ins> <!--more--> <del> Um Node pode ser uma máquina virtual ou física, dependendo do cluster. Possui daemons ou serviços locais necessários para executar {{< glossary_tooltip text=\"Pods\" term_id=\"pod\" >}} e é gerenciado pelo {{< glossary_tooltip text=\"plano de controle\" term_id=\"control-plane\" >}}. Os daemons em um Node incluem  {{< glossary_tooltip text=\"kubelet\" term_id=\"kubelet\" >}}, {{< glossary_tooltip text=\"kube-proxy\" term_id=\"kube-proxy\" >}} e um contêiner runtime implementando o {{< glossary_tooltip text=\"CRI\" term_id=\"cri\" >}} como por exemplo o {{< glossary_tooltip term_id=\"docker\" >}}. </del>  No newline at end of file <ins> Um Nó pode ser uma máquina virtual ou física, dependendo do cluster. Possui daemons ou serviços locais necessários para executar {{< glossary_tooltip text=\"Pods\" term_id=\"pod\" >}} e é gerenciado pelo {{< glossary_tooltip text=\"ambiente de gerenciamento\" term_id=\"control-plane\" >}}. Os daemons em um Node incluem  {{< glossary_tooltip text=\"kubelet\" term_id=\"kubelet\" >}}, {{< glossary_tooltip text=\"kube-proxy\" term_id=\"kube-proxy\" >}} e um contêiner runtime implementando o {{< glossary_tooltip text=\"CRI\" term_id=\"cri\" >}} como por exemplo o {{< glossary_tooltip term_id=\"docker\" >}}. </ins>  No newline at end of file"}
{"_id":"q-en-website-56e2b6f843e32522b62d46f3c8be76a4f5efb8ad9a9f62537af6ddc2f9b38a98","text":"replace `<image-name>:<tag>` with `<image-name>@<digest>` (for example, `image@sha256:45b23dee08af5e43a7fea6c4cf9c25ccf269ee113168c19722f87876677c5cb2`). <del> When using image tags, if the image registry were to change the code that the tag on that image represents, you might end up with a mix of Pods running the old and new code. An image digest uniquely identifies a specific version of the image, so Kubernetes runs the same code every time it starts a container with that image name and digest specified. Specifying an image fixes the code that you run so that a change at the registry cannot lead to that mix of versions. </del> <ins> When using image tags, if the image registry were to change the code that the tag on that image represents, you might end up with a mix of Pods running the old and new code. An image digest uniquely identifies a specific version of the image, so Kubernetes runs the same code every time it starts a container with that image name and digest specified. Specifying an image by digest fixes the code that you run so that a change at the registry cannot lead to that mix of versions. </ins> There are third-party [admission controllers](/docs/reference/access-authn-authz/admission-controllers/) that mutate Pods (and pod templates) when they are created, so that the"}
{"_id":"q-en-website-57f46a4e46aa41f046de1205eeca488f7dd0ac9ffe95635e64c628f03ca9126a","text":"* CronJob * [Services](/ja/docs/concepts/services-networking/service/) <del> A Kubernetes Service is an abstraction which defines a logical set of Pods and a policy by which to access them - sometimes called a micro-service. You can use services for cross-operating system connectivity. In Windows, services can utilize the following types, properties and capabilities: </del> <ins> Kubernetes Serviceは、Podの論理セットとPodにアクセスするためのポリシーを定義する抽象概念です。マイクロサービスと呼ばれることもあります。オペレーティングシステム間の接続にServiceを使用できます。WindowsでのServiceは、次のタイプ、プロパティと機能を利用できます。: </ins> <del> * Service Environment variables </del> <ins> * サービス環境変数 </ins> * NodePort * ClusterIP * LoadBalancer * ExternalName * Headless services <del> Pods, Controllers and Services are critical elements to managing Windows workloads on Kubernetes. However, on their own they are not enough to enable the proper lifecycle management of Windows workloads in a dynamic cloud native environment. We added support for the following features: </del> <ins> Pod、Controller、Serviceは、KubernetesでWindowsワークロードを管理するための重要な要素です。ただし、それだけでは、動的なクラウドネイティブ環境でWindowsワークロードの適切なライフサイクル管理を可能にするのに十分ではありません。次の機能のサポートを追加しました： </ins> <del> * Pod and container metrics * Horizontal Pod Autoscaler support </del> <ins> * Podとコンテナのメトリクス * Horizontal Pod Autoscalerサポート </ins> * kubectl Exec <del> * Resource Quotas * Scheduler preemption </del> <ins> * リソースクウォータ * Schedulerのプリエンプション </ins> <del> #### Container Runtime </del> <ins> #### コンテナランタイム </ins> <del> Docker EE-basic 18.09 is required on Windows Server 2019 / 1809 nodes for Kubernetes. This works with the dockershim code included in the kubelet. Additional runtimes such as CRI-ContainerD may be supported in later Kubernetes versions. </del> <ins> KubernetesのWindows Server 2019/1809ノードでは、Docker EE-basic 18.09が必要です。これは、kubeletに含まれているdockershimコードで動作します。CRI-ContainerDなどの追加のランタイムは、Kubernetesの以降のバージョンでサポートされる可能性があります。 </ins> <del> #### Persistent Storage </del> <ins> #### 永続化ストレージ </ins> <del> Kubernetes [volumes](/docs/concepts/storage/volumes/) enable complex applications, with data persistence and Pod volume sharing requirements, to be deployed on Kubernetes. Management of persistent volumes associated with a specific storage back-end or protocol includes actions such as: provisioning/de-provisioning/resizing of volumes, attaching/detaching a volume to/from a Kubernetes node and mounting/dismounting a volume to/from individual containers in a pod that needs to persist data. The code implementing these volume management actions for a specific storage back-end or protocol is shipped in the form of a Kubernetes volume [plugin](/docs/concepts/storage/volumes/#types-of-volumes). The following broad classes of Kubernetes volume plugins are supported on Windows: </del> <ins> Kubernetes[ボリューム](/docs/concepts/storage/volumes/)を使用すると、データの永続性とPodボリュームの共有要件を備えた複雑なアプリケーションをKubernetesにデプロイできます。特定のストレージバックエンドまたはプロトコルに関連付けられた永続化ボリュームの管理には、ボリュームのプロビジョニング/プロビジョニング解除/サイズ変更、Kubernetesノードへのボリュームのアタッチ/デタッチ、およびデータを永続化する必要があるPod内の個別のコンテナへのボリュームのマウント/マウント解除などのアクションが含まれます。特定のストレージバックエンドまたはプロトコルに対してこれらのボリューム管理アクションを実装するコードは、Kubernetesボリューム[プラグイン](/docs/concepts/storage/volumes/#types-of-volumes)の形式で出荷されます。次の幅広いクラスのKubernetesボリュームプラグインがWindowsでサポートされています。: </ins> <del> ##### In-tree Volume Plugins Code associated with in-tree volume plugins ship as part of the core Kubernetes code base. Deployment of in-tree volume plugins do not require installation of additional scripts or deployment of separate containerized plugin components. These plugins can handle: provisioning/de-provisioning and resizing of volumes in the storage backend, attaching/detaching of volumes to/from a Kubernetes node and mounting/dismounting a volume to/from individual containers in a pod. The following in-tree plugins support Windows nodes: </del> <ins> ##### In-treeボリュームプラグイン In-treeボリュームプラグインに関連付けられたコードは、コアKubernetesコードベースの一部として提供されます。In-treeボリュームプラグインのデプロイでは、追加のスクリプトをインストールしたり、個別のコンテナ化されたプラグインコンポーネントをデプロイしたりする必要はありません。これらのプラグインは、ストレージバックエンドでのボリュームのプロビジョニング/プロビジョニング解除とサイズ変更、Kubernetesノードへのボリュームのアタッチ/アタッチ解除、Pod内の個々のコンテナーへのボリュームのマウント/マウント解除を処理できます。次のIn-treeプラグインは、Windowsノードをサポートしています。: </ins> * [awsElasticBlockStore](/docs/concepts/storage/volumes/#awselasticblockstore) * [azureDisk](/docs/concepts/storage/volumes/#azuredisk)"}
{"_id":"q-en-website-5984884eb04922e903a7295f93d95f268a00793140dc59ff6231c59eb5857a5e","text":"$($(CertUtil -hashfile .kubectl-convert.exe SHA256)[1] -replace \" \", \"\") -eq $(type .kubectl-convert.exe.sha256) ``` <del> 1. Append or prepend the kubectl binary folder to your `PATH` environment variable. </del> <ins> 1. Append or prepend the `kubectl-convert` binary folder to your `PATH` environment variable. </ins> 1. Verify plugin is successfully installed"}
{"_id":"q-en-website-5c9b14a22c967590409437a62aa32eb2eae196219df96d01cc668e825f8f9b75","text":"* Node: A single virtual or physical machine in a Kubernetes cluster. * Cluster: A group of nodes firewalled from the internet, that are the primary compute resources managed by Kubernetes. * Edge router: A router that enforces the firewall policy for your cluster. This could be a gateway managed by a cloudprovider or a physical piece of hardware. <del> * Cluster network: A set of links, logical or physical, that facilitate communication within a cluster according to the [Kubernetes networking model](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/admin/networking.md). Examples of a Cluster network include Overlays such as [flannel](https://github.com/coreos/flannel#flannel) or SDNs such as [OVS](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/admin/ovs-networking.md). * Service: A Kubernetes [Service](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/user-guide/services.md) that identifies a set of pods using label selectors. Unless mentioned otherwise, Services are assumed to have virtual IPs only routable within the cluster network. </del> <ins> * Cluster network: A set of links, logical or physical, that facilitate communication within a cluster according to the [Kubernetes networking model](/docs/admin/networking/). Examples of a Cluster network include Overlays such as [flannel](https://github.com/coreos/flannel#flannel) or SDNs such as [OVS](/docs/admin/ovs-networking/). * Service: A Kubernetes [Service](/docs/user-guide/services/) that identifies a set of pods using label selectors. Unless mentioned otherwise, Services are assumed to have virtual IPs only routable within the cluster network. </ins> ## What is Ingress?"}
{"_id":"q-en-website-5cbdd09874fa370cf00fad707c963f48c874231465c7444fff24cc736bc2b245","text":"<ins> <?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"no\"?> <svg viewBox=\"0 0 794.6667 1122.6667\" version=\"1.1\" id=\"svg3201\" sodipodi:docname=\"flowchart-meh.svg\" inkscape:version=\"1.2.2 (732a01da63, 2022-12-09, custom)\" xmlns:inkscape=\"http://www.inkscape.org/namespaces/inkscape\" xmlns:sodipodi=\"http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd\" xmlns=\"http://www.w3.org/2000/svg\" xmlns:svg=\"http://www.w3.org/2000/svg\"> <sodipodi:namedview id=\"namedview3203\" pagecolor=\"#ffffff\" bordercolor=\"#666666\" borderopacity=\"1.0\" inkscape:showpageshadow=\"2\" inkscape:pageopacity=\"0.0\" inkscape:pagecheckerboard=\"0\" inkscape:deskcolor=\"#d1d1d1\" showgrid=\"false\" inkscape:zoom=\"2.4563074\" inkscape:cx=\"468.58956\" inkscape:cy=\"873.87272\" inkscape:window-width=\"2234\" inkscape:window-height=\"1703\" inkscape:window-x=\"26\" inkscape:window-y=\"23\" inkscape:window-maximized=\"0\" inkscape:current-layer=\"svg3201\" /> <defs id=\"defs3005\"> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"o\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"p\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"q\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"r\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"s\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"t\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"u\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"v\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"b\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"d\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"e\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"h\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"i\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"j\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"l\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"m\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"c\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"a\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"f\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"g\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"k\" /> <clipPath clipPathUnits=\"userSpaceOnUse\" id=\"n\" /> </defs> <path style=\"fill:#326ce5;fill-opacity:1;fill-rule:nonzero;stroke:#fff;stroke-width:1.93243;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" d=\"M 294.473,196.602 351.344,139.73 294.473,82.863 237.602,139.73 Z\" transform=\"scale(1.33333)\" id=\"path3007\" /> <path style=\"fill:#326ce5;fill-opacity:1;fill-rule:nonzero;stroke:#fff;stroke-width:1.93243;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" d=\"m 304.066,704.547 52.793,-52.789 -52.793,-52.793 -52.789,52.793 z\" transform=\"scale(1.33333)\" id=\"path5645\" /> <path style=\"fill:#326ce5;fill-opacity:1;fill-rule:nonzero;stroke:#fff;stroke-width:1.93243;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" d=\"m 256.48,442.438 54.075,-54.075 -54.075,-54.078 -54.078,54.078 z\" transform=\"scale(1.33333)\" id=\"path5643\" /> <path d=\"m297.4997 77.2499-2.7844 5.8518-3.0126-5.7381z\" style=\"fill:#333;fill-opacity:1;fill-rule:nonzero;stroke:#333;stroke-width:.579728;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" clip-path=\"url(#a)\" transform=\"scale(1.33333)\" id=\"path3011\" /> <path d=\"m267.898 170.027-7.55 8.375c-7.547 8.371-22.645 25.121-30.192 39.977-7.551 14.859-7.551 27.82-7.551 39.816v50.969c0 4.992 0 9.02 2.633 16.137 2.637 7.117 7.903 17.328 10.535 22.433l2.637 5.106\" style=\"fill:none;stroke:#333;stroke-width:.966214;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3013\" /> <path d=\"m238.328 346.359.082 6.481-5.234-3.824z\" style=\"fill:#333;fill-opacity:1;fill-rule:nonzero;stroke:none\" clip-path=\"url(#b)\" transform=\"scale(1.33333)\" id=\"path3015\" /> <path d=\"m238.3283 346.3596.0814 6.48-5.2334-3.8246z\" style=\"fill:none;stroke:#333;stroke-width:.579728;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" clip-path=\"url(#c)\" transform=\"scale(1.33333)\" id=\"path3017\" /> <path d=\"m236.191 422.148-4.55 7.329c-4.551 7.324-13.649 21.98-18.2 33.25-4.55 11.273-4.55 19.164-4.55 23.109v3.945\" style=\"fill:none;stroke:#333;stroke-width:.966214;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3019\" /> <path d=\"m211.789 483.984-2.898 5.797-2.899-5.797z\" style=\"fill:#333;fill-opacity:1;fill-rule:nonzero;stroke:#333;stroke-width:.579728;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" clip-path=\"url(#d)\" transform=\"scale(1.33333)\" id=\"path3021\" /> <path d=\"M208.891 508.625v47.344\" style=\"fill:none;stroke:#333;stroke-width:.966214;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:1.44932,1.44932;stroke-dashoffset:0;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3023\" /> <path d=\"M208.891 574.809v2.011c0 2.016 0 6.039 10.671 15.34 10.672 9.297 32.012 23.867 42.684 31.156l10.668 7.286\" style=\"fill:none;stroke:#333;stroke-width:.966214;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3025\" /> <path d=\"m269.762 624.938 3.152 5.664-6.422-.875z\" style=\"fill:#333;fill-opacity:1;fill-rule:nonzero;stroke:none\" clip-path=\"url(#e)\" transform=\"scale(1.33333)\" id=\"path3027\" /> <path d=\"m269.7622 624.9374 3.1518 5.6634-6.4216-.8744z\" style=\"fill:none;stroke:#333;stroke-width:.579728;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" clip-path=\"url(#f)\" transform=\"scale(1.33333)\" id=\"path3029\" /> <path d=\"m277.254 422.148 4.469 7.329c4.468 7.324 13.406 21.98 17.875 34.82 4.468 12.844 4.468 23.875 4.468 34.906v64.254c0 9.098 0 16.266.043 21.898.039 5.637.121 9.747.161 11.797l.039 2.055\" style=\"fill:none;stroke:#333;stroke-width:.966214;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3031\" /> <path d=\"m307.0934 593.3512-2.7843 5.8559-3.0117-5.7422z\" style=\"fill:#333;fill-opacity:1;fill-rule:nonzero;stroke:#333;stroke-width:.579728;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" clip-path=\"url(#g)\" transform=\"scale(1.33333)\" id=\"path3033\" /> <path d=\"m283.652 684.133-4.168 6.379c-4.168 6.383-12.507 19.148-16.675 28.508-4.168 9.359-4.168 15.32-4.168 18.296v2.981\" style=\"fill:none;stroke:#333;stroke-width:.966214;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3035\" /> <path d=\"m261.539 734.5-2.898 5.797-2.899-5.797z\" style=\"fill:#333;fill-opacity:1;fill-rule:nonzero;stroke:#333;stroke-width:.579728;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" clip-path=\"url(#h)\" transform=\"scale(1.33333)\" id=\"path3037\" /> <path d=\"M258.641 759.137v24.156\" style=\"fill:none;stroke:#333;stroke-width:.966214;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:1.44932,1.44932;stroke-dashoffset:0;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3039\" /> <path d=\"m333.727 675.371 9.878 7.844c9.875 7.84 29.633 23.523 39.512 34.344 9.879 10.82 9.879 16.781 9.879 19.757v2.981\" style=\"fill:none;stroke:#333;stroke-width:.966214;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3041\" /> <path d=\"m395.895 734.5-2.899 5.797-2.898-5.797z\" style=\"fill:#333;fill-opacity:1;fill-rule:nonzero;stroke:#333;stroke-width:.579728;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" clip-path=\"url(#i)\" transform=\"scale(1.33333)\" id=\"path3043\" /> <path d=\"m326.656 164.898 11.84 9.231c11.836 9.226 35.512 27.687 47.352 43.398 11.836 15.711 11.836 28.672 11.836 40.668v305.262c0 9.098 0 16.266-10.364 27.098-10.367 10.832-31.097 25.332-41.461 32.586l-10.367 7.25\" style=\"fill:none;stroke:#333;stroke-width:.966214;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3045\" /> <path d=\"m341.906 629.441-6.414.95 3.09-5.7z\" style=\"fill:#333;fill-opacity:1;fill-rule:nonzero;stroke:none\" clip-path=\"url(#j)\" transform=\"scale(1.33333)\" id=\"path3047\" /> <path d=\"m341.906 629.4418-6.4133.949 3.089-5.6993z\" style=\"fill:none;stroke:#333;stroke-width:.579728;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" clip-path=\"url(#k)\" transform=\"scale(1.33333)\" id=\"path3049\" /> <path d=\"m294.715 196.844-.043 3.902c-.039 3.906-.117 11.715-.16 19.566-.039 7.852-.039 15.743-.039 19.688v3.945\" style=\"fill:none;stroke:#333;stroke-width:.966214;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3051\" clip-path=\"none\" /> <path d=\"m297.371 238.148-2.898 5.797-2.899-5.797z\" style=\"fill:#333;fill-opacity:1;fill-rule:nonzero;stroke:#333;stroke-width:.579728;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" clip-path=\"url(#l)\" transform=\"scale(1.33333)\" id=\"path3053\" /> <path id=\"path506\" clip-path=\"none\" style=\"fill:#ffffff;fill-opacity:1;fill-rule:nonzero;stroke:none\" d=\"M 198.75467 286.45709 L 198.75467 295.47759 L 198.75467 296.00054 L 246.4617 296.00054 L 246.4617 295.47759 L 246.4617 286.45709 L 198.75467 286.45709 z \" transform=\"matrix(1.3333333,0,0,1.3333333,0.546513,0.182228)\" /> <path id=\"path520\" clip-path=\"none\" style=\"fill:#ffffff;fill-opacity:1;fill-rule:nonzero;stroke:none\" d=\"M 174.00028 454.51568 L 174.00028 463.00006 L 173.65604 463.00006 L 173.65604 463.53473 L 173.65604 472.55524 L 173.65604 473.00055 L 244.1326 473.00055 L 244.1326 463.00006 L 243.9993 463.00006 L 243.9993 454.51568 L 174.00028 454.51568 z \" transform=\"matrix(1.3333333,0,0,1.3333333,0.546513,0.182228)\" /> <path id=\"path556\" clip-path=\"none\" style=\"fill:#ffffff;fill-opacity:1;fill-rule:nonzero;stroke:none\" d=\"M 265.17655 520.70251 L 265.17655 529.72301 L 265.17655 529.99987 L 283.46805 529.99987 L 283.46805 538.60143 L 283.87967 538.60143 L 283.87967 538.73913 L 324.25809 538.73913 L 324.25809 529.99987 L 342.96561 529.99987 L 342.96561 529.72301 L 342.97294 529.72301 L 342.97294 520.70251 L 342.96561 520.70251 L 265.17655 520.70251 z \" transform=\"matrix(1.3333333,0,0,1.3333333,0.546513,13.130399)\" /> <g id=\"g13394\"> <path d=\"m 357.72607,709.9639 q -1.2128,0 -1.91733,0.81021 -0.6995,0.80518 -0.6995,2.20921 0,1.44429 0.67434,2.23438 0.67937,0.78505 1.93243,0.78505 0.76995,0 1.7563,-0.27678 v 0.74982 q -0.76492,0.28684 -1.88714,0.28684 -1.62546,0 -2.51116,-0.98634 -0.88066,-0.98635 -0.88066,-2.80303 0,-1.13732 0.42272,-1.99282 0.42775,-0.85551 1.2279,-1.31848 0.80518,-0.46298 1.89217,-0.46298 1.15744,0 2.02301,0.42272 l -0.36233,0.73472 q -0.83537,-0.39252 -1.67075,-0.39252 z\" id=\"path7557\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 366.65182,713.89921 q 0,1.34868 -0.67937,2.10857 -0.67937,0.75485 -1.87708,0.75485 -0.73976,0 -1.31345,-0.34723 -0.57369,-0.34723 -0.8857,-0.99641 -0.312,-0.64917 -0.312,-1.51978 0,-1.34867 0.67433,-2.0985 0.67434,-0.75485 1.87205,-0.75485 1.15744,0 1.83681,0.76995 0.68441,0.76996 0.68441,2.0834 z m -4.20204,0 q 0,1.0568 0.42272,1.61036 0.42272,0.55356 1.243,0.55356 0.82028,0 1.243,-0.54852 0.42775,-0.55356 0.42775,-1.6154 0,-1.05176 -0.42775,-1.59526 -0.42272,-0.54853 -1.25306,-0.54853 -0.82028,0 -1.23797,0.53847 -0.41769,0.53846 -0.41769,1.60532 z\" id=\"path7559\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 371.39573,716.66199 v -3.56796 q 0,-0.67433 -0.30698,-1.00647 -0.30697,-0.33214 -0.96118,-0.33214 -0.86557,0 -1.26816,0.46801 -0.40259,0.46801 -0.40259,1.54494 v 2.89362 h -0.83537 v -5.51548 h 0.67937 l 0.13587,0.75485 h 0.0403 q 0.25665,-0.40762 0.71963,-0.62904 0.46298,-0.22646 1.03164,-0.22646 0.99641,0 1.49964,0.48311 0.50324,0.47807 0.50324,1.53487 v 3.59815 z\" id=\"path7561\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 375.13313,716.0732 q 0.22143,0 0.42775,-0.0302 0.20633,-0.0352 0.32711,-0.0705 v 0.63911 q -0.13588,0.0654 -0.40259,0.10568 -0.26169,0.0453 -0.47305,0.0453 -1.60029,0 -1.60029,-1.68584 v -3.28111 h -0.79008 v -0.40259 l 0.79008,-0.34723 0.35227,-1.17758 h 0.4831 v 1.27823 h 1.6003 v 0.64917 h -1.6003 v 3.24588 q 0,0.49821 0.23652,0.76492 0.23653,0.26672 0.64918,0.26672 z\" id=\"path7563\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 379.59832,716.66199 -0.16607,-0.78505 h -0.0403 q -0.41265,0.51833 -0.82531,0.70453 -0.40762,0.18116 -1.02157,0.18116 -0.82028,0 -1.28829,-0.42271 -0.46298,-0.42272 -0.46298,-1.20274 0,-1.67075 2.67219,-1.75127 l 0.93603,-0.0302 v -0.3422 q 0,-0.64918 -0.28182,-0.95615 -0.27678,-0.31201 -0.89073,-0.31201 -0.68943,0 -1.56003,0.42272 l -0.25665,-0.63911 q 0.40762,-0.22143 0.89073,-0.34724 0.48814,-0.12581 0.97628,-0.12581 0.98634,0 1.45938,0.43782 0.47808,0.43782 0.47808,1.40403 v 3.76422 z m -1.88714,-0.58879 q 0.78002,0 1.22286,-0.42775 0.44789,-0.42775 0.44789,-1.19771 v -0.4982 l -0.83538,0.0352 q -0.99641,0.0352 -1.43926,0.31201 -0.43781,0.27175 -0.43781,0.85047 0,0.45292 0.27174,0.68944 0.27679,0.23652 0.76996,0.23652 z\" id=\"path7565\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 382.77225,716.66199 h -0.83537 v -5.51548 h 0.83537 z m -0.90583,-7.0101 q 0,-0.28684 0.14091,-0.41769 0.14091,-0.13587 0.35226,-0.13587 0.2013,0 0.34724,0.13587 0.14594,0.13588 0.14594,0.41769 0,0.28181 -0.14594,0.42272 -0.14594,0.13587 -0.34724,0.13587 -0.21135,0 -0.35226,-0.13587 -0.14091,-0.14091 -0.14091,-0.42272 z\" id=\"path7567\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 387.99915,716.66199 v -3.56796 q 0,-0.67433 -0.30697,-1.00647 -0.30698,-0.33214 -0.96119,-0.33214 -0.86557,0 -1.26816,0.46801 -0.40259,0.46801 -0.40259,1.54494 v 2.89362 h -0.83537 v -5.51548 h 0.67937 l 0.13587,0.75485 h 0.0403 q 0.25665,-0.40762 0.71963,-0.62904 0.46298,-0.22646 1.03164,-0.22646 0.99641,0 1.49965,0.48311 0.50323,0.47807 0.50323,1.53487 v 3.59815 z\" id=\"path7569\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 392.28511,716.76263 q -1.22286,0 -1.93243,-0.74479 -0.70453,-0.74479 -0.70453,-2.0683 0,-1.33358 0.65421,-2.11863 0.65924,-0.78505 1.76636,-0.78505 1.03667,0 1.64056,0.6844 0.60388,0.67937 0.60388,1.79656 v 0.5284 h -3.79944 q 0.0252,0.97125 0.48814,1.47448 0.46801,0.50324 1.31345,0.50324 0.89073,0 1.76133,-0.37239 v 0.74479 q -0.44285,0.19123 -0.84041,0.27174 -0.39252,0.0855 -0.95112,0.0855 z m -0.22645,-5.01727 q -0.66428,0 -1.06183,0.43278 -0.39253,0.43279 -0.46298,1.19771 h 2.88355 q 0,-0.79008 -0.35227,-1.20777 -0.35226,-0.42272 -1.00647,-0.42272 z\" id=\"path7571\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 398.20157,711.04586 q 0.36736,0 0.65924,0.0604 l -0.11575,0.77498 q -0.3422,-0.0755 -0.60388,-0.0755 -0.66931,0 -1.14738,0.54349 -0.47305,0.5435 -0.47305,1.35371 v 2.95904 h -0.83537 v -5.51548 h 0.68944 l 0.0956,1.02157 h 0.0403 q 0.30697,-0.53847 0.73976,-0.83034 0.43278,-0.29188 0.95112,-0.29188 z\" id=\"path7573\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 398.65438,714.28167 v -0.76492 h 2.47089 v 0.76492 z\" id=\"path7575\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 405.11587,711.05592 q 1.087,0 1.68585,0.74479 0.60388,0.73976 0.60388,2.0985 0,1.35875 -0.60891,2.1136 -0.60389,0.74982 -1.68082,0.74982 -0.53846,0 -0.98634,-0.19626 -0.44285,-0.20129 -0.74479,-0.61395 h -0.0604 l -0.17613,0.70957 h -0.59886 v -7.83038 h 0.83538 v 1.90224 q 0,0.63911 -0.0403,1.14738 h 0.0403 q 0.58375,-0.82531 1.73113,-0.82531 z m -0.12077,0.6995 q -0.85551,0 -1.23293,0.49318 -0.37743,0.48814 -0.37743,1.65061 0,1.16248 0.38749,1.66572 0.38749,0.4982 1.243,0.4982 0.76995,0 1.14738,-0.55859 0.37743,-0.56362 0.37743,-1.61539 0,-1.07693 -0.37743,-1.60533 -0.37743,-0.5284 -1.16751,-0.5284 z\" id=\"path7577\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 411.67144,716.66199 -0.16607,-0.78505 h -0.0403 q -0.41265,0.51833 -0.82531,0.70453 -0.40762,0.18116 -1.02157,0.18116 -0.82028,0 -1.28829,-0.42271 -0.46298,-0.42272 -0.46298,-1.20274 0,-1.67075 2.67219,-1.75127 l 0.93603,-0.0302 v -0.3422 q 0,-0.64918 -0.28182,-0.95615 -0.27678,-0.31201 -0.89073,-0.31201 -0.68943,0 -1.56003,0.42272 l -0.25665,-0.63911 q 0.40762,-0.22143 0.89073,-0.34724 0.48814,-0.12581 0.97628,-0.12581 0.98634,0 1.45938,0.43782 0.47808,0.43782 0.47808,1.40403 v 3.76422 z m -1.88714,-0.58879 q 0.78002,0 1.22286,-0.42775 0.44789,-0.42775 0.44789,-1.19771 v -0.4982 l -0.83538,0.0352 q -0.99641,0.0352 -1.43926,0.31201 -0.43781,0.27175 -0.43781,0.85047 0,0.45292 0.27175,0.68944 0.27678,0.23652 0.76995,0.23652 z\" id=\"path7579\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 417.56776,715.15731 q 0,0.76995 -0.57369,1.18764 -0.57369,0.41768 -1.61036,0.41768 -1.09706,0 -1.71101,-0.34723 v -0.77498 q 0.39756,0.20129 0.85048,0.31704 0.45794,0.11574 0.88066,0.11574 0.65421,0 1.00648,-0.20633 0.35226,-0.21136 0.35226,-0.63911 0,-0.32207 -0.28181,-0.54853 -0.27678,-0.23149 -1.08699,-0.54349 -0.76996,-0.28685 -1.09706,-0.49821 -0.32207,-0.21639 -0.48311,-0.48814 -0.156,-0.27175 -0.156,-0.64918 0,-0.67433 0.54853,-1.06183 0.54852,-0.39252 1.50468,-0.39252 0.89073,0 1.7412,0.36233 l -0.29691,0.67937 q -0.83034,-0.3422 -1.50468,-0.3422 -0.59382,0 -0.89577,0.1862 -0.30194,0.18619 -0.30194,0.5133 0,0.22142 0.11071,0.37743 0.11575,0.156 0.36737,0.29691 0.25162,0.1409 0.96621,0.40762 0.98132,0.3573 1.32352,0.71963 0.34723,0.36233 0.34723,0.91086 z\" id=\"path7581\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 421.49303,716.76263 q -1.22287,0 -1.93243,-0.74479 -0.70453,-0.74479 -0.70453,-2.0683 0,-1.33358 0.65421,-2.11863 0.65924,-0.78505 1.76636,-0.78505 1.03667,0 1.64055,0.6844 0.60389,0.67937 0.60389,1.79656 v 0.5284 h -3.79945 q 0.0252,0.97125 0.48815,1.47448 0.46801,0.50324 1.31344,0.50324 0.89073,0 1.76134,-0.37239 v 0.74479 q -0.44285,0.19123 -0.84041,0.27174 -0.39253,0.0855 -0.95112,0.0855 z m -0.22646,-5.01727 q -0.66427,0 -1.06183,0.43278 -0.39252,0.43279 -0.46298,1.19771 h 2.88355 q 0,-0.79008 -0.35226,-1.20777 -0.35227,-0.42272 -1.00648,-0.42272 z\" id=\"path7583\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 428.64745,715.92223 h -0.0453 q -0.57873,0.8404 -1.73114,0.8404 -1.08196,0 -1.68585,-0.73975 -0.59885,-0.73976 -0.59885,-2.10354 0,-1.36377 0.60389,-2.11863 0.60388,-0.75485 1.68081,-0.75485 1.12222,0 1.72107,0.81524 h 0.0654 l -0.0352,-0.39755 -0.0201,-0.3875 v -2.24444 h 0.83537 v 7.83038 h -0.67937 z m -1.67075,0.1409 q 0.8555,0 1.23796,-0.46297 0.3875,-0.46801 0.3875,-1.50468 v -0.17614 q 0,-1.17254 -0.39253,-1.67074 -0.38749,-0.50324 -1.243,-0.50324 -0.73472,0 -1.12725,0.57369 -0.38749,0.56866 -0.38749,1.61036 0,1.0568 0.38749,1.59526 0.3875,0.53846 1.13732,0.53846 z\" id=\"path7585\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 433.60419,716.66199 v -7.35733 h 0.8555 v 6.58234 h 3.24588 v 0.77499 z\" id=\"path7587\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 440.0441,716.66199 h -0.83537 v -5.51548 h 0.83537 z m -0.90583,-7.0101 q 0,-0.28684 0.14091,-0.41769 0.14091,-0.13587 0.35227,-0.13587 0.20129,0 0.34723,0.13587 0.14594,0.13588 0.14594,0.41769 0,0.28181 -0.14594,0.42272 -0.14594,0.13587 -0.34723,0.13587 -0.21136,0 -0.35227,-0.13587 -0.14091,-0.14091 -0.14091,-0.42272 z\" id=\"path7589\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 445.27103,716.66199 v -3.56796 q 0,-0.67433 -0.30697,-1.00647 -0.30698,-0.33214 -0.96119,-0.33214 -0.86557,0 -1.26816,0.46801 -0.40258,0.46801 -0.40258,1.54494 v 2.89362 h -0.83538 v -5.51548 h 0.67937 l 0.13588,0.75485 h 0.0403 q 0.25666,-0.40762 0.71963,-0.62904 0.46298,-0.22646 1.03164,-0.22646 0.99641,0 1.49965,0.48311 0.50323,0.47807 0.50323,1.53487 v 3.59815 z\" id=\"path7591\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 448.01203,711.14651 v 3.57801 q 0,0.67434 0.30697,1.00648 0.30698,0.33213 0.96118,0.33213 0.86557,0 1.26313,-0.47304 0.40259,-0.47304 0.40259,-1.54494 v -2.89864 h 0.83537 v 5.51548 h -0.68943 l -0.12078,-0.73976 h -0.0453 q -0.25665,0.40762 -0.7146,0.62401 -0.45291,0.21639 -1.03667,0.21639 -1.00647,0 -1.50971,-0.47807 -0.4982,-0.47808 -0.4982,-1.52984 v -3.60821 z\" id=\"path7593\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 454.28578,713.83883 -1.91734,-2.69232 h 0.95112 l 1.45436,2.11359 1.44932,-2.11359 h 0.94105 l -1.91733,2.69232 2.01798,2.82316 h -0.94608 l -1.54494,-2.23438 -1.56004,2.23438 h -0.94608 z\" id=\"path7595\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 384.14965,725.92338 q 0,1.34868 -0.67937,2.10857 -0.67937,0.75485 -1.87708,0.75485 -0.73976,0 -1.31345,-0.34723 -0.57369,-0.34723 -0.88569,-0.99641 -0.31201,-0.64918 -0.31201,-1.51978 0,-1.34867 0.67434,-2.0985 0.67434,-0.75485 1.87204,-0.75485 1.15745,0 1.83682,0.76995 0.6844,0.76995 0.6844,2.0834 z m -4.20203,0 q 0,1.0568 0.42272,1.61036 0.42272,0.55356 1.24299,0.55356 0.82028,0 1.243,-0.54852 0.42775,-0.55356 0.42775,-1.6154 0,-1.05176 -0.42775,-1.59526 -0.42272,-0.54853 -1.25306,-0.54853 -0.82028,0 -1.23797,0.53847 -0.41768,0.53846 -0.41768,1.60532 z\" id=\"path7598\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 387.63547,723.07003 q 0.36736,0 0.65924,0.0604 l -0.11575,0.77498 q -0.3422,-0.0755 -0.60388,-0.0755 -0.66931,0 -1.14738,0.54349 -0.47305,0.5435 -0.47305,1.35371 v 2.95904 h -0.83537 v -5.51548 h 0.68943 l 0.0956,1.02157 h 0.0403 q 0.30697,-0.53847 0.73976,-0.83034 0.43278,-0.29188 0.95112,-0.29188 z\" id=\"path7600\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 397.95332,728.68616 h -0.84544 l -1.48455,-4.9267 q -0.10568,-0.3271 -0.23652,-0.82531 -0.13084,-0.4982 -0.13587,-0.59885 -0.11071,0.66428 -0.35227,1.45436 l -1.43926,4.8965 h -0.84543 l -1.9576,-7.35733 h 0.90583 l 1.16248,4.54423 q 0.24155,0.95615 0.35226,1.73114 0.13588,-0.92093 0.40259,-1.80159 l 1.31848,-4.47378 h 0.90583 l 1.3839,4.51404 q 0.24156,0.78001 0.40763,1.76133 0.0956,-0.7146 0.36233,-1.7412 l 1.15744,-4.53417 h 0.90583 z\" id=\"path7602\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 401.96036,728.68616 h -0.83537 v -5.51548 h 0.83537 z m -0.90583,-7.0101 q 0,-0.28684 0.14091,-0.41769 0.14091,-0.13587 0.35227,-0.13587 0.20129,0 0.34723,0.13587 0.14594,0.13588 0.14594,0.41769 0,0.28181 -0.14594,0.42272 -0.14594,0.13587 -0.34723,0.13587 -0.21136,0 -0.35227,-0.13587 -0.14091,-0.14091 -0.14091,-0.42272 z\" id=\"path7604\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 407.18726,728.68616 v -3.56796 q 0,-0.67433 -0.30697,-1.00647 -0.30698,-0.33214 -0.96119,-0.33214 -0.86557,0 -1.26816,0.46801 -0.40259,0.46801 -0.40259,1.54494 v 2.89362 h -0.83537 v -5.51548 h 0.67937 l 0.13587,0.75485 h 0.0403 q 0.25665,-0.40762 0.71963,-0.62904 0.46298,-0.22646 1.03164,-0.22646 0.99641,0 1.49965,0.48311 0.50323,0.47807 0.50323,1.53487 v 3.59815 z\" id=\"path7606\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 412.89739,727.9464 h -0.0453 q -0.57872,0.8404 -1.73113,0.8404 -1.08196,0 -1.68585,-0.73975 -0.59885,-0.73976 -0.59885,-2.10354 0,-1.36377 0.60389,-2.11863 0.60388,-0.75485 1.68081,-0.75485 1.12222,0 1.72107,0.81524 h 0.0654 l -0.0352,-0.39755 -0.0201,-0.3875 v -2.24444 h 0.83538 v 7.83038 h -0.67937 z m -1.67075,0.1409 q 0.8555,0 1.23796,-0.46297 0.38749,-0.46801 0.38749,-1.50468 v -0.17614 q 0,-1.17254 -0.39252,-1.67074 -0.38749,-0.50324 -1.243,-0.50324 -0.73472,0 -1.12725,0.57369 -0.38749,0.56866 -0.38749,1.61036 0,1.0568 0.38749,1.59526 0.38749,0.53846 1.13732,0.53846 z\" id=\"path7608\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 419.63409,725.92338 q 0,1.34868 -0.67938,2.10857 -0.67937,0.75485 -1.87707,0.75485 -0.73976,0 -1.31345,-0.34723 -0.57369,-0.34723 -0.8857,-0.99641 -0.312,-0.64918 -0.312,-1.51978 0,-1.34867 0.67433,-2.0985 0.67434,-0.75485 1.87205,-0.75485 1.15744,0 1.83681,0.76995 0.68441,0.76995 0.68441,2.0834 z m -4.20204,0 q 0,1.0568 0.42272,1.61036 0.42272,0.55356 1.243,0.55356 0.82028,0 1.243,-0.54852 0.42775,-0.55356 0.42775,-1.6154 0,-1.05176 -0.42775,-1.59526 -0.42272,-0.54853 -1.25307,-0.54853 -0.82027,0 -1.23796,0.53847 -0.41769,0.53846 -0.41769,1.60532 z\" id=\"path7610\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 425.10769,728.68616 -1.01151,-3.23582 q -0.0956,-0.29691 -0.3573,-1.34867 h -0.0403 q -0.20129,0.88066 -0.35226,1.35874 l -1.0417,3.22575 h -0.96622 l -1.50468,-5.51548 h 0.87564 q 0.53343,2.07837 0.81021,3.16536 0.28181,1.08699 0.32207,1.46442 h 0.0403 q 0.0554,-0.28685 0.17613,-0.73976 0.12581,-0.45795 0.21639,-0.72466 l 1.01151,-3.16536 h 0.90583 l 0.98634,3.16536 q 0.28182,0.86557 0.38246,1.45435 h 0.0403 q 0.0201,-0.18116 0.10568,-0.55859 0.0906,-0.37743 1.05177,-4.06112 h 0.86557 l -1.52481,5.51548 z\" id=\"path7612\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 431.6028,727.18148 q 0,0.76995 -0.57369,1.18764 -0.5737,0.41768 -1.61036,0.41768 -1.09706,0 -1.71101,-0.34723 v -0.77498 q 0.39756,0.20129 0.85047,0.31703 0.45795,0.11575 0.88067,0.11575 0.6542,0 1.00647,-0.20633 0.35227,-0.21136 0.35227,-0.63911 0,-0.32207 -0.28182,-0.54853 -0.27678,-0.23149 -1.08699,-0.54349 -0.76995,-0.28685 -1.09706,-0.49821 -0.32207,-0.21639 -0.4831,-0.48814 -0.15601,-0.27175 -0.15601,-0.64918 0,-0.67433 0.54853,-1.06183 0.54853,-0.39252 1.50468,-0.39252 0.89073,0 1.7412,0.36233 l -0.29691,0.67937 q -0.83034,-0.3422 -1.50468,-0.3422 -0.59382,0 -0.89576,0.1862 -0.30194,0.18619 -0.30194,0.5133 0,0.22142 0.11071,0.37743 0.11574,0.156 0.36736,0.29691 0.25162,0.1409 0.96622,0.40762 0.98131,0.3573 1.32351,0.71963 0.34724,0.36233 0.34724,0.91086 z\" id=\"path7614\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> </g> <path d=\"m 252.336,716.625 h 12.609 v 9.02 h -12.609 z\" style=\"fill:#ffffff;fill-opacity:1;fill-rule:nonzero;stroke:none\" id=\"path586\" clip-path=\"none\" transform=\"matrix(1.3333333,0,0,1.3333333,0.546513,0.182228)\" /> <g id=\"g1390\" transform=\"matrix(1.3333333,0,0,1.3333333,0.546513,0.182228)\" style=\"fill:#ffffff;fill-opacity:1\"> <path d=\"m 252.336,716.625 h 12.617 V 726 h -12.617 z\" id=\"path1388\" style=\"fill:#ffffff;fill-opacity:1\" /> </g> <path id=\"path608\" clip-path=\"none\" style=\"fill:#ffffff;fill-opacity:1;fill-rule:nonzero;stroke:none\" d=\"M 388.05442 716.62458 L 388.05442 725.64509 L 388.05442 725.99958 L 397.93333 725.99958 L 397.93333 725.64509 L 397.93333 716.62458 L 388.05442 716.62458 z \" transform=\"matrix(1.3333333,0,0,1.3333333,-6.665649,0.182228)\" /> <path d=\"m 329.992,382.566 h 135.383 v 9.02 H 329.992 Z\" style=\"fill:#ffffff;fill-opacity:1;fill-rule:nonzero;stroke:none\" id=\"path630\" clip-path=\"none\" transform=\"matrix(1.3333333,0,0,1.3333333,0.546513,0.182228)\" /> <path d=\"m 440.53584,510.27022 h 180.52132 v 12.57866 H 440.53584 Z\" id=\"path1422\" style=\"stroke-width:1.33333;stroke:none;fill:#ffffff;fill-opacity:1\" clip-path=\"none\" /> <g aria-label=\"Fully managed control plane and nodes\" transform=\"scale(1.33333)\" id=\"text3107\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal'\"> <path d=\"m 331.39296,389.65039 h -0.64162 v -5.51799 h 3.07603 v 0.56992 h -2.43441 v 2.01924 h 2.28721 v 0.56991 h -2.28721 z\" id=\"path7629\" /> <path d=\"m 335.96094,385.51379 v 2.68351 q 0,0.50575 0.23023,0.75485 0.23024,0.2491 0.72089,0.2491 0.64918,0 0.94734,-0.35478 0.30195,-0.35478 0.30195,-1.1587 v -2.17398 h 0.62652 v 4.1366 h -0.51707 l -0.0906,-0.55482 h -0.034 q -0.19249,0.30572 -0.53595,0.46801 -0.33968,0.1623 -0.7775,0.1623 -0.75485,0 -1.13228,-0.35856 -0.37365,-0.35856 -0.37365,-1.14738 v -2.70615 z\" id=\"path7631\" /> <path d=\"m 340.29642,389.65039 h -0.62653 v -5.87277 h 0.62653 z\" id=\"path7633\" /> <path d=\"m 342.01239,389.65039 h -0.62653 v -5.87277 h 0.62653 z\" id=\"path7635\" /> <path d=\"m 342.44514,385.51379 h 0.67182 l 0.90583,2.35892 q 0.29816,0.80769 0.36987,1.16625 h 0.0302 q 0.0491,-0.19249 0.20381,-0.65672 0.15852,-0.46801 1.0266,-2.86845 h 0.67182 l -1.77768,4.71029 q -0.2642,0.69824 -0.61898,0.98886 -0.35101,0.29439 -0.86431,0.29439 -0.28684,0 -0.56614,-0.0642 v -0.50198 q 0.20758,0.0453 0.46424,0.0453 0.6454,0 0.92092,-0.72466 l 0.23023,-0.58878 z\" id=\"path7637\" /> <path d=\"m 354.38053,389.65039 v -2.69106 q 0,-0.49443 -0.21136,-0.73975 -0.21135,-0.24911 -0.65672,-0.24911 -0.58501,0 -0.86431,0.33592 -0.27929,0.33591 -0.27929,1.03415 v 2.30985 h -0.62653 v -2.69106 q 0,-0.49443 -0.21136,-0.73975 -0.21136,-0.24911 -0.6605,-0.24911 -0.58879,0 -0.86431,0.35479 -0.27175,0.351 -0.27175,1.15492 v 2.17021 h -0.62652 v -4.1366 h 0.50952 l 0.10191,0.56614 h 0.0302 q 0.17739,-0.30194 0.49821,-0.47179 0.32458,-0.16984 0.72466,-0.16984 0.96998,0 1.26815,0.70202 h 0.0302 q 0.18494,-0.32459 0.53594,-0.5133 0.35101,-0.18872 0.80015,-0.18872 0.70201,0 1.04925,0.36233 0.351,0.35856 0.351,1.15116 v 2.6986 z\" id=\"path7639\" /> <path d=\"m 358.09052,389.65039 -0.12455,-0.58879 h -0.0302 q -0.30949,0.38875 -0.61898,0.5284 -0.30572,0.13588 -0.76618,0.13588 -0.6152,0 -0.96621,-0.31704 -0.34723,-0.31704 -0.34723,-0.90205 0,-1.25306 2.00414,-1.31345 l 0.70201,-0.0226 v -0.25665 q 0,-0.48688 -0.21136,-0.71711 -0.20758,-0.234 -0.66805,-0.234 -0.51707,0 -1.17002,0.31704 l -0.19249,-0.47934 q 0.30572,-0.16607 0.66805,-0.26042 0.3661,-0.0944 0.73221,-0.0944 0.73975,0 1.09454,0.32836 0.35855,0.32836 0.35855,1.05302 v 2.82316 z m -1.41536,-0.44159 q 0.58502,0 0.91715,-0.32081 0.33591,-0.32082 0.33591,-0.89828 v -0.37365 l -0.62653,0.0264 q -0.7473,0.0264 -1.07944,0.234 -0.32836,0.20381 -0.32836,0.63785 0,0.33969 0.20381,0.51708 0.20759,0.17739 0.57746,0.17739 z\" id=\"path7641\" /> <path d=\"m 362.67509,389.65039 v -2.67596 q 0,-0.50575 -0.23023,-0.75485 -0.23023,-0.24911 -0.72089,-0.24911 -0.64917,0 -0.95111,0.35101 -0.30194,0.35101 -0.30194,1.1587 v 2.17021 h -0.62653 v -4.1366 h 0.50952 l 0.10191,0.56614 h 0.0302 q 0.19249,-0.30572 0.53972,-0.47179 0.34724,-0.16984 0.77373,-0.16984 0.74731,0 1.12473,0.36233 0.37743,0.35856 0.37743,1.15116 v 2.6986 z\" id=\"path7643\" /> <path d=\"m 366.68595,389.65039 -0.12456,-0.58879 h -0.0302 q -0.30949,0.38875 -0.61898,0.5284 -0.30572,0.13588 -0.76618,0.13588 -0.6152,0 -0.96621,-0.31704 -0.34723,-0.31704 -0.34723,-0.90205 0,-1.25306 2.00413,-1.31345 l 0.70202,-0.0226 v -0.25665 q 0,-0.48688 -0.21136,-0.71711 -0.20759,-0.234 -0.66805,-0.234 -0.51707,0 -1.17002,0.31704 l -0.19249,-0.47934 q 0.30572,-0.16607 0.66805,-0.26042 0.3661,-0.0944 0.73221,-0.0944 0.73975,0 1.09453,0.32836 0.35856,0.32836 0.35856,1.05302 v 2.82316 z m -1.41536,-0.44159 q 0.58502,0 0.91715,-0.32081 0.33591,-0.32082 0.33591,-0.89828 v -0.37365 l -0.62653,0.0264 q -0.7473,0.0264 -1.07944,0.234 -0.32836,0.20381 -0.32836,0.63785 0,0.33969 0.20381,0.51708 0.20758,0.17739 0.57746,0.17739 z\" id=\"path7645\" /> <path d=\"m 371.8254,385.51379 v 0.3963 l -0.76618,0.0906 q 0.10568,0.1321 0.18871,0.34723 0.083,0.21136 0.083,0.47933 0,0.60766 -0.41517,0.96999 -0.41517,0.36233 -1.13983,0.36233 -0.18494,0 -0.34723,-0.0302 -0.40008,0.21136 -0.40008,0.53217 0,0.16984 0.13965,0.25288 0.13965,0.0793 0.47933,0.0793 h 0.73221 q 0.67182,0 1.03038,0.28307 0.36233,0.28307 0.36233,0.82279 0,0.68692 -0.55104,1.04547 -0.55105,0.36233 -1.60785,0.36233 -0.81146,0 -1.25305,-0.30194 -0.43782,-0.30194 -0.43782,-0.85298 0,-0.37743 0.24155,-0.65295 0.24156,-0.27553 0.67937,-0.37366 -0.15852,-0.0717 -0.26797,-0.22268 -0.10568,-0.15097 -0.10568,-0.35101 0,-0.22645 0.12078,-0.39629 0.12077,-0.16985 0.3812,-0.32837 -0.32081,-0.1321 -0.52463,-0.44913 -0.20003,-0.31704 -0.20003,-0.72467 0,-0.67936 0.40762,-1.04547 0.40762,-0.36988 1.15493,-0.36988 0.32458,0 0.58501,0.0755 z m -3.29872,4.83107 q 0,0.33591 0.28307,0.50952 0.28308,0.17362 0.81147,0.17362 0.78883,0 1.16625,-0.23778 0.38121,-0.234 0.38121,-0.63785 0,-0.33591 -0.20759,-0.46801 -0.20758,-0.12833 -0.78127,-0.12833 h -0.75108 q -0.4265,0 -0.66428,0.20381 -0.23778,0.20382 -0.23778,0.58502 z m 0.33969,-3.5063 q 0,0.43404 0.24533,0.65672 0.24532,0.22268 0.68314,0.22268 0.91715,0 0.91715,-0.89073 0,-0.93224 -0.92847,-0.93224 -0.44159,0 -0.67937,0.23778 -0.23778,0.23778 -0.23778,0.70579 z\" id=\"path7647\" /> <path d=\"m 374.48506,389.72588 q -0.91714,0 -1.44932,-0.5586 -0.5284,-0.55859 -0.5284,-1.55122 0,-1.00018 0.49066,-1.58897 0.49443,-0.58879 1.32477,-0.58879 0.7775,0 1.23041,0.5133 0.45292,0.50953 0.45292,1.34742 v 0.3963 h -2.84958 q 0.0189,0.72843 0.3661,1.10586 0.35101,0.37743 0.98509,0.37743 0.66805,0 1.32099,-0.2793 v 0.55859 q -0.33213,0.14343 -0.6303,0.20381 -0.29439,0.0642 -0.71334,0.0642 z m -0.16984,-3.76295 q -0.4982,0 -0.79637,0.32458 -0.29439,0.32459 -0.34723,0.89828 h 2.16265 q 0,-0.59256 -0.26419,-0.90582 -0.2642,-0.31704 -0.75486,-0.31704 z\" id=\"path7649\" /> <path d=\"m 379.85088,389.09557 h -0.034 q -0.43404,0.63031 -1.29835,0.63031 -0.81147,0 -1.26438,-0.55482 -0.44914,-0.55482 -0.44914,-1.57765 0,-1.02283 0.45292,-1.58897 0.45291,-0.56614 1.2606,-0.56614 0.84167,0 1.2908,0.61143 h 0.0491 l -0.0264,-0.29816 -0.0151,-0.29062 v -1.68333 h 0.62653 v 5.87277 h -0.50952 z m -1.25306,0.10568 q 0.64163,0 0.92847,-0.34723 0.29062,-0.35101 0.29062,-1.12851 v -0.1321 q 0,-0.8794 -0.29439,-1.25306 -0.29062,-0.37742 -0.93225,-0.37742 -0.55104,0 -0.84543,0.43026 -0.29062,0.4265 -0.29062,1.20777 0,0.7926 0.29062,1.19645 0.29062,0.40384 0.85298,0.40384 z\" id=\"path7651\" /> <path d=\"m 385.12722,389.72588 q -0.89828,0 -1.39271,-0.55105 -0.49065,-0.55482 -0.49065,-1.56632 0,-1.03793 0.4982,-1.60407 0.50198,-0.56614 1.42667,-0.56614 0.29817,0 0.59634,0.0642 0.29817,0.0642 0.46801,0.15097 l -0.19249,0.53217 q -0.20758,-0.083 -0.45291,-0.13588 -0.24533,-0.0566 -0.43404,-0.0566 -1.26061,0 -1.26061,1.60784 0,0.7624 0.30572,1.17003 0.30949,0.40762 0.91337,0.40762 0.51708,0 1.06057,-0.22269 v 0.55482 q -0.41517,0.21514 -1.04547,0.21514 z\" id=\"path7653\" /> <path d=\"m 390.90945,387.57832 q 0,1.0115 -0.50953,1.58142 -0.50953,0.56614 -1.4078,0.56614 -0.55482,0 -0.98509,-0.26043 -0.43027,-0.26042 -0.66427,-0.7473 -0.23401,-0.48689 -0.23401,-1.13983 0,-1.01151 0.50576,-1.57388 0.50575,-0.56614 1.40403,-0.56614 0.86808,0 1.37761,0.57747 0.5133,0.57746 0.5133,1.56255 z m -3.15152,0 q 0,0.79259 0.31704,1.20776 0.31704,0.41517 0.93224,0.41517 0.61521,0 0.93225,-0.41139 0.32081,-0.41517 0.32081,-1.21154 0,-0.78883 -0.32081,-1.19645 -0.31704,-0.4114 -0.93979,-0.4114 -0.61521,0 -0.92848,0.40385 -0.31326,0.40385 -0.31326,1.204 z\" id=\"path7655\" /> <path d=\"m 394.46739,389.65039 v -2.67596 q 0,-0.50575 -0.23023,-0.75485 -0.23023,-0.24911 -0.72089,-0.24911 -0.64917,0 -0.95111,0.35101 -0.30195,0.35101 -0.30195,1.1587 v 2.17021 h -0.62653 v -4.1366 h 0.50953 l 0.10191,0.56614 h 0.0302 q 0.19249,-0.30572 0.53972,-0.47179 0.34723,-0.16984 0.77373,-0.16984 0.7473,0 1.12473,0.36233 0.37743,0.35856 0.37743,1.15116 v 2.6986 z\" id=\"path7657\" /> <path d=\"m 397.27048,389.2088 q 0.16606,0 0.32081,-0.0226 0.15474,-0.0264 0.24533,-0.0528 v 0.47933 q -0.10191,0.0491 -0.30195,0.0793 -0.19626,0.034 -0.35478,0.034 -1.20022,0 -1.20022,-1.26439 v -2.46082 h -0.59256 v -0.30194 l 0.59256,-0.26043 0.2642,-0.88318 h 0.36233 v 0.95867 h 1.20022 v 0.48688 h -1.20022 v 2.4344 q 0,0.37366 0.17739,0.57369 0.1774,0.20004 0.48689,0.20004 z\" id=\"path7659\" /> <path d=\"m 399.96269,385.4383 q 0.27553,0 0.49443,0.0453 l -0.0868,0.58124 q -0.25666,-0.0566 -0.45292,-0.0566 -0.50198,0 -0.86053,0.40762 -0.35478,0.40762 -0.35478,1.01528 v 2.21927 h -0.62653 v -4.1366 h 0.51707 l 0.0717,0.76618 h 0.0302 q 0.23023,-0.40385 0.55482,-0.62276 0.32458,-0.21891 0.71333,-0.21891 z\" id=\"path7661\" /> <path d=\"m 404.22002,387.57832 q 0,1.0115 -0.50952,1.58142 -0.50953,0.56614 -1.40781,0.56614 -0.55481,0 -0.98508,-0.26043 -0.43027,-0.26042 -0.66427,-0.7473 -0.23401,-0.48689 -0.23401,-1.13983 0,-1.01151 0.50575,-1.57388 0.50576,-0.56614 1.40403,-0.56614 0.86809,0 1.37761,0.57747 0.5133,0.57746 0.5133,1.56255 z m -3.15151,0 q 0,0.79259 0.31704,1.20776 0.31703,0.41517 0.93224,0.41517 0.61521,0 0.93225,-0.41139 0.32081,-0.41517 0.32081,-1.21154 0,-0.78883 -0.32081,-1.19645 -0.31704,-0.4114 -0.9398,-0.4114 -0.6152,0 -0.92847,0.40385 -0.31326,0.40385 -0.31326,1.204 z\" id=\"path7663\" /> <path d=\"m 405.57379,389.65039 h -0.62653 v -5.87277 h 0.62653 z\" id=\"path7665\" /> <path d=\"m 410.72926,389.72588 q -0.40385,0 -0.73976,-0.1472 -0.33214,-0.15097 -0.55859,-0.46046 h -0.0453 q 0.0453,0.36233 0.0453,0.68692 v 1.70219 h -0.62653 v -5.99354 h 0.50952 l 0.0868,0.56614 h 0.0302 q 0.24155,-0.33969 0.56236,-0.49066 0.32082,-0.15097 0.73599,-0.15097 0.82279,0 1.26815,0.56237 0.44914,0.56237 0.44914,1.57765 0,1.01905 -0.45669,1.58519 -0.45291,0.56237 -1.2606,0.56237 z m -0.0906,-3.75541 q -0.63407,0 -0.91714,0.35101 -0.28307,0.35101 -0.29062,1.11719 v 0.13965 q 0,0.87185 0.29062,1.24928 0.29062,0.37365 0.93224,0.37365 0.53595,0 0.83789,-0.43404 0.30572,-0.43404 0.30572,-1.19644 0,-0.77373 -0.30572,-1.18513 -0.30194,-0.41517 -0.85299,-0.41517 z\" id=\"path7667\" /> <path d=\"m 413.72861,389.65039 h -0.62653 v -5.87277 h 0.62653 z\" id=\"path7669\" /> <path d=\"m 417.36194,389.65039 -0.12455,-0.58879 h -0.0302 q -0.3095,0.38875 -0.61899,0.5284 -0.30571,0.13588 -0.76617,0.13588 -0.61521,0 -0.96622,-0.31704 -0.34723,-0.31704 -0.34723,-0.90205 0,-1.25306 2.00414,-1.31345 l 0.70201,-0.0226 v -0.25665 q 0,-0.48688 -0.21136,-0.71711 -0.20758,-0.234 -0.66804,-0.234 -0.51708,0 -1.17003,0.31704 l -0.19248,-0.47934 q 0.30571,-0.16607 0.66804,-0.26042 0.36611,-0.0944 0.73221,-0.0944 0.73976,0 1.09454,0.32836 0.35856,0.32836 0.35856,1.05302 v 2.82316 z m -1.41535,-0.44159 q 0.58501,0 0.91715,-0.32081 0.33591,-0.32082 0.33591,-0.89828 v -0.37365 l -0.62653,0.0264 q -0.74731,0.0264 -1.07944,0.234 -0.32837,0.20381 -0.32837,0.63785 0,0.33969 0.20381,0.51708 0.20759,0.17739 0.57747,0.17739 z\" id=\"path7671\" /> <path d=\"m 421.94648,389.65039 v -2.67596 q 0,-0.50575 -0.23023,-0.75485 -0.23023,-0.24911 -0.72088,-0.24911 -0.64918,0 -0.95112,0.35101 -0.30194,0.35101 -0.30194,1.1587 v 2.17021 h -0.62653 v -4.1366 h 0.50953 l 0.1019,0.56614 h 0.0302 q 0.19248,-0.30572 0.53972,-0.47179 0.34723,-0.16984 0.77372,-0.16984 0.74731,0 1.12474,0.36233 0.37742,0.35856 0.37742,1.15116 v 2.6986 z\" id=\"path7673\" /> <path d=\"m 425.16106,389.72588 q -0.91715,0 -1.44932,-0.5586 -0.5284,-0.55859 -0.5284,-1.55122 0,-1.00018 0.49065,-1.58897 0.49443,-0.58879 1.32477,-0.58879 0.7775,0 1.23042,0.5133 0.45291,0.50953 0.45291,1.34742 v 0.3963 h -2.84958 q 0.0189,0.72843 0.36611,1.10586 0.35101,0.37743 0.98508,0.37743 0.66805,0 1.321,-0.2793 v 0.55859 q -0.33214,0.14343 -0.6303,0.20381 -0.2944,0.0642 -0.71334,0.0642 z m -0.16984,-3.76295 q -0.49821,0 -0.79638,0.32458 -0.29439,0.32459 -0.34723,0.89828 h 2.16266 q 0,-0.59256 -0.2642,-0.90582 -0.2642,-0.31704 -0.75485,-0.31704 z\" id=\"path7675\" /> <path d=\"m 432.39624,389.65039 -0.12455,-0.58879 h -0.0302 q -0.30949,0.38875 -0.61898,0.5284 -0.30572,0.13588 -0.76618,0.13588 -0.61521,0 -0.96621,-0.31704 -0.34724,-0.31704 -0.34724,-0.90205 0,-1.25306 2.00414,-1.31345 l 0.70202,-0.0226 v -0.25665 q 0,-0.48688 -0.21136,-0.71711 -0.20759,-0.234 -0.66805,-0.234 -0.51708,0 -1.17002,0.31704 l -0.19249,-0.47934 q 0.30571,-0.16607 0.66804,-0.26042 0.36611,-0.0944 0.73221,-0.0944 0.73976,0 1.09454,0.32836 0.35856,0.32836 0.35856,1.05302 v 2.82316 z m -1.41535,-0.44159 q 0.58501,0 0.91715,-0.32081 0.33591,-0.32082 0.33591,-0.89828 v -0.37365 l -0.62653,0.0264 q -0.74731,0.0264 -1.07944,0.234 -0.32836,0.20381 -0.32836,0.63785 0,0.33969 0.20381,0.51708 0.20758,0.17739 0.57746,0.17739 z\" id=\"path7677\" /> <path d=\"m 436.98079,389.65039 v -2.67596 q 0,-0.50575 -0.23023,-0.75485 -0.23024,-0.24911 -0.72089,-0.24911 -0.64918,0 -0.95112,0.35101 -0.30194,0.35101 -0.30194,1.1587 v 2.17021 h -0.62653 v -4.1366 h 0.50953 l 0.1019,0.56614 h 0.0302 q 0.19249,-0.30572 0.53972,-0.47179 0.34723,-0.16984 0.77372,-0.16984 0.74731,0 1.12474,0.36233 0.37742,0.35856 0.37742,1.15116 v 2.6986 z\" id=\"path7679\" /> <path d=\"m 441.26348,389.09557 h -0.034 q -0.43404,0.63031 -1.29835,0.63031 -0.81147,0 -1.26438,-0.55482 -0.44914,-0.55482 -0.44914,-1.57765 0,-1.02283 0.45291,-1.58897 0.45292,-0.56614 1.26061,-0.56614 0.84166,0 1.2908,0.61143 h 0.0491 l -0.0264,-0.29816 -0.0151,-0.29062 v -1.68333 h 0.62653 v 5.87277 h -0.50953 z m -1.25306,0.10568 q 0.64163,0 0.92847,-0.34723 0.29062,-0.35101 0.29062,-1.12851 v -0.1321 q 0,-0.8794 -0.29439,-1.25306 -0.29062,-0.37742 -0.93225,-0.37742 -0.55104,0 -0.84543,0.43026 -0.29062,0.4265 -0.29062,1.20777 0,0.7926 0.29062,1.19645 0.29061,0.40384 0.85298,0.40384 z\" id=\"path7681\" /> <path d=\"m 447.71739,389.65039 v -2.67596 q 0,-0.50575 -0.23023,-0.75485 -0.23023,-0.24911 -0.72089,-0.24911 -0.64917,0 -0.95111,0.35101 -0.30195,0.35101 -0.30195,1.1587 v 2.17021 h -0.62653 v -4.1366 h 0.50953 l 0.10191,0.56614 h 0.0302 q 0.19249,-0.30572 0.53972,-0.47179 0.34723,-0.16984 0.77373,-0.16984 0.7473,0 1.12473,0.36233 0.37743,0.35856 0.37743,1.15116 v 2.6986 z\" id=\"path7683\" /> <path d=\"m 452.77804,387.57832 q 0,1.0115 -0.50953,1.58142 -0.50953,0.56614 -1.4078,0.56614 -0.55482,0 -0.98509,-0.26043 -0.43026,-0.26042 -0.66427,-0.7473 -0.234,-0.48689 -0.234,-1.13983 0,-1.01151 0.50575,-1.57388 0.50575,-0.56614 1.40403,-0.56614 0.86808,0 1.37761,0.57747 0.5133,0.57746 0.5133,1.56255 z m -3.15152,0 q 0,0.79259 0.31704,1.20776 0.31704,0.41517 0.93224,0.41517 0.61521,0 0.93225,-0.41139 0.32081,-0.41517 0.32081,-1.21154 0,-0.78883 -0.32081,-1.19645 -0.31704,-0.4114 -0.93979,-0.4114 -0.61521,0 -0.92847,0.40385 -0.31327,0.40385 -0.31327,1.204 z\" id=\"path7685\" /> <path d=\"m 456.32088,389.09557 h -0.034 q -0.43404,0.63031 -1.29835,0.63031 -0.81146,0 -1.26438,-0.55482 -0.44914,-0.55482 -0.44914,-1.57765 0,-1.02283 0.45292,-1.58897 0.45291,-0.56614 1.2606,-0.56614 0.84167,0 1.29081,0.61143 h 0.0491 l -0.0264,-0.29816 -0.0151,-0.29062 v -1.68333 h 0.62653 v 5.87277 h -0.50952 z m -1.25306,0.10568 q 0.64163,0 0.92848,-0.34723 0.29061,-0.35101 0.29061,-1.12851 v -0.1321 q 0,-0.8794 -0.29439,-1.25306 -0.29062,-0.37742 -0.93224,-0.37742 -0.55105,0 -0.84544,0.43026 -0.29062,0.4265 -0.29062,1.20777 0,0.7926 0.29062,1.19645 0.29062,0.40384 0.85298,0.40384 z\" id=\"path7687\" /> <path d=\"m 459.55055,389.72588 q -0.91714,0 -1.44932,-0.5586 -0.52839,-0.55859 -0.52839,-1.55122 0,-1.00018 0.49065,-1.58897 0.49443,-0.58879 1.32477,-0.58879 0.7775,0 1.23041,0.5133 0.45292,0.50953 0.45292,1.34742 v 0.3963 h -2.84958 q 0.0189,0.72843 0.3661,1.10586 0.35101,0.37743 0.98509,0.37743 0.66805,0 1.321,-0.2793 v 0.55859 q -0.33214,0.14343 -0.63031,0.20381 -0.29439,0.0642 -0.71334,0.0642 z m -0.16984,-3.76295 q -0.4982,0 -0.79637,0.32458 -0.29439,0.32459 -0.34723,0.89828 h 2.16266 q 0,-0.59256 -0.2642,-0.90582 -0.2642,-0.31704 -0.75486,-0.31704 z\" id=\"path7689\" /> <path d=\"m 464.76918,388.52188 q 0,0.57747 -0.43027,0.89073 -0.43027,0.31327 -1.20777,0.31327 -0.82279,0 -1.28325,-0.26043 v -0.58124 q 0.29817,0.15097 0.63785,0.23778 0.34346,0.0868 0.6605,0.0868 0.49065,0 0.75485,-0.15474 0.2642,-0.15852 0.2642,-0.47934 0,-0.24155 -0.21136,-0.41139 -0.20758,-0.17362 -0.81524,-0.40762 -0.57746,-0.21514 -0.82279,-0.37366 -0.24156,-0.16229 -0.36233,-0.3661 -0.117,-0.20381 -0.117,-0.48688 0,-0.50576 0.41139,-0.79637 0.4114,-0.2944 1.12851,-0.2944 0.66805,0 1.3059,0.27175 l -0.22268,0.50953 q -0.62276,-0.25665 -1.12851,-0.25665 -0.44537,0 -0.67182,0.13964 -0.22646,0.13965 -0.22646,0.38498 0,0.16607 0.083,0.28307 0.0868,0.117 0.27553,0.22268 0.18871,0.10568 0.72466,0.30572 0.73598,0.26797 0.99263,0.53972 0.26043,0.27175 0.26043,0.68314 z\" id=\"path7691\" /> </g> <path id=\"path652\" clip-path=\"none\" style=\"fill:#ffffff;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-opacity:1\" d=\"M 254.0701 208.67974 L 254.0701 217.70025 L 254.0701 218.00054 L 259.2454 218.00054 L 259.2454 228.09185 L 328.87821 228.09185 L 328.87821 226.7149 L 329.28837 226.7149 L 329.28837 218.00054 L 334.87967 218.00054 L 334.87967 217.70025 L 334.88553 217.70025 L 334.88553 208.67974 L 254.0701 208.67974 z \" transform=\"matrix(1.3333333,0,0,1.3333333,0.546513,0.182228)\" /> <path d=\"M294.473 274.383v34.781c0 4.992 0 9.02-3.004 16.371-3.004 7.356-9.012 18.039-12.016 23.379l-3.004 5.34\" style=\"fill:none;stroke:#333;stroke-width:.966214;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3055\" /> <path d=\"m281.816 350.621-5.367 3.633.317-6.473z\" style=\"fill:#333;fill-opacity:1;fill-rule:nonzero;stroke:none\" clip-path=\"url(#m)\" transform=\"scale(1.33333)\" id=\"path3057\" /> <path d=\"m281.8166 350.6206-5.3676 3.6338.317-6.4731z\" style=\"fill:none;stroke:#333;stroke-width:.579728;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" clip-path=\"url(#n)\" transform=\"scale(1.33333)\" id=\"path3059\" /> <path d=\"M198.754 286.457h47.707v9.02h-47.707z\" style=\"fill:#fff;fill-opacity:1;fill-rule:nonzero;stroke:none\" clip-path=\"url(#o)\" transform=\"scale(1.33333)\" id=\"path3061\" /> <path d=\"M174.504 454.516h68.77v9.02h-68.77z\" style=\"fill:#fff;fill-opacity:1;fill-rule:nonzero;stroke:none\" clip-path=\"url(#p)\" transform=\"scale(1.33333)\" id=\"path3067\" /> <path d=\"M173.656 463.535h70.469v9.02h-70.469z\" style=\"fill:#fff;fill-opacity:1;fill-rule:nonzero;stroke:none\" clip-path=\"url(#q)\" transform=\"scale(1.33333)\" id=\"path3073\" /> <path d=\"M265.176 520.703h77.797v9.02h-77.797z\" style=\"fill:#fff;fill-opacity:1;fill-rule:nonzero;stroke:none\" clip-path=\"url(#r)\" transform=\"scale(1.33333)\" id=\"path3079\" /> <path d=\"M252.336 716.625h12.609v9.02h-12.609z\" style=\"fill:#fff;fill-opacity:1;fill-rule:nonzero;stroke:none\" clip-path=\"url(#s)\" transform=\"scale(1.33333)\" id=\"path3091\" /> <path d=\"M388.055 716.625h9.879v9.02h-9.879z\" style=\"fill:#fff;fill-opacity:1;fill-rule:nonzero;stroke:none\" clip-path=\"url(#t)\" transform=\"translate(-7.2122) scale(1.33333)\" id=\"path3097\" /> <path d=\"M329.992 382.566h135.383v9.02H329.992Z\" style=\"fill:#fff;fill-opacity:1;fill-rule:nonzero;stroke:none\" clip-path=\"url(#u)\" transform=\"scale(1.33333)\" id=\"path3103\" /> <path d=\"M254.07 208.68h80.816v9.02H254.07Z\" style=\"fill:#fff;fill-opacity:1;fill-rule:nonzero;stroke:none\" clip-path=\"url(#v)\" transform=\"scale(1.33333)\" id=\"path3109\" /> <path d=\"M289.75 39.863h9.445c5.2 0 9.422 4.223 9.422 9.422 0 5.199-4.222 9.422-9.422 9.422h-9.445c-5.199 0-9.422-4.223-9.422-9.422 0-5.199 4.223-9.422 9.422-9.422z\" style=\"fill:#ddd;fill-opacity:1;fill-rule:nonzero;stroke:none\" transform=\"scale(1.33333)\" id=\"path3121\" /> <path d=\"M289.75 39.863h9.445c5.2 0 9.422 4.223 9.422 9.422 0 5.199-4.222 9.422-9.422 9.422h-9.445c-5.199 0-9.422-4.223-9.422-9.422 0-5.199 4.223-9.422 9.422-9.422z\" style=\"fill:none;stroke:none;stroke-width:1.93243;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3123\" /> <g aria-label=\"Start\" transform=\"scale(1.33333)\" id=\"text3127\" style=\"font-weight:700;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Bold'\"> <path d=\"m 288.79785,50.513544 q 0,0.747306 -0.53972,1.177573 -0.53594,0.430267 -1.49461,0.430267 -0.88318,0 -1.56255,-0.332136 v -1.086991 q 0.5586,0.249102 0.94357,0.351008 0.38875,0.101905 0.70956,0.101905 0.38498,0 0.58879,-0.147197 0.20759,-0.147196 0.20759,-0.437815 0,-0.162294 -0.0906,-0.286845 -0.0906,-0.128325 -0.26797,-0.245328 -0.17362,-0.117002 -0.71334,-0.373653 -0.50575,-0.237779 -0.75863,-0.456686 -0.25287,-0.218908 -0.40384,-0.509527 -0.15097,-0.290619 -0.15097,-0.679369 0,-0.732209 0.49443,-1.151153 0.4982,-0.418945 1.37383,-0.418945 0.43027,0 0.81902,0.101906 0.39252,0.101905 0.81901,0.286844 l -0.37742,0.9096 q -0.44159,-0.181165 -0.73221,-0.252876 -0.28685,-0.07171 -0.56614,-0.07171 -0.33214,0 -0.50953,0.154745 -0.17739,0.154745 -0.17739,0.403847 0,0.154745 0.0717,0.271748 0.0717,0.113228 0.22646,0.222682 0.15852,0.105679 0.74353,0.384975 0.77373,0.369879 1.06057,0.743532 0.28684,0.369879 0.28684,0.9096 z\" id=\"path7768\" /> <path d=\"m 291.48514,51.204236 q 0.30194,0 0.72466,-0.1321 v 0.85676 q -0.43027,0.192488 -1.0568,0.192488 -0.69069,0 -1.00773,-0.347233 -0.31326,-0.351008 -0.31326,-1.049248 V 48.69057 h -0.55105 v -0.486881 l 0.63408,-0.384976 0.33214,-0.890728 h 0.73598 v 0.898277 h 1.18135 v 0.864308 h -1.18135 v 2.034333 q 0,0.245328 0.13587,0.36233 0.13965,0.117003 0.36611,0.117003 z\" id=\"path7770\" /> <path d=\"m 295.74252,52.045898 -0.22269,-0.573689 h -0.0302 q -0.29062,0.366104 -0.60011,0.509527 -0.30572,0.139648 -0.80014,0.139648 -0.60766,0 -0.95867,-0.347233 -0.34723,-0.347233 -0.34723,-0.98886 0,-0.67182 0.46801,-0.988859 0.47178,-0.320813 1.41912,-0.354782 l 0.73221,-0.02265 v -0.18494 q 0,-0.641626 -0.65672,-0.641626 -0.50575,0 -1.1889,0.305716 l -0.3812,-0.7775 q 0.72844,-0.381201 1.61539,-0.381201 0.84921,0 1.30212,0.369878 0.45292,0.369879 0.45292,1.124733 v 2.811833 z m -0.33969,-1.955073 -0.44536,0.0151 q -0.50198,0.0151 -0.74731,0.181165 -0.24533,0.166068 -0.24533,0.505753 0,0.486881 0.5586,0.486881 0.40007,0 0.63785,-0.230231 0.24155,-0.23023 0.24155,-0.611432 z\" id=\"path7772\" /> <path d=\"m 300.0867,47.747002 q 0.23401,0 0.38875,0.03397 l -0.0868,1.079441 q -0.13965,-0.03774 -0.33969,-0.03774 -0.55104,0 -0.86053,0.28307 -0.30572,0.283071 -0.30572,0.792597 v 2.147561 h -1.15115 v -4.219636 h 0.87185 l 0.16985,0.709563 h 0.0566 q 0.19626,-0.354782 0.5284,-0.569915 0.33591,-0.218908 0.72843,-0.218908 z\" id=\"path7774\" /> <path d=\"m 303.01931,51.204236 q 0.30195,0 0.72466,-0.1321 v 0.85676 q -0.43026,0.192488 -1.05679,0.192488 -0.69069,0 -1.00773,-0.347233 -0.31327,-0.351008 -0.31327,-1.049248 V 48.69057 h -0.55104 v -0.486881 l 0.63408,-0.384976 0.33213,-0.890728 h 0.73599 v 0.898277 h 1.18134 v 0.864308 h -1.18134 v 2.034333 q 0,0.245328 0.13587,0.36233 0.13965,0.117003 0.3661,0.117003 z\" id=\"path7776\" /> </g> <g id=\"g13099\"> <path d=\"m 371.73508,176.99057 h -1.30841 l -1.24802,-4.3882 q -0.0805,-0.28684 -0.20129,-0.82531 -0.1208,-0.54349 -0.14594,-0.75485 -0.0503,0.32207 -0.16606,0.83537 -0.11067,0.51329 -0.1862,0.76492 l -1.21782,4.36807 h -1.30841 l -0.95112,-3.68367 -0.96621,-3.67362 h 1.22789 l 1.05175,4.28756 q 0.24659,1.03163 0.35227,1.82172 0.0553,-0.42776 0.16607,-0.95616 0.11066,-0.5284 0.20129,-0.85549 l 1.1977,-4.29763 h 1.19267 l 1.2279,4.31775 q 0.17613,0.59885 0.37239,1.79153 0.0755,-0.71964 0.36233,-1.83178 l 1.04673,-4.2775 h 1.21782 z\" id=\"path7779\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 379.43592,176.99057 h -1.18763 v -3.42199 q 0,-0.64415 -0.26169,-0.96119 -0.25664,-0.31704 -0.82026,-0.31704 -0.74479,0 -1.09705,0.44788 -0.34724,0.44285 -0.34724,1.48959 v 2.76275 h -1.1826 v -7.83033 h 1.1826 v 1.98777 q 0,0.47808 -0.0604,1.02157 h 0.0755 q 0.24156,-0.40259 0.66931,-0.62401 0.43278,-0.22143 1.00648,-0.22143 2.02299,0 2.02299,2.0381 z\" id=\"path7781\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 383.75208,176.99057 -0.23652,-0.77497 h -0.0403 q -0.40258,0.50826 -0.81021,0.69446 -0.40762,0.18116 -1.04673,0.18116 -0.82026,0 -1.28325,-0.44285 -0.45794,-0.44284 -0.45794,-1.25305 0,-0.86053 0.63912,-1.29834 0.6391,-0.43782 1.94751,-0.47808 l 0.96118,-0.0301 v -0.29692 q 0,-0.53342 -0.25162,-0.7951 -0.24659,-0.26672 -0.76995,-0.26672 -0.42775,0 -0.82027,0.12587 -0.39252,0.12586 -0.75486,0.2969 l -0.38245,-0.84544 q 0.45291,-0.23651 0.99137,-0.35729 0.53846,-0.12586 1.01653,-0.12586 1.06183,0 1.60029,0.46298 0.5435,0.46297 0.5435,1.45434 v 3.7491 z m -1.76131,-0.80517 q 0.64413,0 1.03162,-0.3573 0.39253,-0.36233 0.39253,-1.0115 v -0.4831 l -0.7146,0.0301 q -0.83537,0.0301 -1.21782,0.28181 -0.37743,0.24659 -0.37743,0.75989 0,0.3724 0.22142,0.57872 0.22142,0.20129 0.66428,0.20129 z\" id=\"path7783\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 388.0734,176.13508 q 0.43278,0 0.86556,-0.13588 v 0.89073 q -0.19625,0.0856 -0.50826,0.14091 -0.30698,0.0604 -0.63911,0.0604 -1.68081,0 -1.68081,-1.77138 v -2.99928 h -0.75988 v -0.52336 l 0.81524,-0.43279 0.40259,-1.17757 h 0.72969 v 1.23796 h 1.58519 v 0.89576 h -1.58519 v 2.97915 q 0,0.42775 0.21136,0.63408 0.21638,0.20129 0.56362,0.20129 z\" id=\"path7785\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 392.85199,174.05168 0.66931,-0.83537 1.68081,-1.79151 h 1.36377 l -2.23941,2.39036 2.38031,3.17541 h -1.38893 l -1.78649,-2.44069 -0.64917,0.53344 v 1.90725 h -1.17254 v -7.83033 h 1.17254 v 3.81955 l -0.0604,1.07189 z\" id=\"path7787\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 398.04544,176.99057 h -1.18261 v -5.56577 h 1.18261 z m -1.25306,-7.04025 q 0,-0.31704 0.17111,-0.48815 0.17613,-0.17109 0.4982,-0.17109 0.31201,0 0.4831,0.17109 0.17613,0.17111 0.17613,0.48815 0,0.30193 -0.17613,0.47806 -0.17109,0.17111 -0.4831,0.17111 -0.32207,0 -0.4982,-0.17111 -0.17111,-0.17613 -0.17111,-0.47806 z\" id=\"path7789\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 404.04731,176.99057 h -1.18764 v -3.42199 q 0,-0.64415 -0.26168,-0.96119 -0.25665,-0.31704 -0.82026,-0.31704 -0.74983,0 -1.09707,0.44286 -0.34722,0.44285 -0.34722,1.48454 v 2.77282 h -1.1826 v -5.56577 h 0.92595 l 0.16606,0.72969 h 0.0604 q 0.25163,-0.39756 0.7146,-0.61395 0.46297,-0.2164 1.0266,-0.2164 2.00287,0 2.00287,2.0381 z\" id=\"path7791\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 406.75816,177.09122 q -1.04171,0 -1.62545,-0.75485 -0.58376,-0.75485 -0.58376,-2.11862 0,-1.3688 0.58878,-2.12869 0.59383,-0.76492 1.64055,-0.76492 1.09706,0 1.67074,0.81021 h 0.0604 q -0.0856,-0.59885 -0.0856,-0.94607 v -2.02804 h 1.18764 v 7.83033 h -0.92596 l -0.20632,-0.72968 h -0.0553 q -0.56866,0.83033 -1.66571,0.83033 z m 0.31704,-0.95614 q 0.72969,0 1.06182,-0.40763 0.33213,-0.41265 0.3422,-1.33357 v -0.16606 q 0,-1.05176 -0.3422,-1.49461 -0.3422,-0.44286 -1.07189,-0.44286 -0.62401,0 -0.96119,0.50828 -0.33715,0.50323 -0.33715,1.43925 0,0.92595 0.32709,1.41409 0.3271,0.48311 0.98132,0.48311 z\" id=\"path7793\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 418.40289,174.19762 q 0,1.36377 -0.69951,2.12868 -0.69949,0.76492 -1.94751,0.76492 -0.78001,0 -1.37887,-0.35226 -0.59885,-0.35227 -0.92091,-1.01151 -0.32208,-0.65924 -0.32208,-1.52983 0,-1.35371 0.69446,-2.11359 0.69447,-0.75989 1.9576,-0.75989 1.20775,0 1.91229,0.78003 0.70453,0.77497 0.70453,2.09345 z m -4.05105,0 q 0,1.92739 1.42416,1.92739 1.40905,0 1.40905,-1.92739 0,-1.90727 -1.41912,-1.90727 -0.74478,0 -1.08195,0.49318 -0.33214,0.49317 -0.33214,1.41409 z\" id=\"path7795\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 421.98948,172.32055 h -1.35874 v 4.67002 h -1.18763 v -4.67002 h -0.91589 v -0.55356 l 0.91589,-0.36233 v -0.36233 q 0,-0.98633 0.46297,-1.45937 0.46298,-0.47808 1.41409,-0.47808 0.62402,0 1.22789,0.20632 l -0.312,0.89577 q -0.43781,-0.1409 -0.83537,-0.1409 -0.40258,0 -0.58878,0.25161 -0.18117,0.24658 -0.18117,0.74478 v 0.36234 h 1.35874 z\" id=\"path7797\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 356.24114,189.01453 h -1.39396 l -2.30985,-3.33141 -0.70957,0.57872 v 2.75269 h -1.20273 v -7.35729 h 1.20273 v 3.51257 q 0.49317,-0.60387 0.98132,-1.16247 l 1.98777,-2.3501 h 1.36881 q -1.9274,2.26455 -2.76277,3.22574 z\" id=\"path7800\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 361.28846,189.01453 -0.16607,-0.72968 h -0.0604 q -0.24659,0.38748 -0.70453,0.6089 -0.45292,0.22143 -1.03666,0.22143 -1.01151,0 -1.50971,-0.50324 -0.49821,-0.50323 -0.49821,-1.5248 v -3.63839 h 1.19268 v 3.43206 q 0,0.63912 0.26168,0.96118 0.26168,0.31704 0.82026,0.31704 0.7448,0 1.09202,-0.44285 0.35227,-0.44788 0.35227,-1.49461 v -2.77282 h 1.18764 v 5.56578 z\" id=\"path7802\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 365.93675,183.3481 q 1.04169,0 1.62041,0.75485 0.58376,0.75487 0.58376,2.11862 0,1.36881 -0.58879,2.13373 -0.58878,0.75988 -1.63551,0.75988 -1.0568,0 -1.64054,-0.75988 h -0.0805 l -0.21638,0.65923 h -0.88571 v -7.83033 h 1.18261 v 1.86197 q 0,0.20632 -0.0201,0.61394 -0.0201,0.40761 -0.0301,0.51833 h 0.0503 q 0.56363,-0.83034 1.66068,-0.83034 z m -0.30697,0.96621 q -0.7146,0 -1.03164,0.42272 -0.312,0.41769 -0.32206,1.40404 v 0.0805 q 0,1.01654 0.32206,1.47449 0.32208,0.4529 1.05176,0.4529 0.62905,0 0.95112,-0.49819 0.3271,-0.49822 0.3271,-1.43925 0,-1.89721 -1.29834,-1.89721 z\" id=\"path7804\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 371.25447,189.11518 q -1.29834,0 -2.03307,-0.75485 -0.72969,-0.75989 -0.72969,-2.08842 0,-1.36377 0.67937,-2.14379 0.67937,-0.78002 1.86699,-0.78002 1.10209,0 1.7412,0.6693 0.63912,0.66931 0.63912,1.84185 v 0.63911 h -3.70885 q 0.0252,0.81021 0.43781,1.24802 0.41266,0.43279 1.16248,0.43279 0.49316,0 0.91588,-0.0905 0.42776,-0.0956 0.91589,-0.31201 v 0.96119 q -0.43279,0.20632 -0.87562,0.29188 -0.44286,0.0856 -1.01151,0.0856 z m -0.2164,-4.87132 q -0.56361,0 -0.90581,0.3573 -0.33717,0.3573 -0.4026,1.04169 h 2.52625 q -0.0107,-0.68942 -0.33213,-1.04169 -0.32208,-0.3573 -0.88571,-0.3573 z\" id=\"path7806\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 377.37724,183.3481 q 0.3573,0 0.58879,0.0503 l -0.11573,1.10207 q -0.25162,-0.0604 -0.52336,-0.0604 -0.70956,0 -1.15241,0.46298 -0.43782,0.46298 -0.43782,1.20274 v 2.90869 h -1.18261 v -5.56578 h 0.92596 l 0.156,0.98131 h 0.0604 q 0.27679,-0.4982 0.71963,-0.79008 0.44787,-0.29188 0.96118,-0.29188 z\" id=\"path7808\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 382.88258,189.01453 h -1.18764 v -3.422 q 0,-0.64414 -0.26168,-0.96118 -0.25665,-0.31704 -0.82028,-0.31704 -0.74982,0 -1.09705,0.44285 -0.34724,0.44285 -0.34724,1.48455 v 2.77282 h -1.18259 v -5.56578 h 0.92595 l 0.16607,0.72969 h 0.0604 q 0.25161,-0.39756 0.71458,-0.61394 0.46299,-0.2164 1.02661,-0.2164 2.00288,0 2.00288,2.0381 z\" id=\"path7810\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 386.14697,189.11518 q -1.29835,0 -2.03306,-0.75485 -0.7297,-0.75989 -0.7297,-2.08842 0,-1.36377 0.67936,-2.14379 0.67937,-0.78002 1.86701,-0.78002 1.10208,0 1.7412,0.6693 0.6391,0.66931 0.6391,1.84185 v 0.63911 h -3.70884 q 0.0252,0.81021 0.43781,1.24802 0.41265,0.43279 1.16248,0.43279 0.49317,0 0.91589,-0.0905 0.42774,-0.0956 0.91588,-0.31201 v 0.96119 q -0.43278,0.20632 -0.87563,0.29188 -0.44285,0.0856 -1.0115,0.0856 z m -0.21639,-4.87132 q -0.56362,0 -0.90582,0.3573 -0.33718,0.3573 -0.40259,1.04169 h 2.52624 q -0.0107,-0.68942 -0.33214,-1.04169 -0.32206,-0.3573 -0.88569,-0.3573 z\" id=\"path7812\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 391.51993,188.15903 q 0.43277,0 0.86556,-0.13588 v 0.89074 q -0.19626,0.0856 -0.50827,0.1409 -0.30697,0.0604 -0.6391,0.0604 -1.68081,0 -1.68081,-1.77138 v -2.99929 h -0.75988 v -0.52336 l 0.81524,-0.43278 0.40258,-1.17757 h 0.72969 v 1.23796 h 1.5852 v 0.89575 h -1.5852 v 2.97916 q 0,0.42774 0.21136,0.63407 0.21639,0.2013 0.56363,0.2013 z\" id=\"path7814\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 394.73203,189.11518 q -1.29835,0 -2.03307,-0.75485 -0.72969,-0.75989 -0.72969,-2.08842 0,-1.36377 0.67936,-2.14379 0.67937,-0.78002 1.86701,-0.78002 1.10209,0 1.7412,0.6693 0.6391,0.66931 0.6391,1.84185 v 0.63911 h -3.70884 q 0.0252,0.81021 0.43781,1.24802 0.41265,0.43279 1.16248,0.43279 0.49317,0 0.91589,-0.0905 0.42774,-0.0956 0.91589,-0.31201 v 0.96119 q -0.43279,0.20632 -0.87564,0.29188 -0.44284,0.0856 -1.0115,0.0856 z m -0.21639,-4.87132 q -0.56362,0 -0.90582,0.3573 -0.33718,0.3573 -0.40259,1.04169 h 2.52623 q -0.0107,-0.68942 -0.33213,-1.04169 -0.32206,-0.3573 -0.88569,-0.3573 z\" id=\"path7816\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 401.77069,187.42934 q 0,0.81524 -0.59381,1.25305 -0.59381,0.43279 -1.70093,0.43279 -1.11216,0 -1.78649,-0.33717 v -1.02156 q 0.9813,0.4529 1.82674,0.4529 1.09203,0 1.09203,-0.65923 0,-0.21136 -0.1208,-0.35227 -0.1208,-0.14091 -0.39755,-0.29188 -0.27679,-0.15096 -0.76996,-0.3422 -0.96117,-0.37238 -1.30337,-0.74478 -0.33717,-0.37239 -0.33717,-0.96621 0,-0.7146 0.57369,-1.10712 0.57872,-0.39756 1.57009,-0.39756 0.9813,0 1.85694,0.39756 l -0.38246,0.89073 q -0.90079,-0.3724 -1.51473,-0.3724 -0.93603,0 -0.93603,0.53343 0,0.26169 0.24156,0.44285 0.24659,0.18116 1.06685,0.4982 0.68944,0.26672 1.00144,0.48814 0.31201,0.22143 0.46299,0.51329 0.15096,0.28686 0.15096,0.68944 z\" id=\"path7818\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 408.28421,189.11518 q -1.26312,0 -1.92236,-0.73472 -0.65421,-0.73976 -0.65421,-2.11862 0,-1.40402 0.6844,-2.15889 0.68944,-0.75485 1.98778,-0.75485 0.88066,0 1.5852,0.32711 l -0.35731,0.95111 q -0.74981,-0.29188 -1.23796,-0.29188 -1.44429,0 -1.44429,1.91733 0,0.93601 0.35731,1.40907 0.36233,0.46799 1.0568,0.46799 0.79007,0 1.49459,-0.39251 v 1.03163 q -0.31704,0.18619 -0.67936,0.26671 -0.3573,0.0805 -0.87059,0.0805 z\" id=\"path7820\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 412.3754,189.01453 h -1.1826 v -7.83033 h 1.1826 z\" id=\"path7822\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 417.40604,189.01453 -0.16608,-0.72968 h -0.0604 q -0.24659,0.38748 -0.70453,0.6089 -0.45291,0.22143 -1.03667,0.22143 -1.01149,0 -1.5097,-0.50324 -0.4982,-0.50323 -0.4982,-1.5248 v -3.63839 h 1.19266 v 3.43206 q 0,0.63912 0.26168,0.96118 0.2617,0.31704 0.82028,0.31704 0.74479,0 1.09202,-0.44285 0.35227,-0.44788 0.35227,-1.49461 v -2.77282 h 1.18764 v 5.56578 z\" id=\"path7824\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 422.95009,187.42934 q 0,0.81524 -0.59383,1.25305 -0.59381,0.43279 -1.70092,0.43279 -1.11216,0 -1.78649,-0.33717 v -1.02156 q 0.9813,0.4529 1.82674,0.4529 1.09202,0 1.09202,-0.65923 0,-0.21136 -0.1208,-0.35227 -0.1208,-0.14091 -0.39756,-0.29188 -0.27678,-0.15096 -0.76994,-0.3422 -0.96119,-0.37238 -1.30338,-0.74478 -0.33718,-0.37239 -0.33718,-0.96621 0,-0.7146 0.57369,-1.10712 0.57872,-0.39756 1.57009,-0.39756 0.98132,0 1.85695,0.39756 l -0.38247,0.89073 q -0.90078,-0.3724 -1.51473,-0.3724 -0.93602,0 -0.93602,0.53343 0,0.26169 0.24156,0.44285 0.24658,0.18116 1.06685,0.4982 0.68943,0.26672 1.00143,0.48814 0.31202,0.22143 0.46299,0.51329 0.15097,0.28686 0.15097,0.68944 z\" id=\"path7826\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 426.43756,188.15903 q 0.43279,0 0.86557,-0.13588 v 0.89074 q -0.19626,0.0856 -0.50828,0.1409 -0.30697,0.0604 -0.6391,0.0604 -1.68081,0 -1.68081,-1.77138 v -2.99929 h -0.75988 v -0.52336 l 0.81524,-0.43278 0.40258,-1.17757 h 0.7297 v 1.23796 h 1.58519 v 0.89575 h -1.58519 v 2.97916 q 0,0.42774 0.21136,0.63407 0.21639,0.2013 0.56362,0.2013 z\" id=\"path7828\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 429.64967,189.11518 q -1.29835,0 -2.03307,-0.75485 -0.72969,-0.75989 -0.72969,-2.08842 0,-1.36377 0.67937,-2.14379 0.67937,-0.78002 1.86699,-0.78002 1.10209,0 1.7412,0.6693 0.6391,0.66931 0.6391,1.84185 v 0.63911 h -3.70883 q 0.0252,0.81021 0.43782,1.24802 0.41265,0.43279 1.16246,0.43279 0.49317,0 0.91589,-0.0905 0.42776,-0.0956 0.91589,-0.31201 v 0.96119 q -0.43278,0.20632 -0.87562,0.29188 -0.44286,0.0856 -1.01151,0.0856 z m -0.2164,-4.87132 q -0.56361,0 -0.90582,0.3573 -0.33716,0.3573 -0.40259,1.04169 h 2.52625 q -0.0107,-0.68942 -0.33213,-1.04169 -0.32208,-0.3573 -0.88571,-0.3573 z\" id=\"path7830\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 435.77244,183.3481 q 0.3573,0 0.58879,0.0503 l -0.11573,1.10207 q -0.25162,-0.0604 -0.52336,-0.0604 -0.70957,0 -1.15241,0.46298 -0.43782,0.46298 -0.43782,1.20274 v 2.90869 h -1.18261 v -5.56578 h 0.92596 l 0.156,0.98131 h 0.0604 q 0.27679,-0.4982 0.71963,-0.79008 0.44788,-0.29188 0.96118,-0.29188 z\" id=\"path7832\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 364.40026,201.13916 q -1.04169,0 -1.62545,-0.75486 -0.58374,-0.75485 -0.58374,-2.11861 0,-1.36881 0.58878,-2.12869 0.59381,-0.76492 1.64055,-0.76492 1.09705,0 1.67074,0.81021 h 0.0604 q -0.0856,-0.59885 -0.0856,-0.94609 v -2.02803 h 1.18764 v 7.83034 h -0.92596 l -0.20632,-0.72969 h -0.0553 q -0.56865,0.83034 -1.66571,0.83034 z m 0.31704,-0.95616 q 0.72969,0 1.06183,-0.40761 0.33214,-0.41265 0.34221,-1.33357 v -0.16608 q 0,-1.05176 -0.34221,-1.49459 -0.3422,-0.44286 -1.0719,-0.44286 -0.62401,0 -0.96117,0.50827 -0.33717,0.50324 -0.33717,1.43925 0,0.92596 0.32711,1.41409 0.3271,0.4831 0.9813,0.4831 z\" id=\"path7835\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 373.19019,198.24556 q 0,1.36377 -0.69949,2.12868 -0.69951,0.76492 -1.94753,0.76492 -0.78001,0 -1.37887,-0.35226 -0.59885,-0.35227 -0.92091,-1.01151 -0.32207,-0.65924 -0.32207,-1.52983 0,-1.35371 0.69447,-2.1136 0.69446,-0.75988 1.95758,-0.75988 1.20775,0 1.91229,0.78001 0.70453,0.77499 0.70453,2.09347 z m -4.05105,0 q 0,1.92739 1.42416,1.92739 1.40906,0 1.40906,-1.92739 0,-1.90727 -1.41913,-1.90727 -0.74478,0 -1.08195,0.49318 -0.33214,0.49317 -0.33214,1.41409 z\" id=\"path7837\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 375.99321,195.47272 h 1.28827 l 1.13228,3.15529 q 0.25665,0.67434 0.3422,1.26815 h 0.0403 q 0.0453,-0.27677 0.16606,-0.6693 0.1208,-0.39756 1.27821,-3.75414 h 1.27823 l -2.3803,6.30555 q -0.64919,1.73615 -2.16392,1.73615 -0.39252,0 -0.76492,-0.0856 v -0.93602 q 0.26672,0.0604 0.60892,0.0604 0.85549,0 1.20273,-0.99139 l 0.20632,-0.52335 z\" id=\"path7839\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 386.92843,198.24556 q 0,1.36377 -0.69949,2.12868 -0.6995,0.76492 -1.94753,0.76492 -0.78001,0 -1.37886,-0.35226 -0.59884,-0.35227 -0.92092,-1.01151 -0.32206,-0.65924 -0.32206,-1.52983 0,-1.35371 0.69446,-2.1136 0.69447,-0.75988 1.95758,-0.75988 1.20777,0 1.91229,0.78001 0.70453,0.77499 0.70453,2.09347 z m -4.05104,0 q 0,1.92739 1.42416,1.92739 1.40906,0 1.40906,-1.92739 0,-1.90727 -1.41913,-1.90727 -0.74479,0 -1.08196,0.49318 -0.33213,0.49317 -0.33213,1.41409 z\" id=\"path7841\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 391.6473,201.03851 -0.16607,-0.72969 h -0.0604 q -0.24658,0.38749 -0.70453,0.60892 -0.4529,0.22142 -1.03666,0.22142 -1.01151,0 -1.5097,-0.50324 -0.4982,-0.50324 -0.4982,-1.52481 v -3.63839 h 1.19266 v 3.43207 q 0,0.63911 0.26168,0.96117 0.26169,0.31704 0.82028,0.31704 0.74478,0 1.09202,-0.44283 0.35227,-0.44788 0.35227,-1.49461 v -2.77284 h 1.18762 v 5.56579 z\" id=\"path7843\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 401.20357,201.03851 h -1.18764 v -3.42201 q 0,-0.64413 -0.26168,-0.96117 -0.25665,-0.31704 -0.82027,-0.31704 -0.74479,0 -1.09705,0.44788 -0.34723,0.44285 -0.34723,1.48957 v 2.76277 h -1.18261 v -7.83034 h 1.18261 v 1.98778 q 0,0.47808 -0.0604,1.02157 h 0.0755 q 0.24154,-0.40259 0.6693,-0.62401 0.43279,-0.22143 1.00647,-0.22143 2.023,0 2.023,2.0381 z\" id=\"path7845\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 405.51977,201.03851 -0.23652,-0.77499 h -0.0403 q -0.40259,0.50827 -0.8102,0.69447 -0.40763,0.18117 -1.04673,0.18117 -0.82028,0 -1.28325,-0.44285 -0.45795,-0.44285 -0.45795,-1.25305 0,-0.86053 0.63911,-1.29836 0.6391,-0.43781 1.94751,-0.47806 l 0.96119,-0.0301 v -0.2969 q 0,-0.53343 -0.25162,-0.79512 -0.24658,-0.26671 -0.76995,-0.26671 -0.42775,0 -0.82027,0.12587 -0.39253,0.12573 -0.75485,0.29691 l -0.38247,-0.84544 q 0.45292,-0.23652 0.99138,-0.35729 0.53846,-0.12587 1.01654,-0.12587 1.06182,0 1.60029,0.46297 0.54349,0.46299 0.54349,1.45436 v 3.7491 z m -1.76133,-0.80517 q 0.64415,0 1.03164,-0.35731 0.39252,-0.36232 0.39252,-1.0115 v -0.48311 l -0.71458,0.0301 q -0.83538,0.0301 -1.21784,0.28181 -0.37743,0.24658 -0.37743,0.75988 0,0.37239 0.22143,0.57873 0.22143,0.20129 0.66426,0.20129 z\" id=\"path7847\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 409.03579,201.03851 -2.11359,-5.56579 h 1.24802 l 1.13228,3.23581 q 0.29188,0.81524 0.35226,1.31847 h 0.0403 q 0.0453,-0.36233 0.35226,-1.31847 l 1.13228,-3.23581 h 1.25809 l -2.12366,5.56579 z\" id=\"path7849\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 415.35144,201.13916 q -1.29834,0 -2.03306,-0.75486 -0.72969,-0.75988 -0.72969,-2.08842 0,-1.36377 0.67936,-2.14379 0.67937,-0.78001 1.86701,-0.78001 1.10209,0 1.74119,0.66931 0.63911,0.6693 0.63911,1.84183 v 0.63911 h -3.70885 q 0.0252,0.81021 0.43781,1.24802 0.41266,0.43279 1.16248,0.43279 0.49317,0 0.91589,-0.0905 0.42775,-0.0956 0.91589,-0.312 v 0.96119 q -0.43278,0.20632 -0.87563,0.29187 -0.44284,0.0856 -1.01151,0.0856 z m -0.21638,-4.87132 q -0.56363,0 -0.90583,0.35729 -0.33717,0.35731 -0.40258,1.04171 h 2.52623 q -0.0107,-0.68944 -0.33213,-1.04171 -0.32207,-0.35729 -0.88569,-0.35729 z\" id=\"path7851\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 419.22979,198.80414 v -0.32207 q 0,-0.55355 0.20129,-0.92091 0.2013,-0.36736 0.70454,-0.75989 0.59885,-0.47304 0.76994,-0.73472 0.17613,-0.26168 0.17613,-0.62401 0,-0.42272 -0.28181,-0.64918 -0.28181,-0.22645 -0.8102,-0.22645 -0.47808,0 -0.8857,0.13587 -0.40761,0.13588 -0.79511,0.3271 l -0.42271,-0.88569 q 1.02157,-0.56866 2.18907,-0.56866 0.98634,0 1.56506,0.4831 0.57872,0.48311 0.57872,1.33359 0,0.37742 -0.11067,0.67433 -0.11066,0.29188 -0.33715,0.55858 -0.22143,0.26672 -0.76996,0.69447 -0.468,0.36736 -0.62904,0.60892 -0.156,0.24154 -0.156,0.64917 v 0.22645 z m -0.20633,1.60533 q 0,-0.75989 0.73976,-0.75989 0.36233,0 0.55356,0.20129 0.19124,0.19627 0.19124,0.5586 0,0.35729 -0.19627,0.56865 -0.19123,0.20632 -0.54853,0.20632 -0.3573,0 -0.54852,-0.20129 -0.19124,-0.20632 -0.19124,-0.57368 z\" id=\"path7853\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> </g> <g id=\"g12983\"> <path d=\"m 321.07885,508.49509 h -1.30842 l -1.24803,-4.38822 q -0.0805,-0.28684 -0.20129,-0.8253 -0.1208,-0.5435 -0.14593,-0.75486 -0.0503,0.32207 -0.16607,0.83538 -0.11066,0.5133 -0.1862,0.76491 l -1.21782,4.36809 h -1.30841 l -0.95112,-3.68369 -0.96621,-3.67362 h 1.22789 l 1.05176,4.28757 q 0.24658,1.03163 0.35226,1.82171 0.0553,-0.42774 0.16607,-0.95614 0.11067,-0.5284 0.20129,-0.85551 l 1.19771,-4.29763 h 1.19266 l 1.2279,4.31777 q 0.17614,0.59885 0.37239,1.79151 0.0755,-0.71962 0.36233,-1.83178 l 1.04673,-4.2775 h 1.21783 z\" id=\"path7856\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 328.77964,508.49509 h -1.18763 v -3.42201 q 0,-0.64413 -0.26169,-0.96117 -0.25664,-0.31704 -0.82027,-0.31704 -0.74478,0 -1.09705,0.44788 -0.34724,0.44284 -0.34724,1.48957 v 2.76277 h -1.1826 v -7.83034 h 1.1826 v 1.98778 q 0,0.47806 -0.0604,1.02157 h 0.0755 q 0.24156,-0.4026 0.6693,-0.62401 0.43279,-0.22143 1.00648,-0.22143 2.02301,0 2.02301,2.0381 z\" id=\"path7858\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 333.09579,508.49509 -0.23652,-0.77499 h -0.0403 q -0.40259,0.50827 -0.81021,0.69447 -0.40763,0.18116 -1.04673,0.18116 -0.82027,0 -1.28325,-0.44284 -0.45795,-0.44285 -0.45795,-1.25307 0,-0.86053 0.63912,-1.29834 0.6391,-0.43781 1.94751,-0.47807 l 0.96119,-0.0301 v -0.2969 q 0,-0.53343 -0.25163,-0.79512 -0.24658,-0.26671 -0.76994,-0.26671 -0.42775,0 -0.82028,0.12573 -0.39252,0.12587 -0.75485,0.29692 l -0.38245,-0.84543 q 0.4529,-0.23652 0.99137,-0.35731 0.53846,-0.12573 1.01653,-0.12573 1.06182,0 1.60029,0.46297 0.54349,0.46297 0.54349,1.45436 v 3.74909 z m -1.76131,-0.80519 q 0.64413,0 1.03162,-0.35729 0.39253,-0.36233 0.39253,-1.0115 V 505.838 l -0.71459,0.0301 q -0.83537,0.0301 -1.21783,0.28182 -0.37742,0.24658 -0.37742,0.75987 0,0.3724 0.22141,0.57872 0.22143,0.2013 0.66428,0.2013 z\" id=\"path7860\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 337.417,507.63958 q 0.43277,0 0.86555,-0.13586 v 0.89071 q -0.19626,0.0856 -0.50826,0.14091 -0.30697,0.0604 -0.63911,0.0604 -1.68081,0 -1.68081,-1.77138 v -2.99929 h -0.75989 v -0.52336 l 0.81525,-0.43278 0.40259,-1.17757 h 0.72969 v 1.23795 h 1.58518 v 0.89576 h -1.58518 v 2.97915 q 0,0.42776 0.21136,0.63408 0.21639,0.2013 0.56363,0.2013 z\" id=\"path7862\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 342.19573,505.55619 0.66931,-0.83537 1.68079,-1.79152 h 1.36377 l -2.23939,2.39037 2.3803,3.17542 h -1.38893 l -1.78648,-2.44069 -0.64918,0.53342 v 1.90727 h -1.17253 v -7.83034 h 1.17253 v 3.81955 l -0.0604,1.07189 z\" id=\"path7864\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 347.3892,508.49509 h -1.18261 v -5.56579 h 1.18261 z m -1.25307,-7.04027 q 0,-0.31704 0.17111,-0.48813 0.17613,-0.1711 0.4982,-0.1711 0.31201,0 0.48311,0.1711 0.17613,0.17109 0.17613,0.48813 0,0.30195 -0.17613,0.47808 -0.1711,0.1711 -0.48311,0.1711 -0.32207,0 -0.4982,-0.1711 -0.17111,-0.17613 -0.17111,-0.47808 z\" id=\"path7866\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 353.3909,508.49509 h -1.18763 v -3.42201 q 0,-0.64413 -0.26168,-0.96117 -0.25666,-0.31704 -0.82028,-0.31704 -0.74981,0 -1.09705,0.44284 -0.34723,0.44285 -0.34723,1.48454 v 2.77284 h -1.18261 v -5.56579 h 0.92596 l 0.16607,0.72969 h 0.0604 q 0.25162,-0.39756 0.71459,-0.61394 0.46298,-0.21639 1.0266,-0.21639 2.00288,0 2.00288,2.0381 z\" id=\"path7868\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 356.10187,508.59573 q -1.0417,0 -1.62545,-0.75486 -0.58376,-0.75485 -0.58376,-2.11862 0,-1.36879 0.58879,-2.12867 0.59382,-0.76492 1.64055,-0.76492 1.09705,0 1.67073,0.81021 h 0.0604 q -0.0856,-0.59885 -0.0856,-0.94609 v -2.02803 h 1.18764 v 7.83034 h -0.92596 l -0.20632,-0.7297 h -0.0553 q -0.56865,0.83034 -1.6657,0.83034 z m 0.31704,-0.95615 q 0.72969,0 1.06182,-0.40761 0.33214,-0.41265 0.3422,-1.33358 v -0.16607 q 0,-1.05176 -0.3422,-1.49461 -0.3422,-0.44284 -1.07189,-0.44284 -0.62401,0 -0.96118,0.50827 -0.33716,0.50324 -0.33716,1.43925 0,0.92595 0.32709,1.41409 0.32711,0.4831 0.98132,0.4831 z\" id=\"path7870\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 367.7466,505.70213 q 0,1.36376 -0.6995,2.12868 -0.6995,0.76492 -1.94752,0.76492 -0.78001,0 -1.37886,-0.35227 -0.59885,-0.35225 -0.92092,-1.01149 -0.32208,-0.65924 -0.32208,-1.52984 0,-1.3537 0.69447,-2.11359 0.69446,-0.75988 1.95759,-0.75988 1.20776,0 1.91229,0.78001 0.70453,0.77499 0.70453,2.09346 z m -4.05104,0 q 0,1.92739 1.42415,1.92739 1.40905,0 1.40905,-1.92739 0,-1.90726 -1.41911,-1.90726 -0.74479,0 -1.08196,0.49317 -0.33213,0.49318 -0.33213,1.41409 z\" id=\"path7872\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 371.33307,503.82506 h -1.35874 v 4.67003 h -1.18763 v -4.67003 h -0.91589 v -0.55356 l 0.91589,-0.36232 v -0.36233 q 0,-0.98635 0.46298,-1.45939 0.46297,-0.47807 1.41409,-0.47807 0.62401,0 1.22789,0.20633 l -0.312,0.89576 q -0.43783,-0.14091 -0.83537,-0.14091 -0.40259,0 -0.58879,0.25161 -0.18117,0.24659 -0.18117,0.7448 v 0.36232 h 1.35874 z\" id=\"path7874\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 308.505,517.72594 q 0,1.36377 -0.69949,2.12869 -0.69949,0.76492 -1.94751,0.76492 -0.78003,0 -1.37887,-0.35227 -0.59885,-0.35226 -0.92093,-1.0115 -0.32206,-0.65924 -0.32206,-1.52984 0,-1.3537 0.69446,-2.11358 0.69447,-0.75989 1.95758,-0.75989 1.20777,0 1.9123,0.78001 0.70452,0.77499 0.70452,2.09346 z m -4.05104,0 q 0,1.9274 1.42416,1.9274 1.40906,0 1.40906,-1.9274 0,-1.90726 -1.41913,-1.90726 -0.74479,0 -1.08195,0.49317 -0.33214,0.49318 -0.33214,1.41409 z\" id=\"path7877\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 312.12167,520.61955 q -1.05679,0 -1.64055,-0.75989 h -0.0704 q 0.0704,0.70453 0.0704,0.8555 v 2.27965 h -1.1826 v -8.04169 h 0.95614 q 0.0403,0.156 0.16607,0.74479 h 0.0604 q 0.55356,-0.84544 1.66068,-0.84544 1.0417,0 1.62042,0.75485 0.58376,0.75485 0.58376,2.11862 0,1.36377 -0.59383,2.12869 -0.58878,0.76492 -1.63047,0.76492 z m -0.28685,-4.80087 q -0.70452,0 -1.03162,0.41265 -0.32208,0.41266 -0.32208,1.31848 v 0.17613 q 0,1.01653 0.32208,1.47448 0.32206,0.45292 1.05175,0.45292 0.61395,0 0.94608,-0.50324 0.33215,-0.50324 0.33215,-1.43422 0,-0.93601 -0.33215,-1.41409 -0.32709,-0.48311 -0.96621,-0.48311 z\" id=\"path7879\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 317.45942,520.61955 q -1.29834,0 -2.03308,-0.75485 -0.72969,-0.75989 -0.72969,-2.08844 0,-1.36375 0.67937,-2.14378 0.67938,-0.78001 1.867,-0.78001 1.10209,0 1.7412,0.66931 0.63911,0.6693 0.63911,1.84183 v 0.63912 h -3.70884 q 0.0252,0.8102 0.43781,1.24801 0.41265,0.43279 1.16248,0.43279 0.49316,0 0.91588,-0.0905 0.42776,-0.0956 0.91589,-0.31201 v 0.96118 q -0.43279,0.20632 -0.87563,0.29187 -0.44285,0.0856 -1.0115,0.0856 z m -0.2164,-4.87132 q -0.56361,0 -0.90581,0.35729 -0.33717,0.35731 -0.4026,1.0417 h 2.52625 q -0.0107,-0.68943 -0.33214,-1.0417 -0.32207,-0.35729 -0.8857,-0.35729 z\" id=\"path7881\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 323.58219,514.85247 q 0.35729,0 0.58879,0.0503 l -0.11574,1.10209 q -0.25161,-0.0604 -0.52336,-0.0604 -0.70955,0 -1.15241,0.46297 -0.43781,0.46297 -0.43781,1.20273 v 2.9087 h -1.18261 v -5.56577 h 0.92596 l 0.156,0.9813 h 0.0604 q 0.27678,-0.4982 0.71962,-0.79008 0.4479,-0.29188 0.96119,-0.29188 z\" id=\"path7883\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 327.67341,520.5189 -0.23652,-0.77499 h -0.0403 q -0.4026,0.50828 -0.81021,0.69447 -0.40763,0.18117 -1.04673,0.18117 -0.82028,0 -1.28325,-0.44285 -0.45795,-0.44285 -0.45795,-1.25305 0,-0.86053 0.63911,-1.29836 0.63912,-0.43781 1.94753,-0.47807 l 0.96117,-0.0301 v -0.2969 q 0,-0.53343 -0.25161,-0.79511 -0.24659,-0.26672 -0.76995,-0.26672 -0.42776,0 -0.82028,0.12587 -0.39252,0.12586 -0.75485,0.2969 l -0.38246,-0.84543 q 0.45291,-0.23652 0.99138,-0.3573 0.53845,-0.12586 1.01653,-0.12586 1.06182,0 1.60029,0.46297 0.54349,0.46298 0.54349,1.45436 v 3.74909 z m -1.76132,-0.80517 q 0.64413,0 1.03163,-0.35731 0.39251,-0.36232 0.39251,-1.01149 v -0.48311 l -0.71458,0.0301 q -0.83537,0.0301 -1.21784,0.28181 -0.37742,0.24659 -0.37742,0.75989 0,0.37239 0.22142,0.57872 0.22143,0.20129 0.66428,0.20129 z\" id=\"path7885\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 331.9946,519.66341 q 0.43278,0 0.86557,-0.13588 v 0.89073 q -0.19627,0.0856 -0.50827,0.1409 -0.30697,0.0604 -0.63912,0.0604 -1.68079,0 -1.68079,-1.77139 v -2.99928 h -0.75989 v -0.52337 l 0.81523,-0.43278 0.4026,-1.17756 h 0.7297 v 1.23796 h 1.58518 v 0.89575 h -1.58518 v 2.97916 q 0,0.42774 0.21134,0.63406 0.2164,0.20131 0.56363,0.20131 z\" id=\"path7887\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 333.95866,520.5189 h -1.1826 v -5.56578 h 1.1826 z m -1.25305,-7.04027 q 0,-0.31702 0.1711,-0.48813 0.17614,-0.1711 0.4982,-0.1711 0.312,0 0.48311,0.1711 0.17613,0.17111 0.17613,0.48813 0,0.30195 -0.17613,0.47808 -0.17111,0.17111 -0.48311,0.17111 -0.32206,0 -0.4982,-0.17111 -0.1711,-0.17613 -0.1711,-0.47808 z\" id=\"path7889\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 339.96068,520.5189 h -1.18763 v -3.422 q 0,-0.64414 -0.26168,-0.96118 -0.25666,-0.31704 -0.82028,-0.31704 -0.74983,0 -1.09705,0.44285 -0.34723,0.44284 -0.34723,1.48455 v 2.77282 h -1.18261 v -5.56578 h 0.92596 l 0.16607,0.7297 h 0.0604 q 0.25161,-0.39756 0.71459,-0.61396 0.46298,-0.21639 1.0266,-0.21639 2.00288,0 2.00288,2.0381 z\" id=\"path7891\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 345.49467,514.95312 v 0.64918 l -0.95112,0.17613 q 0.1308,0.17613 0.2164,0.43277 0.0856,0.25665 0.0856,0.54351 0,0.86053 -0.59381,1.35369 -0.59383,0.49317 -1.63552,0.49317 -0.26672,0 -0.4831,-0.0403 -0.38247,0.23652 -0.38247,0.55356 0,0.19123 0.17614,0.28684 0.18117,0.0956 0.65923,0.0956 h 0.97125 q 0.92092,0 1.39899,0.39253 0.47808,0.39252 0.47808,1.13228 0,0.94608 -0.78001,1.45938 -0.78003,0.51329 -2.25451,0.51329 -1.1373,0 -1.73615,-0.40258 -0.59885,-0.40259 -0.59885,-1.14737 0,-0.51331 0.32206,-0.86557 0.32711,-0.34723 0.91087,-0.48311 -0.23652,-0.10067 -0.39254,-0.32207 -0.15096,-0.22645 -0.15096,-0.47303 0,-0.31202 0.17614,-0.5284 0.17613,-0.21639 0.52336,-0.42775 -0.43279,-0.1862 -0.70454,-0.60389 -0.2667,-0.42272 -0.2667,-0.98633 0,-0.90583 0.56865,-1.40404 0.57369,-0.4982 1.63048,-0.4982 0.23652,0 0.49317,0.0352 0.26168,0.0303 0.39252,0.0655 z m -4.37311,6.43135 q 0,0.38245 0.3422,0.58878 0.34723,0.20632 0.97124,0.20632 0.96621,0 1.43925,-0.27677 0.47305,-0.27679 0.47305,-0.73473 0,-0.36232 -0.26169,-0.51833 -0.25664,-0.15098 -0.96117,-0.15098 h -0.89576 q -0.50827,0 -0.81021,0.23654 -0.29691,0.24154 -0.29691,0.64917 z m 0.50827,-4.62976 q 0,0.52335 0.26672,0.80517 0.27174,0.28181 0.77497,0.28181 1.02661,0 1.02661,-1.09705 0,-0.54349 -0.25666,-0.83537 -0.25162,-0.29691 -0.76995,-0.29691 -0.5133,0 -0.78001,0.29187 -0.26168,0.29188 -0.26168,0.85048 z\" id=\"path7893\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 353.11856,518.93371 q 0,0.81524 -0.59383,1.25305 -0.59381,0.43279 -1.70093,0.43279 -1.11215,0 -1.78649,-0.33717 v -1.02157 q 0.98131,0.45292 1.82675,0.45292 1.09202,0 1.09202,-0.65924 0,-0.21136 -0.1208,-0.35227 -0.1208,-0.14091 -0.39756,-0.29188 -0.27678,-0.15097 -0.76994,-0.3422 -0.96119,-0.3724 -1.30339,-0.74478 -0.33717,-0.3724 -0.33717,-0.96621 0,-0.7146 0.57369,-1.10712 0.57872,-0.39756 1.57009,-0.39756 0.98132,0 1.85694,0.39756 l -0.38245,0.89072 q -0.9008,-0.37239 -1.51474,-0.37239 -0.93603,0 -0.93603,0.53343 0,0.26168 0.24156,0.44285 0.24659,0.18116 1.06687,0.4982 0.68942,0.26672 1.00144,0.48813 0.31199,0.22143 0.46297,0.51331 0.15097,0.28683 0.15097,0.68943 z\" id=\"path7895\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 353.68726,514.95312 h 1.28829 l 1.13228,3.15528 q 0.25665,0.67434 0.3422,1.26815 h 0.0403 q 0.0453,-0.27677 0.16606,-0.6693 0.1208,-0.39755 1.27823,-3.75413 h 1.27821 l -2.38031,6.30553 q -0.64917,1.73616 -2.1639,1.73616 -0.39253,0 -0.76491,-0.0856 v -0.93601 q 0.2667,0.0604 0.6089,0.0604 0.8555,0 1.20274,-0.99137 l 0.20632,-0.52337 z\" id=\"path7897\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 363.42476,518.93371 q 0,0.81524 -0.59381,1.25305 -0.59383,0.43279 -1.70095,0.43279 -1.11214,0 -1.78647,-0.33717 v -1.02157 q 0.9813,0.45292 1.82674,0.45292 1.09202,0 1.09202,-0.65924 0,-0.21136 -0.1208,-0.35227 -0.1208,-0.14091 -0.39754,-0.29188 -0.27679,-0.15097 -0.76996,-0.3422 -0.96117,-0.3724 -1.30338,-0.74478 -0.33716,-0.3724 -0.33716,-0.96621 0,-0.7146 0.57369,-1.10712 0.57872,-0.39756 1.57009,-0.39756 0.9813,0 1.85694,0.39756 l -0.38246,0.89072 q -0.90079,-0.37239 -1.51475,-0.37239 -0.93601,0 -0.93601,0.53343 0,0.26168 0.24155,0.44285 0.24658,0.18116 1.06686,0.4982 0.68944,0.26672 1.00144,0.48813 0.31201,0.22143 0.46297,0.51331 0.15097,0.28683 0.15097,0.68943 z\" id=\"path7899\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 366.91224,519.66341 q 0.43277,0 0.86556,-0.13588 v 0.89073 q -0.19627,0.0856 -0.50826,0.1409 -0.30698,0.0604 -0.63911,0.0604 -1.68081,0 -1.68081,-1.77139 v -2.99928 h -0.75988 v -0.52337 l 0.81524,-0.43278 0.40259,-1.17756 h 0.72969 v 1.23796 h 1.58518 v 0.89575 h -1.58518 v 2.97916 q 0,0.42774 0.21136,0.63406 0.21638,0.20131 0.56362,0.20131 z\" id=\"path7901\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 370.12434,520.61955 q -1.29834,0 -2.03306,-0.75485 -0.72969,-0.75989 -0.72969,-2.08844 0,-1.36375 0.67936,-2.14378 0.67937,-0.78001 1.86701,-0.78001 1.10209,0 1.74119,0.66931 0.63911,0.6693 0.63911,1.84183 v 0.63912 h -3.70885 q 0.0252,0.8102 0.43781,1.24801 0.41266,0.43279 1.16248,0.43279 0.49317,0 0.91589,-0.0905 0.42775,-0.0956 0.91589,-0.31201 v 0.96118 q -0.43278,0.20632 -0.87563,0.29187 -0.44284,0.0856 -1.01151,0.0856 z m -0.21638,-4.87132 q -0.56363,0 -0.90583,0.35729 -0.33717,0.35731 -0.40258,1.0417 h 2.52623 q -0.0107,-0.68943 -0.33213,-1.0417 -0.32207,-0.35729 -0.88569,-0.35729 z\" id=\"path7903\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 378.11412,520.5189 h -1.18764 v -3.43206 q 0,-0.63911 -0.24154,-0.95112 -0.24156,-0.31704 -0.75485,-0.31704 -0.6844,0 -1.00648,0.44788 -0.31704,0.44285 -0.31704,1.47952 v 2.77282 h -1.1826 v -5.56578 h 0.92595 l 0.16608,0.7297 h 0.0604 q 0.23148,-0.39756 0.6693,-0.61396 0.44284,-0.21639 0.97124,-0.21639 1.28325,0 1.70093,0.87563 h 0.0805 q 0.24659,-0.41266 0.69447,-0.64414 0.44788,-0.23149 1.02659,-0.23149 0.99641,0 1.44932,0.50324 0.45795,0.50324 0.45795,1.53486 v 3.62833 h -1.1826 v -3.43206 q 0,-0.63911 -0.24659,-0.95112 -0.24156,-0.31704 -0.75485,-0.31704 -0.68944,0 -1.0115,0.43279 -0.31704,0.42774 -0.31704,1.31847 z\" id=\"path7905\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 313.74398,532.64352 q -1.0417,0 -1.62545,-0.75485 -0.58375,-0.75485 -0.58375,-2.11862 0,-1.3688 0.58879,-2.12868 0.59381,-0.76492 1.64054,-0.76492 1.09705,0 1.67074,0.8102 h 0.0604 q -0.0856,-0.59884 -0.0856,-0.94608 v -2.02803 h 1.18764 v 7.83034 h -0.92596 l -0.20632,-0.72969 h -0.0553 q -0.56865,0.83033 -1.66572,0.83033 z m 0.31703,-0.95614 q 0.7297,0 1.06184,-0.40763 0.33213,-0.41265 0.3422,-1.33357 v -0.16607 q 0,-1.05175 -0.3422,-1.49461 -0.34221,-0.44284 -1.07189,-0.44284 -0.62401,0 -0.96118,0.50827 -0.33718,0.50324 -0.33718,1.43925 0,0.92596 0.32711,1.41409 0.32711,0.48311 0.9813,0.48311 z\" id=\"path7908\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 322.53393,529.74993 q 0,1.36375 -0.69951,2.12867 -0.69949,0.76492 -1.94751,0.76492 -0.78001,0 -1.37887,-0.35227 -0.59885,-0.35226 -0.92091,-1.0115 -0.32208,-0.65924 -0.32208,-1.52982 0,-1.35371 0.69446,-2.1136 0.69447,-0.75988 1.95758,-0.75988 1.20777,0 1.91231,0.78002 0.70453,0.77498 0.70453,2.09346 z m -4.05105,0 q 0,1.92738 1.42416,1.92738 1.40905,0 1.40905,-1.92738 0,-1.90727 -1.41912,-1.90727 -0.74478,0 -1.08195,0.49318 -0.33214,0.49316 -0.33214,1.41409 z\" id=\"path7910\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 325.33692,526.97709 h 1.28828 l 1.13227,3.15529 q 0.25666,0.67433 0.3422,1.26816 h 0.0403 q 0.0453,-0.27679 0.16607,-0.66931 0.1208,-0.39756 1.27821,-3.75414 h 1.27822 l -2.3803,6.30553 q -0.64917,1.73617 -2.16392,1.73617 -0.39251,0 -0.76491,-0.0856 v -0.93602 q 0.26672,0.0604 0.60891,0.0604 0.8555,0 1.20273,-0.99137 l 0.20632,-0.52336 z\" id=\"path7912\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 336.27215,529.74993 q 0,1.36375 -0.6995,2.12867 -0.6995,0.76492 -1.94752,0.76492 -0.78002,0 -1.37887,-0.35227 -0.59884,-0.35226 -0.92091,-1.0115 -0.32207,-0.65924 -0.32207,-1.52982 0,-1.35371 0.69446,-2.1136 0.69447,-0.75988 1.95759,-0.75988 1.20777,0 1.91228,0.78002 0.70454,0.77498 0.70454,2.09346 z m -4.05105,0 q 0,1.92738 1.42416,1.92738 1.40906,0 1.40906,-1.92738 0,-1.90727 -1.41913,-1.90727 -0.74478,0 -1.08195,0.49318 -0.33214,0.49316 -0.33214,1.41409 z\" id=\"path7914\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 340.99089,532.54288 -0.16606,-0.72969 h -0.0604 q -0.24659,0.38749 -0.70453,0.6089 -0.45291,0.22143 -1.03667,0.22143 -1.0115,0 -1.5097,-0.50323 -0.4982,-0.50323 -0.4982,-1.52481 v -3.63839 h 1.19266 v 3.43208 q 0,0.6391 0.26168,0.96117 0.26168,0.31704 0.82028,0.31704 0.74479,0 1.09203,-0.44286 0.35225,-0.44788 0.35225,-1.49459 v -2.77284 h 1.18764 v 5.56579 z\" id=\"path7916\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 350.54732,532.54288 h -1.18763 v -3.42201 q 0,-0.64414 -0.26168,-0.96117 -0.25666,-0.31704 -0.82028,-0.31704 -0.74479,0 -1.09705,0.44788 -0.34723,0.44284 -0.34723,1.48957 v 2.76277 h -1.18261 v -7.83034 h 1.18261 v 1.98778 q 0,0.47807 -0.0604,1.02156 h 0.0755 q 0.24156,-0.40259 0.6693,-0.62401 0.43279,-0.22142 1.00647,-0.22142 2.02301,0 2.02301,2.03811 z\" id=\"path7918\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 354.86349,532.54288 -0.23652,-0.77499 h -0.0403 q -0.40259,0.50827 -0.8102,0.69447 -0.40762,0.18116 -1.04673,0.18116 -0.82028,0 -1.28325,-0.44284 -0.45794,-0.44285 -0.45794,-1.25306 0,-0.86053 0.6391,-1.29835 0.63911,-0.43781 1.94753,-0.47808 l 0.96117,-0.0301 v -0.2969 q 0,-0.53344 -0.25161,-0.79512 -0.24659,-0.26671 -0.76996,-0.26671 -0.42775,0 -0.82027,0.12573 -0.39253,0.12587 -0.75485,0.29691 l -0.38246,-0.84542 q 0.45292,-0.23652 0.99137,-0.35731 0.53846,-0.12587 1.01654,-0.12587 1.06183,0 1.60029,0.46298 0.54349,0.46297 0.54349,1.45434 v 3.74911 z m -1.76133,-0.80518 q 0.64414,0 1.03163,-0.3573 0.39252,-0.36233 0.39252,-1.0115 v -0.48311 l -0.71458,0.0301 q -0.83537,0.0301 -1.21784,0.28181 -0.37742,0.24658 -0.37742,0.75988 0,0.3724 0.22142,0.57872 0.22143,0.20129 0.66427,0.20129 z\" id=\"path7920\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 358.3795,532.54288 -2.11359,-5.56579 h 1.24802 l 1.13228,3.23581 q 0.29188,0.81524 0.35227,1.31848 h 0.0403 q 0.0453,-0.36234 0.35227,-1.31848 l 1.13228,-3.23581 h 1.25809 l -2.12367,5.56579 z\" id=\"path7922\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 364.69515,532.64352 q -1.29834,0 -2.03306,-0.75485 -0.72969,-0.75988 -0.72969,-2.08842 0,-1.36377 0.67937,-2.14378 0.67936,-0.78002 1.867,-0.78002 1.10209,0 1.74119,0.6693 0.63911,0.6693 0.63911,1.84184 v 0.63911 h -3.70884 q 0.0252,0.81021 0.43781,1.24802 0.41265,0.43279 1.16247,0.43279 0.49318,0 0.9159,-0.0905 0.42774,-0.0956 0.91589,-0.312 v 0.96117 q -0.43279,0.20633 -0.87564,0.29188 -0.44284,0.0856 -1.01151,0.0856 z m -0.21638,-4.87131 q -0.56363,0 -0.90583,0.35729 -0.33717,0.3573 -0.40258,1.04169 h 2.52623 q -0.0107,-0.68942 -0.33213,-1.04169 -0.32207,-0.35729 -0.88569,-0.35729 z\" id=\"path7924\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 368.57351,530.30851 v -0.32206 q 0,-0.55356 0.20129,-0.92093 0.20129,-0.36736 0.70453,-0.75988 0.59885,-0.47304 0.76994,-0.73472 0.17614,-0.26169 0.17614,-0.62401 0,-0.42272 -0.28182,-0.64919 -0.28181,-0.22645 -0.81019,-0.22645 -0.47808,0 -0.88571,0.13588 -0.40761,0.13587 -0.7951,0.3271 l -0.42272,-0.8857 q 1.02157,-0.56865 2.18907,-0.56865 0.98635,0 1.56507,0.4831 0.57871,0.48311 0.57871,1.33357 0,0.37743 -0.11066,0.67435 -0.11067,0.29186 -0.33716,0.55858 -0.22143,0.26672 -0.76996,0.69447 -0.468,0.36736 -0.62904,0.60892 -0.156,0.24154 -0.156,0.64917 v 0.22645 z m -0.20632,1.60532 q 0,-0.75988 0.73974,-0.75988 0.36233,0 0.55356,0.20129 0.19124,0.19627 0.19124,0.55859 0,0.3573 -0.19627,0.56866 -0.19122,0.20632 -0.54853,0.20632 -0.35729,0 -0.54852,-0.20129 -0.19122,-0.20633 -0.19122,-0.57369 z\" id=\"path7926\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> </g> <path id=\"path3153\" style=\"fill:#dddddd;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:1.93243;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" d=\"m 140.04674,489.78052 c -5.199,0 -9.4219,4.22291 -9.4219,9.4219 l 0.004,13.27298 c 0,5.199 4.2229,9.4219 9.4219,9.4219 h 137.6898 c 5.19999,0 9.42336,-4.2229 9.42336,-9.4219 l -0.004,-13.27298 c 0,-5.19899 -4.22191,-9.4219 -9.4219,-9.4219 z\" sodipodi:nodetypes=\"sccssccss\" transform=\"scale(1.33333)\" /> <path d=\"M146.602 555.969H271.18v18.84H146.602Z\" style=\"fill:#ddd;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:1.93243;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3159\" /> <g aria-label=\"See https://k8s.io/linuxrepos\" id=\"text3163\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\"> <path d=\"m 209.7699,755.34947 q 0,0.97125 -0.70453,1.51475 -0.70453,0.5435 -1.9123,0.5435 -1.30842,0 -2.01295,-0.33717 v -0.82531 q 0.45291,0.19123 0.98635,0.30194 0.53343,0.11071 1.05679,0.11071 0.85551,0 1.28829,-0.32207 0.43279,-0.3271 0.43279,-0.90583 0,-0.38246 -0.15601,-0.62401 -0.15097,-0.24659 -0.5133,-0.45292 -0.3573,-0.20632 -1.09202,-0.46801 -1.02661,-0.36736 -1.46946,-0.8706 -0.43781,-0.50323 -0.43781,-1.31345 0,-0.85047 0.63911,-1.3537 0.63911,-0.50324 1.69087,-0.50324 1.09706,0 2.01799,0.40259 l -0.26672,0.74479 q -0.91086,-0.38246 -1.77139,-0.38246 -0.67938,0 -1.06184,0.29188 -0.38246,0.29187 -0.38246,0.81021 0,0.38246 0.14091,0.62905 0.14091,0.24155 0.47304,0.44788 0.33717,0.20129 1.02661,0.44788 1.15744,0.41265 1.59023,0.8857 0.43781,0.47304 0.43781,1.22789 z\" id=\"path7929\" /> <path d=\"m 214.68634,757.40772 q -1.22286,0 -1.93243,-0.7448 -0.70453,-0.74479 -0.70453,-2.0683 0,-1.33358 0.65421,-2.11863 0.65924,-0.78505 1.76636,-0.78505 1.03667,0 1.64056,0.6844 0.60388,0.67937 0.60388,1.79656 v 0.5284 h -3.79944 q 0.0252,0.97125 0.48814,1.47448 0.46801,0.50324 1.31345,0.50324 0.89073,0 1.76133,-0.37239 v 0.74479 q -0.44285,0.19123 -0.84041,0.27174 -0.39252,0.0856 -0.95112,0.0856 z m -0.22645,-5.01728 q -0.66428,0 -1.06183,0.43278 -0.39253,0.43279 -0.46298,1.19771 h 2.88355 q 0,-0.79008 -0.35227,-1.20777 -0.35226,-0.42272 -1.00647,-0.42272 z\" id=\"path7931\" /> <path d=\"m 220.4166,757.40772 q -1.22287,0 -1.93243,-0.7448 -0.70453,-0.74479 -0.70453,-2.0683 0,-1.33358 0.6542,-2.11863 0.65924,-0.78505 1.76637,-0.78505 1.03667,0 1.64055,0.6844 0.60389,0.67937 0.60389,1.79656 v 0.5284 h -3.79945 q 0.0252,0.97125 0.48814,1.47448 0.46801,0.50324 1.31345,0.50324 0.89073,0 1.76133,-0.37239 v 0.74479 q -0.44285,0.19123 -0.8404,0.27174 -0.39253,0.0856 -0.95112,0.0856 z m -0.22646,-5.01728 q -0.66427,0 -1.06183,0.43278 -0.39252,0.43279 -0.46298,1.19771 h 2.88355 q 0,-0.79008 -0.35226,-1.20777 -0.35227,-0.42272 -1.00648,-0.42272 z\" id=\"path7933\" /> <path d=\"m 230.44608,757.30707 v -3.56795 q 0,-0.67434 -0.30697,-1.00648 -0.30698,-0.33214 -0.96119,-0.33214 -0.8706,0 -1.27319,0.47305 -0.39756,0.47304 -0.39756,1.54997 v 2.88355 h -0.83537 v -7.83037 h 0.83537 v 2.37024 q 0,0.42775 -0.0403,0.70957 h 0.0503 q 0.24658,-0.39756 0.6995,-0.62402 0.45794,-0.23149 1.0417,-0.23149 1.01151,0 1.51474,0.48311 0.50827,0.47808 0.50827,1.52481 v 3.59815 z\" id=\"path7935\" /> <path d=\"m 234.1835,756.71828 q 0.22142,0 0.42775,-0.0302 0.20633,-0.0352 0.32711,-0.0705 v 0.63911 q -0.13588,0.0654 -0.40259,0.10568 -0.26169,0.0453 -0.47305,0.0453 -1.60029,0 -1.60029,-1.68585 v -3.28111 h -0.79008 v -0.40259 l 0.79008,-0.34723 0.35226,-1.17758 h 0.48311 v 1.27823 h 1.6003 v 0.64917 h -1.6003 v 3.24588 q 0,0.49821 0.23652,0.76492 0.23653,0.26672 0.64918,0.26672 z\" id=\"path7937\" /> <path d=\"m 237.0383,756.71828 q 0.22142,0 0.42775,-0.0302 0.20633,-0.0352 0.3271,-0.0705 v 0.63911 q -0.13587,0.0654 -0.40259,0.10568 -0.26168,0.0453 -0.47304,0.0453 -1.60029,0 -1.60029,-1.68585 v -3.28111 h -0.79009 v -0.40259 l 0.79009,-0.34723 0.35226,-1.17758 h 0.48311 v 1.27823 h 1.60029 v 0.64917 h -1.60029 v 3.24588 q 0,0.49821 0.23652,0.76492 0.23652,0.26672 0.64918,0.26672 z\" id=\"path7939\" /> <path d=\"m 240.67828,757.40772 q -0.53846,0 -0.98634,-0.19627 -0.44285,-0.20129 -0.74479,-0.61395 h -0.0604 q 0.0604,0.48311 0.0604,0.9159 v 2.2696 h -0.83538 v -7.99141 h 0.67937 l 0.11575,0.75485 h 0.0403 q 0.32207,-0.45291 0.74982,-0.65421 0.42775,-0.20129 0.98131,-0.20129 1.09706,0 1.69088,0.74982 0.59885,0.74983 0.59885,2.10354 0,1.35874 -0.60892,2.11359 -0.60388,0.74983 -1.68081,0.74983 z m -0.12077,-5.00722 q -0.84544,0 -1.22287,0.46801 -0.37743,0.46802 -0.38749,1.48959 v 0.1862 q 0,1.16247 0.38749,1.66571 0.38749,0.49821 1.24299,0.49821 0.7146,0 1.11719,-0.57873 0.40762,-0.57872 0.40762,-1.59526 0,-1.03164 -0.40762,-1.58016 -0.40259,-0.55357 -1.13731,-0.55357 z\" id=\"path7941\" /> <path d=\"m 247.39991,755.80239 q 0,0.76995 -0.57369,1.18764 -0.57369,0.41769 -1.61036,0.41769 -1.09705,0 -1.711,-0.34724 v -0.77498 q 0.39756,0.20129 0.85047,0.31704 0.45795,0.11574 0.88066,0.11574 0.65421,0 1.00648,-0.20633 0.35227,-0.21136 0.35227,-0.63911 0,-0.32207 -0.28182,-0.54853 -0.27678,-0.23149 -1.08699,-0.54349 -0.76995,-0.28685 -1.09706,-0.49821 -0.32207,-0.21639 -0.48311,-0.48814 -0.156,-0.27175 -0.156,-0.64917 0,-0.67434 0.54853,-1.06184 0.54853,-0.39252 1.50468,-0.39252 0.89073,0 1.7412,0.36233 l -0.29691,0.67937 q -0.83034,-0.3422 -1.50468,-0.3422 -0.59382,0 -0.89576,0.1862 -0.30194,0.18619 -0.30194,0.5133 0,0.22142 0.11071,0.37743 0.11574,0.156 0.36736,0.29691 0.25162,0.1409 0.96622,0.40762 0.98131,0.3573 1.32351,0.71963 0.34723,0.36233 0.34723,0.91086 z\" id=\"path7943\" /> <path d=\"m 248.87431,756.77364 q 0,-0.33717 0.15097,-0.50827 0.15601,-0.17614 0.44285,-0.17614 0.29188,0 0.45291,0.17614 0.16607,0.1711 0.16607,0.50827 0,0.3271 -0.16607,0.50323 -0.16606,0.17614 -0.45291,0.17614 -0.25665,0 -0.42775,-0.15601 -0.16607,-0.16103 -0.16607,-0.52336 z m 0,-4.44359 q 0,-0.67937 0.59382,-0.67937 0.61898,0 0.61898,0.67937 0,0.32711 -0.16607,0.50324 -0.16606,0.17613 -0.45291,0.17613 -0.25665,0 -0.42775,-0.156 -0.16607,-0.16104 -0.16607,-0.52337 z\" id=\"path7945\" /> <path d=\"m 254.64296,749.94974 -2.74264,7.35733 h -0.83538 l 2.74265,-7.35733 z\" id=\"path7947\" /> <path d=\"m 257.49777,749.94974 -2.74264,7.35733 h -0.83538 l 2.74265,-7.35733 z\" id=\"path7949\" /> <path d=\"m 258.3849,754.48391 q 0.21639,-0.30698 0.65924,-0.80518 l 1.78146,-1.88714 h 0.99137 l -2.23437,2.35012 2.39038,3.16536 h -1.01151 l -1.94753,-2.60677 -0.62904,0.54349 v 2.06328 h -0.82531 v -7.83037 h 0.82531 v 4.1517 q 0,0.27678 -0.0403,0.85551 z\" id=\"path7951\" /> <path d=\"m 264.76599,749.84406 q 1.00648,0 1.59527,0.46801 0.58878,0.46801 0.58878,1.29332 0,0.5435 -0.33717,0.99138 -0.33716,0.44788 -1.07692,0.81524 0.89576,0.42775 1.27319,0.9008 0.37742,0.46801 0.37742,1.08699 0,0.91589 -0.63911,1.46442 -0.63911,0.5435 -1.75126,0.5435 -1.17758,0 -1.81166,-0.51331 -0.63408,-0.51833 -0.63408,-1.46442 0,-1.26312 1.53991,-1.96766 -0.69447,-0.39252 -0.99641,-0.84543 -0.30194,-0.45795 -0.30194,-1.02158 0,-0.80014 0.58879,-1.27319 0.59382,-0.47807 1.58519,-0.47807 z m -1.59023,5.60606 q 0,0.60389 0.41769,0.94106 0.42272,0.33716 1.18261,0.33716 0.74982,0 1.16751,-0.35226 0.41769,-0.35227 0.41769,-0.96622 0,-0.48814 -0.39253,-0.86556 -0.39252,-0.38247 -1.36881,-0.73976 -0.74982,0.32207 -1.08699,0.71459 -0.33717,0.3875 -0.33717,0.93099 z m 1.58017,-4.92669 q -0.62905,0 -0.98635,0.30194 -0.3573,0.30194 -0.3573,0.80518 0,0.46298 0.29691,0.79512 0.29691,0.33213 1.09706,0.66427 0.71963,-0.30194 1.01654,-0.64918 0.30194,-0.34723 0.30194,-0.81021 0,-0.50827 -0.36736,-0.80518 -0.36233,-0.30194 -1.00144,-0.30194 z\" id=\"path7953\" /> <path d=\"m 272.00093,755.80239 q 0,0.76995 -0.57369,1.18764 -0.57369,0.41769 -1.61036,0.41769 -1.09706,0 -1.71101,-0.34724 v -0.77498 q 0.39756,0.20129 0.85047,0.31704 0.45795,0.11574 0.88067,0.11574 0.65421,0 1.00647,-0.20633 0.35227,-0.21136 0.35227,-0.63911 0,-0.32207 -0.28181,-0.54853 -0.27679,-0.23149 -1.087,-0.54349 -0.76995,-0.28685 -1.09705,-0.49821 -0.32208,-0.21639 -0.48311,-0.48814 -0.15601,-0.27175 -0.15601,-0.64917 0,-0.67434 0.54853,-1.06184 0.54853,-0.39252 1.50468,-0.39252 0.89073,0 1.7412,0.36233 l -0.29691,0.67937 q -0.83034,-0.3422 -1.50468,-0.3422 -0.59382,0 -0.89576,0.1862 -0.30194,0.18619 -0.30194,0.5133 0,0.22142 0.11071,0.37743 0.11575,0.156 0.36736,0.29691 0.25162,0.1409 0.96622,0.40762 0.98131,0.3573 1.32351,0.71963 0.34724,0.36233 0.34724,0.91086 z\" id=\"path7955\" /> <path d=\"m 273.47543,756.77364 q 0,-0.33717 0.15097,-0.50827 0.15601,-0.17614 0.44285,-0.17614 0.29188,0 0.45291,0.17614 0.16607,0.1711 0.16607,0.50827 0,0.3271 -0.16607,0.50323 -0.16606,0.17614 -0.45291,0.17614 -0.25665,0 -0.42775,-0.15601 -0.16607,-0.16103 -0.16607,-0.52336 z\" id=\"path7957\" /> <path d=\"m 277.28638,757.30707 h -0.83537 v -5.51548 h 0.83537 z m -0.90583,-7.0101 q 0,-0.28684 0.14091,-0.41768 0.1409,-0.13588 0.35226,-0.13588 0.2013,0 0.34724,0.13588 0.14594,0.13587 0.14594,0.41768 0,0.28182 -0.14594,0.42272 -0.14594,0.13588 -0.34724,0.13588 -0.21136,0 -0.35226,-0.13588 -0.14091,-0.1409 -0.14091,-0.42272 z\" id=\"path7959\" /> <path d=\"m 283.49962,754.5443 q 0,1.34867 -0.67937,2.10856 -0.67937,0.75486 -1.87707,0.75486 -0.73976,0 -1.31345,-0.34724 -0.57369,-0.34723 -0.8857,-0.99641 -0.31201,-0.64917 -0.31201,-1.51977 0,-1.34868 0.67434,-2.0985 0.67434,-0.75486 1.87205,-0.75486 1.15744,0 1.83681,0.76995 0.6844,0.76996 0.6844,2.08341 z m -4.20203,0 q 0,1.05679 0.42272,1.61035 0.42272,0.55357 1.243,0.55357 0.82028,0 1.24299,-0.54853 0.42776,-0.55356 0.42776,-1.61539 0,-1.05177 -0.42776,-1.59527 -0.42271,-0.54853 -1.25306,-0.54853 -0.82027,0 -1.23796,0.53847 -0.41769,0.53846 -0.41769,1.60533 z\" id=\"path7961\" /> <path d=\"m 287.26222,749.94974 -2.74264,7.35733 h -0.83538 l 2.74265,-7.35733 z\" id=\"path7963\" /> <path d=\"m 289.08897,757.30707 h -0.83537 v -7.83037 h 0.83537 z\" id=\"path7965\" /> <path d=\"m 291.69574,757.30707 h -0.83537 v -5.51548 h 0.83537 z m -0.90582,-7.0101 q 0,-0.28684 0.1409,-0.41768 0.14091,-0.13588 0.35227,-0.13588 0.20129,0 0.34723,0.13588 0.14594,0.13587 0.14594,0.41768 0,0.28182 -0.14594,0.42272 -0.14594,0.13588 -0.34723,0.13588 -0.21136,0 -0.35227,-0.13588 -0.1409,-0.1409 -0.1409,-0.42272 z\" id=\"path7967\" /> <path d=\"m 297.24142,757.30707 v -3.56795 q 0,-0.67434 -0.30698,-1.00648 -0.30697,-0.33214 -0.96118,-0.33214 -0.86557,0 -1.26816,0.46801 -0.40259,0.46802 -0.40259,1.54494 v 2.89362 h -0.83537 v -5.51548 h 0.67937 l 0.13587,0.75485 h 0.0403 q 0.25665,-0.40762 0.71963,-0.62904 0.46298,-0.22646 1.03164,-0.22646 0.99641,0 1.49964,0.48311 0.50324,0.47807 0.50324,1.53487 v 3.59815 z\" id=\"path7969\" /> <path d=\"m 300.57788,751.79159 v 3.57801 q 0,0.67434 0.30698,1.00648 0.30697,0.33214 0.96118,0.33214 0.86557,0 1.26312,-0.47305 0.40259,-0.47304 0.40259,-1.54494 v -2.89864 h 0.83538 v 5.51548 h -0.68944 l -0.12077,-0.73976 h -0.0453 q -0.25666,0.40762 -0.7146,0.62401 -0.45292,0.2164 -1.03667,0.2164 -1.00648,0 -1.50971,-0.47808 -0.49821,-0.47808 -0.49821,-1.52984 v -3.60821 z\" id=\"path7971\" /> <path d=\"m 307.44707,754.48391 -1.91733,-2.69232 h 0.95111 l 1.45436,2.11359 1.44932,-2.11359 h 0.94106 l -1.91734,2.69232 2.01799,2.82316 h -0.94609 l -1.54494,-2.23438 -1.56004,2.23438 h -0.94608 z\" id=\"path7973\" /> <path d=\"m 314.03445,751.69094 q 0.36736,0 0.65924,0.0604 l -0.11575,0.77498 q -0.3422,-0.0755 -0.60388,-0.0755 -0.66931,0 -1.14738,0.54349 -0.47305,0.5435 -0.47305,1.35371 v 2.95904 h -0.83537 v -5.51548 h 0.68944 l 0.0956,1.02157 h 0.0403 q 0.30697,-0.53847 0.73976,-0.83034 0.43278,-0.29188 0.95112,-0.29188 z\" id=\"path7975\" /> <path d=\"m 318.05531,757.40772 q -1.22286,0 -1.93243,-0.7448 -0.70453,-0.74479 -0.70453,-2.0683 0,-1.33358 0.65421,-2.11863 0.65924,-0.78505 1.76636,-0.78505 1.03667,0 1.64055,0.6844 0.60389,0.67937 0.60389,1.79656 v 0.5284 h -3.79944 q 0.0252,0.97125 0.48814,1.47448 0.46801,0.50324 1.31345,0.50324 0.89073,0 1.76133,-0.37239 v 0.74479 q -0.44285,0.19123 -0.84041,0.27174 -0.39252,0.0856 -0.95112,0.0856 z m -0.22645,-5.01728 q -0.66428,0 -1.06183,0.43278 -0.39253,0.43279 -0.46298,1.19771 h 2.88355 q 0,-0.79008 -0.35227,-1.20777 -0.35227,-0.42272 -1.00647,-0.42272 z\" id=\"path7977\" /> <path d=\"m 324.07403,757.40772 q -0.53846,0 -0.98634,-0.19627 -0.44285,-0.20129 -0.7448,-0.61395 h -0.0604 q 0.0604,0.48311 0.0604,0.9159 v 2.2696 h -0.83537 v -7.99141 h 0.67937 l 0.11574,0.75485 h 0.0403 q 0.32208,-0.45291 0.74983,-0.65421 0.42775,-0.20129 0.98131,-0.20129 1.09706,0 1.69088,0.74982 0.59885,0.74983 0.59885,2.10354 0,1.35874 -0.60892,2.11359 -0.60388,0.74983 -1.68081,0.74983 z m -0.12078,-5.00722 q -0.84544,0 -1.22286,0.46801 -0.37743,0.46802 -0.3875,1.48959 v 0.1862 q 0,1.16247 0.3875,1.66571 0.38749,0.49821 1.24299,0.49821 0.7146,0 1.11719,-0.57873 0.40762,-0.57872 0.40762,-1.59526 0,-1.03164 -0.40762,-1.58016 -0.40259,-0.55357 -1.13732,-0.55357 z\" id=\"path7979\" /> <path d=\"m 332.58377,754.5443 q 0,1.34867 -0.67937,2.10856 -0.67937,0.75486 -1.87707,0.75486 -0.73976,0 -1.31345,-0.34724 -0.57369,-0.34723 -0.8857,-0.99641 -0.31201,-0.64917 -0.31201,-1.51977 0,-1.34868 0.67434,-2.0985 0.67434,-0.75486 1.87204,-0.75486 1.15745,0 1.83682,0.76995 0.6844,0.76996 0.6844,2.08341 z m -4.20203,0 q 0,1.05679 0.42272,1.61035 0.42272,0.55357 1.243,0.55357 0.82027,0 1.24299,-0.54853 0.42775,-0.55356 0.42775,-1.61539 0,-1.05177 -0.42775,-1.59527 -0.42272,-0.54853 -1.25306,-0.54853 -0.82027,0 -1.23796,0.53847 -0.41769,0.53846 -0.41769,1.60533 z\" id=\"path7981\" /> <path d=\"m 337.60608,755.80239 q 0,0.76995 -0.57369,1.18764 -0.57369,0.41769 -1.61036,0.41769 -1.09705,0 -1.711,-0.34724 v -0.77498 q 0.39755,0.20129 0.85047,0.31704 0.45794,0.11574 0.88066,0.11574 0.65421,0 1.00648,-0.20633 0.35226,-0.21136 0.35226,-0.63911 0,-0.32207 -0.28181,-0.54853 -0.27678,-0.23149 -1.08699,-0.54349 -0.76995,-0.28685 -1.09706,-0.49821 -0.32207,-0.21639 -0.48311,-0.48814 -0.156,-0.27175 -0.156,-0.64917 0,-0.67434 0.54853,-1.06184 0.54853,-0.39252 1.50468,-0.39252 0.89073,0 1.7412,0.36233 l -0.29691,0.67937 q -0.83034,-0.3422 -1.50468,-0.3422 -0.59382,0 -0.89576,0.1862 -0.30195,0.18619 -0.30195,0.5133 0,0.22142 0.11072,0.37743 0.11574,0.156 0.36736,0.29691 0.25162,0.1409 0.96622,0.40762 0.98131,0.3573 1.32351,0.71963 0.34723,0.36233 0.34723,0.91086 z\" id=\"path7983\" /> </g> <g id=\"g13206\"> <path d=\"m 365.69163,870.94898 -0.73473,-2.04314 h -2.81309 l -0.71962,2.04314 h -1.26814 l 2.75268,-7.38749 h 1.30841 l 2.7527,7.38749 z m -1.05177,-3.0798 -0.68942,-2.00288 q -0.0755,-0.20129 -0.21136,-0.63406 -0.1308,-0.43279 -0.18118,-0.63408 -0.13586,0.61897 -0.39754,1.3537 l -0.66428,1.91732 z\" id=\"path7986\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 370.68858,865.28256 q 0.35729,0 0.58879,0.0503 l -0.11574,1.10209 q -0.25161,-0.0604 -0.52336,-0.0604 -0.70955,0 -1.15241,0.46298 -0.43781,0.46297 -0.43781,1.20273 v 2.9087 h -1.18261 v -5.56579 h 0.92596 l 0.156,0.98132 h 0.0604 q 0.27678,-0.49822 0.71962,-0.79008 0.44788,-0.29188 0.96119,-0.29188 z\" id=\"path7988\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 373.72805,871.04962 q -1.29834,0 -2.03306,-0.75485 -0.72969,-0.75988 -0.72969,-2.08842 0,-1.36377 0.67936,-2.14378 0.67937,-0.78001 1.86701,-0.78001 1.10207,0 1.74119,0.6693 0.63911,0.66929 0.63911,1.84184 v 0.6391 h -3.70885 q 0.0252,0.81021 0.43782,1.24803 0.41265,0.43278 1.16247,0.43278 0.49317,0 0.91589,-0.0905 0.42775,-0.0956 0.91588,-0.312 v 0.96117 q -0.43277,0.20633 -0.87562,0.29188 -0.44284,0.0856 -1.01151,0.0856 z m -0.21638,-4.87131 q -0.56363,0 -0.90583,0.3573 -0.33717,0.3573 -0.40258,1.0417 h 2.52623 q -0.0107,-0.68944 -0.33213,-1.0417 -0.32207,-0.3573 -0.88569,-0.3573 z\" id=\"path7990\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 379.03705,865.3832 h 1.28829 l 1.13228,3.15528 q 0.25665,0.67435 0.3422,1.26816 h 0.0403 q 0.0453,-0.27679 0.16606,-0.66931 0.1208,-0.39756 1.27823,-3.75413 h 1.27821 l -2.38031,6.30554 q -0.64917,1.73616 -2.1639,1.73616 -0.39253,0 -0.76491,-0.0856 v -0.93603 q 0.2667,0.0604 0.6089,0.0604 0.8555,0 1.20274,-0.99138 l 0.20632,-0.52336 z\" id=\"path7992\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 389.97241,868.15603 q 0,1.36377 -0.69949,2.12869 -0.6995,0.7649 -1.94753,0.7649 -0.78001,0 -1.37886,-0.35225 -0.59885,-0.35227 -0.92092,-1.0115 -0.32207,-0.65924 -0.32207,-1.52984 0,-1.3537 0.69447,-2.1136 0.69446,-0.75987 1.95758,-0.75987 1.20776,0 1.91229,0.78001 0.70453,0.77498 0.70453,2.09346 z m -4.05104,0 q 0,1.92738 1.42415,1.92738 1.40907,0 1.40907,-1.92738 0,-1.90726 -1.41913,-1.90726 -0.74479,0 -1.08196,0.49317 -0.33213,0.49317 -0.33213,1.41409 z\" id=\"path7994\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 394.69116,870.94898 -0.16607,-0.72969 h -0.0604 q -0.24658,0.38749 -0.70453,0.60892 -0.4529,0.22141 -1.03666,0.22141 -1.01151,0 -1.5097,-0.50322 -0.4982,-0.50324 -0.4982,-1.52481 v -3.63839 h 1.19266 v 3.43207 q 0,0.6391 0.26168,0.96117 0.26168,0.31704 0.82028,0.31704 0.74478,0 1.09201,-0.44284 0.35226,-0.44788 0.35226,-1.49461 v -2.77283 h 1.18764 v 5.56578 z\" id=\"path7996\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 403.27635,870.94898 -0.16608,-0.72969 h -0.0604 q -0.24658,0.38749 -0.70453,0.60892 -0.4529,0.22141 -1.03666,0.22141 -1.01149,0 -1.50971,-0.50322 -0.49819,-0.50324 -0.49819,-1.52481 v -3.63839 h 1.19266 v 3.43207 q 0,0.6391 0.26168,0.96117 0.26169,0.31704 0.82028,0.31704 0.74478,0 1.09202,-0.44284 0.35227,-0.44788 0.35227,-1.49461 v -2.77283 h 1.18763 v 5.56578 z\" id=\"path7998\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 408.8204,869.36379 q 0,0.81525 -0.59382,1.25306 -0.59381,0.43277 -1.70093,0.43277 -1.11216,0 -1.78649,-0.33716 v -1.02157 q 0.98131,0.45292 1.82674,0.45292 1.09203,0 1.09203,-0.65924 0,-0.21136 -0.1208,-0.35226 -0.1208,-0.14091 -0.39756,-0.29188 -0.27679,-0.15098 -0.76995,-0.3422 -0.96118,-0.3724 -1.30338,-0.74479 -0.33717,-0.3724 -0.33717,-0.96621 0,-0.7146 0.57369,-1.10711 0.57872,-0.39756 1.57009,-0.39756 0.98132,0 1.85694,0.39756 l -0.38246,0.89071 q -0.90079,-0.37238 -1.51473,-0.37238 -0.93603,0 -0.93603,0.53342 0,0.26168 0.24156,0.44284 0.24659,0.18117 1.06685,0.49821 0.68944,0.26671 1.00144,0.48814 0.31201,0.22142 0.46298,0.5133 0.15098,0.28684 0.15098,0.68943 z\" id=\"path8000\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 411.41702,870.94898 h -1.18259 v -5.56578 h 1.18259 z m -1.25305,-7.04026 q 0,-0.31704 0.1711,-0.48813 0.17613,-0.17111 0.49821,-0.17111 0.312,0 0.48311,0.17111 0.17613,0.17109 0.17613,0.48813 0,0.30195 -0.17613,0.47808 -0.17111,0.17109 -0.48311,0.17109 -0.32208,0 -0.49821,-0.17109 -0.1711,-0.17613 -0.1711,-0.47808 z\" id=\"path8002\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 417.4189,870.94898 h -1.18763 v -3.422 q 0,-0.64413 -0.26168,-0.96117 -0.25666,-0.31704 -0.82028,-0.31704 -0.74981,0 -1.09705,0.44284 -0.34723,0.44285 -0.34723,1.48455 v 2.77282 h -1.18261 v -5.56578 h 0.92596 l 0.16607,0.72969 h 0.0604 q 0.25161,-0.39755 0.71459,-0.61395 0.46298,-0.21638 1.0266,-0.21638 2.00288,0 2.00288,2.0381 z\" id=\"path8004\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 422.95289,865.3832 v 0.64918 l -0.95112,0.17612 q 0.1308,0.17613 0.2164,0.43279 0.0856,0.25665 0.0856,0.54349 0,0.86053 -0.59381,1.3537 -0.59383,0.49317 -1.63552,0.49317 -0.26672,0 -0.4831,-0.0403 -0.38247,0.23652 -0.38247,0.55356 0,0.19122 0.17613,0.28683 0.18118,0.0956 0.65924,0.0956 h 0.97125 q 0.92092,0 1.39899,0.39254 0.47808,0.39252 0.47808,1.13227 0,0.94608 -0.78002,1.45939 -0.78001,0.51329 -2.2545,0.51329 -1.1373,0 -1.73615,-0.40259 -0.59885,-0.40258 -0.59885,-1.14737 0,-0.5133 0.32208,-0.86557 0.32709,-0.34722 0.91085,-0.4831 -0.23652,-0.10067 -0.39252,-0.32207 -0.15098,-0.22647 -0.15098,-0.47304 0,-0.31201 0.17614,-0.5284 0.17613,-0.2164 0.52336,-0.42776 -0.43279,-0.18618 -0.70454,-0.60387 -0.2667,-0.42272 -0.2667,-0.98635 0,-0.90582 0.56865,-1.40402 0.57369,-0.4982 1.63048,-0.4982 0.23652,0 0.49317,0.0352 0.26168,0.0301 0.39253,0.0655 z m -4.37311,6.43134 q 0,0.38247 0.3422,0.58879 0.34723,0.20633 0.97124,0.20633 0.96621,0 1.43926,-0.27679 0.47304,-0.27677 0.47304,-0.73472 0,-0.36233 -0.26168,-0.51833 -0.25665,-0.15097 -0.96118,-0.15097 h -0.89576 q -0.50827,0 -0.81021,0.23652 -0.29691,0.24156 -0.29691,0.64917 z m 0.50827,-4.62976 q 0,0.52337 0.26671,0.80518 0.27175,0.28182 0.77498,0.28182 1.02661,0 1.02661,-1.09707 0,-0.54349 -0.25666,-0.83536 -0.25162,-0.29692 -0.76995,-0.29692 -0.5133,0 -0.78002,0.29188 -0.26167,0.29188 -0.26167,0.85047 z\" id=\"path8006\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 426.96363,870.94898 v -7.3573 h 1.20273 v 6.32566 h 3.11503 v 1.03164 z\" id=\"path8008\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 433.75068,870.94898 h -1.18261 v -5.56578 h 1.18261 z m -1.25307,-7.04026 q 0,-0.31704 0.17111,-0.48813 0.17613,-0.17111 0.4982,-0.17111 0.31201,0 0.4831,0.17111 0.17614,0.17109 0.17614,0.48813 0,0.30195 -0.17614,0.47808 -0.17109,0.17109 -0.4831,0.17109 -0.32207,0 -0.4982,-0.17109 -0.17111,-0.17613 -0.17111,-0.47808 z\" id=\"path8010\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 439.75254,870.94898 h -1.18762 v -3.422 q 0,-0.64413 -0.2617,-0.96117 -0.25664,-0.31704 -0.82026,-0.31704 -0.74983,0 -1.09705,0.44284 -0.34724,0.44285 -0.34724,1.48455 v 2.77282 h -1.1826 v -5.56578 h 0.92595 l 0.16606,0.72969 h 0.0604 q 0.25162,-0.39755 0.71459,-0.61395 0.46298,-0.21638 1.0266,-0.21638 2.00287,0 2.00287,2.0381 z\" id=\"path8012\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 444.51172,870.94898 -0.16607,-0.72969 h -0.0604 q -0.24659,0.38749 -0.70453,0.60892 -0.45291,0.22141 -1.03667,0.22141 -1.0115,0 -1.5097,-0.50322 -0.4982,-0.50324 -0.4982,-1.52481 v -3.63839 h 1.19267 v 3.43207 q 0,0.6391 0.26168,0.96117 0.26167,0.31704 0.82027,0.31704 0.74479,0 1.09201,-0.44284 0.35227,-0.44788 0.35227,-1.49461 v -2.77283 h 1.18764 v 5.56578 z\" id=\"path8014\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 447.55453,868.10571 -1.867,-2.72251 h 1.34867 l 1.26815,1.94752 1.27822,-1.94752 h 1.3386 l -1.87204,2.72251 1.96766,2.84327 h -1.33861 l -1.37383,-2.08339 -1.3688,2.08339 h -1.33861 z\" id=\"path8016\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 382.55695,880.18 q 0,1.36377 -0.6995,2.12869 -0.6995,0.76492 -1.94752,0.76492 -0.78001,0 -1.37886,-0.35227 -0.59885,-0.35227 -0.92092,-1.0115 -0.32208,-0.65924 -0.32208,-1.52984 0,-1.3537 0.69447,-2.11358 0.69446,-0.75989 1.95758,-0.75989 1.20777,0 1.9123,0.78002 0.70453,0.77497 0.70453,2.09345 z m -4.05104,0 q 0,1.92739 1.42415,1.92739 1.40905,0 1.40905,-1.92739 0,-1.90726 -1.41911,-1.90726 -0.74479,0 -1.08196,0.49317 -0.33213,0.49317 -0.33213,1.41409 z\" id=\"path8019\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 388.2471,882.97295 h -1.18764 v -3.42199 q 0,-0.64414 -0.26168,-0.96118 -0.25665,-0.31704 -0.82026,-0.31704 -0.74983,0 -1.09707,0.44285 -0.34722,0.44285 -0.34722,1.48454 v 2.77282 h -1.1826 v -5.56577 h 0.92594 l 0.16607,0.72969 h 0.0604 q 0.25162,-0.39756 0.7146,-0.61394 0.46297,-0.2164 1.02659,-0.2164 2.00288,0 2.00288,2.0381 z\" id=\"path8021\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 391.09021,877.40718 h 1.28828 l 1.13227,3.15528 q 0.25666,0.67434 0.34222,1.26815 h 0.0403 q 0.0453,-0.27677 0.16607,-0.66929 0.1208,-0.39756 1.27822,-3.75414 h 1.27821 l -2.3803,6.30553 q -0.64917,1.73617 -2.16391,1.73617 -0.39252,0 -0.76492,-0.0856 v -0.93601 q 0.26672,0.0604 0.60892,0.0604 0.8555,0 1.20273,-0.99137 l 0.20633,-0.52337 z\" id=\"path8023\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 402.02557,880.18 q 0,1.36377 -0.69951,2.12869 -0.69949,0.76492 -1.94751,0.76492 -0.78001,0 -1.37887,-0.35227 -0.59885,-0.35227 -0.92091,-1.0115 -0.32208,-0.65924 -0.32208,-1.52984 0,-1.3537 0.69446,-2.11358 0.69447,-0.75989 1.9576,-0.75989 1.20776,0 1.91229,0.78002 0.70453,0.77497 0.70453,2.09345 z m -4.05104,0 q 0,1.92739 1.42415,1.92739 1.40905,0 1.40905,-1.92739 0,-1.90726 -1.41912,-1.90726 -0.74478,0 -1.08195,0.49317 -0.33213,0.49317 -0.33213,1.41409 z\" id=\"path8025\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 406.74432,882.97295 -0.16607,-0.72968 h -0.0604 q -0.24659,0.38748 -0.70453,0.60891 -0.45292,0.22143 -1.03667,0.22143 -1.0115,0 -1.5097,-0.50324 -0.49821,-0.50323 -0.49821,-1.5248 v -3.63839 h 1.19268 v 3.43206 q 0,0.63912 0.26168,0.96118 0.26168,0.31704 0.82026,0.31704 0.7448,0 1.09202,-0.44285 0.35227,-0.44788 0.35227,-1.49461 v -2.77282 h 1.18764 v 5.56577 z\" id=\"path8027\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 411.37248,877.30653 q 0.35729,0 0.58878,0.0503 l -0.11573,1.10208 q -0.25161,-0.0604 -0.52336,-0.0604 -0.70956,0 -1.15241,0.46297 -0.43781,0.46299 -0.43781,1.20275 v 2.90868 h -1.18261 v -5.56577 h 0.92596 l 0.156,0.9813 h 0.0604 q 0.27678,-0.4982 0.71963,-0.79007 0.44788,-0.29188 0.96117,-0.29188 z\" id=\"path8029\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 419.83327,877.83996 q 0,1.15242 -0.75486,1.76636 -0.75486,0.61395 -2.14881,0.61395 h -0.76492 v 2.75268 h -1.20273 v -7.35729 h 2.11862 q 1.37886,0 2.06326,0.56363 0.68944,0.56362 0.68944,1.66067 z m -3.66859,1.3688 h 0.6391 q 0.92596,0 1.35875,-0.32206 0.43277,-0.32208 0.43277,-1.00648 0,-0.63408 -0.38748,-0.94608 -0.38749,-0.31201 -1.20777,-0.31201 h -0.83537 z\" id=\"path8031\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 424.95607,876.54161 q -1.03666,0 -1.63049,0.73473 -0.59381,0.73472 -0.59381,2.02803 0,1.35371 0.56865,2.04817 0.57369,0.69447 1.65565,0.69447 0.468,0 0.90583,-0.0905 0.43781,-0.0956 0.91085,-0.24154 v 1.03162 q -0.86557,0.32711 -1.96263,0.32711 -1.61538,0 -2.48094,-0.97628 -0.86557,-0.9813 -0.86557,-2.80302 0,-1.14737 0.4177,-2.0079 0.42271,-0.86053 1.21782,-1.31848 0.79512,-0.45794 1.86701,-0.45794 1.12723,0 2.08338,0.47304 l -0.43277,1.00143 q -0.3724,-0.17613 -0.79008,-0.30697 -0.41265,-0.13588 -0.8706,-0.13588 z\" id=\"path8033\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> <path d=\"m 429.72001,880.7386 v -0.32208 q 0,-0.55356 0.20129,-0.92092 0.20129,-0.36736 0.70452,-0.75988 0.59885,-0.47304 0.76995,-0.73473 0.17614,-0.26168 0.17614,-0.62401 0,-0.42272 -0.28181,-0.64917 -0.28182,-0.22646 -0.81022,-0.22646 -0.47806,0 -0.88569,0.13588 -0.40762,0.13587 -0.79512,0.3271 l -0.4227,-0.88569 q 1.02156,-0.56866 2.18906,-0.56866 0.98634,0 1.56506,0.48311 0.57872,0.4831 0.57872,1.33357 0,0.37743 -0.11066,0.67433 -0.11067,0.29188 -0.33718,0.5586 -0.22141,0.26671 -0.76994,0.69446 -0.46801,0.36736 -0.62904,0.60891 -0.15601,0.24156 -0.15601,0.64918 v 0.22646 z m -0.20634,1.60531 q 0,-0.75987 0.73976,-0.75987 0.36233,0 0.55356,0.20129 0.19123,0.19625 0.19123,0.55858 0,0.3573 -0.19627,0.56866 -0.19123,0.20633 -0.54852,0.20633 -0.35729,0 -0.54853,-0.20129 -0.19123,-0.20634 -0.19123,-0.5737 z\" id=\"path8035\" style=\"font-weight:600;font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Semi-Bold';fill:#ffffff;stroke-width:1.33333\" /> </g> <path d=\"M194.957 740.297H322.32c5.2 0 9.422 4.223 9.422 9.422 0 5.199-4.222 9.418-9.422 9.418H194.957c-5.199 0-9.418-4.219-9.418-9.418 0-5.199 4.219-9.422 9.418-9.422z\" style=\"fill:#ddd;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:1.93243;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3173\" /> <g aria-label=\"You may need to update your Linux PC\" transform=\"scale(1.33333)\" id=\"text3177\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal'\"> <path d=\"m 193.67886,748.96592 1.47197,-2.75899 h 0.69447 l -1.84185,3.37797 v 2.14001 h -0.64917 v -2.10981 l -1.83808,-3.40817 h 0.70202 z\" id=\"path8038\" /> <path d=\"m 200.18774,749.65284 q 0,1.0115 -0.50953,1.58142 -0.50953,0.56614 -1.4078,0.56614 -0.55482,0 -0.98509,-0.26042 -0.43027,-0.26043 -0.66427,-0.74731 -0.23401,-0.48688 -0.23401,-1.13983 0,-1.01151 0.50576,-1.57387 0.50575,-0.56614 1.40403,-0.56614 0.86808,0 1.37761,0.57746 0.5133,0.57746 0.5133,1.56255 z m -3.15152,0 q 0,0.7926 0.31704,1.20777 0.31704,0.41517 0.93224,0.41517 0.61521,0 0.93225,-0.4114 0.32081,-0.41517 0.32081,-1.21154 0,-0.78882 -0.32081,-1.19645 -0.31704,-0.41139 -0.9398,-0.41139 -0.6152,0 -0.92847,0.40385 -0.31326,0.40384 -0.31326,1.20399 z\" id=\"path8040\" /> <path d=\"m 201.50385,747.58831 v 2.68351 q 0,0.50575 0.23023,0.75485 0.23023,0.24911 0.72089,0.24911 0.64917,0 0.94734,-0.35479 0.30194,-0.35478 0.30194,-1.1587 v -2.17398 h 0.62653 v 4.1366 h -0.51707 l -0.0906,-0.55481 h -0.034 q -0.19249,0.30571 -0.53595,0.46801 -0.33969,0.16229 -0.7775,0.16229 -0.75486,0 -1.13228,-0.35856 -0.37366,-0.35855 -0.37366,-1.14737 v -2.70616 z\" id=\"path8042\" /> <path d=\"m 212.62654,751.72491 v -2.69105 q 0,-0.49443 -0.21136,-0.73976 -0.21136,-0.2491 -0.65673,-0.2491 -0.58501,0 -0.8643,0.33591 -0.2793,0.33591 -0.2793,1.03415 v 2.30985 h -0.62653 v -2.69105 q 0,-0.49443 -0.21136,-0.73976 -0.21136,-0.2491 -0.6605,-0.2491 -0.58878,0 -0.86431,0.35478 -0.27174,0.35101 -0.27174,1.15493 v 2.1702 h -0.62653 v -4.1366 h 0.50952 l 0.10191,0.56614 h 0.0302 q 0.17739,-0.30194 0.49821,-0.47178 0.32459,-0.16984 0.72466,-0.16984 0.96999,0 1.26815,0.70201 h 0.0302 q 0.18494,-0.32459 0.53594,-0.5133 0.35101,-0.18871 0.80015,-0.18871 0.70202,0 1.04925,0.36233 0.35101,0.35855 0.35101,1.15115 v 2.6986 z\" id=\"path8044\" /> <path d=\"m 216.33663,751.72491 -0.12456,-0.58878 h -0.0302 q -0.30949,0.38875 -0.61898,0.5284 -0.30572,0.13587 -0.76618,0.13587 -0.6152,0 -0.96621,-0.31704 -0.34723,-0.31704 -0.34723,-0.90205 0,-1.25306 2.00413,-1.31345 l 0.70202,-0.0226 v -0.25665 q 0,-0.48688 -0.21136,-0.71711 -0.20758,-0.23401 -0.66805,-0.23401 -0.51707,0 -1.17002,0.31704 l -0.19249,-0.47933 q 0.30572,-0.16607 0.66805,-0.26043 0.3661,-0.0944 0.73221,-0.0944 0.73975,0 1.09454,0.32837 0.35855,0.32836 0.35855,1.05302 v 2.82315 z m -1.41536,-0.44159 q 0.58502,0 0.91715,-0.32081 0.33591,-0.32081 0.33591,-0.89828 v -0.37365 l -0.62653,0.0264 q -0.7473,0.0264 -1.07944,0.23401 -0.32836,0.20381 -0.32836,0.63785 0,0.33968 0.20381,0.51707 0.20758,0.17739 0.57746,0.17739 z\" id=\"path8046\" /> <path d=\"m 217.43374,747.58831 h 0.67182 l 0.90583,2.35892 q 0.29817,0.8077 0.36988,1.16625 h 0.0302 q 0.0491,-0.19249 0.20381,-0.65672 0.15852,-0.46801 1.0266,-2.86845 h 0.67182 l -1.77768,4.71029 q -0.2642,0.69824 -0.61898,0.98886 -0.35101,0.2944 -0.86431,0.2944 -0.28684,0 -0.56614,-0.0642 v -0.50197 q 0.20759,0.0453 0.46424,0.0453 0.6454,0 0.92092,-0.72466 l 0.23023,-0.58879 z\" id=\"path8048\" /> <path d=\"m 226.92718,751.72491 v -2.67595 q 0,-0.50576 -0.23023,-0.75486 -0.23023,-0.2491 -0.72089,-0.2491 -0.64917,0 -0.95111,0.35101 -0.30194,0.351 -0.30194,1.1587 v 2.1702 h -0.62653 v -4.1366 h 0.50952 l 0.10191,0.56614 h 0.0302 q 0.19249,-0.30571 0.53972,-0.47178 0.34724,-0.16984 0.77373,-0.16984 0.74731,0 1.12473,0.36233 0.37743,0.35855 0.37743,1.15115 v 2.6986 z\" id=\"path8050\" /> <path d=\"m 230.14166,751.8004 q -0.91714,0 -1.44932,-0.55859 -0.52839,-0.55859 -0.52839,-1.55123 0,-1.00018 0.49065,-1.58897 0.49443,-0.58878 1.32477,-0.58878 0.7775,0 1.23041,0.5133 0.45292,0.50952 0.45292,1.34741 v 0.3963 h -2.84958 q 0.0189,0.72844 0.3661,1.10586 0.35101,0.37743 0.98509,0.37743 0.66805,0 1.321,-0.2793 v 0.5586 q -0.33214,0.14342 -0.63031,0.20381 -0.29439,0.0642 -0.71334,0.0642 z m -0.16984,-3.76295 q -0.4982,0 -0.79637,0.32459 -0.29439,0.32459 -0.34723,0.89827 h 2.16266 q 0,-0.59256 -0.2642,-0.90582 -0.2642,-0.31704 -0.75486,-0.31704 z\" id=\"path8052\" /> <path d=\"m 234.43936,751.8004 q -0.91714,0 -1.44932,-0.55859 -0.5284,-0.55859 -0.5284,-1.55123 0,-1.00018 0.49066,-1.58897 0.49443,-0.58878 1.32477,-0.58878 0.7775,0 1.23041,0.5133 0.45292,0.50952 0.45292,1.34741 v 0.3963 h -2.84958 q 0.0189,0.72844 0.3661,1.10586 0.35101,0.37743 0.98509,0.37743 0.66805,0 1.32099,-0.2793 v 0.5586 q -0.33213,0.14342 -0.6303,0.20381 -0.29439,0.0642 -0.71334,0.0642 z m -0.16984,-3.76295 q -0.4982,0 -0.79637,0.32459 -0.29439,0.32459 -0.34723,0.89827 h 2.16265 q 0,-0.59256 -0.26419,-0.90582 -0.2642,-0.31704 -0.75486,-0.31704 z\" id=\"path8054\" /> <path d=\"m 239.80518,751.1701 h -0.034 q -0.43404,0.6303 -1.29835,0.6303 -0.81147,0 -1.26438,-0.55482 -0.44914,-0.55482 -0.44914,-1.57764 0,-1.02283 0.45292,-1.58897 0.45291,-0.56614 1.2606,-0.56614 0.84167,0 1.2908,0.61143 h 0.0491 l -0.0264,-0.29817 -0.0151,-0.29062 v -1.68332 h 0.62653 v 5.87276 h -0.50952 z m -1.25306,0.10568 q 0.64163,0 0.92847,-0.34724 0.29062,-0.351 0.29062,-1.1285 v -0.1321 q 0,-0.87941 -0.29439,-1.25306 -0.29062,-0.37743 -0.93225,-0.37743 -0.55104,0 -0.84543,0.43027 -0.29062,0.42649 -0.29062,1.20776 0,0.7926 0.29062,1.19645 0.29062,0.40385 0.85298,0.40385 z\" id=\"path8056\" /> <path d=\"m 244.76457,751.28332 q 0.16607,0 0.32081,-0.0226 0.15475,-0.0264 0.24533,-0.0528 v 0.47933 q -0.1019,0.0491 -0.30194,0.0793 -0.19626,0.034 -0.35478,0.034 -1.20022,0 -1.20022,-1.26438 v -2.46083 h -0.59256 v -0.30194 l 0.59256,-0.26042 0.2642,-0.88318 h 0.36233 v 0.95866 h 1.20022 v 0.48688 h -1.20022 v 2.43441 q 0,0.37365 0.17739,0.57369 0.17739,0.20003 0.48688,0.20003 z\" id=\"path8058\" /> <path d=\"m 249.14004,749.65284 q 0,1.0115 -0.50953,1.58142 -0.50953,0.56614 -1.4078,0.56614 -0.55482,0 -0.98509,-0.26042 -0.43026,-0.26043 -0.66427,-0.74731 -0.234,-0.48688 -0.234,-1.13983 0,-1.01151 0.50575,-1.57387 0.50575,-0.56614 1.40403,-0.56614 0.86808,0 1.37761,0.57746 0.5133,0.57746 0.5133,1.56255 z m -3.15152,0 q 0,0.7926 0.31704,1.20777 0.31704,0.41517 0.93224,0.41517 0.61521,0 0.93225,-0.4114 0.32081,-0.41517 0.32081,-1.21154 0,-0.78882 -0.32081,-1.19645 -0.31704,-0.41139 -0.93979,-0.41139 -0.61521,0 -0.92848,0.40385 -0.31326,0.40384 -0.31326,1.20399 z\" id=\"path8060\" /> <path d=\"m 252.62046,747.58831 v 2.68351 q 0,0.50575 0.23023,0.75485 0.23023,0.24911 0.72089,0.24911 0.64917,0 0.94734,-0.35479 0.30194,-0.35478 0.30194,-1.1587 v -2.17398 h 0.62653 v 4.1366 h -0.51708 l -0.0906,-0.55481 h -0.034 q -0.19248,0.30571 -0.53594,0.46801 -0.33969,0.16229 -0.7775,0.16229 -0.75486,0 -1.13229,-0.35856 -0.37365,-0.35855 -0.37365,-1.14737 v -2.70616 z\" id=\"path8062\" /> <path d=\"m 258.25425,751.8004 q -0.40385,0 -0.73976,-0.1472 -0.33213,-0.15097 -0.55859,-0.46046 h -0.0453 q 0.0453,0.36233 0.0453,0.68692 v 1.7022 h -0.62653 v -5.99355 h 0.50953 l 0.0868,0.56614 h 0.0302 q 0.24155,-0.33968 0.56237,-0.49065 0.32081,-0.15097 0.73598,-0.15097 0.82279,0 1.26816,0.56236 0.44914,0.56237 0.44914,1.57765 0,1.01905 -0.45669,1.58519 -0.45291,0.56237 -1.26061,0.56237 z m -0.0906,-3.7554 q -0.63408,0 -0.91715,0.35101 -0.28307,0.351 -0.29062,1.11718 v 0.13965 q 0,0.87186 0.29062,1.24928 0.29062,0.37366 0.93225,0.37366 0.53594,0 0.83788,-0.43405 0.30572,-0.43404 0.30572,-1.19644 0,-0.77373 -0.30572,-1.18512 -0.30194,-0.41517 -0.85298,-0.41517 z\" id=\"path8064\" /> <path d=\"m 263.44268,751.1701 h -0.034 q -0.43404,0.6303 -1.29835,0.6303 -0.81147,0 -1.26438,-0.55482 -0.44914,-0.55482 -0.44914,-1.57764 0,-1.02283 0.45291,-1.58897 0.45292,-0.56614 1.26061,-0.56614 0.84166,0 1.2908,0.61143 h 0.0491 l -0.0264,-0.29817 -0.0151,-0.29062 v -1.68332 h 0.62653 v 5.87276 h -0.50953 z m -1.25306,0.10568 q 0.64163,0 0.92847,-0.34724 0.29062,-0.351 0.29062,-1.1285 v -0.1321 q 0,-0.87941 -0.29439,-1.25306 -0.29062,-0.37743 -0.93225,-0.37743 -0.55104,0 -0.84544,0.43027 -0.29061,0.42649 -0.29061,1.20776 0,0.7926 0.29061,1.19645 0.29062,0.40385 0.85299,0.40385 z\" id=\"path8066\" /> <path d=\"m 267.46863,751.72491 -0.12455,-0.58878 h -0.0302 q -0.30949,0.38875 -0.61898,0.5284 -0.30571,0.13587 -0.76617,0.13587 -0.61521,0 -0.96622,-0.31704 -0.34723,-0.31704 -0.34723,-0.90205 0,-1.25306 2.00414,-1.31345 l 0.70201,-0.0226 v -0.25665 q 0,-0.48688 -0.21136,-0.71711 -0.20758,-0.23401 -0.66804,-0.23401 -0.51708,0 -1.17003,0.31704 l -0.19248,-0.47933 q 0.30571,-0.16607 0.66804,-0.26043 0.36611,-0.0944 0.73221,-0.0944 0.73976,0 1.09454,0.32837 0.35856,0.32836 0.35856,1.05302 v 2.82315 z m -1.41535,-0.44159 q 0.58501,0 0.91715,-0.32081 0.33591,-0.32081 0.33591,-0.89828 v -0.37365 l -0.62653,0.0264 q -0.74731,0.0264 -1.07945,0.23401 -0.32836,0.20381 -0.32836,0.63785 0,0.33968 0.20381,0.51707 0.20759,0.17739 0.57747,0.17739 z\" id=\"path8068\" /> <path d=\"m 270.55856,751.28332 q 0.16607,0 0.32081,-0.0226 0.15475,-0.0264 0.24533,-0.0528 v 0.47933 q -0.1019,0.0491 -0.30194,0.0793 -0.19626,0.034 -0.35478,0.034 -1.20022,0 -1.20022,-1.26438 v -2.46083 h -0.59256 v -0.30194 l 0.59256,-0.26042 0.2642,-0.88318 h 0.36233 v 0.95866 h 1.20022 v 0.48688 h -1.20022 v 2.43441 q 0,0.37365 0.17739,0.57369 0.17739,0.20003 0.48688,0.20003 z\" id=\"path8070\" /> <path d=\"m 273.11116,751.8004 q -0.91715,0 -1.44932,-0.55859 -0.5284,-0.55859 -0.5284,-1.55123 0,-1.00018 0.49066,-1.58897 0.49443,-0.58878 1.32477,-0.58878 0.7775,0 1.23041,0.5133 0.45291,0.50952 0.45291,1.34741 v 0.3963 h -2.84957 q 0.0189,0.72844 0.3661,1.10586 0.35101,0.37743 0.98509,0.37743 0.66804,0 1.32099,-0.2793 v 0.5586 q -0.33213,0.14342 -0.6303,0.20381 -0.29439,0.0642 -0.71334,0.0642 z m -0.16984,-3.76295 q -0.4982,0 -0.79637,0.32459 -0.2944,0.32459 -0.34723,0.89827 h 2.16265 q 0,-0.59256 -0.2642,-0.90582 -0.26419,-0.31704 -0.75485,-0.31704 z\" id=\"path8072\" /> <path d=\"m 277.14576,747.58831 h 0.67182 l 0.90583,2.35892 q 0.29817,0.8077 0.36988,1.16625 h 0.0302 q 0.0491,-0.19249 0.20381,-0.65672 0.15852,-0.46801 1.0266,-2.86845 h 0.67182 l -1.77768,4.71029 q -0.2642,0.69824 -0.61898,0.98886 -0.35101,0.2944 -0.86431,0.2944 -0.28684,0 -0.56614,-0.0642 v -0.50197 q 0.20759,0.0453 0.46424,0.0453 0.6454,0 0.92092,-0.72466 l 0.23023,-0.58879 z\" id=\"path8074\" /> <path d=\"m 285.23772,749.65284 q 0,1.0115 -0.50952,1.58142 -0.50953,0.56614 -1.40781,0.56614 -0.55481,0 -0.98508,-0.26042 -0.43027,-0.26043 -0.66427,-0.74731 -0.23401,-0.48688 -0.23401,-1.13983 0,-1.01151 0.50575,-1.57387 0.50576,-0.56614 1.40403,-0.56614 0.86809,0 1.37761,0.57746 0.5133,0.57746 0.5133,1.56255 z m -3.15151,0 q 0,0.7926 0.31704,1.20777 0.31703,0.41517 0.93224,0.41517 0.61521,0 0.93225,-0.4114 0.32081,-0.41517 0.32081,-1.21154 0,-0.78882 -0.32081,-1.19645 -0.31704,-0.41139 -0.9398,-0.41139 -0.6152,0 -0.92847,0.40385 -0.31326,0.40384 -0.31326,1.20399 z\" id=\"path8076\" /> <path d=\"m 286.55387,747.58831 v 2.68351 q 0,0.50575 0.23023,0.75485 0.23023,0.24911 0.72089,0.24911 0.64917,0 0.94734,-0.35479 0.30194,-0.35478 0.30194,-1.1587 v -2.17398 h 0.62653 v 4.1366 h -0.51707 l -0.0906,-0.55481 h -0.034 q -0.19248,0.30571 -0.53594,0.46801 -0.33969,0.16229 -0.7775,0.16229 -0.75486,0 -1.13228,-0.35856 -0.37366,-0.35855 -0.37366,-1.14737 v -2.70616 z\" id=\"path8078\" /> <path d=\"m 292.14992,747.51283 q 0.27552,0 0.49443,0.0453 l -0.0868,0.58124 q -0.25665,-0.0566 -0.45291,-0.0566 -0.50198,0 -0.86054,0.40762 -0.35478,0.40762 -0.35478,1.01528 v 2.21927 h -0.62653 v -4.1366 h 0.51708 l 0.0717,0.76618 h 0.0302 q 0.23023,-0.40385 0.55482,-0.62276 0.32459,-0.2189 0.71334,-0.2189 z\" id=\"path8080\" /> <path d=\"m 295.07223,751.72491 v -5.51798 h 0.64162 v 4.93675 h 2.43441 v 0.58123 z\" id=\"path8082\" /> <path d=\"m 299.90219,751.72491 h -0.62653 v -4.1366 h 0.62653 z m -0.67937,-5.25756 q 0,-0.21513 0.10568,-0.31326 0.10568,-0.10191 0.2642,-0.10191 0.15097,0 0.26042,0.10191 0.10946,0.1019 0.10946,0.31326 0,0.21136 -0.10946,0.31704 -0.10945,0.10191 -0.26042,0.10191 -0.15852,0 -0.2642,-0.10191 -0.10568,-0.10568 -0.10568,-0.31704 z\" id=\"path8084\" /> <path d=\"m 303.82228,751.72491 v -2.67595 q 0,-0.50576 -0.23023,-0.75486 -0.23023,-0.2491 -0.72089,-0.2491 -0.64917,0 -0.95112,0.35101 -0.30194,0.351 -0.30194,1.1587 v 2.1702 h -0.62653 v -4.1366 h 0.50953 l 0.10191,0.56614 h 0.0302 q 0.19249,-0.30571 0.53972,-0.47178 0.34723,-0.16984 0.77373,-0.16984 0.7473,0 1.12473,0.36233 0.37743,0.35855 0.37743,1.15115 v 2.6986 z\" id=\"path8086\" /> <path d=\"m 305.87815,747.58831 v 2.68351 q 0,0.50575 0.23023,0.75485 0.23023,0.24911 0.72089,0.24911 0.64917,0 0.94734,-0.35479 0.30194,-0.35478 0.30194,-1.1587 v -2.17398 h 0.62653 v 4.1366 H 308.188 l -0.0906,-0.55481 h -0.034 q -0.19248,0.30571 -0.53594,0.46801 -0.33969,0.16229 -0.7775,0.16229 -0.75486,0 -1.13228,-0.35856 -0.37366,-0.35855 -0.37366,-1.14737 v -2.70616 z\" id=\"path8088\" /> <path d=\"m 310.58347,749.60755 -1.438,-2.01924 h 0.71334 l 1.09076,1.5852 1.087,-1.5852 h 0.70578 l -1.43799,2.01924 1.51348,2.11736 h -0.70956 l -1.15871,-1.67577 -1.17002,1.67577 h -0.70956 z\" id=\"path8090\" /> <path d=\"m 319.18618,747.81477 q 0,0.83789 -0.57369,1.2908 -0.56991,0.44914 -1.63426,0.44914 h -0.64917 v 2.1702 h -0.64163 v -5.51798 h 1.43045 q 2.0683,0 2.0683,1.60784 z m -2.85712,1.18889 h 0.57746 q 0.85299,0 1.23419,-0.27552 0.3812,-0.27552 0.3812,-0.88318 0,-0.54727 -0.35856,-0.81524 -0.35855,-0.26797 -1.11718,-0.26797 h -0.71711 z\" id=\"path8092\" /> <path d=\"m 323.19814,746.70136 q -0.9096,0 -1.438,0.60766 -0.52463,0.60388 -0.52463,1.6569 0,1.08322 0.50576,1.67578 0.50952,0.58878 1.44932,0.58878 0.57746,0 1.31722,-0.20758 v 0.56237 q -0.57369,0.21513 -1.41535,0.21513 -1.21909,0 -1.88337,-0.73976 -0.66049,-0.73975 -0.66049,-2.10227 0,-0.85298 0.31704,-1.49461 0.32081,-0.64163 0.92092,-0.98886 0.60388,-0.34723 1.41912,-0.34723 0.86809,0 1.51726,0.31704 l -0.27175,0.55104 q -0.62652,-0.29439 -1.25305,-0.29439 z\" id=\"path8094\" /> </g> <path d=\"M196.352 783.293H320.93v18.84H196.352Z\" style=\"fill:#ddd;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:1.93243;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3179\" /> <g aria-label=\"See https://k8s.io/linuxrepos\" id=\"text3183\" style=\"font-size:10.3063px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\"> <path d=\"m 276.10041,1058.3434 q 0,0.9713 -0.70453,1.5148 -0.70453,0.5435 -1.9123,0.5435 -1.30842,0 -2.01295,-0.3372 v -0.8253 q 0.45291,0.1912 0.98634,0.3019 0.53343,0.1107 1.0568,0.1107 0.8555,0 1.28829,-0.322 0.43278,-0.3271 0.43278,-0.9058 0,-0.3825 -0.156,-0.6241 -0.15097,-0.2466 -0.5133,-0.4529 -0.3573,-0.2063 -1.09203,-0.468 -1.0266,-0.3674 -1.46945,-0.8706 -0.43782,-0.5032 -0.43782,-1.3134 0,-0.8505 0.63911,-1.3537 0.63911,-0.5033 1.69088,-0.5033 1.09706,0 2.01798,0.4026 l -0.26671,0.7448 q -0.91086,-0.3825 -1.7714,-0.3825 -0.67937,0 -1.06183,0.2919 -0.38246,0.2919 -0.38246,0.8102 0,0.3825 0.14091,0.6291 0.1409,0.2415 0.47304,0.4479 0.33717,0.2012 1.0266,0.4478 1.15745,0.4127 1.59023,0.8857 0.43782,0.4731 0.43782,1.2279 z\" id=\"path8097\" /> <path d=\"m 281.01686,1060.4017 q -1.22286,0 -1.93243,-0.7448 -0.70453,-0.7448 -0.70453,-2.0683 0,-1.3336 0.65421,-2.1187 0.65924,-0.785 1.76636,-0.785 1.03667,0 1.64056,0.6844 0.60388,0.6794 0.60388,1.7966 v 0.5284 h -3.79944 q 0.0252,0.9712 0.48814,1.4744 0.46801,0.5033 1.31345,0.5033 0.89073,0 1.76133,-0.3724 v 0.7448 q -0.44285,0.1912 -0.84041,0.2717 -0.39252,0.086 -0.95112,0.086 z m -0.22645,-5.0173 q -0.66428,0 -1.06183,0.4328 -0.39253,0.4328 -0.46298,1.1977 h 2.88355 q 0,-0.7901 -0.35227,-1.2078 -0.35226,-0.4227 -1.00647,-0.4227 z\" id=\"path8099\" /> <path d=\"m 286.74709,1060.4017 q -1.22287,0 -1.93243,-0.7448 -0.70453,-0.7448 -0.70453,-2.0683 0,-1.3336 0.6542,-2.1187 0.65924,-0.785 1.76637,-0.785 1.03667,0 1.64055,0.6844 0.60389,0.6794 0.60389,1.7966 v 0.5284 h -3.79945 q 0.0252,0.9712 0.48814,1.4744 0.46801,0.5033 1.31345,0.5033 0.89073,0 1.76133,-0.3724 v 0.7448 q -0.44284,0.1912 -0.8404,0.2717 -0.39253,0.086 -0.95112,0.086 z m -0.22646,-5.0173 q -0.66427,0 -1.06183,0.4328 -0.39252,0.4328 -0.46298,1.1977 h 2.88355 q 0,-0.7901 -0.35226,-1.2078 -0.35227,-0.4227 -1.00648,-0.4227 z\" id=\"path8101\" /> <path d=\"m 296.77646,1060.301 v -3.5679 q 0,-0.6744 -0.30697,-1.0065 -0.30698,-0.3321 -0.96118,-0.3321 -0.87061,0 -1.2732,0.473 -0.39755,0.473 -0.39755,1.55 v 2.8835 h -0.83538 v -7.8303 h 0.83538 v 2.3702 q 0,0.4278 -0.0403,0.7096 h 0.0503 q 0.24659,-0.3976 0.6995,-0.624 0.45795,-0.2315 1.0417,-0.2315 1.01151,0 1.51475,0.4831 0.50827,0.478 0.50827,1.5248 v 3.5981 z\" id=\"path8103\" /> <path d=\"m 300.5139,1059.7122 q 0.22142,0 0.42775,-0.03 0.20633,-0.035 0.3271,-0.07 v 0.6391 q -0.13587,0.065 -0.40259,0.1057 -0.26168,0.045 -0.47304,0.045 -1.60029,0 -1.60029,-1.6859 v -3.2811 h -0.79009 v -0.4026 l 0.79009,-0.3472 0.35226,-1.1776 h 0.48311 v 1.2782 h 1.6003 v 0.6492 h -1.6003 v 3.2459 q 0,0.4982 0.23652,0.7649 0.23652,0.2667 0.64918,0.2667 z\" id=\"path8105\" /> <path d=\"m 303.36879,1059.7122 q 0.22142,0 0.42775,-0.03 0.20633,-0.035 0.3271,-0.07 v 0.6391 q -0.13587,0.065 -0.40259,0.1057 -0.26168,0.045 -0.47304,0.045 -1.60029,0 -1.60029,-1.6859 v -3.2811 h -0.79009 v -0.4026 l 0.79009,-0.3472 0.35226,-1.1776 h 0.48311 v 1.2782 h 1.60029 v 0.6492 h -1.60029 v 3.2459 q 0,0.4982 0.23652,0.7649 0.23652,0.2667 0.64918,0.2667 z\" id=\"path8107\" /> <path d=\"m 307.00863,1060.4017 q -0.53846,0 -0.98634,-0.1963 -0.44285,-0.2013 -0.74479,-0.6139 h -0.0604 q 0.0604,0.4831 0.0604,0.9159 v 2.2696 h -0.83538 v -7.9915 h 0.67938 l 0.11574,0.7549 h 0.0403 q 0.32207,-0.4529 0.74982,-0.6542 0.42775,-0.2013 0.98131,-0.2013 1.09706,0 1.69088,0.7498 0.59885,0.7498 0.59885,2.1036 0,1.3587 -0.60891,2.1135 -0.60389,0.7499 -1.68082,0.7499 z m -0.12077,-5.0072 q -0.84544,0 -1.22287,0.468 -0.37743,0.468 -0.38749,1.4896 v 0.1862 q 0,1.1624 0.38749,1.6657 0.38749,0.4982 1.243,0.4982 0.71459,0 1.11718,-0.5787 0.40763,-0.5788 0.40763,-1.5953 0,-1.0316 -0.40763,-1.5802 -0.40259,-0.5535 -1.13731,-0.5535 z\" id=\"path8109\" /> <path d=\"m 313.7303,1058.7963 q 0,0.77 -0.57369,1.1877 -0.57369,0.4177 -1.61036,0.4177 -1.09706,0 -1.71101,-0.3473 v -0.7749 q 0.39756,0.2012 0.85047,0.317 0.45795,0.1157 0.88067,0.1157 0.65421,0 1.00647,-0.2063 0.35227,-0.2113 0.35227,-0.6391 0,-0.3221 -0.28181,-0.5485 -0.27679,-0.2315 -1.087,-0.5435 -0.76995,-0.2869 -1.09705,-0.4982 -0.32208,-0.2164 -0.48311,-0.4882 -0.15601,-0.2717 -0.15601,-0.6491 0,-0.6744 0.54853,-1.0619 0.54853,-0.3925 1.50468,-0.3925 0.89073,0 1.7412,0.3623 l -0.29691,0.6794 q -0.83034,-0.3422 -1.50468,-0.3422 -0.59382,0 -0.89576,0.1862 -0.30194,0.1862 -0.30194,0.5133 0,0.2214 0.11071,0.3774 0.11575,0.156 0.36736,0.2969 0.25162,0.1409 0.96622,0.4077 0.98131,0.3573 1.32351,0.7196 0.34724,0.3623 0.34724,0.9108 z\" id=\"path8111\" /> <path d=\"m 315.2048,1059.7676 q 0,-0.3372 0.15097,-0.5083 0.15601,-0.1761 0.44285,-0.1761 0.29188,0 0.45291,0.1761 0.16607,0.1711 0.16607,0.5083 0,0.3271 -0.16607,0.5032 -0.16606,0.1762 -0.45291,0.1762 -0.25665,0 -0.42775,-0.156 -0.16607,-0.1611 -0.16607,-0.5234 z m 0,-4.4436 q 0,-0.6794 0.59382,-0.6794 0.61898,0 0.61898,0.6794 0,0.3271 -0.16607,0.5032 -0.16606,0.1762 -0.45291,0.1762 -0.25665,0 -0.42775,-0.156 -0.16607,-0.1611 -0.16607,-0.5234 z\" id=\"path8113\" /> <path d=\"m 320.97334,1052.9437 -2.74264,7.3573 h -0.83537 l 2.74264,-7.3573 z\" id=\"path8115\" /> <path d=\"m 323.82826,1052.9437 -2.74264,7.3573 h -0.83538 l 2.74265,-7.3573 z\" id=\"path8117\" /> <path d=\"m 324.7154,1057.4779 q 0.21639,-0.307 0.65924,-0.8052 l 1.78146,-1.8872 h 0.99138 l -2.23437,2.3502 2.39037,3.1653 h -1.0115 l -1.94753,-2.6067 -0.62905,0.5435 v 2.0632 h -0.82531 v -7.8303 h 0.82531 v 4.1517 q 0,0.2767 -0.0403,0.8555 z\" id=\"path8119\" /> <path d=\"m 331.09635,1052.838 q 1.00647,0 1.59526,0.468 0.58879,0.468 0.58879,1.2933 0,0.5435 -0.33717,0.9914 -0.33717,0.4479 -1.07693,0.8153 0.89576,0.4277 1.27319,0.9008 0.37743,0.468 0.37743,1.087 0,0.9158 -0.63911,1.4644 -0.63912,0.5435 -1.75127,0.5435 -1.17757,0 -1.81165,-0.5133 -0.63408,-0.5184 -0.63408,-1.4644 0,-1.2632 1.5399,-1.9677 -0.69446,-0.3925 -0.99641,-0.8454 -0.30194,-0.458 -0.30194,-1.0216 0,-0.8002 0.58879,-1.2732 0.59382,-0.4781 1.5852,-0.4781 z m -1.59023,5.6061 q 0,0.6039 0.41768,0.941 0.42272,0.3372 1.18261,0.3372 0.74982,0 1.16751,-0.3523 0.41769,-0.3522 0.41769,-0.9662 0,-0.4881 -0.39253,-0.8655 -0.39252,-0.3825 -1.3688,-0.7398 -0.74983,0.3221 -1.08699,0.7146 -0.33717,0.3875 -0.33717,0.931 z m 1.58016,-4.9267 q -0.62905,0 -0.98634,0.3019 -0.3573,0.302 -0.3573,0.8052 0,0.463 0.29691,0.7951 0.29691,0.3322 1.09706,0.6643 0.71962,-0.3019 1.01653,-0.6492 0.30195,-0.3472 0.30195,-0.8102 0,-0.5083 -0.36737,-0.8052 -0.36233,-0.3019 -1.00144,-0.3019 z\" id=\"path8121\" /> <path d=\"m 338.33128,1058.7963 q 0,0.77 -0.57369,1.1877 -0.57369,0.4177 -1.61036,0.4177 -1.09706,0 -1.71101,-0.3473 v -0.7749 q 0.39756,0.2012 0.85048,0.317 0.45794,0.1157 0.88066,0.1157 0.65421,0 1.00647,-0.2063 0.35227,-0.2113 0.35227,-0.6391 0,-0.3221 -0.28181,-0.5485 -0.27678,-0.2315 -1.08699,-0.5435 -0.76996,-0.2869 -1.09706,-0.4982 -0.32207,-0.2164 -0.48311,-0.4882 -0.156,-0.2717 -0.156,-0.6491 0,-0.6744 0.54853,-1.0619 0.54852,-0.3925 1.50468,-0.3925 0.89073,0 1.7412,0.3623 l -0.29691,0.6794 q -0.83035,-0.3422 -1.50468,-0.3422 -0.59382,0 -0.89577,0.1862 -0.30194,0.1862 -0.30194,0.5133 0,0.2214 0.11071,0.3774 0.11575,0.156 0.36737,0.2969 0.25162,0.1409 0.96621,0.4077 0.98132,0.3573 1.32352,0.7196 0.34723,0.3623 0.34723,0.9108 z\" id=\"path8123\" /> <path d=\"m 339.80581,1059.7676 q 0,-0.3372 0.15098,-0.5083 0.156,-0.1761 0.44284,-0.1761 0.29188,0 0.45292,0.1761 0.16607,0.1711 0.16607,0.5083 0,0.3271 -0.16607,0.5032 -0.16607,0.1762 -0.45292,0.1762 -0.25665,0 -0.42775,-0.156 -0.16607,-0.1611 -0.16607,-0.5234 z\" id=\"path8125\" /> <path d=\"m 343.61673,1060.301 h -0.83537 v -5.5155 h 0.83537 z m -0.90583,-7.0101 q 0,-0.2868 0.14091,-0.4177 0.14091,-0.1358 0.35227,-0.1358 0.20129,0 0.34723,0.1358 0.14594,0.1359 0.14594,0.4177 0,0.2818 -0.14594,0.4227 -0.14594,0.1359 -0.34723,0.1359 -0.21136,0 -0.35227,-0.1359 -0.14091,-0.1409 -0.14091,-0.4227 z\" id=\"path8127\" /> <path d=\"m 349.82998,1057.5383 q 0,1.3486 -0.67937,2.1085 -0.67937,0.7549 -1.87708,0.7549 -0.73976,0 -1.31345,-0.3473 -0.57369,-0.3472 -0.8857,-0.9964 -0.312,-0.6491 -0.312,-1.5197 0,-1.3487 0.67434,-2.0985 0.67433,-0.7549 1.87204,-0.7549 1.15744,0 1.83681,0.77 0.68441,0.7699 0.68441,2.0834 z m -4.20203,0 q 0,1.0568 0.42272,1.6103 0.42271,0.5536 1.24299,0.5536 0.82028,0 1.243,-0.5486 0.42775,-0.5535 0.42775,-1.6153 0,-1.0518 -0.42775,-1.5953 -0.42272,-0.5485 -1.25306,-0.5485 -0.82028,0 -1.23797,0.5384 -0.41768,0.5385 -0.41768,1.6054 z\" id=\"path8129\" /> <path d=\"m 353.5927,1052.9437 -2.74265,7.3573 h -0.83537 l 2.74264,-7.3573 z\" id=\"path8131\" /> <path d=\"m 355.41945,1060.301 h -0.83538 v -7.8303 h 0.83538 z\" id=\"path8133\" /> <path d=\"m 358.02622,1060.301 h -0.83538 v -5.5155 h 0.83538 z m -0.90583,-7.0101 q 0,-0.2868 0.14091,-0.4177 0.1409,-0.1358 0.35226,-0.1358 0.2013,0 0.34724,0.1358 0.14594,0.1359 0.14594,0.4177 0,0.2818 -0.14594,0.4227 -0.14594,0.1359 -0.34724,0.1359 -0.21136,0 -0.35226,-0.1359 -0.14091,-0.1409 -0.14091,-0.4227 z\" id=\"path8135\" /> <path d=\"m 363.57189,1060.301 v -3.5679 q 0,-0.6744 -0.30697,-1.0065 -0.30698,-0.3321 -0.96119,-0.3321 -0.86556,0 -1.26815,0.468 -0.40259,0.468 -0.40259,1.5449 v 2.8936 h -0.83538 v -5.5155 h 0.67937 l 0.13588,0.7549 h 0.0403 q 0.25665,-0.4076 0.71963,-0.629 0.46297,-0.2265 1.03163,-0.2265 0.99641,0 1.49965,0.4831 0.50324,0.4781 0.50324,1.5349 v 3.5981 z\" id=\"path8137\" /> <path d=\"m 366.90836,1054.7855 v 3.5781 q 0,0.6743 0.30697,1.0064 0.30698,0.3322 0.96118,0.3322 0.86557,0 1.26313,-0.4731 0.40259,-0.473 0.40259,-1.5449 v -2.8987 h 0.83537 v 5.5155 h -0.68943 l -0.12078,-0.7397 h -0.0453 q -0.25665,0.4076 -0.7146,0.624 -0.45291,0.2164 -1.03667,0.2164 -1.00647,0 -1.50971,-0.4781 -0.4982,-0.4781 -0.4982,-1.5298 v -3.6083 z\" id=\"path8139\" /> <path d=\"m 373.77755,1057.4779 -1.91734,-2.6924 h 0.95112 l 1.45436,2.1136 1.44932,-2.1136 h 0.94105 l -1.91733,2.6924 2.01798,2.8231 h -0.94609 l -1.54493,-2.2343 -1.56004,2.2343 h -0.94609 z\" id=\"path8141\" /> <path d=\"m 380.36492,1054.6849 q 0.36736,0 0.65924,0.06 l -0.11574,0.775 q -0.3422,-0.075 -0.60389,-0.075 -0.6693,0 -1.14738,0.5435 -0.47304,0.5435 -0.47304,1.3537 v 2.959 h -0.83537 v -5.5155 h 0.68943 l 0.0956,1.0216 h 0.0403 q 0.30698,-0.5384 0.73976,-0.8303 0.43279,-0.2919 0.95112,-0.2919 z\" id=\"path8143\" /> <path d=\"m 384.38579,1060.4017 q -1.22287,0 -1.93243,-0.7448 -0.70454,-0.7448 -0.70454,-2.0683 0,-1.3336 0.65421,-2.1187 0.65924,-0.785 1.76637,-0.785 1.03666,0 1.64055,0.6844 0.60388,0.6794 0.60388,1.7966 v 0.5284 h -3.79944 q 0.0252,0.9712 0.48814,1.4744 0.46801,0.5033 1.31345,0.5033 0.89073,0 1.76133,-0.3724 v 0.7448 q -0.44285,0.1912 -0.8404,0.2717 -0.39253,0.086 -0.95112,0.086 z m -0.22646,-5.0173 q -0.66427,0 -1.06183,0.4328 -0.39253,0.4328 -0.46298,1.1977 h 2.88355 q 0,-0.7901 -0.35226,-1.2078 -0.35227,-0.4227 -1.00648,-0.4227 z\" id=\"path8145\" /> <path d=\"m 390.40451,1060.4017 q -0.53847,0 -0.98635,-0.1963 -0.44285,-0.2013 -0.74479,-0.6139 h -0.0604 q 0.0604,0.4831 0.0604,0.9159 v 2.2696 h -0.83538 v -7.9915 h 0.67938 l 0.11574,0.7549 h 0.0403 q 0.32207,-0.4529 0.74982,-0.6542 0.42775,-0.2013 0.98132,-0.2013 1.09705,0 1.69087,0.7498 0.59885,0.7498 0.59885,2.1036 0,1.3587 -0.60891,2.1135 -0.60389,0.7499 -1.68081,0.7499 z m -0.12078,-5.0072 q -0.84544,0 -1.22287,0.468 -0.37743,0.468 -0.38749,1.4896 v 0.1862 q 0,1.1624 0.38749,1.6657 0.38749,0.4982 1.243,0.4982 0.71459,0 1.11718,-0.5787 0.40763,-0.5788 0.40763,-1.5953 0,-1.0316 -0.40763,-1.5802 -0.40259,-0.5535 -1.13731,-0.5535 z\" id=\"path8147\" /> <path d=\"m 398.91425,1057.5383 q 0,1.3486 -0.67937,2.1085 -0.67937,0.7549 -1.87708,0.7549 -0.73976,0 -1.31345,-0.3473 -0.57369,-0.3472 -0.88569,-0.9964 -0.31201,-0.6491 -0.31201,-1.5197 0,-1.3487 0.67434,-2.0985 0.67433,-0.7549 1.87204,-0.7549 1.15744,0 1.83682,0.77 0.6844,0.7699 0.6844,2.0834 z m -4.20203,0 q 0,1.0568 0.42272,1.6103 0.42272,0.5536 1.24299,0.5536 0.82028,0 1.243,-0.5486 0.42775,-0.5535 0.42775,-1.6153 0,-1.0518 -0.42775,-1.5953 -0.42272,-0.5485 -1.25306,-0.5485 -0.82028,0 -1.23797,0.5384 -0.41768,0.5385 -0.41768,1.6054 z\" id=\"path8149\" /> <path d=\"m 403.93656,1058.7963 q 0,0.77 -0.57369,1.1877 -0.57369,0.4177 -1.61036,0.4177 -1.09706,0 -1.71101,-0.3473 v -0.7749 q 0.39756,0.2012 0.85047,0.317 0.45795,0.1157 0.88067,0.1157 0.65421,0 1.00647,-0.2063 0.35227,-0.2113 0.35227,-0.6391 0,-0.3221 -0.28181,-0.5485 -0.27678,-0.2315 -1.087,-0.5435 -0.76995,-0.2869 -1.09705,-0.4982 -0.32208,-0.2164 -0.48311,-0.4882 -0.15601,-0.2717 -0.15601,-0.6491 0,-0.6744 0.54853,-1.0619 0.54853,-0.3925 1.50468,-0.3925 0.89073,0 1.7412,0.3623 l -0.29691,0.6794 q -0.83034,-0.3422 -1.50468,-0.3422 -0.59382,0 -0.89576,0.1862 -0.30194,0.1862 -0.30194,0.5133 0,0.2214 0.11071,0.3774 0.11575,0.156 0.36737,0.2969 0.25161,0.1409 0.96621,0.4077 0.98131,0.3573 1.32352,0.7196 0.34723,0.3623 0.34723,0.9108 z\" id=\"path8151\" /> </g> <path d=\"M365.316 740.297h55.36c5.199 0 9.418 4.223 9.418 9.422 0 5.199-4.219 9.418-9.418 9.418h-55.36c-5.199 0-9.418-4.219-9.418-9.418 0-5.199 4.219-9.422 9.418-9.422z\" style=\"fill:#ddd;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:1.93243;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3185\" /> <g aria-label=\"You're good to go!\" transform=\"scale(1.33333)\" id=\"text3189\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal'\"> <path d=\"m 364.03845,748.96592 1.47197,-2.75899 h 0.69446 l -1.84184,3.37797 v 2.14001 h -0.64918 v -2.10981 l -1.83807,-3.40817 h 0.70202 z\" id=\"path8154\" /> <path d=\"m 370.54733,749.65284 q 0,1.0115 -0.50953,1.58142 -0.50953,0.56614 -1.40781,0.56614 -0.55481,0 -0.98508,-0.26042 -0.43027,-0.26043 -0.66427,-0.74731 -0.23401,-0.48688 -0.23401,-1.13983 0,-1.01151 0.50576,-1.57387 0.50575,-0.56614 1.40402,-0.56614 0.86809,0 1.37761,0.57746 0.51331,0.57746 0.51331,1.56255 z m -3.15152,0 q 0,0.7926 0.31704,1.20777 0.31704,0.41517 0.93224,0.41517 0.61521,0 0.93225,-0.4114 0.32081,-0.41517 0.32081,-1.21154 0,-0.78882 -0.32081,-1.19645 -0.31704,-0.41139 -0.9398,-0.41139 -0.6152,0 -0.92847,0.40385 -0.31326,0.40384 -0.31326,1.20399 z\" id=\"path8156\" /> <path d=\"m 371.86335,747.58831 v 2.68351 q 0,0.50575 0.23023,0.75485 0.23023,0.24911 0.72089,0.24911 0.64917,0 0.94734,-0.35479 0.30194,-0.35478 0.30194,-1.1587 v -2.17398 h 0.62653 v 4.1366 h -0.51708 l -0.0906,-0.55481 h -0.034 q -0.19249,0.30571 -0.53594,0.46801 -0.33969,0.16229 -0.7775,0.16229 -0.75486,0 -1.13229,-0.35856 -0.37365,-0.35855 -0.37365,-1.14737 v -2.70616 z\" id=\"path8158\" /> <path d=\"m 376.1121,746.20693 -0.15097,1.99281 h -0.3963 l -0.15474,-1.99281 z\" id=\"path8160\" /> <path d=\"m 378.92812,747.51283 q 0.27552,0 0.49443,0.0453 l -0.0868,0.58124 q -0.25665,-0.0566 -0.45291,-0.0566 -0.50198,0 -0.86054,0.40762 -0.35478,0.40762 -0.35478,1.01528 v 2.21927 h -0.62653 v -4.1366 h 0.51708 l 0.0717,0.76618 h 0.0302 q 0.23023,-0.40385 0.55482,-0.62276 0.32459,-0.2189 0.71334,-0.2189 z\" id=\"path8162\" /> <path d=\"m 381.36247,751.8004 q -0.91714,0 -1.44932,-0.55859 -0.52839,-0.55859 -0.52839,-1.55123 0,-1.00018 0.49065,-1.58897 0.49443,-0.58878 1.32477,-0.58878 0.7775,0 1.23041,0.5133 0.45292,0.50952 0.45292,1.34741 v 0.3963 h -2.84958 q 0.0189,0.72844 0.3661,1.10586 0.35101,0.37743 0.98509,0.37743 0.66805,0 1.321,-0.2793 v 0.5586 q -0.33214,0.14342 -0.63031,0.20381 -0.29439,0.0642 -0.71334,0.0642 z m -0.16984,-3.76295 q -0.4982,0 -0.79637,0.32459 -0.29439,0.32459 -0.34723,0.89827 h 2.16266 q 0,-0.59256 -0.2642,-0.90582 -0.2642,-0.31704 -0.75486,-0.31704 z\" id=\"path8164\" /> <path d=\"m 389.43929,747.58831 v 0.3963 l -0.76618,0.0906 q 0.10568,0.1321 0.18872,0.34724 0.083,0.21136 0.083,0.47933 0,0.60766 -0.41517,0.96999 -0.41517,0.36233 -1.13983,0.36233 -0.18494,0 -0.34723,-0.0302 -0.40008,0.21136 -0.40008,0.53218 0,0.16984 0.13965,0.25287 0.13965,0.0793 0.47934,0.0793 h 0.7322 q 0.67182,0 1.03038,0.28307 0.36233,0.28307 0.36233,0.82279 0,0.68692 -0.55104,1.04548 -0.55105,0.36233 -1.60784,0.36233 -0.81147,0 -1.25306,-0.30195 -0.43782,-0.30194 -0.43782,-0.85298 0,-0.37743 0.24156,-0.65295 0.24155,-0.27552 0.67936,-0.37365 -0.15851,-0.0717 -0.26797,-0.22268 -0.10568,-0.15098 -0.10568,-0.35101 0,-0.22646 0.12078,-0.3963 0.12078,-0.16984 0.3812,-0.32836 -0.32081,-0.1321 -0.52462,-0.44914 -0.20004,-0.31704 -0.20004,-0.72466 0,-0.67937 0.40762,-1.04547 0.40762,-0.36988 1.15493,-0.36988 0.32459,0 0.58501,0.0755 z m -3.29871,4.83107 q 0,0.33591 0.28307,0.50953 0.28307,0.17361 0.81147,0.17361 0.78882,0 1.16625,-0.23778 0.3812,-0.234 0.3812,-0.63785 0,-0.33591 -0.20759,-0.46801 -0.20758,-0.12832 -0.78127,-0.12832 h -0.75108 q -0.4265,0 -0.66427,0.20381 -0.23778,0.20381 -0.23778,0.58501 z m 0.33968,-3.5063 q 0,0.43404 0.24533,0.65672 0.24533,0.22269 0.68314,0.22269 0.91715,0 0.91715,-0.89073 0,-0.93225 -0.92847,-0.93225 -0.44159,0 -0.67937,0.23778 -0.23778,0.23778 -0.23778,0.70579 z\" id=\"path8166\" /> <path d=\"m 393.92202,749.65284 q 0,1.0115 -0.50953,1.58142 -0.50952,0.56614 -1.4078,0.56614 -0.55482,0 -0.98509,-0.26042 -0.43026,-0.26043 -0.66427,-0.74731 -0.234,-0.48688 -0.234,-1.13983 0,-1.01151 0.50575,-1.57387 0.50575,-0.56614 1.40403,-0.56614 0.86808,0 1.37761,0.57746 0.5133,0.57746 0.5133,1.56255 z m -3.15152,0 q 0,0.7926 0.31704,1.20777 0.31704,0.41517 0.93225,0.41517 0.6152,0 0.93224,-0.4114 0.32082,-0.41517 0.32082,-1.21154 0,-0.78882 -0.32082,-1.19645 -0.31704,-0.41139 -0.93979,-0.41139 -0.61521,0 -0.92847,0.40385 -0.31327,0.40384 -0.31327,1.20399 z\" id=\"path8168\" /> <path d=\"m 398.21972,749.65284 q 0,1.0115 -0.50953,1.58142 -0.50952,0.56614 -1.4078,0.56614 -0.55482,0 -0.98509,-0.26042 -0.43026,-0.26043 -0.66427,-0.74731 -0.234,-0.48688 -0.234,-1.13983 0,-1.01151 0.50575,-1.57387 0.50575,-0.56614 1.40403,-0.56614 0.86808,0 1.37761,0.57746 0.5133,0.57746 0.5133,1.56255 z m -3.15152,0 q 0,0.7926 0.31704,1.20777 0.31704,0.41517 0.93225,0.41517 0.6152,0 0.93224,-0.4114 0.32081,-0.41517 0.32081,-1.21154 0,-0.78882 -0.32081,-1.19645 -0.31704,-0.41139 -0.93979,-0.41139 -0.61521,0 -0.92847,0.40385 -0.31327,0.40384 -0.31327,1.20399 z\" id=\"path8170\" /> <path d=\"m 401.76259,751.1701 h -0.034 q -0.43405,0.6303 -1.29835,0.6303 -0.81147,0 -1.26439,-0.55482 -0.44913,-0.55482 -0.44913,-1.57764 0,-1.02283 0.45291,-1.58897 0.45291,-0.56614 1.26061,-0.56614 0.84166,0 1.2908,0.61143 h 0.0491 l -0.0264,-0.29817 -0.0151,-0.29062 v -1.68332 h 0.62652 v 5.87276 h -0.50952 z m -1.25305,0.10568 q 0.64162,0 0.92847,-0.34724 0.29062,-0.351 0.29062,-1.1285 v -0.1321 q 0,-0.87941 -0.2944,-1.25306 -0.29062,-0.37743 -0.93224,-0.37743 -0.55105,0 -0.84544,0.43027 -0.29062,0.42649 -0.29062,1.20776 0,0.7926 0.29062,1.19645 0.29062,0.40385 0.85299,0.40385 z\" id=\"path8172\" /> <path d=\"m 406.72195,751.28332 q 0.16607,0 0.32082,-0.0226 0.15474,-0.0264 0.24532,-0.0528 v 0.47933 q -0.1019,0.0491 -0.30194,0.0793 -0.19626,0.034 -0.35478,0.034 -1.20022,0 -1.20022,-1.26438 v -2.46083 h -0.59256 v -0.30194 l 0.59256,-0.26042 0.2642,-0.88318 h 0.36233 v 0.95866 h 1.20022 v 0.48688 h -1.20022 v 2.43441 q 0,0.37365 0.17739,0.57369 0.17739,0.20003 0.48688,0.20003 z\" id=\"path8174\" /> <path d=\"m 411.09744,749.65284 q 0,1.0115 -0.50953,1.58142 -0.50953,0.56614 -1.40781,0.56614 -0.55481,0 -0.98508,-0.26042 -0.43027,-0.26043 -0.66427,-0.74731 -0.23401,-0.48688 -0.23401,-1.13983 0,-1.01151 0.50576,-1.57387 0.50575,-0.56614 1.40402,-0.56614 0.86809,0 1.37761,0.57746 0.51331,0.57746 0.51331,1.56255 z m -3.15152,0 q 0,0.7926 0.31704,1.20777 0.31704,0.41517 0.93224,0.41517 0.61521,0 0.93225,-0.4114 0.32081,-0.41517 0.32081,-1.21154 0,-0.78882 -0.32081,-1.19645 -0.31704,-0.41139 -0.9398,-0.41139 -0.6152,0 -0.92847,0.40385 -0.31326,0.40384 -0.31326,1.20399 z\" id=\"path8176\" /> <path d=\"m 417.35131,747.58831 v 0.3963 l -0.76618,0.0906 q 0.10568,0.1321 0.18871,0.34724 0.083,0.21136 0.083,0.47933 0,0.60766 -0.41517,0.96999 -0.41517,0.36233 -1.13983,0.36233 -0.18494,0 -0.34723,-0.0302 -0.40008,0.21136 -0.40008,0.53218 0,0.16984 0.13965,0.25287 0.13965,0.0793 0.47933,0.0793 h 0.73221 q 0.67182,0 1.03038,0.28307 0.36233,0.28307 0.36233,0.82279 0,0.68692 -0.55105,1.04548 -0.55104,0.36233 -1.60784,0.36233 -0.81146,0 -1.25305,-0.30195 -0.43782,-0.30194 -0.43782,-0.85298 0,-0.37743 0.24155,-0.65295 0.24156,-0.27552 0.67937,-0.37365 -0.15852,-0.0717 -0.26797,-0.22268 -0.10568,-0.15098 -0.10568,-0.35101 0,-0.22646 0.12078,-0.3963 0.12077,-0.16984 0.3812,-0.32836 -0.32082,-0.1321 -0.52463,-0.44914 -0.20003,-0.31704 -0.20003,-0.72466 0,-0.67937 0.40762,-1.04547 0.40762,-0.36988 1.15493,-0.36988 0.32458,0 0.58501,0.0755 z m -3.29872,4.83107 q 0,0.33591 0.28307,0.50953 0.28307,0.17361 0.81147,0.17361 0.78883,0 1.16625,-0.23778 0.3812,-0.234 0.3812,-0.63785 0,-0.33591 -0.20758,-0.46801 -0.20759,-0.12832 -0.78127,-0.12832 h -0.75108 q -0.4265,0 -0.66428,0.20381 -0.23778,0.20381 -0.23778,0.58501 z m 0.33969,-3.5063 q 0,0.43404 0.24533,0.65672 0.24532,0.22269 0.68314,0.22269 0.91715,0 0.91715,-0.89073 0,-0.93225 -0.92847,-0.93225 -0.44159,0 -0.67937,0.23778 -0.23778,0.23778 -0.23778,0.70579 z\" id=\"path8178\" /> <path d=\"m 421.83395,749.65284 q 0,1.0115 -0.50953,1.58142 -0.50953,0.56614 -1.4078,0.56614 -0.55482,0 -0.98509,-0.26042 -0.43027,-0.26043 -0.66427,-0.74731 -0.23401,-0.48688 -0.23401,-1.13983 0,-1.01151 0.50576,-1.57387 0.50575,-0.56614 1.40403,-0.56614 0.86808,0 1.37761,0.57746 0.5133,0.57746 0.5133,1.56255 z m -3.15152,0 q 0,0.7926 0.31704,1.20777 0.31704,0.41517 0.93224,0.41517 0.61521,0 0.93225,-0.4114 0.32081,-0.41517 0.32081,-1.21154 0,-0.78882 -0.32081,-1.19645 -0.31704,-0.41139 -0.9398,-0.41139 -0.6152,0 -0.92847,0.40385 -0.31326,0.40384 -0.31326,1.20399 z\" id=\"path8180\" /> <path d=\"m 423.12742,750.20388 h -0.3963 l -0.19249,-3.99695 h 0.78127 z m -0.65673,1.12096 q 0,-0.5133 0.45292,-0.5133 0.2189,0 0.33591,0.1321 0.12077,0.1321 0.12077,0.3812 0,0.24156 -0.12077,0.37743 -0.12078,0.1321 -0.33591,0.1321 -0.19627,0 -0.32459,-0.117 -0.12833,-0.12078 -0.12833,-0.39253 z\" id=\"path8182\" /> </g> <path d=\"M258.852 243.945h71.242c8.398 0 15.218 6.821 15.218 15.219s-6.82 15.219-15.218 15.219h-71.242c-8.399 0-15.219-6.821-15.219-15.219s6.82-15.219 15.219-15.219z\" style=\"fill:#ddd;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:1.93243;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3191\" /> <g id=\"g12873\"> <path d=\"m 339.81028,338.53774 1.96263,-3.67864 h 0.92594 l -2.45578,4.50394 v 2.85336 h -0.86557 v -2.81309 l -2.45076,-4.54421 h 0.93603 z\" id=\"path8185\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 348.48878,339.45363 q 0,1.34866 -0.67937,2.10856 -0.67936,0.75485 -1.87706,0.75485 -0.73976,0 -1.31344,-0.34723 -0.57369,-0.34724 -0.8857,-0.99641 -0.312,-0.64917 -0.312,-1.51977 0,-1.34868 0.67433,-2.09849 0.67433,-0.75485 1.87204,-0.75485 1.15743,0 1.8368,0.76995 0.6844,0.76994 0.6844,2.08339 z m -4.20201,0 q 0,1.0568 0.42271,1.61036 0.42272,0.55356 1.243,0.55356 0.82027,0 1.24299,-0.54854 0.42775,-0.55355 0.42775,-1.61538 0,-1.05176 -0.42775,-1.59525 -0.42272,-0.54853 -1.25305,-0.54853 -0.82028,0 -1.23796,0.53847 -0.41769,0.53845 -0.41769,1.60531 z\" id=\"path8187\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 350.24347,336.70093 v 3.57801 q 0,0.67433 0.30699,1.00646 0.30697,0.33215 0.96117,0.33215 0.86557,0 1.26311,-0.47304 0.4026,-0.47305 0.4026,-1.54495 v -2.89863 h 0.83536 v 5.51547 h -0.68942 l -0.1208,-0.73976 h -0.0453 q -0.25665,0.40761 -0.71459,0.62401 -0.45291,0.21639 -1.03667,0.21639 -1.00646,0 -1.5097,-0.47808 -0.4982,-0.47807 -0.4982,-1.52982 v -3.60821 z\" id=\"path8189\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 365.07381,342.2164 v -3.58807 q 0,-0.65924 -0.28182,-0.98635 -0.28181,-0.33213 -0.87562,-0.33213 -0.78001,0 -1.15241,0.44788 -0.3724,0.44788 -0.3724,1.37886 v 3.07981 h -0.83537 v -3.58807 q 0,-0.65924 -0.2818,-0.98635 -0.28181,-0.33213 -0.88066,-0.33213 -0.78506,0 -1.15241,0.47304 -0.36234,0.46801 -0.36234,1.5399 v 2.89361 h -0.83537 v -5.51547 h 0.67937 l 0.13587,0.75485 h 0.0403 q 0.23652,-0.40258 0.66426,-0.62904 0.43279,-0.22645 0.96621,-0.22645 1.29332,0 1.69088,0.93601 h 0.0403 q 0.24659,-0.43278 0.7146,-0.6844 0.46801,-0.25161 1.06685,-0.25161 0.93603,0 1.399,0.48311 0.46801,0.47806 0.46801,1.53486 v 3.59814 z\" id=\"path8191\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 370.02043,342.2164 -0.16606,-0.78505 h -0.0403 q -0.41265,0.51833 -0.8253,0.70453 -0.40763,0.18116 -1.02157,0.18116 -0.82028,0 -1.28828,-0.42272 -0.46299,-0.42272 -0.46299,-1.20273 0,-1.67074 2.67218,-1.75126 l 0.93603,-0.0301 v -0.3422 q 0,-0.64917 -0.28181,-0.95614 -0.27679,-0.31201 -0.89073,-0.31201 -0.68943,0 -1.56003,0.42272 l -0.25665,-0.63911 q 0.40763,-0.22143 0.89073,-0.34724 0.48813,-0.12573 0.97626,-0.12573 0.98635,0 1.45939,0.43781 0.47808,0.43781 0.47808,1.40402 v 3.76421 z m -1.88712,-0.58879 q 0.78001,0 1.22286,-0.42776 0.44788,-0.42774 0.44788,-1.19769 v -0.49821 l -0.83537,0.0352 q -0.99641,0.0352 -1.43925,0.31201 -0.43781,0.27175 -0.43781,0.85047 0,0.4529 0.27174,0.68942 0.27677,0.23654 0.76995,0.23654 z\" id=\"path8193\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 371.48342,336.70093 h 0.89576 l 1.20777,3.14522 q 0.39754,1.07693 0.49317,1.555 h 0.0403 q 0.0655,-0.25664 0.27175,-0.87563 0.21136,-0.62401 1.3688,-3.82459 h 0.89576 l -2.37024,6.28037 q -0.35226,0.931 -0.8253,1.31848 -0.46802,0.39253 -1.15241,0.39253 -0.38246,0 -0.75486,-0.0856 v -0.66929 q 0.27679,0.0604 0.61899,0.0604 0.86053,0 1.22789,-0.96621 l 0.30697,-0.78505 z\" id=\"path8195\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 384.14115,342.2164 v -3.56794 q 0,-0.67434 -0.30698,-1.00648 -0.30697,-0.33213 -0.96118,-0.33213 -0.86556,0 -1.26814,0.46801 -0.4026,0.468 -0.4026,1.54493 v 2.89361 h -0.83537 v -5.51547 h 0.67937 l 0.13588,0.75485 h 0.0403 q 0.25666,-0.40761 0.71963,-0.62904 0.46298,-0.22645 1.03164,-0.22645 0.99639,0 1.49963,0.48311 0.50324,0.47806 0.50324,1.53486 v 3.59814 z\" id=\"path8197\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 388.42711,342.31704 q -1.22286,0 -1.93242,-0.74479 -0.70453,-0.74478 -0.70453,-2.0683 0,-1.33357 0.65421,-2.11862 0.65924,-0.78504 1.76635,-0.78504 1.03667,0 1.64055,0.6844 0.60387,0.67937 0.60387,1.79654 v 0.5284 h -3.79941 q 0.0252,0.97125 0.48813,1.47448 0.46801,0.50324 1.31345,0.50324 0.89072,0 1.76131,-0.37239 v 0.74479 q -0.44283,0.19122 -0.84039,0.27174 -0.39252,0.0856 -0.95112,0.0856 z m -0.22645,-5.01726 q -0.66427,0 -1.06183,0.43279 -0.39253,0.43278 -0.46297,1.1977 h 2.88353 q 0,-0.79009 -0.35227,-1.20777 -0.35225,-0.42272 -1.00646,-0.42272 z\" id=\"path8199\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 394.15748,342.31704 q -1.22286,0 -1.93242,-0.74479 -0.70453,-0.74478 -0.70453,-2.0683 0,-1.33357 0.65421,-2.11862 0.65924,-0.78504 1.76636,-0.78504 1.03666,0 1.64054,0.6844 0.60388,0.67937 0.60388,1.79654 v 0.5284 h -3.79942 q 0.0252,0.97125 0.48813,1.47448 0.46801,0.50324 1.31345,0.50324 0.89072,0 1.76132,-0.37239 v 0.74479 q -0.44284,0.19122 -0.8404,0.27174 -0.39252,0.0856 -0.95112,0.0856 z m -0.22645,-5.01726 q -0.66427,0 -1.06183,0.43279 -0.39251,0.43278 -0.46297,1.1977 h 2.88353 q 0,-0.79009 -0.35227,-1.20777 -0.35225,-0.42272 -1.00646,-0.42272 z\" id=\"path8201\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 401.31189,341.47664 h -0.0453 q -0.57872,0.8404 -1.73113,0.8404 -1.08196,0 -1.68584,-0.73976 -0.59885,-0.73976 -0.59885,-2.10352 0,-1.36377 0.60389,-2.11862 0.60388,-0.75485 1.6808,-0.75485 1.12222,0 1.72106,0.81524 h 0.0655 l -0.0352,-0.39756 -0.0201,-0.38749 v -2.24442 h 0.83537 v 7.83034 h -0.67937 z m -1.67074,0.14091 q 0.8555,0 1.23795,-0.46299 0.3875,-0.468 0.3875,-1.50466 v -0.17614 q 0,-1.17254 -0.39252,-1.67074 -0.38749,-0.50324 -1.243,-0.50324 -0.73472,0 -1.12724,0.5737 -0.38749,0.56865 -0.38749,1.61035 0,1.05679 0.38749,1.59525 0.3875,0.53847 1.13731,0.53847 z\" id=\"path8203\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 407.92427,341.62761 q 0.22143,0 0.42775,-0.0301 0.20633,-0.0352 0.3271,-0.0704 v 0.6391 q -0.13587,0.0655 -0.40258,0.10574 -0.26169,0.0453 -0.47304,0.0453 -1.60029,0 -1.60029,-1.68583 v -3.2811 h -0.79008 v -0.40259 l 0.79008,-0.34722 0.35227,-1.17758 h 0.4831 v 1.27821 h 1.60028 v 0.64918 h -1.60028 v 3.24587 q 0,0.4982 0.23652,0.76492 0.23652,0.26672 0.64917,0.26672 z\" id=\"path8205\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 413.75835,339.45363 q 0,1.34866 -0.67936,2.10856 -0.67937,0.75485 -1.87707,0.75485 -0.73976,0 -1.31344,-0.34723 -0.57369,-0.34724 -0.8857,-0.99641 -0.312,-0.64917 -0.312,-1.51977 0,-1.34868 0.67433,-2.09849 0.67433,-0.75485 1.87204,-0.75485 1.15743,0 1.8368,0.76995 0.6844,0.76994 0.6844,2.08339 z m -4.20201,0 q 0,1.0568 0.42272,1.61036 0.42271,0.55356 1.24299,0.55356 0.82028,0 1.24299,-0.54854 0.42775,-0.55355 0.42775,-1.61538 0,-1.05176 -0.42775,-1.59525 -0.42271,-0.54853 -1.25305,-0.54853 -0.82028,0 -1.23796,0.53847 -0.41769,0.53845 -0.41769,1.60531 z\" id=\"path8207\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 418.39878,336.70093 v 3.57801 q 0,0.67433 0.30697,1.00646 0.30698,0.33215 0.96119,0.33215 0.86556,0 1.26311,-0.47304 0.40259,-0.47305 0.40259,-1.54495 v -2.89863 h 0.83537 v 5.51547 h -0.68942 l -0.1208,-0.73976 h -0.0453 q -0.25665,0.40761 -0.71459,0.62401 -0.45292,0.21639 -1.03667,0.21639 -1.00648,0 -1.5097,-0.47808 -0.49821,-0.47807 -0.49821,-1.52982 v -3.60821 z\" id=\"path8209\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 425.91048,342.31704 q -0.53845,0 -0.98633,-0.19627 -0.44285,-0.20129 -0.7448,-0.61394 h -0.0604 q 0.0604,0.4831 0.0604,0.91589 v 2.26959 h -0.83537 v -7.99138 h 0.67937 l 0.11574,0.75485 h 0.0403 q 0.32208,-0.4529 0.74983,-0.6542 0.42774,-0.20129 0.9813,-0.20129 1.09707,0 1.69088,0.74981 0.59885,0.74983 0.59885,2.10353 0,1.35873 -0.60892,2.11358 -0.60388,0.74983 -1.68081,0.74983 z m -0.1208,-5.00719 q -0.84544,0 -1.22286,0.46801 -0.37743,0.468 -0.38749,1.48957 v 0.1862 q 0,1.16248 0.38749,1.6657 0.38749,0.49822 1.243,0.49822 0.71459,0 1.11718,-0.57872 0.40761,-0.57873 0.40761,-1.59527 0,-1.03162 -0.40761,-1.58015 -0.40259,-0.55356 -1.13732,-0.55356 z\" id=\"path8211\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 432.82837,341.47664 h -0.0453 q -0.57872,0.8404 -1.73113,0.8404 -1.08196,0 -1.68584,-0.73976 -0.59885,-0.73976 -0.59885,-2.10352 0,-1.36377 0.60389,-2.11862 0.60388,-0.75485 1.6808,-0.75485 1.12222,0 1.72106,0.81524 h 0.0655 l -0.0352,-0.39756 -0.0201,-0.38749 v -2.24442 h 0.83538 v 7.83034 h -0.67936 z m -1.67074,0.14091 q 0.8555,0 1.23796,-0.46299 0.38749,-0.468 0.38749,-1.50466 v -0.17614 q 0,-1.17254 -0.39252,-1.67074 -0.38749,-0.50324 -1.243,-0.50324 -0.73472,0 -1.12724,0.5737 -0.38749,0.56865 -0.38749,1.61035 0,1.05679 0.38749,1.59525 0.3875,0.53847 1.13731,0.53847 z\" id=\"path8213\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 438.19641,342.2164 -0.16607,-0.78505 h -0.0403 q -0.41265,0.51833 -0.82531,0.70453 -0.40762,0.18116 -1.02157,0.18116 -0.82027,0 -1.28827,-0.42272 -0.46299,-0.42272 -0.46299,-1.20273 0,-1.67074 2.67218,-1.75126 l 0.93602,-0.0301 v -0.3422 q 0,-0.64917 -0.28181,-0.95614 -0.27678,-0.31201 -0.89073,-0.31201 -0.68942,0 -1.56002,0.42272 l -0.25665,-0.63911 q 0.40762,-0.22143 0.89073,-0.34724 0.48813,-0.12573 0.97626,-0.12573 0.98635,0 1.45938,0.43781 0.47808,0.43781 0.47808,1.40402 v 3.76421 z m -1.88713,-0.58879 q 0.78001,0 1.22287,-0.42776 0.44788,-0.42774 0.44788,-1.19769 v -0.49821 l -0.83538,0.0352 q -0.99639,0.0352 -1.43925,0.31201 -0.43781,0.27175 -0.43781,0.85047 0,0.4529 0.27175,0.68942 0.27677,0.23654 0.76994,0.23654 z\" id=\"path8215\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 442.31632,341.62761 q 0.22141,0 0.42775,-0.0301 0.20632,-0.0352 0.3271,-0.0704 v 0.6391 q -0.13588,0.0655 -0.4026,0.10574 -0.26168,0.0453 -0.47304,0.0453 -1.60028,0 -1.60028,-1.68583 v -3.2811 h -0.79008 v -0.40259 l 0.79008,-0.34722 0.35226,-1.17758 h 0.48311 v 1.27821 h 1.60029 v 0.64918 h -1.60029 v 3.24587 q 0,0.4982 0.23652,0.76492 0.23653,0.26672 0.64918,0.26672 z\" id=\"path8217\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 445.71965,342.31704 q -1.22285,0 -1.93243,-0.74479 -0.70451,-0.74478 -0.70451,-2.0683 0,-1.33357 0.65419,-2.11862 0.65924,-0.78504 1.76636,-0.78504 1.03666,0 1.64054,0.6844 0.60389,0.67937 0.60389,1.79654 v 0.5284 h -3.79943 q 0.0252,0.97125 0.48815,1.47448 0.468,0.50324 1.31344,0.50324 0.89073,0 1.76132,-0.37239 v 0.74479 q -0.44285,0.19122 -0.84041,0.27174 -0.39252,0.0856 -0.95111,0.0856 z m -0.22646,-5.01726 q -0.66426,0 -1.06182,0.43279 -0.39252,0.43278 -0.46297,1.1977 h 2.88354 q 0,-0.79009 -0.35227,-1.20777 -0.35227,-0.42272 -1.00648,-0.42272 z\" id=\"path8219\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 334.75735,348.72491 h 0.89577 l 1.20776,3.14522 q 0.39756,1.07692 0.49317,1.555 h 0.0403 q 0.0655,-0.25665 0.27174,-0.87562 0.21136,-0.62402 1.36881,-3.8246 h 0.89576 l -2.37025,6.28038 q -0.35225,0.93098 -0.8253,1.31847 -0.468,0.39252 -1.1524,0.39252 -0.38246,0 -0.75486,-0.0856 v -0.6693 q 0.27678,0.0604 0.61898,0.0604 0.86053,0 1.22789,-0.96621 l 0.30697,-0.78504 z\" id=\"path8222\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 345.54678,351.47761 q 0,1.34867 -0.67938,2.10856 -0.67935,0.75485 -1.87706,0.75485 -0.73976,0 -1.31345,-0.34724 -0.57368,-0.34722 -0.88569,-0.9964 -0.312,-0.64918 -0.312,-1.51977 0,-1.34867 0.67433,-2.0985 0.67434,-0.75485 1.87204,-0.75485 1.15744,0 1.83681,0.76996 0.6844,0.76994 0.6844,2.08339 z m -4.20202,0 q 0,1.05679 0.42272,1.61035 0.42272,0.55356 1.243,0.55356 0.82026,0 1.24298,-0.54852 0.42774,-0.55356 0.42774,-1.61539 0,-1.05177 -0.42774,-1.59526 -0.42272,-0.54853 -1.25305,-0.54853 -0.82028,0 -1.23796,0.53847 -0.41769,0.53846 -0.41769,1.60532 z\" id=\"path8224\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 347.30147,348.72491 v 3.57801 q 0,0.67433 0.30697,1.00646 0.30697,0.33214 0.96118,0.33214 0.86556,0 1.26312,-0.47304 0.40258,-0.47304 0.40258,-1.54493 v -2.89864 h 0.83538 v 5.51546 h -0.68943 l -0.1208,-0.73976 h -0.0453 q -0.25665,0.40763 -0.7146,0.62401 -0.45292,0.2164 -1.03666,0.2164 -1.00648,0 -1.50971,-0.47808 -0.49821,-0.47808 -0.49821,-1.52983 v -3.6082 z\" id=\"path8226\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 354.76285,348.62426 q 0.36736,0 0.65923,0.0604 l -0.11573,0.77499 q -0.3422,-0.0755 -0.60388,-0.0755 -0.6693,0 -1.14737,0.54349 -0.47305,0.54349 -0.47305,1.35371 v 2.95901 h -0.83537 v -5.51545 h 0.68944 l 0.0956,1.02157 h 0.0403 q 0.30698,-0.53846 0.73975,-0.83034 0.43278,-0.29188 0.95112,-0.29188 z\" id=\"path8228\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 362.09135,352.73569 q 0,0.76996 -0.57368,1.18764 -0.57369,0.41769 -1.61036,0.41769 -1.09705,0 -1.71099,-0.34724 v -0.77498 q 0.39754,0.20129 0.85046,0.31704 0.45795,0.11573 0.88067,0.11573 0.6542,0 1.00646,-0.20632 0.35227,-0.21136 0.35227,-0.63912 0,-0.32206 -0.28182,-0.54852 -0.27677,-0.23149 -1.08698,-0.54349 -0.76996,-0.28685 -1.09705,-0.49821 -0.32208,-0.21639 -0.48311,-0.48813 -0.15601,-0.27175 -0.15601,-0.64918 0,-0.67434 0.54853,-1.06182 0.54854,-0.39253 1.50468,-0.39253 0.89072,0 1.7412,0.36233 l -0.29692,0.67937 q -0.83034,-0.3422 -1.50467,-0.3422 -0.59382,0 -0.89575,0.18619 -0.30195,0.1862 -0.30195,0.5133 0,0.22143 0.11067,0.37743 0.11573,0.156 0.36737,0.29691 0.25161,0.1409 0.96621,0.40762 0.9813,0.35729 1.3235,0.71963 0.34723,0.36233 0.34723,0.91085 z\" id=\"path8230\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 366.01664,354.34102 q -1.22286,0 -1.93242,-0.7448 -0.70453,-0.74478 -0.70453,-2.06829 0,-1.33357 0.65421,-2.11862 0.65924,-0.78505 1.76636,-0.78505 1.03666,0 1.64054,0.6844 0.60388,0.67937 0.60388,1.79656 v 0.52839 h -3.79942 q 0.0252,0.97124 0.48813,1.47448 0.46802,0.50324 1.31345,0.50324 0.89072,0 1.76132,-0.3724 v 0.74479 q -0.44284,0.19123 -0.8404,0.27174 -0.39253,0.0856 -0.95112,0.0856 z m -0.22645,-5.01725 q -0.66428,0 -1.06182,0.43277 -0.39253,0.43278 -0.46299,1.1977 h 2.88354 q 0,-0.79008 -0.35226,-1.20775 -0.35227,-0.42272 -1.00647,-0.42272 z\" id=\"path8232\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 370.25229,354.24037 h -0.83537 v -7.83034 h 0.83537 z\" id=\"path8234\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 374.19089,349.37409 h -1.40402 v 4.86628 h -0.83537 v -4.86628 h -0.98633 v -0.37743 l 0.98633,-0.30195 v -0.30697 q 0,-2.03306 1.77642,-2.03306 0.43781,0 1.0266,0.17613 l -0.21639,0.6693 q -0.48311,-0.156 -0.8253,-0.156 -0.47304,0 -0.6995,0.31703 -0.22646,0.31202 -0.22646,1.00647 v 0.3573 h 1.40402 z\" id=\"path8236\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 384.44481,354.24037 v -3.58807 q 0,-0.65924 -0.28181,-0.98633 -0.28181,-0.33215 -0.87562,-0.33215 -0.78002,0 -1.15242,0.44789 -0.37239,0.44788 -0.37239,1.37887 v 3.07979 h -0.83538 v -3.58807 q 0,-0.65924 -0.28181,-0.98633 -0.2818,-0.33215 -0.88065,-0.33215 -0.78505,0 -1.15241,0.47305 -0.36233,0.468 -0.36233,1.53989 v 2.89361 h -0.83537 v -5.51546 h 0.67937 l 0.13586,0.75486 h 0.0403 q 0.23652,-0.40259 0.66427,-0.62906 0.43278,-0.22645 0.96621,-0.22645 1.29331,0 1.69087,0.93603 h 0.0403 q 0.24659,-0.43279 0.7146,-0.6844 0.46801,-0.25163 1.06685,-0.25163 0.93602,0 1.39899,0.48311 0.46802,0.47808 0.46802,1.53487 v 3.59813 z\" id=\"path8238\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 389.39148,354.24037 -0.16607,-0.78505 h -0.0403 q -0.41266,0.51833 -0.82531,0.70453 -0.40762,0.18117 -1.02157,0.18117 -0.82028,0 -1.28828,-0.42272 -0.46298,-0.42272 -0.46298,-1.20273 0,-1.67074 2.67218,-1.75126 l 0.93602,-0.0301 v -0.3422 q 0,-0.64917 -0.28181,-0.95615 -0.27678,-0.312 -0.89073,-0.312 -0.68943,0 -1.56002,0.42272 l -0.25666,-0.63912 q 0.40763,-0.22142 0.89074,-0.34722 0.48813,-0.12587 0.97626,-0.12587 0.98634,0 1.45938,0.43781 0.47808,0.43782 0.47808,1.40403 v 3.7642 z m -1.88713,-0.58879 q 0.78001,0 1.22286,-0.42774 0.44788,-0.42776 0.44788,-1.19771 v -0.4982 l -0.83537,0.0352 q -0.99641,0.0352 -1.43925,0.312 -0.43781,0.27175 -0.43781,0.85047 0,0.45292 0.27175,0.68944 0.27677,0.23652 0.76994,0.23652 z\" id=\"path8240\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 395.50432,354.24037 v -3.56794 q 0,-0.67433 -0.30697,-1.00646 -0.30698,-0.33215 -0.96119,-0.33215 -0.86556,0 -1.26814,0.46801 -0.4026,0.46801 -0.4026,1.54493 v 2.89361 h -0.83537 v -5.51546 h 0.67937 l 0.13588,0.75486 h 0.0403 q 0.25665,-0.40763 0.71962,-0.62906 0.46299,-0.22645 1.03164,-0.22645 0.99639,0 1.49963,0.48311 0.50324,0.47808 0.50324,1.53487 v 3.59813 z\" id=\"path8242\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 400.8521,354.24037 -0.16606,-0.78505 h -0.0403 q -0.41265,0.51833 -0.8253,0.70453 -0.40763,0.18117 -1.02157,0.18117 -0.82028,0 -1.28828,-0.42272 -0.46299,-0.42272 -0.46299,-1.20273 0,-1.67074 2.67218,-1.75126 l 0.93603,-0.0301 v -0.3422 q 0,-0.64917 -0.28181,-0.95615 -0.27679,-0.312 -0.89074,-0.312 -0.68942,0 -1.56002,0.42272 l -0.25665,-0.63912 q 0.40761,-0.22142 0.89073,-0.34722 0.48813,-0.12587 0.97626,-0.12587 0.98635,0 1.45939,0.43781 0.47808,0.43782 0.47808,1.40403 v 3.7642 z m -1.88712,-0.58879 q 0.78001,0 1.22286,-0.42774 0.44788,-0.42776 0.44788,-1.19771 v -0.4982 l -0.83537,0.0352 q -0.99641,0.0352 -1.43925,0.312 -0.43781,0.27175 -0.43781,0.85047 0,0.45292 0.27174,0.68944 0.27677,0.23652 0.76995,0.23652 z\" id=\"path8244\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 407.70458,348.72491 v 0.5284 l -1.02157,0.1208 q 0.14091,0.17614 0.25161,0.46298 0.11067,0.28181 0.11067,0.6391 0,0.81021 -0.55356,1.29332 -0.55356,0.4831 -1.51977,0.4831 -0.24659,0 -0.46298,-0.0403 -0.53343,0.28181 -0.53343,0.70955 0,0.22646 0.1862,0.33718 0.1862,0.10573 0.6391,0.10573 h 0.97628 q 0.89576,0 1.37384,0.37743 0.4831,0.37742 0.4831,1.09705 0,0.91589 -0.73473,1.39395 -0.73472,0.48311 -2.14378,0.48311 -1.08196,0 -1.67074,-0.40259 -0.58375,-0.40258 -0.58375,-1.1373 0,-0.50324 0.32207,-0.8706 0.32207,-0.36737 0.90582,-0.49821 -0.21136,-0.0956 -0.35729,-0.29691 -0.1409,-0.20129 -0.1409,-0.46801 0,-0.30193 0.16102,-0.52838 0.16104,-0.22647 0.50828,-0.43783 -0.42776,-0.17613 -0.6995,-0.59884 -0.26672,-0.42272 -0.26672,-0.96622 0,-0.90581 0.5435,-1.39396 0.54349,-0.49317 1.53989,-0.49317 0.43279,0 0.78003,0.10066 z m -4.39828,6.44142 q 0,0.44787 0.37742,0.67935 0.37743,0.2315 1.08196,0.2315 1.05176,0 1.555,-0.31704 0.50826,-0.312 0.50826,-0.85047 0,-0.44788 -0.27677,-0.62401 -0.27679,-0.17111 -1.0417,-0.17111 h -1.00144 q -0.56865,0 -0.88569,0.27175 -0.31704,0.27176 -0.31704,0.78003 z m 0.45292,-4.67506 q 0,0.57872 0.32709,0.87562 0.32711,0.29691 0.91086,0.29691 1.22285,0 1.22285,-1.18764 0,-1.24298 -1.23795,-1.24298 -0.58879,0 -0.90583,0.31704 -0.31702,0.31704 -0.31702,0.94105 z\" id=\"path8246\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 411.25079,354.34102 q -1.22287,0 -1.93243,-0.7448 -0.70453,-0.74478 -0.70453,-2.06829 0,-1.33357 0.65421,-2.11862 0.65924,-0.78505 1.76636,-0.78505 1.03666,0 1.64054,0.6844 0.60388,0.67937 0.60388,1.79656 v 0.52839 h -3.79942 q 0.0252,0.97124 0.48814,1.47448 0.46801,0.50324 1.31345,0.50324 0.89071,0 1.76131,-0.3724 v 0.74479 q -0.44285,0.19123 -0.8404,0.27174 -0.39253,0.0856 -0.95111,0.0856 z m -0.22646,-5.01725 q -0.66428,0 -1.06182,0.43277 -0.39253,0.43278 -0.46299,1.1977 h 2.88354 q 0,-0.79008 -0.35226,-1.20775 -0.35227,-0.42272 -1.00647,-0.42272 z\" id=\"path8248\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 418.40519,353.50061 h -0.0453 q -0.57872,0.84041 -1.73113,0.84041 -1.08196,0 -1.68583,-0.73976 -0.59886,-0.73976 -0.59886,-2.10353 0,-1.36377 0.60388,-2.11862 0.60389,-0.75485 1.68081,-0.75485 1.12221,0 1.72106,0.81524 h 0.0655 l -0.0352,-0.39755 -0.0201,-0.38749 v -2.24443 h 0.83537 v 7.83034 h -0.67937 z m -1.67074,0.14091 q 0.85551,0 1.23796,-0.46298 0.38749,-0.46801 0.38749,-1.50467 v -0.17614 q 0,-1.17253 -0.39252,-1.67074 -0.38749,-0.50322 -1.243,-0.50322 -0.73471,0 -1.12725,0.57368 -0.38749,0.56866 -0.38749,1.61035 0,1.0568 0.38749,1.59526 0.3875,0.53846 1.13732,0.53846 z\" id=\"path8250\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 427.01051,354.24037 v -3.56794 q 0,-0.67433 -0.30698,-1.00646 -0.30697,-0.33215 -0.96118,-0.33215 -0.86556,0 -1.26814,0.46801 -0.4026,0.46801 -0.4026,1.54493 v 2.89361 h -0.83537 v -5.51546 h 0.67937 l 0.13588,0.75486 h 0.0403 q 0.25666,-0.40763 0.71963,-0.62906 0.46297,-0.22645 1.03164,-0.22645 0.99639,0 1.49963,0.48311 0.50324,0.47808 0.50324,1.53487 v 3.59813 z\" id=\"path8252\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 433.75802,351.47761 q 0,1.34867 -0.67937,2.10856 -0.67937,0.75485 -1.87706,0.75485 -0.73976,0 -1.31345,-0.34724 -0.57368,-0.34722 -0.88569,-0.9964 -0.312,-0.64918 -0.312,-1.51977 0,-1.34867 0.67433,-2.0985 0.67433,-0.75485 1.87204,-0.75485 1.15743,0 1.8368,0.76996 0.6844,0.76994 0.6844,2.08339 z m -4.20201,0 q 0,1.05679 0.42272,1.61035 0.42271,0.55356 1.24299,0.55356 0.82027,0 1.24299,-0.54852 0.42774,-0.55356 0.42774,-1.61539 0,-1.05177 -0.42774,-1.59526 -0.42272,-0.54853 -1.25305,-0.54853 -0.82028,0 -1.23796,0.53847 -0.41769,0.53846 -0.41769,1.60532 z\" id=\"path8254\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 438.4818,353.50061 h -0.0453 q -0.57871,0.84041 -1.73113,0.84041 -1.08194,0 -1.68583,-0.73976 -0.59884,-0.73976 -0.59884,-2.10353 0,-1.36377 0.60388,-2.11862 0.60388,-0.75485 1.68079,-0.75485 1.12223,0 1.72108,0.81524 h 0.0655 l -0.0352,-0.39755 -0.0201,-0.38749 v -2.24443 h 0.83538 v 7.83034 h -0.67936 z m -1.67075,0.14091 q 0.85551,0 1.23797,-0.46298 0.38748,-0.46801 0.38748,-1.50467 v -0.17614 q 0,-1.17253 -0.39252,-1.67074 -0.38749,-0.50322 -1.24298,-0.50322 -0.73473,0 -1.12725,0.57368 -0.38749,0.56866 -0.38749,1.61035 0,1.0568 0.38749,1.59526 0.38749,0.53846 1.1373,0.53846 z\" id=\"path8256\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 442.78789,354.34102 q -1.22286,0 -1.93242,-0.7448 -0.70453,-0.74478 -0.70453,-2.06829 0,-1.33357 0.65421,-2.11862 0.65924,-0.78505 1.76636,-0.78505 1.03666,0 1.64054,0.6844 0.60388,0.67937 0.60388,1.79656 v 0.52839 h -3.79942 q 0.0252,0.97124 0.48813,1.47448 0.46802,0.50324 1.31345,0.50324 0.89072,0 1.76132,-0.3724 v 0.74479 q -0.44284,0.19123 -0.8404,0.27174 -0.39252,0.0856 -0.95112,0.0856 z m -0.22645,-5.01725 q -0.66426,0 -1.06182,0.43277 -0.39252,0.43278 -0.46298,1.1977 h 2.88353 q 0,-0.79008 -0.35225,-1.20775 -0.35227,-0.42272 -1.00648,-0.42272 z\" id=\"path8258\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 449.74621,352.73569 q 0,0.76996 -0.57369,1.18764 -0.57369,0.41769 -1.61036,0.41769 -1.09705,0 -1.71099,-0.34724 v -0.77498 q 0.39755,0.20129 0.85046,0.31704 0.45795,0.11573 0.88066,0.11573 0.6542,0 1.00647,-0.20632 0.35226,-0.21136 0.35226,-0.63912 0,-0.32206 -0.28181,-0.54852 -0.27677,-0.23149 -1.08698,-0.54349 -0.76995,-0.28685 -1.09705,-0.49821 -0.32207,-0.21639 -0.48311,-0.48813 -0.156,-0.27175 -0.156,-0.64918 0,-0.67434 0.54852,-1.06182 0.54853,-0.39253 1.50468,-0.39253 0.89073,0 1.74119,0.36233 l -0.2969,0.67937 q -0.83035,-0.3422 -1.50468,-0.3422 -0.59382,0 -0.89576,0.18619 -0.30194,0.1862 -0.30194,0.5133 0,0.22143 0.11066,0.37743 0.11574,0.156 0.36736,0.29691 0.25161,0.1409 0.96621,0.40762 0.98131,0.35729 1.32351,0.71963 0.34724,0.36233 0.34724,0.91085 z\" id=\"path8260\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> </g> <g id=\"g13334\"> <path d=\"m 192.30169,662.83727 1.96263,-3.67867 h 0.92596 l -2.4558,4.50397 v 2.85336 h -0.86557 v -2.8131 l -2.45076,-4.54423 h 0.93602 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8263\" /> <path d=\"m 200.8366,663.75316 q 0,1.34867 -0.67937,2.10856 -0.67937,0.75486 -1.87708,0.75486 -0.73975,0 -1.31345,-0.34724 -0.57369,-0.34723 -0.88569,-0.99641 -0.31201,-0.64917 -0.31201,-1.51977 0,-1.34868 0.67434,-2.0985 0.67434,-0.75486 1.87204,-0.75486 1.15745,0 1.83682,0.76995 0.6844,0.76996 0.6844,2.08341 z m -4.20203,0 q 0,1.0568 0.42272,1.61036 0.42272,0.55356 1.24299,0.55356 0.82028,0 1.243,-0.54853 0.42775,-0.55356 0.42775,-1.61539 0,-1.05177 -0.42775,-1.59526 -0.42272,-0.54853 -1.25306,-0.54853 -0.82028,0 -1.23796,0.53846 -0.41769,0.53846 -0.41769,1.60533 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8265\" /> <path d=\"m 203.08607,661.00045 v 3.57802 q 0,0.67433 0.30697,1.00647 0.30698,0.33214 0.96119,0.33214 0.86557,0 1.26312,-0.47305 0.40259,-0.47304 0.40259,-1.54493 v -2.89865 h 0.83538 v 5.51548 h -0.68944 l -0.12077,-0.73976 h -0.0453 q -0.25665,0.40762 -0.71459,0.62402 -0.45292,0.21639 -1.03667,0.21639 -1.00648,0 -1.50971,-0.47808 -0.49821,-0.47807 -0.49821,-1.52984 v -3.60821 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8267\" /> <path d=\"m 218.33416,666.51593 v -3.58808 q 0,-0.65924 -0.28181,-0.98635 -0.28181,-0.33213 -0.87563,-0.33213 -0.78002,0 -1.15242,0.44788 -0.37239,0.44788 -0.37239,1.37887 v 3.07981 h -0.83538 v -3.58808 q 0,-0.65924 -0.28181,-0.98635 -0.28181,-0.33213 -0.88067,-0.33213 -0.78505,0 -1.15241,0.47304 -0.36233,0.46801 -0.36233,1.53991 v 2.89361 h -0.83537 v -5.51548 h 0.67937 l 0.13587,0.75486 h 0.0403 q 0.23652,-0.40259 0.66427,-0.62905 0.43279,-0.22646 0.96622,-0.22646 1.29332,0 1.69088,0.93602 h 0.0403 q 0.24659,-0.43278 0.7146,-0.6844 0.46801,-0.25162 1.06686,-0.25162 0.93603,0 1.399,0.48311 0.46802,0.47808 0.46802,1.53487 v 3.59815 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8269\" /> <path d=\"m 224.28243,666.51593 -0.16607,-0.78505 h -0.0403 q -0.41266,0.51833 -0.82531,0.70453 -0.40762,0.18117 -1.02157,0.18117 -0.82028,0 -1.28829,-0.42272 -0.46298,-0.42272 -0.46298,-1.20274 0,-1.67075 2.67219,-1.75126 l 0.93602,-0.0302 v -0.3422 q 0,-0.64918 -0.28181,-0.95615 -0.27678,-0.31201 -0.89073,-0.31201 -0.68943,0 -1.56004,0.42272 l -0.25665,-0.63911 q 0.40763,-0.22142 0.89073,-0.34723 0.48814,-0.12581 0.97628,-0.12581 0.98635,0 1.45939,0.43781 0.47808,0.43782 0.47808,1.40404 v 3.76421 z m -1.88714,-0.58879 q 0.78001,0 1.22286,-0.42775 0.44788,-0.42775 0.44788,-1.1977 v -0.49821 l -0.83537,0.0352 q -0.99641,0.0352 -1.43926,0.312 -0.43782,0.27175 -0.43782,0.85048 0,0.45291 0.27175,0.68943 0.27678,0.23652 0.76996,0.23652 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8271\" /> <path d=\"m 225.74685,661.00045 h 0.89576 l 1.20777,3.14523 q 0.39756,1.07693 0.49317,1.55501 h 0.0403 q 0.0654,-0.25666 0.27175,-0.87564 0.21136,-0.62401 1.3688,-3.8246 h 0.89577 l -2.37025,6.2804 q -0.35227,0.93099 -0.82531,1.31848 -0.46801,0.39253 -1.15241,0.39253 -0.38246,0 -0.75486,-0.0856 V 668.237 q 0.27678,0.0604 0.61898,0.0604 0.86054,0 1.2279,-0.96622 l 0.30698,-0.78505 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8273\" /> <path d=\"m 238.26739,666.51593 v -3.56795 q 0,-0.67434 -0.30697,-1.00648 -0.30698,-0.33213 -0.96119,-0.33213 -0.86556,0 -1.26815,0.46801 -0.40259,0.46801 -0.40259,1.54494 v 2.89361 h -0.83538 v -5.51548 h 0.67937 l 0.13588,0.75486 h 0.0403 q 0.25665,-0.40763 0.71963,-0.62905 0.46297,-0.22646 1.03163,-0.22646 0.99641,0 1.49965,0.48311 0.50324,0.47808 0.50324,1.53487 v 3.59815 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8275\" /> <path d=\"m 243.14879,666.61658 q -1.22286,0 -1.93243,-0.74479 -0.70453,-0.74479 -0.70453,-2.06831 0,-1.33358 0.65421,-2.11863 0.65924,-0.78505 1.76636,-0.78505 1.03667,0 1.64055,0.6844 0.60389,0.67937 0.60389,1.79656 v 0.5284 h -3.79944 q 0.0252,0.97125 0.48814,1.47449 0.46801,0.50323 1.31345,0.50323 0.89073,0 1.76133,-0.37239 v 0.74479 q -0.44285,0.19123 -0.84041,0.27175 -0.39252,0.0856 -0.95112,0.0856 z m -0.22645,-5.01728 q -0.66428,0 -1.06183,0.43279 -0.39253,0.43278 -0.46298,1.1977 h 2.88355 q 0,-0.79008 -0.35227,-1.20777 -0.35227,-0.42272 -1.00647,-0.42272 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8277\" /> <path d=\"m 248.93099,666.61658 q -1.22287,0 -1.93243,-0.74479 -0.70453,-0.74479 -0.70453,-2.06831 0,-1.33358 0.6542,-2.11863 0.65924,-0.78505 1.76637,-0.78505 1.03667,0 1.64055,0.6844 0.60389,0.67937 0.60389,1.79656 v 0.5284 h -3.79945 q 0.0252,0.97125 0.48814,1.47449 0.46801,0.50323 1.31345,0.50323 0.89073,0 1.76133,-0.37239 v 0.74479 q -0.44285,0.19123 -0.8404,0.27175 -0.39253,0.0856 -0.95112,0.0856 z m -0.22646,-5.01728 q -0.66427,0 -1.06183,0.43279 -0.39252,0.43278 -0.46298,1.1977 h 2.88355 q 0,-0.79008 -0.35226,-1.20777 -0.35227,-0.42272 -1.00648,-0.42272 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8279\" /> <path d=\"m 256.13735,665.77617 h -0.0453 q -0.57873,0.84041 -1.73114,0.84041 -1.08196,0 -1.68585,-0.73976 -0.59885,-0.73976 -0.59885,-2.10353 0,-1.36378 0.60389,-2.11863 0.60388,-0.75486 1.68081,-0.75486 1.12222,0 1.72107,0.81525 h 0.0654 l -0.0352,-0.39756 -0.0201,-0.38749 v -2.24444 h 0.83537 v 7.83037 h -0.67937 z m -1.67075,0.14091 q 0.8555,0 1.23796,-0.46298 0.3875,-0.46801 0.3875,-1.50468 v -0.17613 q 0,-1.17255 -0.39253,-1.67075 -0.38749,-0.50324 -1.243,-0.50324 -0.73472,0 -1.12725,0.57369 -0.38749,0.56866 -0.38749,1.61036 0,1.0568 0.38749,1.59526 0.38749,0.53847 1.13732,0.53847 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8281\" /> <path d=\"m 263.15751,665.92714 q 0.22142,0 0.42775,-0.0302 0.20633,-0.0352 0.3271,-0.0704 v 0.63911 q -0.13587,0.0654 -0.40259,0.10568 -0.26168,0.0453 -0.47304,0.0453 -1.60029,0 -1.60029,-1.68585 v -3.2811 h -0.79009 v -0.40259 l 0.79009,-0.34724 0.35226,-1.17757 h 0.48311 v 1.27822 h 1.60029 v 0.64918 h -1.60029 v 3.24588 q 0,0.4982 0.23652,0.76492 0.23652,0.26671 0.64918,0.26671 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8283\" /> <path d=\"m 269.77508,663.75316 q 0,1.34867 -0.67937,2.10856 -0.67937,0.75486 -1.87708,0.75486 -0.73976,0 -1.31345,-0.34724 -0.57369,-0.34723 -0.8857,-0.99641 -0.312,-0.64917 -0.312,-1.51977 0,-1.34868 0.67434,-2.0985 0.67433,-0.75486 1.87204,-0.75486 1.15744,0 1.83681,0.76995 0.68441,0.76996 0.68441,2.08341 z m -4.20203,0 q 0,1.0568 0.42271,1.61036 0.42272,0.55356 1.243,0.55356 0.82028,0 1.243,-0.54853 0.42775,-0.55356 0.42775,-1.61539 0,-1.05177 -0.42775,-1.59526 -0.42272,-0.54853 -1.25306,-0.54853 -0.82028,0 -1.23797,0.53846 -0.41768,0.53846 -0.41768,1.60533 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8285\" /> <path d=\"m 274.70177,661.00045 v 3.57802 q 0,0.67433 0.30697,1.00647 0.30698,0.33214 0.96119,0.33214 0.86557,0 1.26312,-0.47305 0.40259,-0.47304 0.40259,-1.54493 v -2.89865 h 0.83538 v 5.51548 h -0.68944 l -0.12077,-0.73976 h -0.0453 q -0.25665,0.40762 -0.71459,0.62402 -0.45292,0.21639 -1.03667,0.21639 -1.00648,0 -1.50971,-0.47808 -0.49821,-0.47807 -0.49821,-1.52984 v -3.60821 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8287\" /> <path d=\"m 282.80893,666.61658 q -0.53847,0 -0.98635,-0.19626 -0.44285,-0.2013 -0.74479,-0.61395 h -0.0604 q 0.0604,0.4831 0.0604,0.91589 v 2.2696 h -0.83537 v -7.99141 h 0.67937 l 0.11574,0.75486 h 0.0403 q 0.32207,-0.45292 0.74983,-0.65421 0.42775,-0.2013 0.98131,-0.2013 1.09706,0 1.69088,0.74983 0.59885,0.74982 0.59885,2.10353 0,1.35874 -0.60892,2.11359 -0.60388,0.74983 -1.68081,0.74983 z m -0.12078,-5.00721 q -0.84544,0 -1.22286,0.46801 -0.37743,0.46801 -0.3875,1.48958 v 0.1862 q 0,1.16248 0.3875,1.66571 0.38749,0.49821 1.24299,0.49821 0.7146,0 1.11719,-0.57873 0.40762,-0.57872 0.40762,-1.59526 0,-1.03163 -0.40762,-1.58016 -0.40259,-0.55356 -1.13732,-0.55356 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8289\" /> <path d=\"m 290.3122,665.77617 h -0.0453 q -0.57873,0.84041 -1.73114,0.84041 -1.08196,0 -1.68585,-0.73976 -0.59885,-0.73976 -0.59885,-2.10353 0,-1.36378 0.60389,-2.11863 0.60388,-0.75486 1.68081,-0.75486 1.12222,0 1.72107,0.81525 h 0.0654 l -0.0352,-0.39756 -0.0201,-0.38749 v -2.24444 h 0.83537 v 7.83037 h -0.67937 z m -1.67075,0.14091 q 0.8555,0 1.23796,-0.46298 0.3875,-0.46801 0.3875,-1.50468 v -0.17613 q 0,-1.17255 -0.39253,-1.67075 -0.38749,-0.50324 -1.243,-0.50324 -0.73472,0 -1.12725,0.57369 -0.38749,0.56866 -0.38749,1.61036 0,1.0568 0.38749,1.59526 0.3875,0.53847 1.13732,0.53847 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8291\" /> <path d=\"m 296.26549,666.51593 -0.16606,-0.78505 h -0.0403 q -0.41266,0.51833 -0.82531,0.70453 -0.40762,0.18117 -1.02157,0.18117 -0.82028,0 -1.28829,-0.42272 -0.46298,-0.42272 -0.46298,-1.20274 0,-1.67075 2.67219,-1.75126 l 0.93602,-0.0302 v -0.3422 q 0,-0.64918 -0.28181,-0.95615 -0.27678,-0.31201 -0.89073,-0.31201 -0.68944,0 -1.56004,0.42272 L 293.08,661.38291 q 0.40762,-0.22142 0.89073,-0.34723 0.48814,-0.12581 0.97628,-0.12581 0.98635,0 1.45939,0.43781 0.47808,0.43782 0.47808,1.40404 v 3.76421 z m -1.88714,-0.58879 q 0.78002,0 1.22287,-0.42775 0.44788,-0.42775 0.44788,-1.1977 v -0.49821 l -0.83537,0.0352 q -0.99641,0.0352 -1.43926,0.312 -0.43782,0.27175 -0.43782,0.85048 0,0.45291 0.27175,0.68943 0.27678,0.23652 0.76995,0.23652 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8293\" /> <path d=\"m 300.38701,665.92714 q 0.22142,0 0.42775,-0.0302 0.20633,-0.0352 0.3271,-0.0704 v 0.63911 q -0.13587,0.0654 -0.40259,0.10568 -0.26168,0.0453 -0.47304,0.0453 -1.60029,0 -1.60029,-1.68585 v -3.2811 h -0.79009 v -0.40259 l 0.79009,-0.34724 0.35226,-1.17757 h 0.48311 v 1.27822 h 1.60029 v 0.64918 h -1.60029 v 3.24588 q 0,0.4982 0.23652,0.76492 0.23652,0.26671 0.64918,0.26671 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8295\" /> <path d=\"m 304.57394,666.61658 q -1.22287,0 -1.93243,-0.74479 -0.70453,-0.74479 -0.70453,-2.06831 0,-1.33358 0.65421,-2.11863 0.65924,-0.78505 1.76636,-0.78505 1.03667,0 1.64055,0.6844 0.60389,0.67937 0.60389,1.79656 v 0.5284 h -3.79944 q 0.0252,0.97125 0.48814,1.47449 0.46801,0.50323 1.31344,0.50323 0.89074,0 1.76134,-0.37239 v 0.74479 q -0.44285,0.19123 -0.84041,0.27175 -0.39253,0.0856 -0.95112,0.0856 z m -0.22646,-5.01728 q -0.66427,0 -1.06183,0.43279 -0.39252,0.43278 -0.46298,1.1977 h 2.88355 q 0,-0.79008 -0.35226,-1.20777 -0.35227,-0.42272 -1.00648,-0.42272 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8297\" /> <path d=\"m 312.48483,665.92714 q 0.22143,0 0.42775,-0.0302 0.20633,-0.0352 0.32711,-0.0704 v 0.63911 q -0.13588,0.0654 -0.40259,0.10568 -0.26169,0.0453 -0.47305,0.0453 -1.60029,0 -1.60029,-1.68585 v -3.2811 h -0.79008 v -0.40259 l 0.79008,-0.34724 0.35227,-1.17757 h 0.4831 v 1.27822 h 1.6003 v 0.64918 h -1.6003 v 3.24588 q 0,0.4982 0.23653,0.76492 0.23652,0.26671 0.64917,0.26671 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8299\" /> <path d=\"m 318.11606,666.51593 v -3.56795 q 0,-0.67434 -0.30698,-1.00648 -0.30697,-0.33213 -0.96118,-0.33213 -0.8706,0 -1.27319,0.47304 -0.39756,0.47304 -0.39756,1.54997 v 2.88355 h -0.83537 v -7.83037 h 0.83537 v 2.37025 q 0,0.42775 -0.0403,0.70956 h 0.0503 q 0.24659,-0.39756 0.6995,-0.62401 0.45795,-0.23149 1.04171,-0.23149 1.0115,0 1.51474,0.4831 0.50827,0.47808 0.50827,1.52481 v 3.59815 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8301\" /> <path d=\"m 322.99746,666.61658 q -1.22286,0 -1.93243,-0.74479 -0.70453,-0.74479 -0.70453,-2.06831 0,-1.33358 0.65421,-2.11863 0.65924,-0.78505 1.76636,-0.78505 1.03667,0 1.64056,0.6844 0.60388,0.67937 0.60388,1.79656 v 0.5284 h -3.79944 q 0.0252,0.97125 0.48814,1.47449 0.46801,0.50323 1.31345,0.50323 0.89073,0 1.76133,-0.37239 v 0.74479 q -0.44285,0.19123 -0.84041,0.27175 -0.39252,0.0856 -0.95112,0.0856 z m -0.22645,-5.01728 q -0.66428,0 -1.06183,0.43279 -0.39253,0.43278 -0.46298,1.1977 h 2.88355 q 0,-0.79008 -0.35227,-1.20777 -0.35226,-0.42272 -1.00647,-0.42272 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8303\" /> <path d=\"m 331.6934,666.61658 q -0.53847,0 -0.98635,-0.19626 -0.44285,-0.2013 -0.74479,-0.61395 h -0.0604 q 0.0604,0.4831 0.0604,0.91589 v 2.2696 h -0.83537 v -7.99141 h 0.67937 l 0.11574,0.75486 h 0.0403 q 0.32207,-0.45292 0.74982,-0.65421 0.42776,-0.2013 0.98132,-0.2013 1.09705,0 1.69087,0.74983 0.59886,0.74982 0.59886,2.10353 0,1.35874 -0.60892,2.11359 -0.60389,0.74983 -1.68081,0.74983 z m -0.12078,-5.00721 q -0.84544,0 -1.22287,0.46801 -0.37742,0.46801 -0.38749,1.48958 v 0.1862 q 0,1.16248 0.38749,1.66571 0.3875,0.49821 1.243,0.49821 0.7146,0 1.11719,-0.57873 0.40762,-0.57872 0.40762,-1.59526 0,-1.03163 -0.40762,-1.58016 -0.40259,-0.55356 -1.13732,-0.55356 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8305\" /> <path d=\"m 338.83433,666.51593 -0.16606,-0.78505 h -0.0403 q -0.41266,0.51833 -0.82531,0.70453 -0.40762,0.18117 -1.02157,0.18117 -0.82028,0 -1.28829,-0.42272 -0.46298,-0.42272 -0.46298,-1.20274 0,-1.67075 2.67219,-1.75126 l 0.93602,-0.0302 v -0.3422 q 0,-0.64918 -0.28181,-0.95615 -0.27678,-0.31201 -0.89073,-0.31201 -0.68944,0 -1.56004,0.42272 l -0.25665,-0.63911 q 0.40762,-0.22142 0.89073,-0.34723 0.48814,-0.12581 0.97628,-0.12581 0.98635,0 1.45939,0.43781 0.47808,0.43782 0.47808,1.40404 v 3.76421 z m -1.88714,-0.58879 q 0.78002,0 1.22287,-0.42775 0.44788,-0.42775 0.44788,-1.1977 v -0.49821 l -0.83537,0.0352 q -0.99641,0.0352 -1.43926,0.312 -0.43782,0.27175 -0.43782,0.85048 0,0.45291 0.27175,0.68943 0.27678,0.23652 0.76995,0.23652 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8307\" /> <path d=\"m 343.37857,666.61658 q -1.19771,0 -1.85695,-0.73473 -0.65421,-0.73976 -0.65421,-2.08843 0,-1.38391 0.66428,-2.13876 0.6693,-0.75486 1.90223,-0.75486 0.39756,0 0.79512,0.0856 0.39756,0.0856 0.62401,0.2013 l -0.25665,0.70956 q -0.27678,-0.11071 -0.60388,-0.18116 -0.32711,-0.0755 -0.57873,-0.0755 -1.68081,0 -1.68081,2.14379 0,1.01654 0.40762,1.56004 0.41266,0.54349 1.21784,0.54349 0.68943,0 1.41409,-0.29691 v 0.73976 q -0.55356,0.28685 -1.39396,0.28685 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8309\" /> <path d=\"m 346.90627,663.69277 q 0.21639,-0.30698 0.65924,-0.80518 l 1.78146,-1.88714 h 0.99138 l -2.23438,2.35012 2.39038,3.16536 h -1.01151 l -1.94753,-2.60677 -0.62904,0.5435 v 2.06327 h -0.82531 v -7.83037 h 0.82531 v 4.15171 q 0,0.27678 -0.0403,0.8555 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8311\" /> <path d=\"m 354.88257,666.51593 -0.16607,-0.78505 h -0.0403 q -0.41265,0.51833 -0.82531,0.70453 -0.40762,0.18117 -1.02157,0.18117 -0.82028,0 -1.28829,-0.42272 -0.46298,-0.42272 -0.46298,-1.20274 0,-1.67075 2.67219,-1.75126 l 0.93602,-0.0302 v -0.3422 q 0,-0.64918 -0.28181,-0.95615 -0.27678,-0.31201 -0.89073,-0.31201 -0.68943,0 -1.56003,0.42272 l -0.25666,-0.63911 q 0.40763,-0.22142 0.89073,-0.34723 0.48815,-0.12581 0.97629,-0.12581 0.98634,0 1.45938,0.43781 0.47808,0.43782 0.47808,1.40404 v 3.76421 z m -1.88714,-0.58879 q 0.78002,0 1.22286,-0.42775 0.44789,-0.42775 0.44789,-1.1977 v -0.49821 l -0.83538,0.0352 q -0.99641,0.0352 -1.43926,0.312 -0.43781,0.27175 -0.43781,0.85048 0,0.45291 0.27174,0.68943 0.27678,0.23652 0.76996,0.23652 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8313\" /> <path d=\"m 361.73666,661.00045 v 0.5284 l -1.02157,0.12078 q 0.1409,0.17613 0.25162,0.46297 0.11071,0.28182 0.11071,0.63912 0,0.81021 -0.55356,1.29331 -0.55356,0.48311 -1.51978,0.48311 -0.24659,0 -0.46298,-0.0403 -0.53343,0.28182 -0.53343,0.70957 0,0.22646 0.1862,0.33717 0.1862,0.10568 0.63911,0.10568 h 0.97628 q 0.89576,0 1.37384,0.37743 0.48311,0.37742 0.48311,1.09705 0,0.91589 -0.73473,1.39397 -0.73473,0.48311 -2.14379,0.48311 -1.08196,0 -1.67075,-0.40259 -0.58375,-0.40259 -0.58375,-1.13732 0,-0.50324 0.32207,-0.8706 0.32207,-0.36736 0.90582,-0.4982 -0.21136,-0.0956 -0.35729,-0.29691 -0.14091,-0.2013 -0.14091,-0.46801 0,-0.30195 0.16104,-0.5284 0.16103,-0.22646 0.50826,-0.43782 -0.42775,-0.17613 -0.6995,-0.59885 -0.26671,-0.42272 -0.26671,-0.96622 0,-0.90583 0.5435,-1.39397 0.54349,-0.49317 1.5399,-0.49317 0.43279,0 0.78002,0.10065 z m -4.3983,6.44144 q 0,0.44788 0.37743,0.67937 0.37743,0.23149 1.08196,0.23149 1.05177,0 1.55501,-0.31704 0.50827,-0.31201 0.50827,-0.85047 0,-0.44789 -0.27678,-0.62402 -0.27679,-0.1711 -1.04171,-0.1711 h -1.00144 q -0.56866,0 -0.8857,0.27175 -0.31704,0.27175 -0.31704,0.78002 z m 0.45292,-4.67508 q 0,0.57873 0.3271,0.87564 0.32711,0.29691 0.91086,0.29691 1.22287,0 1.22287,-1.18764 0,-1.243 -1.23796,-1.243 -0.58879,0 -0.90583,0.31704 -0.31704,0.31704 -0.31704,0.94105 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8315\" /> <path d=\"m 365.19894,666.61658 q -1.22287,0 -1.93243,-0.74479 -0.70453,-0.74479 -0.70453,-2.06831 0,-1.33358 0.65421,-2.11863 0.65924,-0.78505 1.76636,-0.78505 1.03667,0 1.64055,0.6844 0.60389,0.67937 0.60389,1.79656 v 0.5284 h -3.79944 q 0.0252,0.97125 0.48814,1.47449 0.46801,0.50323 1.31344,0.50323 0.89074,0 1.76134,-0.37239 v 0.74479 q -0.44285,0.19123 -0.84041,0.27175 -0.39253,0.0856 -0.95112,0.0856 z m -0.22646,-5.01728 q -0.66427,0 -1.06183,0.43279 -0.39252,0.43278 -0.46298,1.1977 h 2.88355 q 0,-0.79008 -0.35226,-1.20777 -0.35227,-0.42272 -1.00648,-0.42272 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8317\" /> <path d=\"m 197.2611,676.82223 v -3.58808 q 0,-0.65924 -0.28181,-0.98635 -0.28182,-0.33213 -0.87564,-0.33213 -0.78002,0 -1.15241,0.44788 -0.3724,0.44788 -0.3724,1.37887 v 3.07981 h -0.83537 v -3.58808 q 0,-0.65924 -0.28181,-0.98635 -0.28182,-0.33213 -0.88067,-0.33213 -0.78505,0 -1.15241,0.47304 -0.36233,0.46801 -0.36233,1.53991 v 2.89361 h -0.83538 v -5.51548 h 0.67937 l 0.13588,0.75486 h 0.0403 q 0.23652,-0.40259 0.66427,-0.62905 0.43278,-0.22646 0.96622,-0.22646 1.29332,0 1.69087,0.93602 h 0.0403 q 0.24659,-0.43278 0.7146,-0.6844 0.46801,-0.25162 1.06686,-0.25162 0.93602,0 1.399,0.48311 0.46801,0.47808 0.46801,1.53487 v 3.59815 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8319\" /> <path d=\"m 203.20936,676.82223 -0.16606,-0.78505 h -0.0403 q -0.41266,0.51833 -0.82531,0.70453 -0.40763,0.18117 -1.02157,0.18117 -0.82028,0 -1.28829,-0.42272 -0.46298,-0.42272 -0.46298,-1.20274 0,-1.67075 2.67219,-1.75126 l 0.93602,-0.0302 v -0.3422 q 0,-0.64918 -0.28181,-0.95615 -0.27678,-0.31201 -0.89073,-0.31201 -0.68944,0 -1.56004,0.42272 l -0.25665,-0.63911 q 0.40762,-0.22142 0.89073,-0.34723 0.48814,-0.12581 0.97628,-0.12581 0.98635,0 1.45939,0.43781 0.47808,0.43782 0.47808,1.40404 v 3.76421 z m -1.88714,-0.58879 q 0.78002,0 1.22287,-0.42775 0.44788,-0.42775 0.44788,-1.1977 v -0.49821 l -0.83537,0.0352 q -0.99641,0.0352 -1.43926,0.312 -0.43782,0.27175 -0.43782,0.85048 0,0.45291 0.27175,0.68943 0.27678,0.23652 0.76995,0.23652 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8321\" /> <path d=\"m 209.3237,676.82223 v -3.56795 q 0,-0.67434 -0.30698,-1.00648 -0.30697,-0.33213 -0.96118,-0.33213 -0.86557,0 -1.26816,0.46801 -0.40259,0.46801 -0.40259,1.54494 v 2.89361 h -0.83537 v -5.51548 h 0.67937 l 0.13587,0.75486 h 0.0403 q 0.25665,-0.40763 0.71963,-0.62905 0.46298,-0.22646 1.03164,-0.22646 0.99641,0 1.49964,0.48311 0.50324,0.47808 0.50324,1.53487 v 3.59815 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8323\" /> <path d=\"m 215.26693,676.82223 -0.16607,-0.78505 h -0.0403 q -0.41265,0.51833 -0.82531,0.70453 -0.40762,0.18117 -1.02157,0.18117 -0.82027,0 -1.28829,-0.42272 -0.46297,-0.42272 -0.46297,-1.20274 0,-1.67075 2.67219,-1.75126 l 0.93602,-0.0302 v -0.3422 q 0,-0.64918 -0.28182,-0.95615 -0.27678,-0.31201 -0.89073,-0.31201 -0.68943,0 -1.56003,0.42272 l -0.25665,-0.63911 q 0.40762,-0.22142 0.89073,-0.34723 0.48814,-0.12581 0.97628,-0.12581 0.98634,0 1.45939,0.43781 0.47807,0.43782 0.47807,1.40404 v 3.76421 z m -1.88714,-0.58879 q 0.78002,0 1.22287,-0.42775 0.44788,-0.42775 0.44788,-1.1977 v -0.49821 l -0.83538,0.0352 q -0.99641,0.0352 -1.43925,0.312 -0.43782,0.27175 -0.43782,0.85048 0,0.45291 0.27175,0.68943 0.27678,0.23652 0.76995,0.23652 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8325\" /> <path d=\"m 222.12102,671.30675 v 0.5284 l -1.02157,0.12078 q 0.14091,0.17613 0.25162,0.46297 0.11071,0.28182 0.11071,0.63912 0,0.81021 -0.55356,1.29332 -0.55356,0.4831 -1.51978,0.4831 -0.24658,0 -0.46297,-0.0403 -0.53344,0.28182 -0.53344,0.70957 0,0.22646 0.1862,0.33717 0.1862,0.10568 0.63911,0.10568 h 0.97628 q 0.89577,0 1.37384,0.37743 0.48311,0.37742 0.48311,1.09705 0,0.91589 -0.73473,1.39397 -0.73472,0.48311 -2.14379,0.48311 -1.08196,0 -1.67075,-0.40259 -0.58375,-0.40259 -0.58375,-1.13732 0,-0.50324 0.32207,-0.8706 0.32207,-0.36736 0.90583,-0.4982 -0.21136,-0.0956 -0.3573,-0.29691 -0.14091,-0.2013 -0.14091,-0.46801 0,-0.30195 0.16104,-0.5284 0.16103,-0.22646 0.50827,-0.43782 -0.42775,-0.17613 -0.6995,-0.59885 -0.26672,-0.42272 -0.26672,-0.96622 0,-0.90583 0.5435,-1.39397 0.54349,-0.49317 1.5399,-0.49317 0.43279,0 0.78002,0.10065 z m -4.39829,6.44144 q 0,0.44788 0.37743,0.67937 0.37742,0.23149 1.08196,0.23149 1.05176,0 1.555,-0.31704 0.50827,-0.31201 0.50827,-0.85047 0,-0.44789 -0.27678,-0.62402 -0.27678,-0.1711 -1.0417,-0.1711 h -1.00144 q -0.56866,0 -0.8857,0.27175 -0.31704,0.27175 -0.31704,0.78002 z m 0.45291,-4.67508 q 0,0.57873 0.32711,0.87564 0.3271,0.29691 0.91086,0.29691 1.22286,0 1.22286,-1.18764 0,-1.243 -1.23796,-1.243 -0.58879,0 -0.90583,0.31704 -0.31704,0.31704 -0.31704,0.94105 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8327\" /> <path d=\"m 225.5833,676.92288 q -1.22287,0 -1.93243,-0.74479 -0.70454,-0.74479 -0.70454,-2.06831 0,-1.33358 0.65421,-2.11863 0.65924,-0.78505 1.76636,-0.78505 1.03667,0 1.64056,0.6844 0.60388,0.67938 0.60388,1.79656 v 0.5284 h -3.79944 q 0.0252,0.97125 0.48814,1.47449 0.46801,0.50323 1.31345,0.50323 0.89073,0 1.76133,-0.37239 v 0.74479 q -0.44285,0.19123 -0.84041,0.27175 -0.39252,0.0856 -0.95111,0.0856 z m -0.22646,-5.01728 q -0.66427,0 -1.06183,0.43279 -0.39253,0.43278 -0.46298,1.1977 h 2.88355 q 0,-0.79008 -0.35227,-1.20777 -0.35226,-0.42272 -1.00647,-0.42272 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8329\" /> <path d=\"m 231.55169,671.2061 q 0.36736,0 0.65924,0.0604 l -0.11574,0.77499 q -0.3422,-0.0755 -0.60389,-0.0755 -0.6693,0 -1.14738,0.5435 -0.47304,0.54349 -0.47304,1.3537 v 2.95904 h -0.83538 v -5.51548 h 0.68944 l 0.0956,1.02157 h 0.0403 q 0.30698,-0.53846 0.73976,-0.83034 0.43279,-0.29188 0.95112,-0.29188 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8331\" /> <path d=\"m 238.12397,676.92288 q -1.19771,0 -1.85695,-0.73473 -0.65421,-0.73976 -0.65421,-2.08843 0,-1.38391 0.66428,-2.13876 0.6693,-0.75486 1.90223,-0.75486 0.39756,0 0.79512,0.0856 0.39756,0.0856 0.62401,0.2013 l -0.25665,0.70956 q -0.27678,-0.11071 -0.60388,-0.18116 -0.32711,-0.0755 -0.57873,-0.0755 -1.68081,0 -1.68081,2.14379 0,1.01654 0.40762,1.56004 0.41266,0.54349 1.21784,0.54349 0.68943,0 1.4141,-0.29691 v 0.73976 q -0.55357,0.28685 -1.39397,0.28685 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8333\" /> <path d=\"m 245.58698,674.05946 q 0,1.34867 -0.67937,2.10856 -0.67937,0.75486 -1.87708,0.75486 -0.73976,0 -1.31345,-0.34724 -0.57369,-0.34723 -0.8857,-0.99641 -0.312,-0.64917 -0.312,-1.51977 0,-1.34868 0.67433,-2.0985 0.67434,-0.75486 1.87205,-0.75486 1.15744,0 1.83681,0.76996 0.68441,0.76995 0.68441,2.0834 z m -4.20204,0 q 0,1.0568 0.42272,1.61036 0.42272,0.55356 1.243,0.55356 0.82028,0 1.243,-0.54853 0.42775,-0.55356 0.42775,-1.61539 0,-1.05177 -0.42775,-1.59526 -0.42272,-0.54853 -1.25306,-0.54853 -0.82028,0 -1.23797,0.53846 -0.41769,0.53846 -0.41769,1.60533 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8335\" /> <path d=\"m 250.82568,676.82223 v -3.56795 q 0,-0.67434 -0.30698,-1.00648 -0.30697,-0.33213 -0.96118,-0.33213 -0.86557,0 -1.26816,0.46801 -0.40259,0.46801 -0.40259,1.54494 v 2.89361 h -0.83537 v -5.51548 h 0.67937 l 0.13587,0.75486 h 0.0403 q 0.25665,-0.40763 0.71963,-0.62905 0.46298,-0.22646 1.03164,-0.22646 0.99641,0 1.49965,0.48311 0.50323,0.47808 0.50323,1.53487 v 3.59815 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8337\" /> <path d=\"m 255.86308,671.95593 h -1.40403 v 4.8663 h -0.83537 v -4.8663 h -0.98635 v -0.37743 l 0.98635,-0.30194 v -0.30698 q 0,-2.03308 1.77642,-2.03308 0.43782,0 1.02661,0.17613 l -0.21639,0.66931 q -0.48311,-0.156 -0.82531,-0.156 -0.47305,0 -0.6995,0.31704 -0.22646,0.312 -0.22646,1.00647 v 0.3573 h 1.40403 z m 1.84185,4.8663 h -0.83537 v -5.51548 h 0.83537 z m -0.90583,-7.0101 q 0,-0.28684 0.14091,-0.41768 0.14091,-0.13588 0.35227,-0.13588 0.20129,0 0.34723,0.13588 0.14594,0.13587 0.14594,0.41768 0,0.28182 -0.14594,0.42272 -0.14594,0.13588 -0.34723,0.13588 -0.21136,0 -0.35227,-0.13588 -0.14091,-0.1409 -0.14091,-0.42272 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8339\" /> <path d=\"m 263.99036,671.30675 v 0.5284 l -1.02157,0.12078 q 0.14091,0.17613 0.25162,0.46297 0.11071,0.28182 0.11071,0.63912 0,0.81021 -0.55356,1.29332 -0.55356,0.4831 -1.51977,0.4831 -0.24659,0 -0.46298,-0.0403 -0.53343,0.28182 -0.53343,0.70957 0,0.22646 0.18619,0.33717 0.1862,0.10568 0.63912,0.10568 h 0.97628 q 0.89576,0 1.37383,0.37743 0.48311,0.37742 0.48311,1.09705 0,0.91589 -0.73472,1.39397 -0.73473,0.48311 -2.1438,0.48311 -1.08196,0 -1.67074,-0.40259 -0.58376,-0.40259 -0.58376,-1.13732 0,-0.50324 0.32207,-0.8706 0.32207,-0.36736 0.90583,-0.4982 -0.21136,-0.0956 -0.3573,-0.29691 -0.1409,-0.2013 -0.1409,-0.46801 0,-0.30195 0.16103,-0.5284 0.16104,-0.22646 0.50827,-0.43782 -0.42775,-0.17613 -0.6995,-0.59885 -0.26671,-0.42272 -0.26671,-0.96622 0,-0.90583 0.54349,-1.39397 0.5435,-0.49317 1.53991,-0.49317 0.43278,0 0.78002,0.10065 z m -4.39829,6.44144 q 0,0.44788 0.37743,0.67937 0.37743,0.23149 1.08196,0.23149 1.05176,0 1.555,-0.31704 0.50827,-0.31201 0.50827,-0.85047 0,-0.44789 -0.27678,-0.62402 -0.27678,-0.1711 -1.0417,-0.1711 h -1.00144 q -0.56866,0 -0.8857,0.27175 -0.31704,0.27175 -0.31704,0.78002 z m 0.45291,-4.67508 q 0,0.57873 0.32711,0.87564 0.3271,0.29691 0.91086,0.29691 1.22286,0 1.22286,-1.18764 0,-1.243 -1.23796,-1.243 -0.58879,0 -0.90583,0.31704 -0.31704,0.31704 -0.31704,0.94105 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8341\" /> <path d=\"m 265.9077,671.30675 v 3.57802 q 0,0.67433 0.30698,1.00647 0.30697,0.33214 0.96118,0.33214 0.86557,0 1.26312,-0.47305 0.40259,-0.47304 0.40259,-1.54493 v -2.89865 h 0.83538 v 5.51548 h -0.68944 l -0.12077,-0.73976 h -0.0453 q -0.25665,0.40762 -0.71459,0.62402 -0.45292,0.21639 -1.03667,0.21639 -1.00648,0 -1.50971,-0.47808 -0.49821,-0.47807 -0.49821,-1.52984 v -3.60821 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8343\" /> <path d=\"m 273.96453,671.2061 q 0.36736,0 0.65924,0.0604 l -0.11575,0.77499 q -0.3422,-0.0755 -0.60388,-0.0755 -0.66931,0 -1.14738,0.5435 -0.47304,0.54349 -0.47304,1.3537 v 2.95904 h -0.83538 v -5.51548 h 0.68944 l 0.0956,1.02157 h 0.0403 q 0.30698,-0.53846 0.73976,-0.83034 0.43278,-0.29188 0.95112,-0.29188 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8345\" /> <path d=\"m 279.04723,676.82223 -0.16607,-0.78505 h -0.0403 q -0.41265,0.51833 -0.82531,0.70453 -0.40762,0.18117 -1.02157,0.18117 -0.82027,0 -1.28829,-0.42272 -0.46297,-0.42272 -0.46297,-1.20274 0,-1.67075 2.67219,-1.75126 l 0.93602,-0.0302 v -0.3422 q 0,-0.64918 -0.28181,-0.95615 -0.27679,-0.31201 -0.89074,-0.31201 -0.68943,0 -1.56003,0.42272 l -0.25665,-0.63911 q 0.40762,-0.22142 0.89073,-0.34723 0.48814,-0.12581 0.97628,-0.12581 0.98634,0 1.45939,0.43781 0.47807,0.43782 0.47807,1.40404 v 3.76421 z m -1.88714,-0.58879 q 0.78002,0 1.22287,-0.42775 0.44788,-0.42775 0.44788,-1.1977 v -0.49821 l -0.83538,0.0352 q -0.99641,0.0352 -1.43925,0.312 -0.43782,0.27175 -0.43782,0.85048 0,0.45291 0.27175,0.68943 0.27678,0.23652 0.76995,0.23652 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8347\" /> <path d=\"m 283.16874,676.23344 q 0.22143,0 0.42776,-0.0302 0.20632,-0.0352 0.3271,-0.0705 v 0.63911 q -0.13587,0.0654 -0.40259,0.10568 -0.26168,0.0453 -0.47304,0.0453 -1.6003,0 -1.6003,-1.68585 v -3.2811 h -0.79008 v -0.40259 l 0.79008,-0.34724 0.35227,-1.17757 h 0.48311 v 1.27822 h 1.60029 v 0.64918 h -1.60029 v 3.24588 q 0,0.4982 0.23652,0.76492 0.23652,0.26671 0.64917,0.26671 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8349\" /> <path d=\"m 285.86106,676.82223 h -0.83537 v -5.51548 h 0.83537 z m -0.90582,-7.0101 q 0,-0.28684 0.1409,-0.41768 0.14091,-0.13588 0.35227,-0.13588 0.20129,0 0.34723,0.13588 0.14594,0.13587 0.14594,0.41768 0,0.28182 -0.14594,0.42272 -0.14594,0.13588 -0.34723,0.13588 -0.21136,0 -0.35227,-0.13588 -0.1409,-0.1409 -0.1409,-0.42272 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8351\" /> <path d=\"m 292.39308,674.05946 q 0,1.34867 -0.67937,2.10856 -0.67937,0.75486 -1.87708,0.75486 -0.73976,0 -1.31345,-0.34724 -0.57369,-0.34723 -0.88569,-0.99641 -0.31201,-0.64917 -0.31201,-1.51977 0,-1.34868 0.67434,-2.0985 0.67434,-0.75486 1.87204,-0.75486 1.15745,0 1.83682,0.76996 0.6844,0.76995 0.6844,2.0834 z m -4.20203,0 q 0,1.0568 0.42272,1.61036 0.42272,0.55356 1.24299,0.55356 0.82028,0 1.243,-0.54853 0.42775,-0.55356 0.42775,-1.61539 0,-1.05177 -0.42775,-1.59526 -0.42272,-0.54853 -1.25306,-0.54853 -0.82028,0 -1.23797,0.53846 -0.41768,0.53846 -0.41768,1.60533 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8353\" /> <path d=\"m 297.63178,676.82223 v -3.56795 q 0,-0.67434 -0.30698,-1.00648 -0.30697,-0.33213 -0.96118,-0.33213 -0.86557,0 -1.26816,0.46801 -0.40259,0.46801 -0.40259,1.54494 v 2.89361 h -0.83537 v -5.51548 h 0.67937 l 0.13587,0.75486 h 0.0403 q 0.25665,-0.40763 0.71963,-0.62905 0.46298,-0.22646 1.03164,-0.22646 0.99641,0 1.49964,0.48311 0.50324,0.47808 0.50324,1.53487 v 3.59815 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8355\" /> <path d=\"m 307.62105,674.05946 q 0,1.34867 -0.67937,2.10856 -0.67938,0.75486 -1.87708,0.75486 -0.73976,0 -1.31345,-0.34724 -0.57369,-0.34723 -0.8857,-0.99641 -0.312,-0.64917 -0.312,-1.51977 0,-1.34868 0.67433,-2.0985 0.67434,-0.75486 1.87205,-0.75486 1.15744,0 1.83681,0.76996 0.68441,0.76995 0.68441,2.0834 z m -4.20204,0 q 0,1.0568 0.42272,1.61036 0.42272,0.55356 1.243,0.55356 0.82028,0 1.243,-0.54853 0.42775,-0.55356 0.42775,-1.61539 0,-1.05177 -0.42775,-1.59526 -0.42272,-0.54853 -1.25307,-0.54853 -0.82027,0 -1.23796,0.53846 -0.41769,0.53846 -0.41769,1.60533 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8357\" /> <path d=\"m 312.85974,676.82223 v -3.56795 q 0,-0.67434 -0.30697,-1.00648 -0.30697,-0.33213 -0.96118,-0.33213 -0.86557,0 -1.26816,0.46801 -0.40259,0.46801 -0.40259,1.54494 v 2.89361 h -0.83538 v -5.51548 h 0.67938 l 0.13587,0.75486 h 0.0403 q 0.25665,-0.40763 0.71963,-0.62905 0.46298,-0.22646 1.03163,-0.22646 0.99641,0 1.49965,0.48311 0.50324,0.47808 0.50324,1.53487 v 3.59815 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8359\" /> <path d=\"m 317.21275,671.30675 h 0.89576 l 1.20777,3.14523 q 0.39756,1.07693 0.49317,1.55501 h 0.0403 q 0.0654,-0.25666 0.27175,-0.87564 0.21136,-0.62401 1.3688,-3.8246 h 0.89577 l -2.37025,6.2804 q -0.35227,0.93099 -0.82531,1.31848 -0.46801,0.39253 -1.15241,0.39253 -0.38246,0 -0.75486,-0.0856 v -0.66931 q 0.27678,0.0604 0.61898,0.0604 0.86054,0 1.2279,-0.96622 l 0.30698,-0.78505 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8361\" /> <path d=\"m 328.04242,674.05946 q 0,1.34867 -0.67937,2.10856 -0.67937,0.75486 -1.87708,0.75486 -0.73976,0 -1.31345,-0.34724 -0.57369,-0.34723 -0.8857,-0.99641 -0.312,-0.64917 -0.312,-1.51977 0,-1.34868 0.67434,-2.0985 0.67433,-0.75486 1.87204,-0.75486 1.15744,0 1.83681,0.76996 0.68441,0.76995 0.68441,2.0834 z m -4.20203,0 q 0,1.0568 0.42271,1.61036 0.42272,0.55356 1.243,0.55356 0.82028,0 1.243,-0.54853 0.42775,-0.55356 0.42775,-1.61539 0,-1.05177 -0.42775,-1.59526 -0.42272,-0.54853 -1.25306,-0.54853 -0.82028,0 -1.23797,0.53846 -0.41768,0.53846 -0.41768,1.60533 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8363\" /> <path d=\"m 330.29188,671.30675 v 3.57802 q 0,0.67433 0.30697,1.00647 0.30698,0.33214 0.96119,0.33214 0.86556,0 1.26312,-0.47305 0.40259,-0.47304 0.40259,-1.54493 v -2.89865 h 0.83538 v 5.51548 h -0.68944 l -0.12078,-0.73976 h -0.0453 q -0.25665,0.40762 -0.71459,0.62402 -0.45292,0.21639 -1.03667,0.21639 -1.00648,0 -1.50972,-0.47808 -0.4982,-0.47807 -0.4982,-1.52984 v -3.60821 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8365\" /> <path d=\"m 338.34871,671.2061 q 0.36737,0 0.65924,0.0604 l -0.11574,0.77499 q -0.3422,-0.0755 -0.60388,-0.0755 -0.66931,0 -1.14739,0.5435 -0.47304,0.54349 -0.47304,1.3537 v 2.95904 h -0.83537 v -5.51548 h 0.68943 l 0.0956,1.02157 h 0.0403 q 0.30697,-0.53846 0.73976,-0.83034 0.43278,-0.29188 0.95111,-0.29188 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8367\" /> <path d=\"m 342.84263,676.82223 v -7.35733 h 0.8555 v 6.58234 h 3.24588 v 0.77499 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8369\" /> <path d=\"m 348.9016,676.82223 h -0.83537 v -5.51548 h 0.83537 z m -0.90582,-7.0101 q 0,-0.28684 0.1409,-0.41768 0.14091,-0.13588 0.35227,-0.13588 0.2013,0 0.34723,0.13588 0.14594,0.13587 0.14594,0.41768 0,0.28182 -0.14594,0.42272 -0.14593,0.13588 -0.34723,0.13588 -0.21136,0 -0.35227,-0.13588 -0.1409,-0.1409 -0.1409,-0.42272 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8371\" /> <path d=\"m 354.44728,676.82223 v -3.56795 q 0,-0.67434 -0.30698,-1.00648 -0.30697,-0.33213 -0.96118,-0.33213 -0.86557,0 -1.26816,0.46801 -0.40259,0.46801 -0.40259,1.54494 v 2.89361 H 350.673 v -5.51548 h 0.67937 l 0.13587,0.75486 h 0.0403 q 0.25665,-0.40763 0.71963,-0.62905 0.46298,-0.22646 1.03164,-0.22646 0.99641,0 1.49964,0.48311 0.50324,0.47808 0.50324,1.53487 v 3.59815 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8373\" /> <path d=\"m 357.78375,671.30675 v 3.57802 q 0,0.67433 0.30697,1.00647 0.30698,0.33214 0.96118,0.33214 0.86557,0 1.26313,-0.47305 0.40259,-0.47304 0.40259,-1.54493 v -2.89865 h 0.83537 v 5.51548 h -0.68943 l -0.12078,-0.73976 h -0.0453 q -0.25665,0.40762 -0.7146,0.62402 -0.45291,0.21639 -1.03667,0.21639 -1.00647,0 -1.50971,-0.47808 -0.4982,-0.47807 -0.4982,-1.52984 v -3.60821 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8375\" /> <path d=\"m 364.65293,673.99907 -1.91734,-2.69232 h 0.95112 l 1.45436,2.1136 1.44932,-2.1136 h 0.94105 l -1.91733,2.69232 2.01798,2.82316 H 366.686 l -1.54493,-2.23437 -1.56004,2.23437 h -0.94609 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8377\" /> <path d=\"m 268.46918,687.12853 v -3.56795 q 0,-0.67434 -0.30698,-1.00648 -0.30697,-0.33213 -0.96118,-0.33213 -0.86557,0 -1.26816,0.46801 -0.40259,0.46801 -0.40259,1.54494 v 2.89361 h -0.83537 v -5.51548 h 0.67937 l 0.13587,0.75486 h 0.0403 q 0.25665,-0.40763 0.71963,-0.62905 0.46298,-0.22646 1.03164,-0.22646 0.99641,0 1.49964,0.48311 0.50324,0.47808 0.50324,1.53487 v 3.59815 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8379\" /> <path d=\"m 275.78122,684.36576 q 0,1.34867 -0.67937,2.10856 -0.67937,0.75486 -1.87708,0.75486 -0.73976,0 -1.31345,-0.34724 -0.57369,-0.34723 -0.8857,-0.99641 -0.312,-0.64917 -0.312,-1.51977 0,-1.34868 0.67433,-2.0985 0.67434,-0.75486 1.87205,-0.75486 1.15744,0 1.83681,0.76996 0.68441,0.76995 0.68441,2.0834 z m -4.20203,0 q 0,1.0568 0.42271,1.61036 0.42272,0.55356 1.243,0.55356 0.82028,0 1.243,-0.54853 0.42775,-0.55356 0.42775,-1.61539 0,-1.05177 -0.42775,-1.59526 -0.42272,-0.54853 -1.25306,-0.54853 -0.82028,0 -1.23797,0.53846 -0.41768,0.53846 -0.41768,1.60533 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8381\" /> <path d=\"m 280.99979,686.38877 h -0.0453 q -0.57873,0.84041 -1.73114,0.84041 -1.08196,0 -1.68584,-0.73976 -0.59886,-0.73976 -0.59886,-2.10353 0,-1.36378 0.60389,-2.11863 0.60388,-0.75486 1.68081,-0.75486 1.12222,0 1.72107,0.81525 h 0.0654 l -0.0352,-0.39756 -0.0201,-0.38749 v -2.24444 h 0.83537 v 7.83037 h -0.67937 z m -1.67075,0.14091 q 0.8555,0 1.23796,-0.46298 0.3875,-0.46801 0.3875,-1.50468 v -0.17613 q 0,-1.17255 -0.39253,-1.67075 -0.38749,-0.50324 -1.24299,-0.50324 -0.73473,0 -1.12726,0.57369 -0.38749,0.56866 -0.38749,1.61036 0,1.0568 0.38749,1.59526 0.3875,0.53847 1.13732,0.53847 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8383\" /> <path d=\"m 285.89125,687.22918 q -1.22286,0 -1.93243,-0.74479 -0.70453,-0.74479 -0.70453,-2.06831 0,-1.33358 0.65421,-2.11863 0.65924,-0.78505 1.76636,-0.78505 1.03667,0 1.64056,0.6844 0.60388,0.67938 0.60388,1.79656 v 0.5284 h -3.79944 q 0.0252,0.97125 0.48814,1.47449 0.46801,0.50323 1.31345,0.50323 0.89073,0 1.76133,-0.37239 v 0.74479 q -0.44285,0.19123 -0.84041,0.27175 -0.39252,0.0856 -0.95112,0.0856 z m -0.22645,-5.01728 q -0.66428,0 -1.06183,0.43279 -0.39253,0.43278 -0.46298,1.1977 h 2.88355 q 0,-0.79008 -0.35227,-1.20777 -0.35226,-0.42272 -1.00647,-0.42272 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8385\" /> <path d=\"m 292.90135,685.62385 q 0,0.76995 -0.57369,1.18764 -0.57369,0.41769 -1.61036,0.41769 -1.09706,0 -1.71101,-0.34724 v -0.77498 q 0.39756,0.20129 0.85047,0.31704 0.45795,0.11574 0.88067,0.11574 0.65421,0 1.00647,-0.20632 0.35227,-0.21136 0.35227,-0.63912 0,-0.32207 -0.28181,-0.54852 -0.27678,-0.23149 -1.087,-0.5435 -0.76995,-0.28685 -1.09705,-0.49821 -0.32207,-0.21639 -0.48311,-0.48814 -0.156,-0.27174 -0.156,-0.64917 0,-0.67434 0.54852,-1.06183 0.54853,-0.39253 1.50468,-0.39253 0.89073,0 1.74121,0.36233 l -0.29691,0.67937 q -0.83035,-0.3422 -1.50468,-0.3422 -0.59382,0 -0.89577,0.1862 -0.30194,0.1862 -0.30194,0.5133 0,0.22143 0.11071,0.37743 0.11575,0.156 0.36737,0.29691 0.25161,0.14091 0.96621,0.40762 0.98131,0.3573 1.32352,0.71963 0.34723,0.36233 0.34723,0.91086 z\" style=\"font-size:10.3063px;line-height:1;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';text-align:center;text-anchor:middle;stroke-width:1.33333\" id=\"path8387\" /> </g> <path d=\"M294.473 58.707v2.012c0 2.011 0 6.039.039 10.105.043 4.067.121 8.172.16 10.227l.043 2.051\" style=\"fill:none;stroke:#333;stroke-width:.966214;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1\" transform=\"scale(1.33333)\" id=\"path3009\" /> <g id=\"g12795\"> <path d=\"m 343.02458,287.68475 -2.49604,-6.52193 h -0.0403 q 0.0704,0.77498 0.0704,1.84185 v 4.68008 h -0.79008 v -7.3573 h 1.28828 l 2.32998,6.06902 h 0.0403 l 2.35012,-6.06902 h 1.27821 v 7.3573 h -0.85549 v -4.74048 q 0,-0.81524 0.0704,-1.77139 h -0.0403 l -2.51617,6.51187 z\" id=\"path7694\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 351.61969,287.68475 -0.16608,-0.78505 h -0.0403 q -0.41265,0.51833 -0.82531,0.70453 -0.40762,0.18116 -1.02157,0.18116 -0.82026,0 -1.28827,-0.42271 -0.46298,-0.42272 -0.46298,-1.20274 0,-1.67073 2.67217,-1.75125 l 0.93602,-0.0301 v -0.3422 q 0,-0.64918 -0.28181,-0.95615 -0.27678,-0.31201 -0.89073,-0.31201 -0.68942,0 -1.56002,0.42272 l -0.25665,-0.63911 q 0.40762,-0.22142 0.89073,-0.34722 0.48813,-0.12587 0.97627,-0.12587 0.98634,0 1.45937,0.43781 0.47808,0.43782 0.47808,1.40403 v 3.7642 z m -1.88714,-0.58879 q 0.78003,0 1.22287,-0.42774 0.44787,-0.42776 0.44787,-1.19771 v -0.4982 l -0.83537,0.0352 q -0.99639,0.0352 -1.43925,0.312 -0.43781,0.27175 -0.43781,0.85047 0,0.45292 0.27175,0.68944 0.27677,0.23652 0.76994,0.23652 z\" id=\"path7696\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 357.7324,287.68475 v -3.56794 q 0,-0.67433 -0.30697,-1.00646 -0.30698,-0.33215 -0.96119,-0.33215 -0.86556,0 -1.26814,0.46801 -0.4026,0.46801 -0.4026,1.54493 v 2.89361 h -0.83537 v -5.51546 h 0.67937 l 0.13588,0.75486 h 0.0403 q 0.25665,-0.40763 0.71962,-0.62906 0.46299,-0.22645 1.03164,-0.22645 0.9964,0 1.49963,0.48311 0.50324,0.47808 0.50324,1.53486 v 3.59814 z\" id=\"path7698\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 363.08036,287.68475 -0.16608,-0.78505 h -0.0403 q -0.41265,0.51833 -0.8253,0.70453 -0.40763,0.18116 -1.02157,0.18116 -0.82027,0 -1.28828,-0.42271 -0.46297,-0.42272 -0.46297,-1.20274 0,-1.67073 2.67217,-1.75125 l 0.93602,-0.0301 v -0.3422 q 0,-0.64918 -0.28181,-0.95615 -0.27679,-0.31201 -0.89073,-0.31201 -0.68943,0 -1.56003,0.42272 l -0.25665,-0.63911 q 0.40763,-0.22142 0.89073,-0.34722 0.48813,-0.12587 0.97628,-0.12587 0.98633,0 1.45937,0.43781 0.47808,0.43782 0.47808,1.40403 v 3.7642 z m -1.88714,-0.58879 q 0.78002,0 1.22286,-0.42774 0.44788,-0.42776 0.44788,-1.19771 v -0.4982 l -0.83537,0.0352 q -0.9964,0.0352 -1.43925,0.312 -0.43781,0.27175 -0.43781,0.85047 0,0.45292 0.27174,0.68944 0.27677,0.23652 0.76995,0.23652 z\" id=\"path7700\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 369.93282,282.16929 v 0.5284 l -1.02157,0.1208 q 0.14091,0.17614 0.25161,0.46298 0.11067,0.28181 0.11067,0.6391 0,0.81021 -0.55356,1.29332 -0.55356,0.4831 -1.51977,0.4831 -0.24658,0 -0.46298,-0.0403 -0.53343,0.28181 -0.53343,0.70955 0,0.22646 0.1862,0.33718 0.1862,0.10573 0.63911,0.10573 h 0.97627 q 0.89576,0 1.37384,0.37743 0.48311,0.37742 0.48311,1.09705 0,0.91589 -0.73474,1.39395 -0.73471,0.48311 -2.14378,0.48311 -1.08195,0 -1.67074,-0.40259 -0.58375,-0.40258 -0.58375,-1.13731 0,-0.50323 0.32207,-0.8706 0.32208,-0.36736 0.90583,-0.4982 -0.21136,-0.0956 -0.3573,-0.29691 -0.1409,-0.20129 -0.1409,-0.46801 0,-0.30193 0.16104,-0.5284 0.16102,-0.22645 0.50826,-0.43781 -0.42776,-0.17613 -0.6995,-0.59885 -0.26671,-0.42272 -0.26671,-0.96621 0,-0.90583 0.54349,-1.39396 0.54349,-0.49317 1.53991,-0.49317 0.43277,0 0.78001,0.10066 z m -4.39828,6.44142 q 0,0.44787 0.37743,0.67935 0.37742,0.2315 1.08195,0.2315 1.05176,0 1.555,-0.31704 0.50826,-0.31202 0.50826,-0.85047 0,-0.44788 -0.27677,-0.62401 -0.27678,-0.17111 -1.0417,-0.17111 h -1.00144 q -0.56865,0 -0.88569,0.27175 -0.31704,0.27175 -0.31704,0.78003 z m 0.45292,-4.67506 q 0,0.57872 0.3271,0.87562 0.3271,0.29691 0.91086,0.29691 1.22286,0 1.22286,-1.18764 0,-1.24298 -1.23796,-1.24298 -0.58878,0 -0.90582,0.31704 -0.31704,0.31704 -0.31704,0.94105 z\" id=\"path7702\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 373.47903,287.78539 q -1.22287,0 -1.93243,-0.74479 -0.70453,-0.74478 -0.70453,-2.06829 0,-1.33358 0.65421,-2.11862 0.65924,-0.78505 1.76636,-0.78505 1.03666,0 1.64054,0.6844 0.60388,0.67937 0.60388,1.79656 v 0.52839 h -3.79942 q 0.0252,0.97124 0.48814,1.47448 0.46801,0.50324 1.31345,0.50324 0.89071,0 1.76131,-0.3724 v 0.74478 q -0.44284,0.19123 -0.8404,0.27175 -0.39252,0.0856 -0.95111,0.0856 z m -0.22646,-5.01726 q -0.66426,0 -1.06182,0.43279 -0.39253,0.43278 -0.46299,1.1977 h 2.88354 q 0,-0.79008 -0.35226,-1.20777 -0.35227,-0.42272 -1.00647,-0.42272 z\" id=\"path7704\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 380.63344,286.94499 h -0.0453 q -0.57872,0.8404 -1.73113,0.8404 -1.08195,0 -1.68583,-0.73975 -0.59885,-0.73976 -0.59885,-2.10353 0,-1.36377 0.60387,-2.11862 0.6039,-0.75485 1.68081,-0.75485 1.12221,0 1.72107,0.81524 h 0.0655 l -0.0352,-0.39755 -0.0201,-0.38749 v -2.24443 h 0.83537 v 7.83034 h -0.67937 z m -1.67075,0.14091 q 0.85551,0 1.23796,-0.46298 0.38749,-0.46801 0.38749,-1.50467 v -0.17614 q 0,-1.17253 -0.39252,-1.67074 -0.38749,-0.50324 -1.24299,-0.50324 -0.73472,0 -1.12724,0.57369 -0.38749,0.56866 -0.38749,1.61036 0,1.0568 0.38749,1.59525 0.38748,0.53847 1.1373,0.53847 z\" id=\"path7706\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 387.66866,287.78539 q -1.19771,0 -1.85694,-0.73472 -0.6542,-0.73976 -0.6542,-2.08842 0,-1.38391 0.66426,-2.13876 0.66931,-0.75485 1.90222,-0.75485 0.39756,0 0.79512,0.0856 0.39756,0.0856 0.62401,0.20129 l -0.25665,0.70958 q -0.27677,-0.11067 -0.60388,-0.18118 -0.3271,-0.0755 -0.57872,-0.0755 -1.68081,0 -1.68081,2.14378 0,1.01653 0.40763,1.56002 0.41265,0.54351 1.21782,0.54351 0.68944,0 1.41409,-0.29692 v 0.73975 q -0.55355,0.28684 -1.39395,0.28684 z\" id=\"path7708\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 395.3781,284.92198 q 0,1.34868 -0.67935,2.10856 -0.67938,0.75485 -1.87708,0.75485 -0.73974,0 -1.31344,-0.34723 -0.57369,-0.34724 -0.88569,-0.99641 -0.31201,-0.64917 -0.31201,-1.51977 0,-1.34866 0.67433,-2.09849 0.67435,-0.75485 1.87204,-0.75485 1.15745,0 1.83681,0.76995 0.68439,0.76995 0.68439,2.08339 z m -4.202,0 q 0,1.0568 0.42272,1.61036 0.42272,0.55356 1.24298,0.55356 0.82028,0 1.243,-0.54854 0.42775,-0.55354 0.42775,-1.61538 0,-1.05176 -0.42775,-1.59525 -0.42272,-0.54853 -1.25306,-0.54853 -0.82027,0 -1.23796,0.53847 -0.41768,0.53846 -0.41768,1.60531 z\" id=\"path7710\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 400.12219,287.68475 v -3.56794 q 0,-0.67433 -0.30698,-1.00646 -0.30697,-0.33215 -0.96118,-0.33215 -0.86556,0 -1.26814,0.46801 -0.4026,0.46801 -0.4026,1.54493 v 2.89361 h -0.83537 v -5.51546 h 0.67937 l 0.13588,0.75486 h 0.0403 q 0.25666,-0.40763 0.71963,-0.62906 0.46297,-0.22645 1.03164,-0.22645 0.99639,0 1.49963,0.48311 0.50324,0.47808 0.50324,1.53486 v 3.59814 z\" id=\"path7712\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 403.85963,287.09596 q 0.22141,0 0.42775,-0.0301 0.20632,-0.0352 0.3271,-0.0704 v 0.63912 q -0.13588,0.0655 -0.4026,0.10573 -0.26168,0.0453 -0.47304,0.0453 -1.60029,0 -1.60029,-1.68583 v -3.28109 h -0.79007 v -0.40258 l 0.79007,-0.34724 0.35227,-1.17757 h 0.48311 v 1.27822 h 1.60029 v 0.64917 h -1.60029 v 3.24586 q 0,0.49821 0.23652,0.76492 0.23653,0.26672 0.64918,0.26672 z\" id=\"path7714\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 407.44911,282.06864 q 0.36736,0 0.65924,0.0604 l -0.11573,0.77499 q -0.3422,-0.0755 -0.60388,-0.0755 -0.6693,0 -1.14737,0.54349 -0.47304,0.54349 -0.47304,1.3537 v 2.95902 h -0.83537 v -5.51545 h 0.68943 l 0.0956,1.02156 h 0.0403 q 0.30697,-0.53845 0.73975,-0.83033 0.43278,-0.29188 0.95111,-0.29188 z\" id=\"path7716\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 413.12554,284.92198 q 0,1.34868 -0.67936,2.10856 -0.67937,0.75485 -1.87707,0.75485 -0.73976,0 -1.31344,-0.34723 -0.57369,-0.34724 -0.88569,-0.99641 -0.31201,-0.64917 -0.31201,-1.51977 0,-1.34866 0.67433,-2.09849 0.67434,-0.75485 1.87203,-0.75485 1.15744,0 1.83681,0.76995 0.6844,0.76995 0.6844,2.08339 z m -4.202,0 q 0,1.0568 0.4227,1.61036 0.42272,0.55356 1.243,0.55356 0.82028,0 1.24298,-0.54854 0.42776,-0.55354 0.42776,-1.61538 0,-1.05176 -0.42776,-1.59525 -0.4227,-0.54853 -1.25305,-0.54853 -0.82027,0 -1.23795,0.53847 -0.41768,0.53846 -0.41768,1.60531 z\" id=\"path7718\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 414.93056,287.68475 h -0.83537 v -7.83034 h 0.83537 z\" id=\"path7720\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 421.80451,287.78539 q -0.53847,0 -0.98635,-0.19626 -0.44285,-0.20129 -0.74478,-0.61394 h -0.0604 q 0.0604,0.4831 0.0604,0.91588 v 2.26959 h -0.83537 v -7.99137 h 0.67935 l 0.11574,0.75486 h 0.0403 q 0.32207,-0.45292 0.74981,-0.65422 0.42776,-0.20129 0.98132,-0.20129 1.09705,0 1.69086,0.74983 0.59886,0.74981 0.59886,2.10351 0,1.35874 -0.60892,2.1136 -0.60388,0.74981 -1.6808,0.74981 z m -0.1208,-5.00719 q -0.84543,0 -1.22287,0.46801 -0.37742,0.46801 -0.38748,1.48958 v 0.18619 q 0,1.16248 0.38748,1.66572 0.38749,0.4982 1.243,0.4982 0.7146,0 1.11718,-0.57872 0.40762,-0.57872 0.40762,-1.59527 0,-1.03162 -0.40762,-1.58015 -0.40258,-0.55356 -1.13731,-0.55356 z\" id=\"path7722\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 425.80362,287.68475 h -0.83536 v -7.83034 h 0.83536 z\" id=\"path7724\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 430.64818,287.68475 -0.16607,-0.78505 h -0.0403 q -0.41266,0.51833 -0.82531,0.70453 -0.40762,0.18116 -1.02156,0.18116 -0.82028,0 -1.28829,-0.42271 -0.46297,-0.42272 -0.46297,-1.20274 0,-1.67073 2.67218,-1.75125 l 0.93601,-0.0301 v -0.3422 q 0,-0.64918 -0.28182,-0.95615 -0.27677,-0.31201 -0.89071,-0.31201 -0.68944,0 -1.56004,0.42272 l -0.25664,-0.63911 q 0.40761,-0.22142 0.89072,-0.34722 0.48814,-0.12587 0.97628,-0.12587 0.98634,0 1.45938,0.43781 0.47808,0.43782 0.47808,1.40403 v 3.7642 z m -1.88713,-0.58879 q 0.78001,0 1.22286,-0.42774 0.44788,-0.42776 0.44788,-1.19771 v -0.4982 l -0.83537,0.0352 q -0.99641,0.0352 -1.43925,0.312 -0.43783,0.27175 -0.43783,0.85047 0,0.45292 0.27175,0.68944 0.27679,0.23652 0.76996,0.23652 z\" id=\"path7726\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 436.76088,287.68475 v -3.56794 q 0,-0.67433 -0.30697,-1.00646 -0.30697,-0.33215 -0.96117,-0.33215 -0.86557,0 -1.26816,0.46801 -0.40258,0.46801 -0.40258,1.54493 v 2.89361 h -0.83538 v -5.51546 h 0.67938 l 0.13586,0.75486 h 0.0403 q 0.25664,-0.40763 0.71962,-0.62906 0.46298,-0.22645 1.03163,-0.22645 0.99641,0 1.49965,0.48311 0.50322,0.47808 0.50322,1.53486 v 3.59814 z\" id=\"path7728\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 441.04686,287.78539 q -1.22287,0 -1.93242,-0.74479 -0.70454,-0.74478 -0.70454,-2.06829 0,-1.33358 0.6542,-2.11862 0.65924,-0.78505 1.76636,-0.78505 1.03666,0 1.64055,0.6844 0.60388,0.67937 0.60388,1.79656 v 0.52839 h -3.79943 q 0.0252,0.97124 0.48815,1.47448 0.468,0.50324 1.31343,0.50324 0.89074,0 1.76133,-0.3724 v 0.74478 q -0.44285,0.19123 -0.84041,0.27175 -0.39252,0.0856 -0.9511,0.0856 z m -0.22647,-5.01726 q -0.66426,0 -1.06182,0.43279 -0.39252,0.43278 -0.46297,1.1977 h 2.88353 q 0,-0.79008 -0.35226,-1.20777 -0.35227,-0.42272 -1.00648,-0.42272 z\" id=\"path7730\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 445.32275,286.48704 0.0755,0.11574 q -0.1308,0.50324 -0.37743,1.1675 -0.24657,0.66931 -0.51329,1.243 h -0.62905 q 0.13588,-0.52337 0.29692,-1.29332 0.16607,-0.76994 0.23148,-1.23293 z\" id=\"path7732\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 350.65124,298.20405 q 0,0.76995 -0.57369,1.18764 -0.57369,0.41768 -1.61035,0.41768 -1.09706,0 -1.711,-0.34723 v -0.77498 q 0.39756,0.20129 0.85046,0.31704 0.45795,0.11573 0.88067,0.11573 0.6542,0 1.00646,-0.20632 0.35227,-0.21136 0.35227,-0.6391 0,-0.32208 -0.28181,-0.54853 -0.27678,-0.2315 -1.08699,-0.5435 -0.76994,-0.28684 -1.09705,-0.4982 -0.32208,-0.21639 -0.4831,-0.48814 -0.156,-0.27175 -0.156,-0.64917 0,-0.67433 0.54852,-1.06183 0.54853,-0.39252 1.50467,-0.39252 0.89072,0 1.7412,0.36232 l -0.29692,0.67938 q -0.83033,-0.3422 -1.50467,-0.3422 -0.59382,0 -0.89575,0.1862 -0.30195,0.1862 -0.30195,0.51329 0,0.22142 0.11067,0.37742 0.11573,0.15602 0.36737,0.29692 0.25161,0.14091 0.96621,0.40762 0.98131,0.3573 1.3235,0.71962 0.34724,0.36233 0.34724,0.91086 z\" id=\"path7735\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 354.57653,299.80937 q -1.22287,0 -1.93242,-0.74478 -0.70454,-0.74479 -0.70454,-2.06831 0,-1.33357 0.65422,-2.11862 0.65923,-0.78504 1.76635,-0.78504 1.03666,0 1.64054,0.6844 0.60388,0.67936 0.60388,1.79655 v 0.52839 h -3.79942 q 0.0252,0.97125 0.48814,1.47448 0.46801,0.50324 1.31345,0.50324 0.89071,0 1.76131,-0.3724 v 0.7448 q -0.44284,0.19122 -0.8404,0.27174 -0.39251,0.0856 -0.95111,0.0856 z m -0.22646,-5.01725 q -0.66426,0 -1.06182,0.43278 -0.39253,0.43279 -0.46299,1.19769 h 2.88354 q 0,-0.79008 -0.35226,-1.20775 -0.35227,-0.42272 -1.00647,-0.42272 z\" id=\"path7737\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 358.81217,299.70872 h -0.83537 v -7.83033 h 0.83537 z\" id=\"path7739\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 362.75079,294.84244 h -1.40404 v 4.86628 h -0.83537 v -4.86628 h -0.98633 v -0.37743 l 0.98633,-0.30193 v -0.30697 q 0,-2.03308 1.77642,-2.03308 0.43781,0 1.0266,0.17613 l -0.21639,0.66931 q -0.4831,-0.15601 -0.8253,-0.15601 -0.47304,0 -0.69949,0.31703 -0.22647,0.31202 -0.22647,1.00648 v 0.35729 h 1.40404 z\" id=\"path7741\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 373.00469,299.70872 v -3.58806 q 0,-0.65924 -0.28181,-0.98634 -0.28181,-0.33214 -0.87562,-0.33214 -0.78001,0 -1.15241,0.44788 -0.3724,0.44788 -0.3724,1.37887 v 3.07979 h -0.83536 v -3.58806 q 0,-0.65924 -0.28181,-0.98634 -0.28182,-0.33214 -0.88067,-0.33214 -0.78505,0 -1.15241,0.47304 -0.36233,0.46801 -0.36233,1.5399 v 2.8936 h -0.83537 v -5.51546 h 0.67937 l 0.13588,0.75486 h 0.0403 q 0.23652,-0.40259 0.66426,-0.62904 0.43279,-0.22646 0.96621,-0.22646 1.29332,0 1.69088,0.93602 h 0.0403 q 0.24659,-0.43279 0.7146,-0.6844 0.46801,-0.25162 1.06687,-0.25162 0.93601,0 1.39898,0.48311 0.46801,0.47807 0.46801,1.53486 v 3.59813 z\" id=\"path7743\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 377.95138,299.70872 -0.16608,-0.78504 h -0.0403 q -0.41265,0.51833 -0.82531,0.70453 -0.40762,0.18116 -1.02157,0.18116 -0.82026,0 -1.28827,-0.42272 -0.46298,-0.42272 -0.46298,-1.20273 0,-1.67074 2.67217,-1.75126 l 0.93603,-0.0301 v -0.3422 q 0,-0.64918 -0.28182,-0.95615 -0.27678,-0.31201 -0.89073,-0.31201 -0.68942,0 -1.56002,0.42272 l -0.25665,-0.63911 q 0.40762,-0.22142 0.89073,-0.34724 0.48813,-0.12586 0.97628,-0.12586 0.98633,0 1.45936,0.43782 0.47808,0.43782 0.47808,1.40403 v 3.76419 z m -1.88715,-0.58879 q 0.78003,0 1.22287,-0.42774 0.44788,-0.42775 0.44788,-1.19771 v -0.4982 l -0.83538,0.0352 q -0.99639,0.0352 -1.43925,0.31202 -0.43781,0.27174 -0.43781,0.85046 0,0.45291 0.27175,0.68943 0.27677,0.23652 0.76994,0.23652 z\" id=\"path7745\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 384.06408,299.70872 v -3.56793 q 0,-0.67434 -0.30697,-1.00647 -0.30698,-0.33214 -0.96119,-0.33214 -0.86555,0 -1.26814,0.46802 -0.4026,0.46799 -0.4026,1.54492 v 2.8936 h -0.83537 v -5.51546 h 0.67937 l 0.13588,0.75486 h 0.0403 q 0.25665,-0.40762 0.71962,-0.62904 0.46297,-0.22646 1.03164,-0.22646 0.9964,0 1.49964,0.48311 0.50323,0.47807 0.50323,1.53486 v 3.59813 z\" id=\"path7747\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 389.41187,299.70872 -0.16607,-0.78504 h -0.0403 q -0.41265,0.51833 -0.8253,0.70453 -0.40763,0.18116 -1.02157,0.18116 -0.82028,0 -1.28828,-0.42272 -0.46298,-0.42272 -0.46298,-1.20273 0,-1.67074 2.67218,-1.75126 l 0.93602,-0.0301 v -0.3422 q 0,-0.64918 -0.28181,-0.95615 -0.27679,-0.31201 -0.89073,-0.31201 -0.68943,0 -1.56003,0.42272 l -0.25665,-0.63911 q 0.40761,-0.22142 0.89072,-0.34724 0.48814,-0.12586 0.97628,-0.12586 0.98634,0 1.45938,0.43782 0.47808,0.43782 0.47808,1.40403 v 3.76419 z m -1.88713,-0.58879 q 0.78001,0 1.22286,-0.42774 0.44788,-0.42775 0.44788,-1.19771 v -0.4982 l -0.83537,0.0352 q -0.99641,0.0352 -1.43925,0.31202 -0.43781,0.27174 -0.43781,0.85046 0,0.45291 0.27174,0.68943 0.27678,0.23652 0.76995,0.23652 z\" id=\"path7749\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 396.26446,294.19326 v 0.5284 l -1.02157,0.1208 q 0.14091,0.17614 0.25161,0.46299 0.11067,0.28181 0.11067,0.6391 0,0.81021 -0.55356,1.29332 -0.55356,0.48311 -1.51977,0.48311 -0.24658,0 -0.46298,-0.0403 -0.53343,0.28181 -0.53343,0.70957 0,0.22645 0.1862,0.33716 0.1862,0.10573 0.63911,0.10573 h 0.97627 q 0.89576,0 1.37384,0.37743 0.48311,0.37742 0.48311,1.09705 0,0.91589 -0.73474,1.39397 -0.73471,0.4831 -2.14378,0.4831 -1.08195,0 -1.67074,-0.40259 -0.58374,-0.40259 -0.58374,-1.13731 0,-0.50324 0.32206,-0.8706 0.32208,-0.36736 0.90583,-0.49819 -0.21136,-0.0956 -0.3573,-0.29692 -0.1409,-0.2013 -0.1409,-0.468 0,-0.30195 0.16102,-0.5284 0.16104,-0.22645 0.50828,-0.43781 -0.42776,-0.17614 -0.6995,-0.59886 -0.26671,-0.42271 -0.26671,-0.96621 0,-0.90582 0.54349,-1.39395 0.5435,-0.49318 1.53989,-0.49318 0.43279,0 0.78003,0.10067 z m -4.39828,6.44142 q 0,0.44787 0.37743,0.67937 0.37742,0.23148 1.08195,0.23148 1.05176,0 1.555,-0.31704 0.50826,-0.312 0.50826,-0.85047 0,-0.44788 -0.27677,-0.62401 -0.27678,-0.17109 -1.0417,-0.17109 h -1.00144 q -0.56865,0 -0.88569,0.27174 -0.31704,0.27175 -0.31704,0.78002 z m 0.45292,-4.67506 q 0,0.57872 0.32709,0.87562 0.32711,0.29692 0.91087,0.29692 1.22286,0 1.22286,-1.18763 0,-1.243 -1.23797,-1.243 -0.58877,0 -0.90581,0.31704 -0.31704,0.31704 -0.31704,0.94105 z\" id=\"path7751\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 399.81067,299.80937 q -1.22287,0 -1.93242,-0.74478 -0.70454,-0.74479 -0.70454,-2.06831 0,-1.33357 0.65422,-2.11862 0.65923,-0.78504 1.76635,-0.78504 1.03667,0 1.64054,0.6844 0.60388,0.67936 0.60388,1.79655 v 0.52839 h -3.79942 q 0.0252,0.97125 0.48814,1.47448 0.46801,0.50324 1.31345,0.50324 0.89071,0 1.76131,-0.3724 v 0.7448 q -0.44284,0.19122 -0.8404,0.27174 -0.39251,0.0856 -0.95111,0.0856 z m -0.22646,-5.01725 q -0.66427,0 -1.06182,0.43278 -0.39253,0.43279 -0.46299,1.19769 h 2.88354 q 0,-0.79008 -0.35226,-1.20775 -0.35227,-0.42272 -1.00647,-0.42272 z\" id=\"path7753\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 406.96508,298.96897 h -0.0453 q -0.57872,0.8404 -1.73113,0.8404 -1.08195,0 -1.68583,-0.73976 -0.59885,-0.73976 -0.59885,-2.10351 0,-1.36377 0.60387,-2.11862 0.6039,-0.75486 1.68081,-0.75486 1.12221,0 1.72107,0.81524 h 0.0655 l -0.0352,-0.39756 -0.0201,-0.38749 v -2.24442 h 0.83537 v 7.83033 h -0.67937 z m -1.67075,0.14091 q 0.85551,0 1.23796,-0.46299 0.38749,-0.468 0.38749,-1.50466 v -0.17613 q 0,-1.17255 -0.39252,-1.67074 -0.38749,-0.50324 -1.24299,-0.50324 -0.73472,0 -1.12724,0.57369 -0.38749,0.56865 -0.38749,1.61034 0,1.0568 0.38749,1.59526 0.38748,0.53847 1.1373,0.53847 z\" id=\"path7755\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 415.57027,299.70872 v -3.56793 q 0,-0.67434 -0.30697,-1.00647 -0.30698,-0.33214 -0.96119,-0.33214 -0.86556,0 -1.26814,0.46802 -0.4026,0.46799 -0.4026,1.54492 v 2.8936 H 411.796 v -5.51546 h 0.67937 l 0.13588,0.75486 h 0.0403 q 0.25665,-0.40762 0.71962,-0.62904 0.46297,-0.22646 1.03164,-0.22646 0.99639,0 1.49963,0.48311 0.50324,0.47807 0.50324,1.53486 v 3.59813 z\" id=\"path7757\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 422.28698,296.94596 q 0,1.34867 -0.67937,2.10856 -0.67937,0.75485 -1.87706,0.75485 -0.73976,0 -1.31345,-0.34723 -0.57369,-0.34723 -0.88569,-0.99641 -0.31201,-0.64917 -0.31201,-1.51977 0,-1.34867 0.67434,-2.09848 0.67433,-0.75486 1.87204,-0.75486 1.15743,0 1.83681,0.76995 0.68439,0.76994 0.68439,2.08339 z m -4.20201,0 q 0,1.0568 0.42272,1.61036 0.42272,0.55356 1.24298,0.55356 0.82028,0 1.243,-0.54853 0.42774,-0.55356 0.42774,-1.61539 0,-1.05175 -0.42774,-1.59526 -0.42272,-0.54852 -1.25307,-0.54852 -0.82026,0 -1.23795,0.53847 -0.41768,0.53845 -0.41768,1.60531 z\" id=\"path7759\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 427.01076,298.96897 h -0.0453 q -0.57872,0.8404 -1.73113,0.8404 -1.08196,0 -1.68584,-0.73976 -0.59885,-0.73976 -0.59885,-2.10351 0,-1.36377 0.60389,-2.11862 0.60388,-0.75486 1.6808,-0.75486 1.12222,0 1.72106,0.81524 h 0.0655 l -0.0352,-0.39756 -0.0201,-0.38749 v -2.24442 h 0.83537 v 7.83033 h -0.67937 z m -1.67074,0.14091 q 0.8555,0 1.23795,-0.46299 0.3875,-0.468 0.3875,-1.50466 v -0.17613 q 0,-1.17255 -0.39252,-1.67074 -0.3875,-0.50324 -1.243,-0.50324 -0.73472,0 -1.12724,0.57369 -0.38749,0.56865 -0.38749,1.61034 0,1.0568 0.38749,1.59526 0.3875,0.53847 1.13731,0.53847 z\" id=\"path7761\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 431.31686,299.80937 q -1.22287,0 -1.93243,-0.74478 -0.70453,-0.74479 -0.70453,-2.06831 0,-1.33357 0.65421,-2.11862 0.65924,-0.78504 1.76636,-0.78504 1.03666,0 1.64054,0.6844 0.60388,0.67936 0.60388,1.79655 v 0.52839 h -3.79942 q 0.0252,0.97125 0.48813,1.47448 0.46802,0.50324 1.31345,0.50324 0.89072,0 1.76132,-0.3724 v 0.7448 q -0.44284,0.19122 -0.8404,0.27174 -0.39252,0.0856 -0.95111,0.0856 z m -0.22646,-5.01725 q -0.66428,0 -1.06182,0.43278 -0.39253,0.43279 -0.46299,1.19769 h 2.88354 q 0,-0.79008 -0.35226,-1.20775 -0.35227,-0.42272 -1.00647,-0.42272 z\" id=\"path7763\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 438.275,298.20405 q 0,0.76995 -0.57368,1.18764 -0.57369,0.41768 -1.61036,0.41768 -1.09705,0 -1.71099,-0.34723 v -0.77498 q 0.39754,0.20129 0.85046,0.31704 0.45795,0.11573 0.88067,0.11573 0.65419,0 1.00646,-0.20632 0.35227,-0.21136 0.35227,-0.6391 0,-0.32208 -0.28182,-0.54853 -0.27678,-0.2315 -1.08698,-0.5435 -0.76996,-0.28684 -1.09705,-0.4982 -0.32208,-0.21639 -0.48312,-0.48814 -0.156,-0.27175 -0.156,-0.64917 0,-0.67433 0.54853,-1.06183 0.54852,-0.39252 1.50468,-0.39252 0.89072,0 1.74118,0.36232 l -0.2969,0.67938 q -0.83034,-0.3422 -1.50468,-0.3422 -0.59381,0 -0.89576,0.1862 -0.30193,0.1862 -0.30193,0.51329 0,0.22142 0.11067,0.37742 0.11573,0.15602 0.36735,0.29692 0.25163,0.14091 0.96622,0.40762 0.98131,0.3573 1.32351,0.71962 0.34723,0.36233 0.34723,0.91086 z\" id=\"path7765\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> </g> <g aria-label=\"Self managed\" transform=\"scale(1.33333)\" id=\"text3065\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal'\"> <path d=\"m 202.6251,292.07612 q 0,0.72843 -0.52839,1.13606 -0.5284,0.40762 -1.43423,0.40762 -0.98131,0 -1.50971,-0.25288 v -0.61898 q 0.33969,0.14342 0.73976,0.22646 0.40007,0.083 0.7926,0.083 0.64162,0 0.96621,-0.24155 0.32459,-0.24533 0.32459,-0.67937 0,-0.28685 -0.117,-0.46801 -0.11323,-0.18494 -0.38498,-0.33969 -0.26797,-0.15474 -0.81902,-0.351 -0.76995,-0.27553 -1.10208,-0.65295 -0.32837,-0.37743 -0.32837,-0.98509 0,-0.63785 0.47934,-1.01528 0.47933,-0.37742 1.26815,-0.37742 0.82279,0 1.51349,0.30194 l -0.20004,0.55859 q -0.68314,-0.28685 -1.32854,-0.28685 -0.50953,0 -0.79638,0.21891 -0.28684,0.21891 -0.28684,0.60766 0,0.28685 0.10568,0.47178 0.10568,0.18117 0.35478,0.33591 0.25288,0.15098 0.76995,0.33592 0.86809,0.30949 1.19267,0.66427 0.32836,0.35478 0.32836,0.92092 z\" id=\"path7466\" /> <path d=\"m 206.31246,293.6198 q -0.91715,0 -1.44932,-0.5586 -0.5284,-0.55859 -0.5284,-1.55122 0,-1.00018 0.49065,-1.58897 0.49443,-0.58879 1.32477,-0.58879 0.7775,0 1.23042,0.5133 0.45291,0.50953 0.45291,1.34742 v 0.3963 h -2.84958 q 0.0189,0.72843 0.36611,1.10586 0.351,0.37743 0.98508,0.37743 0.66805,0 1.321,-0.2793 v 0.55859 q -0.33214,0.14343 -0.63031,0.20381 -0.29439,0.0642 -0.71333,0.0642 z m -0.16985,-3.76295 q -0.4982,0 -0.79637,0.32458 -0.29439,0.32459 -0.34723,0.89828 h 2.16266 q 0,-0.59256 -0.2642,-0.90582 -0.2642,-0.31704 -0.75486,-0.31704 z\" id=\"path7468\" /> <path d=\"m 209.4892,293.54431 h -0.62653 v -5.87277 h 0.62653 z\" id=\"path7470\" /> <path d=\"m 212.44316,289.89459 h -1.05302 v 3.64972 h -0.62653 v -3.64972 h -0.73976 v -0.28307 l 0.73976,-0.22646 v -0.23023 q 0,-1.5248 1.33232,-1.5248 0.32836,0 0.76995,0.1321 l -0.16229,0.50197 q -0.36233,-0.117 -0.61899,-0.117 -0.35478,0 -0.52462,0.23778 -0.16984,0.23401 -0.16984,0.75486 v 0.26797 h 1.05302 z\" id=\"path7472\" /> <path d=\"m 220.13363,293.54431 v -2.69105 q 0,-0.49443 -0.21136,-0.73976 -0.21136,-0.2491 -0.65672,-0.2491 -0.58501,0 -0.86431,0.33591 -0.2793,0.33591 -0.2793,1.03415 v 2.30985 h -0.62652 v -2.69105 q 0,-0.49443 -0.21136,-0.73976 -0.21136,-0.2491 -0.6605,-0.2491 -0.58879,0 -0.86431,0.35478 -0.27175,0.351 -0.27175,1.15492 v 2.17021 h -0.62653 v -4.1366 h 0.50953 l 0.10191,0.56614 h 0.0302 q 0.17739,-0.30194 0.4982,-0.47178 0.32459,-0.16985 0.72466,-0.16985 0.96999,0 1.26816,0.70202 h 0.0302 q 0.18494,-0.32459 0.53595,-0.5133 0.35101,-0.18872 0.80015,-0.18872 0.70201,0 1.04924,0.36233 0.35101,0.35856 0.35101,1.15116 v 2.6986 z\" id=\"path7474\" /> <path d=\"m 223.84363,293.54431 -0.12455,-0.58878 h -0.0302 q -0.30949,0.38875 -0.61898,0.52839 -0.30571,0.13588 -0.76617,0.13588 -0.61521,0 -0.96622,-0.31704 -0.34723,-0.31704 -0.34723,-0.90205 0,-1.25306 2.00414,-1.31345 l 0.70201,-0.0226 v -0.25665 q 0,-0.48688 -0.21136,-0.71711 -0.20758,-0.234 -0.66804,-0.234 -0.51708,0 -1.17003,0.31704 l -0.19248,-0.47934 q 0.30571,-0.16606 0.66804,-0.26042 0.36611,-0.0944 0.73221,-0.0944 0.73976,0 1.09454,0.32836 0.35856,0.32837 0.35856,1.05303 v 2.82315 z m -1.41535,-0.44159 q 0.58501,0 0.91715,-0.32081 0.33591,-0.32081 0.33591,-0.89828 v -0.37365 l -0.62653,0.0264 q -0.74731,0.0264 -1.07945,0.234 -0.32836,0.20381 -0.32836,0.63786 0,0.33968 0.20381,0.51707 0.20759,0.17739 0.57747,0.17739 z\" id=\"path7476\" /> <path d=\"m 228.42828,293.54431 v -2.67596 q 0,-0.50575 -0.23023,-0.75485 -0.23023,-0.2491 -0.72089,-0.2491 -0.64917,0 -0.95111,0.351 -0.30194,0.35101 -0.30194,1.1587 v 2.17021 h -0.62653 v -4.1366 h 0.50952 l 0.10191,0.56614 h 0.0302 q 0.19249,-0.30572 0.53972,-0.47178 0.34724,-0.16985 0.77373,-0.16985 0.7473,0 1.12473,0.36233 0.37743,0.35856 0.37743,1.15116 v 2.6986 z\" id=\"path7478\" /> <path d=\"m 232.43913,293.54431 -0.12455,-0.58878 h -0.0302 q -0.30949,0.38875 -0.61898,0.52839 -0.30572,0.13588 -0.76618,0.13588 -0.61521,0 -0.96621,-0.31704 -0.34724,-0.31704 -0.34724,-0.90205 0,-1.25306 2.00414,-1.31345 l 0.70202,-0.0226 v -0.25665 q 0,-0.48688 -0.21136,-0.71711 -0.20759,-0.234 -0.66805,-0.234 -0.51707,0 -1.17002,0.31704 l -0.19249,-0.47934 q 0.30572,-0.16606 0.66805,-0.26042 0.3661,-0.0944 0.73221,-0.0944 0.73975,0 1.09453,0.32836 0.35856,0.32837 0.35856,1.05303 v 2.82315 z m -1.41535,-0.44159 q 0.58501,0 0.91715,-0.32081 0.33591,-0.32081 0.33591,-0.89828 v -0.37365 l -0.62653,0.0264 q -0.7473,0.0264 -1.07944,0.234 -0.32836,0.20381 -0.32836,0.63786 0,0.33968 0.20381,0.51707 0.20758,0.17739 0.57746,0.17739 z\" id=\"path7480\" /> <path d=\"m 237.5785,289.40771 v 0.3963 l -0.76618,0.0906 q 0.10568,0.1321 0.18871,0.34723 0.083,0.21136 0.083,0.47934 0,0.60765 -0.41517,0.96998 -0.41517,0.36233 -1.13983,0.36233 -0.18494,0 -0.34724,-0.0302 -0.40007,0.21136 -0.40007,0.53217 0,0.16984 0.13965,0.25288 0.13965,0.0793 0.47933,0.0793 h 0.73221 q 0.67182,0 1.03038,0.28307 0.36233,0.28307 0.36233,0.82279 0,0.68692 -0.55105,1.04547 -0.55104,0.36233 -1.60784,0.36233 -0.81147,0 -1.25306,-0.30194 -0.43781,-0.30194 -0.43781,-0.85298 0,-0.37743 0.24155,-0.65295 0.24156,-0.27552 0.67937,-0.37366 -0.15852,-0.0717 -0.26797,-0.22268 -0.10568,-0.15097 -0.10568,-0.35101 0,-0.22645 0.12077,-0.39629 0.12078,-0.16985 0.38121,-0.32837 -0.32082,-0.1321 -0.52463,-0.44913 -0.20003,-0.31704 -0.20003,-0.72466 0,-0.67937 0.40762,-1.04548 0.40762,-0.36988 1.15492,-0.36988 0.32459,0 0.58502,0.0755 z m -3.29872,4.83107 q 0,0.33591 0.28307,0.50952 0.28307,0.17362 0.81147,0.17362 0.78882,0 1.16625,-0.23778 0.3812,-0.234 0.3812,-0.63785 0,-0.33591 -0.20758,-0.46801 -0.20759,-0.12833 -0.78128,-0.12833 h -0.75108 q -0.42649,0 -0.66427,0.20382 -0.23778,0.20381 -0.23778,0.58501 z m 0.33969,-3.5063 q 0,0.43404 0.24532,0.65672 0.24533,0.22268 0.68315,0.22268 0.91715,0 0.91715,-0.89072 0,-0.93225 -0.92848,-0.93225 -0.44159,0 -0.67936,0.23778 -0.23778,0.23778 -0.23778,0.70579 z\" id=\"path7482\" /> <path d=\"m 240.23816,293.6198 q -0.91715,0 -1.44932,-0.5586 -0.5284,-0.55859 -0.5284,-1.55122 0,-1.00018 0.49066,-1.58897 0.49443,-0.58879 1.32477,-0.58879 0.7775,0 1.23041,0.5133 0.45291,0.50953 0.45291,1.34742 v 0.3963 h -2.84957 q 0.0189,0.72843 0.3661,1.10586 0.35101,0.37743 0.98509,0.37743 0.66804,0 1.32099,-0.2793 v 0.55859 q -0.33213,0.14343 -0.6303,0.20381 -0.29439,0.0642 -0.71334,0.0642 z m -0.16984,-3.76295 q -0.49821,0 -0.79637,0.32458 -0.2944,0.32459 -0.34724,0.89828 h 2.16266 q 0,-0.59256 -0.2642,-0.90582 -0.2642,-0.31704 -0.75485,-0.31704 z\" id=\"path7484\" /> <path d=\"m 245.60398,292.98949 h -0.034 q -0.43404,0.63031 -1.29835,0.63031 -0.81147,0 -1.26438,-0.55482 -0.44914,-0.55482 -0.44914,-1.57765 0,-1.02282 0.45291,-1.58897 0.45292,-0.56614 1.26061,-0.56614 0.84166,0 1.2908,0.61144 h 0.0491 l -0.0264,-0.29817 -0.0151,-0.29062 v -1.68333 h 0.62653 v 5.87277 h -0.50953 z m -1.25306,0.10568 q 0.64163,0 0.92847,-0.34723 0.29062,-0.35101 0.29062,-1.12851 v -0.1321 q 0,-0.8794 -0.29439,-1.25306 -0.29062,-0.37742 -0.93225,-0.37742 -0.55104,0 -0.84544,0.43026 -0.29061,0.4265 -0.29061,1.20777 0,0.7926 0.29061,1.19645 0.29062,0.40384 0.85299,0.40384 z\" id=\"path7486\" /> </g> <g id=\"g13462\"> <path d=\"m 239.55408,611.7175 q 0,1.82171 -0.99137,2.78792 -0.98634,0.96117 -2.84327,0.96117 h -2.0381 v -7.35728 h 2.25448 q 1.71604,0 2.66714,0.95111 0.95112,0.95111 0.95112,2.65708 z m -0.90582,0.0301 q 0,-1.43925 -0.72465,-2.16894 -0.71963,-0.72969 -2.14379,-0.72969 h -1.24299 v 5.87778 h 1.0417 q 1.52984,0 2.29978,-0.74982 0.76995,-0.75485 0.76995,-2.22933 z\" id=\"path7489\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 243.32654,615.56725 q -1.22287,0 -1.93242,-0.74479 -0.70454,-0.74478 -0.70454,-2.0683 0,-1.33357 0.65422,-2.11862 0.65923,-0.78504 1.76635,-0.78504 1.03667,0 1.64054,0.6844 0.60388,0.67936 0.60388,1.79654 v 0.5284 h -3.79941 q 0.0252,0.97125 0.48813,1.47448 0.46801,0.50324 1.31345,0.50324 0.89072,0 1.76131,-0.3724 v 0.7448 q -0.44284,0.19122 -0.84039,0.27174 -0.39252,0.0856 -0.95112,0.0856 z m -0.22645,-5.01726 q -0.66427,0 -1.06183,0.43279 -0.39252,0.43278 -0.46297,1.19769 h 2.88353 q 0,-0.79008 -0.35226,-1.20776 -0.35226,-0.42272 -1.00647,-0.42272 z\" id=\"path7491\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 249.29331,609.86057 q 1.087,0 1.68584,0.74478 0.60389,0.73976 0.60389,2.09849 0,1.35873 -0.60892,2.11358 -0.60388,0.74983 -1.68081,0.74983 -0.53845,0 -0.98633,-0.19627 -0.44285,-0.20129 -0.7448,-0.61394 h -0.0604 l -0.17613,0.70955 h -0.59885 v -7.83032 h 0.83537 v 1.90222 q 0,0.6391 -0.0403,1.14738 h 0.0403 q 0.58376,-0.8253 1.73113,-0.8253 z m -0.1208,0.69949 q -0.8555,0 -1.23293,0.49317 -0.37743,0.48813 -0.37743,1.65061 0,1.16248 0.3875,1.6657 0.38749,0.49822 1.24299,0.49822 0.76995,0 1.14737,-0.5586 0.37743,-0.56363 0.37743,-1.61539 0,-1.07691 -0.37743,-1.60531 -0.37742,-0.5284 -1.1675,-0.5284 z\" id=\"path7493\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 253.29255,615.46659 h -0.83537 v -5.51545 h 0.83537 z m -0.90582,-7.01006 q 0,-0.28684 0.14091,-0.41768 0.1409,-0.13588 0.35226,-0.13588 0.20129,0 0.34724,0.13588 0.14593,0.13587 0.14593,0.41768 0,0.28181 -0.14593,0.42272 -0.14595,0.13588 -0.34724,0.13588 -0.21136,0 -0.35226,-0.13588 -0.14091,-0.14091 -0.14091,-0.42272 z\" id=\"path7495\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 258.13687,615.46659 -0.16607,-0.78503 h -0.0403 q -0.41265,0.51833 -0.82531,0.70453 -0.40762,0.18116 -1.02157,0.18116 -0.82026,0 -1.28827,-0.42272 -0.46298,-0.42272 -0.46298,-1.20273 0,-1.67074 2.67217,-1.75126 l 0.93603,-0.0301 v -0.3422 q 0,-0.64917 -0.28182,-0.95614 -0.27677,-0.31201 -0.89073,-0.31201 -0.68942,0 -1.56002,0.42272 l -0.25665,-0.63911 q 0.40762,-0.22143 0.89073,-0.34724 0.48813,-0.12586 0.97627,-0.12586 0.98634,0 1.45939,0.43781 0.47806,0.43781 0.47806,1.40402 v 3.76419 z m -1.88714,-0.58878 q 0.78003,0 1.22287,-0.42775 0.44788,-0.42774 0.44788,-1.1977 v -0.4982 l -0.83538,0.0352 q -0.99639,0.0352 -1.43925,0.31201 -0.43781,0.27175 -0.43781,0.85047 0,0.4529 0.27175,0.68942 0.27678,0.23652 0.76994,0.23652 z\" id=\"path7497\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 264.2497,615.46659 v -3.56792 q 0,-0.67434 -0.30697,-1.00648 -0.30698,-0.33213 -0.96119,-0.33213 -0.86556,0 -1.26814,0.46801 -0.40259,0.468 -0.40259,1.54493 v 2.89359 h -0.83537 v -5.51545 h 0.67936 l 0.13588,0.75485 h 0.0403 q 0.25665,-0.40761 0.71962,-0.62904 0.46299,-0.22645 1.03164,-0.22645 0.99641,0 1.49964,0.48311 0.50323,0.47806 0.50323,1.53486 v 3.59812 z\" id=\"path7499\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 265.74271,613.08629 v -0.76491 h 2.47089 v 0.76491 z\" id=\"path7501\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 272.20419,609.86057 q 1.08698,0 1.68583,0.74478 0.60388,0.73976 0.60388,2.09849 0,1.35873 -0.6089,2.11358 -0.6039,0.74983 -1.68081,0.74983 -0.53847,0 -0.98635,-0.19627 -0.44284,-0.20129 -0.74478,-0.61394 h -0.0604 l -0.17614,0.70955 h -0.59885 v -7.83032 h 0.83537 v 1.90222 q 0,0.6391 -0.0403,1.14738 h 0.0403 q 0.58376,-0.8253 1.73113,-0.8253 z m -0.1208,0.69949 q -0.85551,0 -1.23293,0.49317 -0.37743,0.48813 -0.37743,1.65061 0,1.16248 0.38749,1.6657 0.3875,0.49822 1.24299,0.49822 0.76995,0 1.14738,-0.5586 0.37743,-0.56363 0.37743,-1.61539 0,-1.07691 -0.37743,-1.60531 -0.37743,-0.5284 -1.1675,-0.5284 z\" id=\"path7503\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 278.75974,615.46659 -0.16606,-0.78503 h -0.0403 q -0.41265,0.51833 -0.8253,0.70453 -0.40762,0.18116 -1.02156,0.18116 -0.82028,0 -1.28829,-0.42272 -0.46297,-0.42272 -0.46297,-1.20273 0,-1.67074 2.67218,-1.75126 l 0.93601,-0.0301 v -0.3422 q 0,-0.64917 -0.28182,-0.95614 -0.27677,-0.31201 -0.89071,-0.31201 -0.68944,0 -1.56004,0.42272 l -0.25664,-0.63911 q 0.40761,-0.22143 0.89072,-0.34724 0.48814,-0.12586 0.97628,-0.12586 0.98634,0 1.45938,0.43781 0.47808,0.43781 0.47808,1.40402 v 3.76419 z m -1.88713,-0.58878 q 0.78002,0 1.22287,-0.42775 0.44788,-0.42774 0.44788,-1.1977 v -0.4982 l -0.83537,0.0352 q -0.99642,0.0352 -1.43927,0.31201 -0.43781,0.27175 -0.43781,0.85047 0,0.4529 0.27175,0.68942 0.27678,0.23652 0.76995,0.23652 z\" id=\"path7505\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 284.65606,613.96193 q 0,0.76995 -0.57369,1.18764 -0.57368,0.41768 -1.61034,0.41768 -1.09707,0 -1.71101,-0.34723 v -0.77498 q 0.39756,0.20129 0.85046,0.31704 0.45795,0.11573 0.88067,0.11573 0.65421,0 1.00647,-0.20632 0.35227,-0.21136 0.35227,-0.63911 0,-0.32207 -0.28181,-0.54853 -0.27679,-0.23149 -1.087,-0.54349 -0.76994,-0.28684 -1.09705,-0.4982 -0.32207,-0.2164 -0.48311,-0.48814 -0.156,-0.27175 -0.156,-0.64917 0,-0.67434 0.54854,-1.06183 0.54852,-0.39252 1.50466,-0.39252 0.89073,0 1.7412,0.36232 l -0.29691,0.67937 q -0.83035,-0.3422 -1.50468,-0.3422 -0.59381,0 -0.89575,0.1862 -0.30195,0.1862 -0.30195,0.5133 0,0.22142 0.11067,0.37742 0.11573,0.15601 0.36735,0.29692 0.25162,0.14091 0.96622,0.40761 0.9813,0.35731 1.3235,0.71963 0.34724,0.36233 0.34724,0.91086 z\" id=\"path7507\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 288.58136,615.56725 q -1.22287,0 -1.93242,-0.74479 -0.70453,-0.74478 -0.70453,-2.0683 0,-1.33357 0.65419,-2.11862 0.65924,-0.78504 1.76636,-0.78504 1.03666,0 1.64054,0.6844 0.60389,0.67936 0.60389,1.79654 v 0.5284 h -3.79943 q 0.0252,0.97125 0.48815,1.47448 0.468,0.50324 1.31344,0.50324 0.89073,0 1.76132,-0.3724 v 0.7448 q -0.44285,0.19122 -0.84041,0.27174 -0.39252,0.0856 -0.9511,0.0856 z m -0.22647,-5.01726 q -0.66426,0 -1.06182,0.43279 -0.39252,0.43278 -0.46297,1.19769 h 2.88354 q 0,-0.79008 -0.35227,-1.20776 -0.35227,-0.42272 -1.00648,-0.42272 z\" id=\"path7509\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 295.73575,614.72685 h -0.0453 q -0.57873,0.8404 -1.73113,0.8404 -1.08196,0 -1.68585,-0.73976 -0.59884,-0.73976 -0.59884,-2.10352 0,-1.36377 0.60388,-2.11862 0.60388,-0.75485 1.68081,-0.75485 1.12221,0 1.72106,0.81524 h 0.0655 l -0.0352,-0.39756 -0.0201,-0.38749 v -2.24442 h 0.83536 v 7.83032 h -0.67936 z m -1.67073,0.14091 q 0.8555,0 1.23796,-0.46299 0.38749,-0.468 0.38749,-1.50466 v -0.17614 q 0,-1.17254 -0.39253,-1.67074 -0.38749,-0.50324 -1.24298,-0.50324 -0.73473,0 -1.12725,0.5737 -0.38749,0.56865 -0.38749,1.61034 0,1.0568 0.38749,1.59526 0.38749,0.53847 1.13731,0.53847 z\" id=\"path7511\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 300.6925,615.46659 v -7.35728 h 0.85549 v 6.58231 h 3.24587 v 0.77497 z\" id=\"path7513\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 307.13243,615.46659 h -0.83537 v -5.51545 h 0.83537 z m -0.90582,-7.01006 q 0,-0.28684 0.1409,-0.41768 0.14091,-0.13588 0.35227,-0.13588 0.20129,0 0.34723,0.13588 0.14594,0.13587 0.14594,0.41768 0,0.28181 -0.14594,0.42272 -0.14594,0.13588 -0.34723,0.13588 -0.21136,0 -0.35227,-0.13588 -0.1409,-0.14091 -0.1409,-0.42272 z\" id=\"path7515\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 312.35933,615.46659 v -3.56792 q 0,-0.67434 -0.30698,-1.00648 -0.30697,-0.33213 -0.96118,-0.33213 -0.86556,0 -1.26816,0.46801 -0.40258,0.468 -0.40258,1.54493 v 2.89359 h -0.83537 v -5.51545 h 0.67937 l 0.13586,0.75485 h 0.0403 q 0.25665,-0.40761 0.71962,-0.62904 0.46298,-0.22645 1.03164,-0.22645 0.9964,0 1.49964,0.48311 0.50324,0.47806 0.50324,1.53486 v 3.59812 z\" id=\"path7517\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 315.10036,609.95114 v 3.57801 q 0,0.67433 0.30697,1.00646 0.30697,0.33215 0.96117,0.33215 0.86557,0 1.26313,-0.47306 0.40259,-0.47303 0.40259,-1.54493 v -2.89863 h 0.83537 v 5.51545 h -0.68944 l -0.1208,-0.73974 h -0.0453 q -0.25665,0.40761 -0.71459,0.62401 -0.45292,0.21639 -1.03666,0.21639 -1.00648,0 -1.50972,-0.47808 -0.4982,-0.47807 -0.4982,-1.52982 v -3.60821 z\" id=\"path7519\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 321.3741,612.64346 -1.91733,-2.69232 h 0.95112 l 1.45435,2.1136 1.44931,-2.1136 h 0.94105 l -1.91733,2.69232 2.01799,2.82313 h -0.9461 l -1.54492,-2.23435 -1.56003,2.23435 h -0.94608 z\" id=\"path7521\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 237.18879,624.72781 q 0,1.34868 -0.67937,2.10856 -0.67937,0.75486 -1.87706,0.75486 -0.73976,0 -1.31345,-0.34724 -0.57369,-0.34722 -0.88569,-0.99641 -0.31201,-0.64917 -0.31201,-1.51977 0,-1.34866 0.67434,-2.09849 0.67433,-0.75485 1.87204,-0.75485 1.15743,0 1.83681,0.76996 0.68439,0.76994 0.68439,2.08338 z m -4.20201,0 q 0,1.0568 0.42272,1.61036 0.42272,0.55356 1.24298,0.55356 0.82028,0 1.243,-0.54852 0.42774,-0.55356 0.42774,-1.6154 0,-1.05176 -0.42774,-1.59525 -0.42272,-0.54853 -1.25307,-0.54853 -0.82026,0 -1.23795,0.53847 -0.41768,0.53846 -0.41768,1.60531 z\" id=\"path7524\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 240.67461,621.87447 q 0.36736,0 0.65924,0.0604 l -0.11573,0.77499 q -0.3422,-0.0755 -0.60388,-0.0755 -0.66931,0 -1.14739,0.54349 -0.47303,0.54349 -0.47303,1.35371 v 2.95901 h -0.83538 v -5.51545 h 0.68944 l 0.0956,1.02156 h 0.0403 q 0.30699,-0.53845 0.73976,-0.83033 0.43278,-0.29188 0.95111,-0.29188 z\" id=\"path7526\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 245.42665,624.43091 v 3.05967 h -0.85549 v -7.3573 h 2.01797 q 1.3537,0 1.99784,0.51833 0.64918,0.51833 0.64918,1.56003 0,1.45939 -1.47952,1.97268 l 1.99785,3.30626 h -1.0115 l -1.78146,-3.05967 z m 0,-0.73472 h 1.17255 q 0.90582,0 1.32854,-0.3573 0.42271,-0.36233 0.42271,-1.08195 0,-0.72969 -0.43278,-1.05177 -0.42776,-0.32207 -1.37886,-0.32207 h -1.11216 z\" id=\"path7528\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 256.67721,622.27706 q 0,1.11718 -0.76492,1.72106 -0.75989,0.59885 -2.179,0.59885 h -0.86558 v 2.89361 h -0.85549 v -7.3573 h 1.90727 q 2.75772,0 2.75772,2.14378 z m -3.8095,1.58519 h 0.76996 q 1.13731,0 1.64557,-0.36736 0.50827,-0.36735 0.50827,-1.17757 0,-0.72969 -0.47807,-1.08698 -0.47808,-0.35731 -1.48958,-0.35731 h -0.95615 z\" id=\"path7530\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 262.13213,627.49058 -2.49605,-6.52193 h -0.0403 q 0.0704,0.77498 0.0704,1.84185 v 4.68008 h -0.79008 v -7.3573 h 1.28828 l 2.32998,6.06902 h 0.0403 l 2.3501,-6.06902 h 1.27823 v 7.3573 h -0.85551 v -4.74047 q 0,-0.81525 0.0704,-1.7714 h -0.0403 l -2.51618,6.51187 z\" id=\"path7532\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 266.87259,625.11028 v -0.76492 h 2.47088 v 0.76492 z\" id=\"path7534\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 273.33393,621.88454 q 1.08698,0 1.68584,0.74478 0.60387,0.73976 0.60387,2.09849 0,1.35874 -0.60891,2.1136 -0.60388,0.74982 -1.6808,0.74982 -0.53847,0 -0.98634,-0.19627 -0.44286,-0.20129 -0.74479,-0.61394 h -0.0604 l -0.17613,0.70956 h -0.59884 v -7.83034 h 0.83537 v 1.90223 q 0,0.63911 -0.0403,1.14737 h 0.0403 q 0.58375,-0.8253 1.73113,-0.8253 z m -0.1208,0.69949 q -0.85549,0 -1.23292,0.49317 -0.37742,0.48815 -0.37742,1.65061 0,1.16248 0.38748,1.66572 0.38749,0.4982 1.24299,0.4982 0.76995,0 1.14737,-0.55859 0.37743,-0.56362 0.37743,-1.61538 0,-1.07693 -0.37743,-1.60533 -0.37742,-0.5284 -1.1675,-0.5284 z\" id=\"path7536\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 279.88961,627.49058 -0.16607,-0.78505 h -0.0403 q -0.41265,0.51833 -0.8253,0.70453 -0.40763,0.18117 -1.02157,0.18117 -0.82027,0 -1.28828,-0.42272 -0.46297,-0.42272 -0.46297,-1.20273 0,-1.67074 2.67218,-1.75126 l 0.93601,-0.0301 v -0.3422 q 0,-0.64917 -0.28181,-0.95615 -0.27677,-0.312 -0.89073,-0.312 -0.68943,0 -1.56003,0.42271 l -0.25665,-0.63911 q 0.40763,-0.22142 0.89073,-0.34722 0.48813,-0.12587 0.97628,-0.12587 0.98633,0 1.45938,0.43781 0.47807,0.43782 0.47807,1.40403 v 3.7642 z m -1.88715,-0.58879 q 0.78003,0 1.22287,-0.42774 0.44788,-0.42776 0.44788,-1.19771 v -0.4982 l -0.83537,0.0352 q -0.9964,0.0352 -1.43925,0.312 -0.43782,0.27175 -0.43782,0.85047 0,0.45292 0.27175,0.68944 0.27679,0.23652 0.76994,0.23652 z\" id=\"path7538\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 285.78593,625.9859 q 0,0.76996 -0.5737,1.18764 -0.57369,0.41769 -1.61035,0.41769 -1.09705,0 -1.711,-0.34724 v -0.77498 q 0.39756,0.20129 0.85047,0.31704 0.45794,0.11573 0.88066,0.11573 0.6542,0 1.00647,-0.20632 0.35226,-0.21136 0.35226,-0.63912 0,-0.32206 -0.28181,-0.54852 -0.27677,-0.23149 -1.08699,-0.54349 -0.76994,-0.28685 -1.09705,-0.49821 -0.32206,-0.21639 -0.4831,-0.48813 -0.156,-0.27175 -0.156,-0.64917 0,-0.67435 0.54852,-1.06183 0.54853,-0.39253 1.50467,-0.39253 0.89073,0 1.7412,0.36233 l -0.29691,0.67937 q -0.83034,-0.3422 -1.50467,-0.3422 -0.59383,0 -0.89576,0.18619 -0.30195,0.1862 -0.30195,0.51331 0,0.22142 0.11067,0.37742 0.11573,0.156 0.36736,0.29691 0.25161,0.1409 0.96621,0.40762 0.9813,0.35729 1.3235,0.71963 0.34724,0.36233 0.34724,0.91085 z\" id=\"path7540\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 289.71121,627.59123 q -1.22286,0 -1.93242,-0.7448 -0.70453,-0.74478 -0.70453,-2.06829 0,-1.33357 0.65421,-2.11862 0.65924,-0.78505 1.76635,-0.78505 1.03667,0 1.64055,0.6844 0.60387,0.67937 0.60387,1.79656 v 0.52839 h -3.79941 q 0.0252,0.97124 0.48813,1.47448 0.46801,0.50324 1.31345,0.50324 0.89072,0 1.76131,-0.3724 v 0.74479 q -0.44283,0.19122 -0.84039,0.27174 -0.39252,0.0856 -0.95112,0.0856 z m -0.22645,-5.01725 q -0.66427,0 -1.06183,0.43277 -0.39252,0.43278 -0.46297,1.1977 h 2.88353 q 0,-0.79008 -0.35227,-1.20777 -0.35225,-0.4227 -1.00646,-0.4227 z\" id=\"path7542\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 296.86564,626.75082 h -0.0453 q -0.57872,0.84041 -1.73113,0.84041 -1.08196,0 -1.68583,-0.73976 -0.59886,-0.73976 -0.59886,-2.10353 0,-1.36377 0.60388,-2.11862 0.60388,-0.75485 1.68081,-0.75485 1.12221,0 1.72106,0.81524 h 0.0655 l -0.0352,-0.39755 -0.0201,-0.38749 v -2.24443 h 0.83537 v 7.83034 h -0.67937 z m -1.67074,0.14091 q 0.85549,0 1.23796,-0.46298 0.38749,-0.46801 0.38749,-1.50467 v -0.17614 q 0,-1.17253 -0.39253,-1.67074 -0.38748,-0.50322 -1.24298,-0.50322 -0.73472,0 -1.12726,0.57368 -0.38749,0.56866 -0.38749,1.61035 0,1.0568 0.38749,1.59525 0.3875,0.53847 1.13732,0.53847 z\" id=\"path7544\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 301.82235,627.49058 v -7.3573 h 0.85551 v 6.58231 h 3.24586 v 0.77499 z\" id=\"path7546\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 308.26216,627.49058 h -0.83537 v -5.51545 h 0.83537 z m -0.90582,-7.01006 q 0,-0.28686 0.1409,-0.4177 0.14091,-0.13586 0.35227,-0.13586 0.20129,0 0.34724,0.13586 0.14593,0.13588 0.14593,0.4177 0,0.28181 -0.14593,0.42271 -0.14595,0.13587 -0.34724,0.13587 -0.21136,0 -0.35227,-0.13587 -0.1409,-0.1409 -0.1409,-0.42271 z\" id=\"path7548\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 313.48906,627.49058 v -3.56794 q 0,-0.67433 -0.30698,-1.00646 -0.30697,-0.33215 -0.96117,-0.33215 -0.86557,0 -1.26815,0.46801 -0.40259,0.46801 -0.40259,1.54493 v 2.89361 h -0.83537 v -5.51545 h 0.67936 l 0.13588,0.75485 h 0.0403 q 0.25666,-0.40763 0.71964,-0.62906 0.46297,-0.22645 1.03163,-0.22645 0.99641,0 1.49963,0.48311 0.50324,0.47808 0.50324,1.53487 v 3.59813 z\" id=\"path7550\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 316.23022,621.97513 v 3.578 q 0,0.67433 0.30698,1.00646 0.30697,0.33214 0.96117,0.33214 0.86557,0 1.26311,-0.47304 0.4026,-0.47304 0.4026,-1.54493 v -2.89863 h 0.83537 v 5.51545 h -0.68943 l -0.1208,-0.73976 h -0.0453 q -0.25665,0.40763 -0.7146,0.62401 -0.4529,0.2164 -1.03666,0.2164 -1.00646,0 -1.5097,-0.47808 -0.4982,-0.47808 -0.4982,-1.52983 v -3.60819 z\" id=\"path7552\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> <path d=\"m 322.50397,624.66742 -1.91733,-2.69229 h 0.95112 l 1.45434,2.11358 1.44932,-2.11358 h 0.94105 l -1.91733,2.69229 2.01797,2.82316 h -0.94608 l -1.54493,-2.23437 -1.56002,2.23437 h -0.94609 z\" id=\"path7554\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal';stroke-width:1.33333\" /> </g> <g aria-label=\"Yes\" transform=\"scale(1.33333)\" id=\"text3095\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal'\"> <path d=\"m 254.49795,720.9517 1.47197,-2.75899 h 0.69447 l -1.84185,3.37797 v 2.14001 h -0.64917 v -2.10981 l -1.83807,-3.40817 h 0.70201 z\" id=\"path7617\" /> <path d=\"m 259.18395,723.78618 q -0.91715,0 -1.44932,-0.55859 -0.5284,-0.5586 -0.5284,-1.55123 0,-1.00018 0.49065,-1.58897 0.49443,-0.58878 1.32477,-0.58878 0.7775,0 1.23042,0.5133 0.45291,0.50952 0.45291,1.34741 v 0.3963 h -2.84958 q 0.0189,0.72843 0.36611,1.10586 0.351,0.37743 0.98508,0.37743 0.66805,0 1.321,-0.2793 v 0.5586 q -0.33214,0.14342 -0.63031,0.20381 -0.29439,0.0642 -0.71333,0.0642 z m -0.16985,-3.76295 q -0.4982,0 -0.79637,0.32459 -0.29439,0.32458 -0.34723,0.89827 h 2.16266 q 0,-0.59256 -0.2642,-0.90582 -0.2642,-0.31704 -0.75486,-0.31704 z\" id=\"path7619\" /> <path d=\"m 264.40257,722.58219 q 0,0.57746 -0.43027,0.89072 -0.43027,0.31327 -1.20777,0.31327 -0.82279,0 -1.28325,-0.26043 v -0.58123 q 0.29817,0.15097 0.63785,0.23778 0.34346,0.0868 0.6605,0.0868 0.49066,0 0.75486,-0.15474 0.26419,-0.15852 0.26419,-0.47933 0,-0.24156 -0.21135,-0.4114 -0.20759,-0.17362 -0.81525,-0.40762 -0.57746,-0.21513 -0.82279,-0.37365 -0.24155,-0.1623 -0.36233,-0.36611 -0.117,-0.20381 -0.117,-0.48688 0,-0.50575 0.41139,-0.79637 0.4114,-0.29439 1.12851,-0.29439 0.66805,0 1.3059,0.27174 l -0.22268,0.50953 q -0.62276,-0.25665 -1.12851,-0.25665 -0.44536,0 -0.67182,0.13965 -0.22646,0.13965 -0.22646,0.38497 0,0.16607 0.083,0.28307 0.0868,0.11701 0.27552,0.22269 0.18871,0.10568 0.72466,0.30571 0.73598,0.26797 0.99263,0.53972 0.26043,0.27175 0.26043,0.68315 z\" id=\"path7621\" /> </g> <g aria-label=\"No\" transform=\"scale(1.33333)\" id=\"text3101\" style=\"font-size:7.72971px;font-family:'Open Sans';-inkscape-font-specification:'Open Sans, Normal'\"> <path d=\"m 387.71585,723.71069 h -0.73221 l -3.01564,-4.63103 h -0.0302 q 0.0604,0.81524 0.0604,1.49461 v 3.13642 h -0.59256 v -5.51798 h 0.72466 l 3.0081,4.61216 h 0.0302 q -0.008,-0.10191 -0.034,-0.65295 -0.0264,-0.55482 -0.0189,-0.7926 v -3.16661 h 0.60011 z\" id=\"path7624\" /> <path d=\"m 392.46264,721.63862 q 0,1.0115 -0.50953,1.58142 -0.50952,0.56614 -1.4078,0.56614 -0.55482,0 -0.98509,-0.26043 -0.43026,-0.26042 -0.66427,-0.7473 -0.234,-0.48688 -0.234,-1.13983 0,-1.01151 0.50575,-1.57387 0.50575,-0.56614 1.40403,-0.56614 0.86808,0 1.37761,0.57746 0.5133,0.57746 0.5133,1.56255 z m -3.15152,0 q 0,0.79259 0.31704,1.20776 0.31704,0.41517 0.93225,0.41517 0.6152,0 0.93224,-0.41139 0.32081,-0.41517 0.32081,-1.21154 0,-0.78883 -0.32081,-1.19645 -0.31704,-0.41139 -0.93979,-0.41139 -0.61521,0 -0.92847,0.40384 -0.31327,0.40385 -0.31327,1.204 z\" id=\"path7626\" /> </g> </svg> </ins>"}
{"_id":"q-en-website-5d279b8c28073f6f6ba190b908cc0c20c1974b7bbabbfedf3edfa17988d24861","text":"<!--more--> <!-- <del> [Pod Priority](/docs/concepts/configuration/pod-priority-preemption/#pod-priority) gives the ability to set scheduling priority of a Pod to be higher and lower than other Pods — an important feature for production clusters workload. </del> <ins> [Pod Priority](/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority) gives the ability to set scheduling priority of a Pod to be higher and lower than other Pods — an important feature for production clusters workload. </ins> --> <del> [Pod 优先级](/zh/docs/concepts/configuration/pod-priority-preemption/#pod-priority) </del> <ins> [Pod 优先级](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority) </ins> 允许用户为 Pod 设置高于或低于其他 Pod 的优先级 -- 这对于生产集群 工作负载而言是一个重要的特性。"}
{"_id":"q-en-website-5d80c943e9f392b79f86339eb517f56b112d1b5cf9a149ba9c692d2eaf21418e","text":"<ins> --- title: Container Environment content_type: concept weight: 20 --- <!-- overview --> Questa pagina descrive le risorse disponibili nei Container eseguiti in Kubernetes. <!-- body --> ## Container environment Quando si esegue un Container in Kubernetes, le seguenti risorse sono rese disponibili: * Un filesystem, composto dal file system dell'[image](/docs/concepts/containers/images/) e da uno o più [volumes](/docs/concepts/storage/volumes/). * Una serie di informazioni sul Container stesso. * Una serie di informazioni sugli oggetti nel cluster. ### Informazioni sul Container L' *hostname* di un Container è il nome del Pod all'interno del quale è eseguito il Container. È consultabile tramite il comando `hostname` o tramite la funzione [`gethostname`](http://man7.org/linux/man-pages/man2/gethostname.2.html) disponibile in libc. Il nome del Pod e il namespace possono essere resi disponibili come environment variables attraverso l'uso delle [downward API](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/). Gli utenti possono aggiungere altre environment variables nella definizione del Pod; anche queste saranno disponibili nel Container come tutte le altre environment variables definite staticamente nella Docker image. ### Informazioni sul cluster Al momento della creazione del Container è generata una serie di environment variables con la lista di servizi in esecuzione nel cluster. Queste environment variables rispettano la sintassi dei Docker links. Per un servizio chiamato *foo* che è in esecuzione in un Container di nome *bar*, le seguenti variabili sono generate: ```shell FOO_SERVICE_HOST=<host su cui il servizio è attivo> FOO_SERVICE_PORT=<porta su cui il servizio è pubblicato> ``` I servizi hanno un indirizzo IP dedicato e sono disponibili nei Container anche via DNS se il [DNS addon](http://releases.k8s.io/{{< param \"githubbranch\" >}}/cluster/addons/dns/) è installato nel cluster. ## {{% heading \"whatsnext\" %}} * Approfondisci [Container lifecycle hooks](/docs/concepts/containers/container-lifecycle-hooks/). * Esegui un tutorial su come [definire degli handlers per i Container lifecycle events](/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/). </ins>"}
{"_id":"q-en-website-5df4e3cd07917b865b93c28205b7cdf1eeb7423f4d02702036ac679ca2678e89","text":"## Memory QoS with cgroup v2 <del> {{< feature-state feature-gate-name=\"MemoryQoS\" >}} </del> <ins> {{< feature-state feature_gate_name=\"MemoryQoS\" >}} </ins> Memory QoS uses the memory controller of cgroup v2 to guarantee memory resources in Kubernetes. Memory requests and limits of containers in pod are used to set specific interfaces `memory.min`"}
{"_id":"q-en-website-5eb9ec7db4d6db503bd94e0ddea3f69cb30b65d7a11570eb2e0324271492512d","text":"- The ConfigMap parameters for the kube-proxy cannot all be validated and verified on startup.  For example, if your operating system doesn't allow you to run iptables commands, the standard kernel kube-proxy implementation will not work.  Likewise, if you have an operating system which doesn't support `netsh`, it will not run in Windows userspace mode. ### User space proxy mode {#proxy-mode-userspace} <ins> {{< feature-state for_k8s_version=\"v1.23\" state=\"deprecated\" >}} </ins> In this (legacy) mode, kube-proxy watches the Kubernetes control plane for the addition and removal of Service and Endpoint objects. For each Service it opens a"}
{"_id":"q-en-website-5ee860e3eb5050a6ab172524742abd322c98c4e091c2e7a9977219f488c1f4f5","text":"<ins> --- title: Gateway API content_type: concept description: >- 网关（Gateway）API 是一组 API 类别，可提供动态基础设施配置和高级流量路由。 weight: 55 --- <!-- title: Gateway API content_type: concept description: >- Gateway API is a family of API kinds that provide dynamic infrastructure provisioning and advanced traffic routing. weight: 55 --> <!-- overview --> <!-- Make network services available by using an extensible, role-oriented, protocol-aware configuration mechanism. [Gateway API](https://gateway-api.sigs.k8s.io/) is an {{<glossary_tooltip text=\"add-on\" term_id=\"addons\">}} containing API [kinds](https://gateway-api.sigs.k8s.io/references/spec/) that provide dynamic infrastructure provisioning and advanced traffic routing. --> [Gateway API](https://gateway-api.sigs.k8s.io/) 通过使用可扩展的、角色导向的、 协议感知的配置机制来提供网络服务。它是一个{{<glossary_tooltip text=\"附加组件\" term_id=\"addons\">}}， 包含可提供动态基础设施配置和高级流量路由的 API [类别](https://gateway-api.sigs.k8s.io/references/spec/)。 <!-- body --> <!-- ## Design principles The following principles shaped the design and architecture of Gateway API: --> ## 设计原则 {#design-principles} Gateway API 的设计和架构遵从以下原则： <!-- * __Role-oriented:__ Gateway API kinds are modeled after organizational roles that are responsible for managing Kubernetes service networking: * __Infrastructure Provider:__ Manages infrastructure that allows multiple isolated clusters to serve multiple tenants, e.g. a cloud provider. * __Cluster Operator:__ Manages clusters and is typically concerned with policies, network access, application permissions, etc. * __Application Developer:__ Manages an application running in a cluster and is typically concerned with application-level configuration and [Service](/docs/concepts/services-networking/service/) composition. --> * **角色导向：** Gateway API 类别是基于负责管理 Kubernetes 服务网络的组织角色建模的： * **基础设施提供者：** 管理使用多个独立集群为多个租户提供服务的基础设施，例如，云提供商。 * **集群操作员：** 管理集群，通常关注策略、网络访问、应用程序权限等。 * **应用程序开发人员：** 管理在集群中运行的应用程序，通常关注应用程序级配置和 [Service](/zh-cn/docs/concepts/services-networking/service/) 组合。 <!-- * __Portable:__ Gateway API specifications are defined as [custom resources](/docs/concepts/extend-kubernetes/api-extension/custom-resources) and are supported by many [implementations](https://gateway-api.sigs.k8s.io/implementations/). * __Expressive:__ Gateway API kinds support functionality for common traffic routing use cases such as header-based matching, traffic weighting, and others that were only possible in [Ingress](/docs/concepts/services-networking/ingress/) by using custom annotations. * __Extensible:__ Gateway allows for custom resources to be linked at various layers of the API. This makes granular customization possible at the appropriate places within the API structure. --> * **可移植：** Gateway API 规范用[自定义资源](/zh-cn/docs/concepts/extend-kubernetes/api-extension/custom-resources)来定义， 并受到许多[实现](https://gateway-api.sigs.k8s.io/implementations/)的支持。 * **表达能力强：** Gateway API 类别支持常见流量路由场景的功能，例如基于标头的匹配、流量加权以及其他只能在 [Ingress](/zh-cn/docs/concepts/services-networking/ingress/) 中使用自定义注解才能实现的功能。 * **可扩展的：** Gateway 允许在 API 的各个层链接自定义资源。这使得在 API 结构内的适当位置进行精细定制成为可能。 <!-- ## Resource model Gateway API has three stable API kinds: --> ## 资源模型 {#resource-model} Gateway API 具有三种稳定的 API 类别： <!-- * __GatewayClass:__ Defines a set of gateways with common configuration and managed by a controller that implements the class. * __Gateway:__ Defines an instance of traffic handling infrastructure, such as cloud load balancer. * __HTTPRoute:__ Defines HTTP-specific rules for mapping traffic from a Gateway listener to a representation of backend network endpoints. These endpoints are often represented as a {{<glossary_tooltip text=\"Service\" term_id=\"service\">}}. --> * **GatewayClass：** 定义一组具有配置相同的网关，由实现该类的控制器管理。 * **Gateway：** 定义流量处理基础设施（例如云负载均衡器）的一个实例。 * **HTTPRoute：** 定义特定于 HTTP 的规则，用于将流量从网关监听器映射到后端网络端点的表示。 这些端点通常表示为 {{<glossary_tooltip text=\"Service\" term_id=\"service\">}}。 <!-- Gateway API is organized into different API kinds that have interdependent relationships to support the role-oriented nature of organizations. A Gateway object is associated with exactly one GatewayClass; the GatewayClass describes the gateway controller responsible for managing Gateways of this class. One or more route kinds such as HTTPRoute, are then associated to Gateways. A Gateway can filter the routes that may be attached to its `listeners`, forming a bidirectional trust model with routes. --> Gateway API 被组织成不同的 API 类别，这些 API 类别具有相互依赖的关系，以支持组织中角色导向的特点。 一个 Gateway 对象只能与一个 GatewayClass 相关联；GatewayClass 描述负责管理此类 Gateway 的网关控制器。 各个（可以是多个）路由类别（例如 HTTPRoute）可以关联到此 Gateway 对象。 Gateway 可以对能够挂接到其 `listeners` 的路由进行过滤，从而与路由形成双向信任模型。 <!-- The following figure illustrates the relationships of the three stable Gateway API kinds: {{< figure src=\"/docs/images/gateway-kind-relationships.svg\" alt=\"A figure illustrating the relationships of the three stable Gateway API kinds\" class=\"diagram-medium\" >}} --> 下图说明这三个稳定的 Gateway API 类别之间的关系： {{< figure src=\"/docs/images/gateway-kind-relationships.svg\" alt=\"此图呈现的是三个稳定的 Gateway API 类别之间的关系\" class=\"diagram-medium\" >}} <!-- ### GatewayClass {#api-kind-gateway-class} Gateways can be implemented by different controllers, often with different configurations. A Gateway must reference a GatewayClass that contains the name of the controller that implements the class. A minimal GatewayClass example: --> ### GatewayClass {#api-kind-gateway-class} Gateway 可以由不同的控制器实现，通常具有不同的配置。 Gateway 必须引用某 GatewayClass，而后者中包含实现该类的控制器的名称。 下面是一个最精简的 GatewayClass 示例： ```yaml apiVersion: gateway.networking.k8s.io/v1 kind: GatewayClass metadata: name: example-class spec: controllerName: example.com/gateway-controller ``` <!-- In this example, a controller that has implemented Gateway API is configured to manage GatewayClasses with the controller name `example.com/gateway-controller`. Gateways of this class will be managed by the implementation's controller. See the [GatewayClass](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.GatewayClass) reference for a full definition of this API kind. --> 在此示例中，一个实现了 Gateway API 的控制器被配置为管理某些 GatewayClass 对象， 这些对象的控制器名为 `example.com/gateway-controller`。 归属于此类的 Gateway 对象将由此实现的控制器来管理。 有关此 API 类别的完整定义，请参阅 [GatewayClass](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.GatewayClass)。 <!-- ### Gateway {#api-kind-gateway} A Gateway describes an instance of traffic handling infrastructure. It defines a network endpoint that can be used for processing traffic, i.e. filtering, balancing, splitting, etc. for backends such as a Service. For example, a Gateway may represent a cloud load balancer or an in-cluster proxy server that is configured to accept HTTP traffic. A minimal Gateway resource example: --> ### Gateway {#api-kind-gateway} Gateway 用来描述流量处理基础设施的一个实例。Gateway 定义了一个网络端点，该端点可用于处理流量， 即对 Service 等后端进行过滤、平衡、拆分等。 例如，Gateway 可以代表某个云负载均衡器，或配置为接受 HTTP 流量的集群内代理服务器。 下面是一个精简的 Gateway 资源示例： ```yaml apiVersion: gateway.networking.k8s.io/v1 kind: Gateway metadata: name: example-gateway spec: gatewayClassName: example-class listeners: - name: http protocol: HTTP port: 80 ``` <!-- In this example, an instance of traffic handling infrastructure is programmed to listen for HTTP traffic on port 80. Since the `addresses` field is unspecified, an address or hostname is assigned to the Gateway by the implementation's controller. This address is used as a network endpoint for processing traffic of backend network endpoints defined in routes. See the [Gateway](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.Gateway) reference for a full definition of this API kind. --> 在此示例中，流量处理基础设施的实例被编程为监听 80 端口上的 HTTP 流量。 由于未指定 `addresses` 字段，因此对应实现的控制器负责将地址或主机名设置到 Gateway 之上。 该地址用作网络端点，用于处理路由中定义的后端网络端点的流量。 有关此类 API 的完整定义，请参阅 [Gateway](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.Gateway)。 <!-- ### HTTPRoute {#api-kind-httproute} The HTTPRoute kind specifies routing behavior of HTTP requests from a Gateway listener to backend network endpoints. For a Service backend, an implementation may represent the backend network endpoint as a Service IP or the backing Endpoints of the Service. An HTTPRoute represents configuration that is applied to the underlying Gateway implementation. For example, defining a new HTTPRoute may result in configuring additional traffic routes in a cloud load balancer or in-cluster proxy server. A minimal HTTPRoute example: --> ### HTTPRoute {#api-kind-httproute} HTTPRoute 类别指定从 Gateway 监听器到后端网络端点的 HTTP 请求的路由行为。 对于服务后端，实现可以将后端网络端点表示为服务 IP 或服务的支持端点。 HTTPRoute 表示将被应用到下层 Gateway 实现的配置。 例如，定义新的 HTTPRoute 可能会导致在云负载均衡器或集群内代理服务器中配置额外的流量路由。 下面是一个最精简的 HTTPRoute 示例： ```yaml apiVersion: gateway.networking.k8s.io/v1 kind: HTTPRoute metadata: name: example-httproute spec: parentRefs: - name: example-gateway hostnames: - \"www.example.com\" rules: - matches: - path: type: PathPrefix value: /login backendRefs: - name: example-svc port: 8080 ``` <!-- In this example, HTTP traffic from Gateway `example-gateway` with the Host: header set to `www.example.com` and the request path specified as `/login` will be routed to Service `example-svc` on port `8080`. See the [HTTPRoute](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.HTTPRoute) reference for a full definition of this API kind. --> 在此示例中，来自 Gateway `example-gateway` 的 HTTP 流量， 如果 Host 的标头设置为 `www.example.com` 且请求路径指定为 `/login`， 将被路由到 Service `example-svc` 的 `8080` 端口。 有关此类 API 的完整定义，请参阅 [HTTPRoute](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.HTTPRoute)。 <!-- ## Request flow Here is a simple example of HTTP traffic being routed to a Service by using a Gateway and an HTTPRoute: {{< figure src=\"/docs/images/gateway-request-flow.svg\" alt=\"A diagram that provides an example of HTTP traffic being routed to a Service by using a Gateway and an HTTPRoute\" class=\"diagram-medium\" >}} In this example, the request flow for a Gateway implemented as a reverse proxy is: --> ## 请求数据流 {#request-flow} 以下是使用 Gateway 和 HTTPRoute 将 HTTP 流量路由到服务的简单示例： {{< figure src=\"/docs/images/gateway-request-flow.svg\" alt=\"此图为使用 Gateway 和 HTTPRoute 将 HTTP 流量路由到服务的示例\" class=\"diagram-medium\" >}} 在此示例中，实现为反向代理的 Gateway 的请求数据流如下： <!-- 1. The client starts to prepare an HTTP request for the URL `http://www.example.com` 2. The client's DNS resolver queries for the destination name and learns a mapping to one or more IP addresses associated with the Gateway. 3. The client sends a request to the Gateway IP address; the reverse proxy receives the HTTP request and uses the Host: header to match a configuration that was derived from the Gateway and attached HTTPRoute. 4. Optionally, the reverse proxy can perform request header and/or path matching based on match rules of the HTTPRoute. 5. Optionally, the reverse proxy can modify the request; for example, to add or remove headers, based on filter rules of the HTTPRoute. 6. Lastly, the reverse proxy forwards the request to one or more backends. --> 1. 客户端开始准备 URL 为 `http://www.example.com` 的 HTTP 请求 2. 客户端的 DNS 解析器查询目标名称并了解与 Gateway 关联的一个或多个 IP 地址的映射。 3. 客户端向 Gateway IP 地址发送请求；反向代理接收 HTTP 请求并使用 Host: 标头来匹配基于 Gateway 和附加的 HTTPRoute 所获得的配置。 4. 可选的，反向代理可以根据 HTTPRoute 的匹配规则进行请求头和（或）路径匹配。 5. 可选地，反向代理可以修改请求；例如，根据 HTTPRoute 的过滤规则添加或删除标头。 6. 最后，反向代理将请求转发到一个或多个后端。 <!-- ## Conformance Gateway API covers a broad set of features and is widely implemented. This combination requires clear conformance definitions and tests to ensure that the API provides a consistent experience wherever it is used. See the [conformance](https://gateway-api.sigs.k8s.io/concepts/conformance/) documentation to understand details such as release channels, support levels, and running conformance tests. --> ## 标准合规性 {#conformance} Gateway API 涵盖广泛的功能并得到广泛实现。 这种组合需要明确的标准合规性定义和测试，以确保 API 在任何地方使用时都能提供一致的体验。 请参阅[合规性](https://gateway-api.sigs.k8s.io/concepts/conformance/)相关的文档， 以了解发布渠道、支持级别和运行合规性测试等详细信息。 <!-- ## Migrating from Ingress Gateway API is the successor to the [Ingress](/docs/concepts/services-networking/ingress/) API. However, it does not include the Ingress kind. As a result, a one-time conversion from your existing Ingress resources to Gateway API resources is necessary. Refer to the [ingress migration](https://gateway-api.sigs.k8s.io/guides/migrating-from-ingress/#migrating-from-ingress) guide for details on migrating Ingress resources to Gateway API resources. --> ## 从 Ingress 迁移 {#migrating-from-ingress} Gateway API 是 [Ingress](/zh-cn/docs/concepts/services-networking/ingress/) API 的后继者。 但是其中不包括 Ingress 类型。因此，需要将现有 Ingress 资源一次性转换为 Gateway API 资源。 有关将 Ingress 资源迁移到 Gateway API 资源的详细信息，请参阅 [Ingress 迁移](https://gateway-api.sigs.k8s.io/guides/migration-from-ingress/#migration-from-ingress)指南。 ## {{% heading \"whatsnext\" %}} <!-- Instead of Gateway API resources being natively implemented by Kubernetes, the specifications are defined as [Custom Resources](/docs/concepts/extend-kubernetes/api-extension/custom-resources/) supported by a wide range of [implementations](https://gateway-api.sigs.k8s.io/implementations/). [Install](https://gateway-api.sigs.k8s.io/guides/#installing-gateway-api) the Gateway API CRDs or follow the installation instructions of your selected implementation. After installing an implementation, use the [Getting Started](https://gateway-api.sigs.k8s.io/guides/) guide to help you quickly start working with Gateway API. --> Gateway API 资源不是由 Kubernetes 原生实现的， 而是被定义为受广泛[实现](https://gateway-api.sigs.k8s.io/implementations/)支持的[自定义资源](/zh-cn/docs/concepts/extend-kubernetes/api-extension/custom-resources/)。 用户需要[安装](https://gateway-api.sigs.k8s.io/guides/#installing-gateway-api) Gateway API CRD 或按照所选实现的安装说明进行操作。 安装完成后，使用[入门](https://gateway-api.sigs.k8s.io/guides/)指南来帮助你快速开始使用 Gateway API。 {{< note >}} <!-- Make sure to review the documentation of your selected implementation to understand any caveats. --> 请务必查看所选实现的文档以了解可能存在的注意事项。 {{< /note >}} <!-- Refer to the [API specification](https://gateway-api.sigs.k8s.io/reference/spec/) for additional details of all Gateway API kinds. --> 有关所有 Gateway API 类型的其他详细信息，请参阅 [API 规范](https://gateway-api.sigs.k8s.io/reference/spec/)。 </ins>"}
{"_id":"q-en-website-5f5aeaafb5541d5e04d7be01b54ff946e2d606ede3a9baf330734d2627c9adae","text":"The output is similar to this: ```none <del> PriorityLevelName, ActiveQueues, IsIdle, IsQuiescing, WaitingRequests, ExecutingRequests, workload-low,      0,            true,   false,       0,               0, global-default,    0,            true,   false,       0,               0, exempt,            <none>,       <none>, <none>,      <none>,          <none>, catch-all,         0,            true,   false,       0,               0, system,            0,            true,   false,       0,               0, leader-election,   0,            true,   false,       0,               0, workload-high,     0,            true,   false,       0,               0, </del> <ins> PriorityLevelName, ActiveQueues, IsIdle, IsQuiescing, WaitingRequests, ExecutingRequests, DispatchedRequests, RejectedRequests, TimedoutRequests, CancelledRequests catch-all,         0,            true,   false,       0,               0,                 1,                  0,                0,                0 exempt,            <none>,       <none>, <none>,      <none>,          <none>,            <none>,             <none>,           <none>,           <none> global-default,    0,            true,   false,       0,               0,                 46,                 0,                0,                0 leader-election,   0,            true,   false,       0,               0,                 4,                  0,                0,                0 node-high,         0,            true,   false,       0,               0,                 34,                 0,                0,                0 system,            0,            true,   false,       0,               0,                 48,                 0,                0,                0 workload-high,     0,            true,   false,       0,               0,                 500,                0,                0,                0 workload-low,      0,            true,   false,       0,               0,                 0,                  0,                0,                0 </ins> ``` - `/debug/api_priority_and_fairness/dump_queues` - a listing of all the"}
{"_id":"q-en-website-60390ff95ad9213fba5fc03c9dd9266c5fb0804b29838637c530b515afb49c61","text":"<ins> --- title: Upgrading Linux nodes content_type: task weight: 100 --- <!-- overview --> This page explains how to upgrade a Linux Worker Nodes created with kubeadm. ## {{% heading \"prerequisites\" %}} {{< include \"task-tutorial-prereqs.md\" >}} {{< version-check >}} * Familiarize yourself with [the process for upgrading the rest of your kubeadm cluster](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade). You will want to upgrade the control plane nodes before upgrading your Linux Worker nodes. <!-- steps --> ## Upgrading worker nodes ### Upgrade kubeadm Upgrade kubeadm: {{< tabs name=\"k8s_install_kubeadm_worker_nodes\" >}} {{% tab name=\"Ubuntu, Debian or HypriotOS\" %}} ```shell # replace x in {{< skew currentVersion >}}.x-00 with the latest patch version apt-mark unhold kubeadm &&  apt-get update && apt-get install -y kubeadm={{< skew currentVersion >}}.x-00 &&  apt-mark hold kubeadm ``` {{% /tab %}} {{% tab name=\"CentOS, RHEL or Fedora\" %}} ```shell # replace x in {{< skew currentVersion >}}.x-0 with the latest patch version yum install -y kubeadm-{{< skew currentVersion >}}.x-0 --disableexcludes=kubernetes ``` {{% /tab %}} {{< /tabs >}} ### Call \"kubeadm upgrade\" - For worker nodes this upgrades the local kubelet configuration: ```shell sudo kubeadm upgrade node ``` ### Drain the node - Prepare the node for maintenance by marking it unschedulable and evicting the workloads: ```shell # replace <node-to-drain> with the name of your node you are draining kubectl drain <node-to-drain> --ignore-daemonsets ``` ### Upgrade kubelet and kubectl - Upgrade the kubelet and kubectl: {{< tabs name=\"k8s_kubelet_and_kubectl\" >}} {{% tab name=\"Ubuntu, Debian or HypriotOS\" %}} ```shell # replace x in {{< skew currentVersion >}}.x-00 with the latest patch version apt-mark unhold kubelet kubectl &&  apt-get update && apt-get install -y kubelet={{< skew currentVersion >}}.x-00 kubectl={{< skew currentVersion >}}.x-00 &&  apt-mark hold kubelet kubectl ``` {{% /tab %}} {{% tab name=\"CentOS, RHEL or Fedora\" %}} ```shell # replace x in {{< skew currentVersion >}}.x-0 with the latest patch version yum install -y kubelet-{{< skew currentVersion >}}.x-0 kubectl-{{< skew currentVersion >}}.x-0 --disableexcludes=kubernetes ``` {{% /tab %}} {{< /tabs >}} <br /> - Restart the kubelet: ```shell sudo systemctl daemon-reload sudo systemctl restart kubelet ``` ### Uncordon the node - Bring the node back online by marking it schedulable: ```shell # replace <node-to-uncordon> with the name of your node kubectl uncordon <node-to-uncordon> ``` ## {{% heading \"whatsnext\" %}} * See how to [Upgrade Windows nodes](/docs/tasks/administer-cluster/kubeadm/upgrading-windows-nodes/). </ins>  No newline at end of file"}
{"_id":"q-en-website-623cfdd1df56666e5b3341d452cc76626d73a31052aed15797b65e574d0f0e27","text":"<ins> --- title: 垃圾收集 id: garbage-collection date: 2021-07-07 full_link: /zh/docs/concepts/workloads/controllers/garbage-collection/ short_description: > Kubernetes 用于清理集群资源的各种机制的统称。 aka: tags: - fundamental - operation --- <!-- title: Garbage Collection id: garbage-collection date: 2021-07-07 full_link: /docs/concepts/workloads/controllers/garbage-collection/ short_description: > A collective term for the various mechanisms Kubernetes uses to clean up cluster resources. aka: tags: - fundamental - operation --> <!-- Garbage collection is a collective term for the various mechanisms Kubernetes uses to clean up cluster resources. --> 垃圾收集是 Kubernetes 用于清理集群资源的各种机制的统称。 <!--more--> <!-- Kubernetes uses garbage collection to clean up resources like [unused containers and images](/docs/concepts/workloads/controllers/garbage-collection/#containers-images), [failed Pods](/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection), [objects owned by the targeted resource](/docs/concepts/overview/working-with-objects/owners-dependents/), [completed Jobs](/docs/concepts/workloads/controllers/ttlafterfinished/), and resources that have expired or failed. --> Kubernetes 使用垃圾收集机制来清理资源，例如： [未使用的容器和镜像](/zh/docs/concepts/workloads/controllers/garbage-collection/#containers-images)、 [失败的 Pod](/zh/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection)、 [目标资源拥有的对象](/zh/docs/concepts/overview/working-with-objects/owners-dependents/)、 [已完成的 Job](/zh/docs/concepts/workloads/controllers/ttlafterfinished/)、 过期或出错的资源。 </ins>  No newline at end of file"}
{"_id":"q-en-website-6330740d4a4b7f06afa4a6c5b0014543abb978e385fd60d94cd38b5a66d84e7b","text":"<ins> --- layout: blog title: \"Kubernetes 旧版软件包仓库将于 2023 年 9 月 13 日被冻结\" date: 2023-08-31T15:30:00-07:00 slug: legacy-package-repository-deprecation evergreen: true --- <!-- layout: blog title: \"Kubernetes Legacy Package Repositories Will Be Frozen On September 13, 2023\" date: 2023-08-31T15:30:00-07:00 slug: legacy-package-repository-deprecation evergreen: true --> <!-- **Authors**: Bob Killen (Google), Chris Short (AWS), Jeremy Rickard (Microsoft), Marko Mudrinić (Kubermatic), Tim Bannister (The Scale Factory) --> **作者**：Bob Killen (Google), Chris Short (AWS), Jeremy Rickard (Microsoft), Marko Mudrinić (Kubermatic), Tim Bannister (The Scale Factory) **译者**：[Mengjiao Liu](https://github.com/mengjiao-liu) (DaoCloud) <!-- On August 15, 2023, the Kubernetes project announced the general availability of the community-owned package repositories for Debian and RPM packages available at `pkgs.k8s.io`. The new package repositories are replacement for the legacy Google-hosted package repositories: `apt.kubernetes.io` and `yum.kubernetes.io`. The [announcement blog post for `pkgs.k8s.io`](/blog/2023/08/15/pkgs-k8s-io-introduction/) highlighted that we will stop publishing packages to the legacy repositories in the future. --> 2023 年 8 月 15 日，Kubernetes 项目宣布社区拥有的 Debian 和 RPM 软件包仓库在 `pkgs.k8s.io` 上正式提供。新的软件包仓库将取代旧的由 Google 托管的软件包仓库：`apt.kubernetes.io` 和 `yum.kubernetes.io`。 [`pkgs.k8s.io` 的公告博客文章](/zh-cn/blog/2023/08/15/pkgs-k8s-io-introduction/)强调我们未来将停止将软件包发布到旧仓库。 <!-- Today, we're formally deprecating the legacy package repositories (`apt.kubernetes.io` and `yum.kubernetes.io`), and we're announcing our plans to freeze the contents of the repositories as of **September 13, 2023**. --> 今天，我们正式弃用旧软件包仓库（`apt.kubernetes.io` 和 `yum.kubernetes.io`）， 并且宣布我们计划在 **2023 年 9 月 13 日** 冻结仓库的内容。 <!-- Please continue reading in order to learn what does this mean for you as an user or distributor, and what steps you may need to take. --> 请继续阅读以了解这对于作为用户或分发商的你意味着什么， 以及你可能需要采取哪些步骤。 <!-- ## How does this affect me as a Kubernetes end user? This change affects users **directly installing upstream versions of Kubernetes**, either manually by following the official [installation](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/) and [upgrade](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) instructions, or by **using a Kubernetes installer** that's using packages provided by the Kubernetes project. --> ## 作为 Kubernetes 最终用户，这对我有何影响？ {#how-does-this-affect-me-as-a-kubernetes-end-user} 此更改影响**直接安装 Kubernetes 的上游版本**的用户， 无论是按照官方手动[安装](/zh-cn/docs/setup/生产环境/工具/kubeadm/install-kubeadm/) 和[升级](/zh-cn/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/)说明， 还是通过**使用 Kubernetes 安装工具**，该安装工具使用 Kubernetes 项目提供的软件包。 <!-- **This change also affects you if you run Linux on your own PC and have installed `kubectl` using the legacy package repositories**. We'll explain later on how to [check](#check-if-affected) if you're affected. --> **如果你在自己的 PC 上运行 Linux 并使用旧软件包仓库安装了 `kubectl`，则此更改也会影响你**。 我们稍后将解释如何[检查](#check-if-affected)是否你会受到影响。 <!-- If you use **fully managed** Kubernetes, for example through a service from a cloud provider, you would only be affected by this change if you also installed `kubectl` on your Linux PC using packages from the legacy repositories. Cloud providers are generally using their own Kubernetes distributions and therefore they don't use packages provided by the Kubernetes project; more importantly, if someone else is managing Kubernetes for you, then they would usually take responsibility for that check. --> 如果你使用**完全托管的** Kubernetes，例如从云提供商获取服务， 那么只有在你还使用旧仓库中的软件包在你的 Linux PC 上安装 `kubectl` 时， 你才会受到此更改的影响。云提供商通常使用他们自己的 Kubernetes 发行版， 因此他们不使用 Kubernetes 项目提供的软件包；更重要的是，如果有其他人为你管理 Kubernetes， 那么他们通常会负责该检查。 <!-- If you have a managed [control plane](/docs/concepts/overview/components/#control-plane-components) but you are responsible for **managing the nodes yourself**, and any of those nodes run Linux, you should [check](#check-if-affected) whether you are affected. --> 如果你使用的是托管的[控制平面](/zh-cn/docs/concepts/overview/components/#control-plane-components) 但你负责**自行管理节点**，并且每个节点都运行 Linux， 你应该[检查](#check-if-affected)你是否会受到影响。 <!-- If you're managing your clusters on your own by following the official installation and upgrade instructions, please follow the instructions in this blog post to migrate to the (new) community-owned package repositories. --> 如果你按照官方的安装和升级说明自己管理你的集群， 请按照本博客文章中的说明迁移到（新的）社区拥有的软件包仓库。 <!-- If you're using a Kubernetes installer that's using packages provided by the Kubernetes project, please check the installer tool's communication channels for information about what steps you need to take, and eventually if needed, follow up with maintainers to let them know about this change. --> 如果你使用的 Kubernetes 安装程序使用 Kubernetes 项目提供的软件包， 请检查安装程序工具的通信渠道，了解有关你需要采取的步骤的信息，最后如果需要， 请与维护人员联系，让他们了解此更改。 <!-- The following diagram shows who's affected by this change in a visual form (click on diagram for the larger version): {{< figure src=\"/blog/2023/08/31/legacy-package-repository-deprecation/flow.svg\" alt=\"Visual explanation of who's affected by the legacy repositories being deprecated and frozen. Textual explanation is available above this diagram.\" class=\"diagram-large\" link=\"/blog/2023/08/31/legacy-package-repository-deprecation/flow.svg\" >}} --> 下图以可视化形式显示了谁受到此更改的影响（单击图表可查看大图）： {{< figure src=\"/zh-cn/blog/2023/08/31/legacy-package-repository-deprecation/flow.svg\" alt=\"直观地解释谁受到弃用和冻结的遗留仓库的影响。图上提供了文字解释。\" class=\"diagram-large\" link=\"/zh-cn/blog/2023/08/31/legacy-package-repository-deprecation/flow.svg\" >}} <!-- ## How does this affect me as a Kubernetes distributor? If you're using the legacy repositories as part of your project (e.g. a Kubernetes installer tool), you should migrate to the community-owned repositories as soon as possible and inform your users about this change and what steps they need to take. --> ## 这对我作为 Kubernetes 分发商有何影响？  {#how-does-this-affect-me-as-a-kubernetes-distributor} 如果你将旧仓库用作项目的一部分（例如 Kubernetes 安装程序工具）， 则应尽快迁移到社区拥有的仓库，并告知用户此更改以及他们需要采取哪些步骤。 <!-- ## Timeline of changes - **15th August 2023:** Kubernetes announces a new, community-managed source for Linux software packages of Kubernetes components - **31st August 2023:** _(this announcement)_ Kubernetes formally deprecates the legacy package repositories - **13th September 2023** (approximately): Kubernetes will freeze the legacy package repositories, (`apt.kubernetes.io` and `yum.kubernetes.io`). The freeze will happen immediately following the patch releases that are scheduled for September, 2023. --> ## 变更时间表  {#timeline-of-changes} <!-- note to maintainers - the trailing whitespace is significant --> - **2023 年 8 月 15 日：** Kubernetes 宣布推出一个新的社区管理的 Kubernetes 组件 Linux 软件包源 - **2023 年 8 月 31 日：** **（本公告）** Kubernetes 正式弃用旧版软件包仓库 - **2023 年 9 月 13 日**（左右）： Kubernetes 将冻结旧软件包仓库（`apt.kubernetes.io` 和 `yum.kubernetes.io`）。 冻结将计划于 2023 年 9 月发布补丁版本后立即进行。 <!-- The Kubernetes patch releases scheduled for September 2023 (v1.28.2, v1.27.6, v1.26.9, v1.25.14) will have packages published **both** to the community-owned and the legacy repositories. --> 计划于 2023 年 9 月发布的 Kubernetes 补丁（v1.28.2、v1.27.6、v1.26.9、v1.25.14） 将把软件包发布到社区拥有的仓库和旧仓库。 <!-- We'll freeze the legacy repositories after cutting the patch releases for September which means that we'll completely stop publishing packages to the legacy repositories at that point. --> 在发布 9 月份的补丁版本后，我们将冻结旧仓库，这意味着届时我们将完全停止向旧仓库发布软件包。 <!-- For the v1.28, v1.27, v1.26, and v1.25 patch releases from October 2023 and onwards, we'll only publish packages to the new package repositories (`pkgs.k8s.io`). --> 对于 2023 年 10 月及以后的 v1.28、v1.27、v1.26 和 v1.25 补丁版本， 我们仅将软件包发布到新的软件包仓库 (`pkgs.k8s.io`)。 <!-- ### What about future minor releases? Kubernetes 1.29 and onwards will have packages published **only** to the community-owned repositories (`pkgs.k8s.io`). --> ### 未来的次要版本怎么样？  {#what-about-future-minor-releases} Kubernetes 1.29 及以后的版本将**仅**发布软件包到社区拥有的仓库（`pkgs.k8s.io`）。 <!-- ## Can I continue to use the legacy package repositories? The existing packages in the legacy repositories will be available for the foreseeable future. However, the Kubernetes project can't provide _any_ guarantees on how long is that going to be. The deprecated legacy repositories, and their contents, might be removed at any time in the future and without a further notice period. --> ## 我可以继续使用旧软件包仓库吗？ {#can-i-continue-to-use-the-legacy-package-repositories} 旧仓库中的现有软件包将在可预见的未来内保持可用。然而， Kubernetes 项目无法对这会持续多久提供**任何**保证。 已弃用的旧仓库及其内容可能会在未来随时删除，恕不另行通知。 <!-- The Kubernetes project **strongly recommends** migrating to the new community-owned repositories **as soon as possible**. --> Kubernetes 项目**强烈建议尽快**迁移到新的社区拥有的仓库。 <!-- Given that no new releases will be published to the legacy repositories **after the September 13, 2023** cut-off point, **you will not be able to upgrade to any patch or minor release made from that date onwards.** --> 鉴于**在 2023 年 9 月 13 日**截止时间点之后不会向旧仓库发布任何新版本， **你将无法升级到自该日期起发布的任何补丁或次要版本。** <!-- Whilst the project makes every effort to release secure software, there may one day be a high-severity vulnerability in Kubernetes, and consequently an important release to upgrade to. The advice we're announcing will help you be as prepared for any future security update, whether trivial or urgent. --> 尽管该项目会尽一切努力发布安全软件，但有一天 Kubernetes 可能会出现一个高危性漏洞， 因此需要升级到一个重要版本。我们所公开的建议将帮助你为未来的所有安全更新（无论是微不足道的还是紧急的）做好准备。 <!-- ## How can I check if I'm using the legacy repositories? {#check-if-affected} The steps to check if you're using the legacy repositories depend on whether you're using Debian-based distributions (Debian, Ubuntu, and more) or RPM-based distributions (CentOS, RHEL, Rocky Linux, and more) in your cluster. Run these instructions on one of your nodes in the cluster. --> ## 如何检查我是否正在使用旧仓库？ {#check-if-affected} 检查你是否使用旧仓库的步骤取决于你在集群中使用的是基于 Debian 的发行版（Debian、Ubuntu 等）还是基于 RPM 的发行版（CentOS、RHEL、Rocky Linux 等）。 在集群中的一个节点上运行以下指令。 <!-- ### Debian-based Linux distributions The repository definitions (sources) are located in `/etc/apt/sources.list` and `/etc/apt/sources.list.d/` on Debian-based distributions. Inspect these two locations and try to locate a package repository definition that looks like: --> ### 基于 Debian 的 Linux 发行版  {#debian-based-linux-distributions} 在基于 Debian 的发行版上，仓库定义（源）位于`/etc/apt/sources.list` 和 `/etc/apt/sources.list.d/`中。检查这两个位置并尝试找到如下所示的软件包仓库定义： ``` deb [signed-by=/etc/apt/keyrings/kubernetes-archive-keyring.gpg] https://apt.kubernetes.io/ kubernetes-xenial main ``` <!-- **If you find a repository definition that looks like this, you're using the legacy repository and you need to migrate.** If the repository definition uses `pkgs.k8s.io`, you're already using the community-hosted repositories and you don't need to take any action. --> **如果你发现像这样的仓库定义，则你正在使用旧仓库并且需要迁移。** 如果仓库定义使用 `pkgs.k8s.io`，则你已经在使用社区托管的仓库，无需执行任何操作。 <!-- On most systems, this repository definition should be located in `/etc/apt/sources.list.d/kubernetes.list` (as recommended by the Kubernetes documentation), but on some systems it might be in a different location. --> 在大多数系统上，此仓库定义应位于 `/etc/apt/sources.list.d/kubernetes.list` （按照 Kubernetes 文档的建议），但在某些系统上它可能位于不同的位置。 <!-- If you can't find a repository definition related to Kubernetes, it's likely that you don't use package managers to install Kubernetes and you don't need to take any action. --> 如果你找不到与 Kubernetes 相关的仓库定义， 则很可能你没有使用软件包管理器来安装 Kubernetes，因此不需要执行任何操作。 <!-- ### RPM-based Linux distributions The repository definitions are located in `/etc/yum.repos.d` if you're using the `yum` package manager, or `/etc/dnf/dnf.conf` and `/etc/dnf/repos.d/` if you're using `dnf` package manager. Inspect those locations and try to locate a package repository definition that looks like this: --> ### 基于 RPM 的 Linux 发行版  {#rpm-based-linux-distributions} 如果你使用的是 `yum` 软件包管理器，则仓库定义位于 `/etc/yum.repos.d`，或者 `/etc/dnf/dnf.conf` 和 `/etc/dnf/repos.d/` 如果你使用的是 `dnf` 软件包管理器。检查这些位置并尝试找到如下所示的软件包仓库定义： ``` [kubernetes] name=Kubernetes baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-$basearch enabled=1 gpgcheck=1 gpgkey=https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg exclude=kubelet kubeadm kubectl ``` <!-- **If you find a repository definition that looks like this, you're using the legacy repository and you need to migrate.** If the repository definition uses `pkgs.k8s.io`, you're already using the community-hosted repositories and you don't need to take any action. --> **如果你发现像这样的仓库定义，则你正在使用旧仓库并且需要迁移。** 如果仓库定义使用 `pkgs.k8s.io`，则你已经在使用社区托管的仓库，无需执行任何操作。 <!-- On most systems, that repository definition should be located in `/etc/yum.repos.d/kubernetes.repo` (as recommended by the Kubernetes documentation), but on some systems it might be in a different location. --> 在大多数系统上，该仓库定义应位于 `/etc/yum.repos.d/kubernetes.repo` （按照 Kubernetes 文档的建议），但在某些系统上它可能位于不同的位置。 <!-- If you can't find a repository definition related to Kubernetes, it's likely that you don't use package managers to install Kubernetes and you don't need to take any action. --> 如果你找不到与 Kubernetes 相关的仓库定义，则很可能你没有使用软件包管理器来安装 Kubernetes，那么你不需要执行任何操作。 <!-- ## How can I migrate to the new community-operated repositories? For more information on how to migrate to the new community managed packages, please refer to the [announcement blog post for `pkgs.k8s.io`](/blog/2023/08/15/pkgs-k8s-io-introduction/). --> ## 我如何迁移到新的社区运营的仓库？  {#how-can-i-migrate-to-the-new-community-operated-repositories} 有关如何迁移到新的社区管理软件包的更多信息，请参阅 [`pkgs.k8s.io`的公告博客文章](/zh-cn/blog/2023/08/15/pkgs-k8s-io-introduction/) 。 <!-- ## Why is the Kubernetes project making this change? Kubernetes has been publishing packages solely to the Google-hosted repository since Kubernetes v1.5, or the past **seven** years! Following in the footsteps of migrating to our community-managed registry, `registry.k8s.io`, we are now migrating the Kubernetes package repositories to our own community-managed infrastructure. We’re thankful to Google for their continuous hosting and support all these years, but this transition marks another big milestone for the project’s goal of migrating to complete community-owned infrastructure. --> ## 为什么 Kubernetes 项目要做出这样的改变？  {#why-is-the-kubernetes-project-making-this-change} 自 Kubernetes v1.5 或过去**七**年以来，Kubernetes 一直只将软件包发布到 Google 托管的仓库！继迁移到社区管理的注册表 `registry.k8s.io` 之后， 我们现在正在将 Kubernetes 软件包仓库迁移到我们自己的社区管理的基础设施。 我们感谢 Google 这些年来持续的托管和支持， 但这一转变标志着该项目迁移到完全由社区拥有的基础设施的目标的又一个重要里程碑。 <!-- ## Is there a Kubernetes tool to help me migrate? We don't have any announcement to make about tooling there. As a Kubernetes user, you have to manually modify your configuration to use the new repositories. Automating the migration from the legacy to the community-owned repositories is technically challenging and we want to avoid any potential risks associated with this. --> ## 有 Kubernetes 工具可以帮助我迁移吗？ {#is-there-a-kubernetes-tool-to-help-me-migrate} 关于迁移工具方面，我们目前没有任何公告。作为 Kubernetes 用户， 你必须手动修改配置才能使用新仓库。自动从旧仓库迁移到社区拥有的仓库在技术上具有挑战性， 我们希望避免与此相关的任何潜在风险。 <!-- ## Acknowledgments First of all, we want to acknowledge the contributions from Alphabet. Staff at Google have provided their time; Google as a business has provided both the infrastructure to serve packages, and the security context for giving those packages trustworthy digital signatures. These have been important to the adoption and growth of Kubernetes. --> ## 致谢  {#acknowledgments} 首先，我们要感谢 Alphabet 的贡献。Google 的员工投入了他们的时间； 作为一家企业，谷歌既提供了服务于软件包的基础设施，也提供了为这些软件包提供可信数字签名的安全上下文。 这些对于 Kubernetes 的采用和成长非常重要。 <!-- Releasing software might not be glamorous but it's important. Many people within the Kubernetes contributor community have contributed to the new way that we, as a project, have for building and publishing packages. --> 发布软件可能并不那么引人注目，但很重要。Kubernetes 贡献者社区中的许多人都为我们作为一个项目构建和发布软件包的新方法做出了贡献。 <!-- And finally, we want to once again acknowledge the help from SUSE. OpenBuildService, from SUSE, is the technology that the powers the new community-managed package repositories. --> 最后，我们要再次感谢 SUSE 的帮助。SUSE 的 OpenBuildService 为新的社区管理的软件包仓库提供支持的技术。 </ins>"}
{"_id":"q-en-website-633f6251665906f2a1cdac04235de270b16af79a402255e74b120c74e9bba78f","text":"<ins> $(document).ready(function() { function setCookie(name, value, days) { let expires = \"\"; let date = new Date(); // Create a new Date object let dateToSecond = 24 * 60 * 60 * 1000; if (days) { date.setTime(date.getTime() + days * dateToSecond); // Modify the existing Date object expires = \"; expires=\" + date.toUTCString(); } document.cookie = name + \"=\" + value + expires + \"; path=/\"; } function getCookie(name) { let matches = document.cookie.match(new RegExp( \"(?:^|; )\" + name.replace(/([.$?*|{}()[]/+^])/g, '$1') + \"=([^;]*)\" )); return matches ? \"true\" : undefined; } /* Check the presence of a cookie */ let announcement = document.querySelector(\"#announcement\"); let token = `announcement_ack_${announcement.getAttribute('data-announcement-name').replace(/s/g, '_')}`; // Generate the unique token for announcement let acknowledged = getCookie(token); if (acknowledged === \"true\") { announcement.remove(); // Remove the announcement if the cookie is set } else { announcement.classList.add('display-announcement') // Display the announcement if the cookie is not set } /* Driver code to set the cookie */ let button = document.querySelector('#banner-dismiss'); button.removeAttribute('style'); button.addEventListener('click', function() { setCookie(token, \"true\", button.getAttribute('data-ttl')); // Set a cookie with time to live parameter announcement.remove(); }); }); </ins>"}
{"_id":"q-en-website-637b39c1c7ef35c3090c6367444c0f4e0c1a40d6099b86dd958afd26687d2420","text":"Add user details to your configuration file: <ins> {{< caution >}} Storing passwords in Kubernetes client config is risky. A better alternative would be to use a credential plugin and store them separately. See: [client-go credential plugins](/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins) {{< /caution >}} </ins> ```shell kubectl config --kubeconfig=config-demo set-credentials developer --client-certificate=fake-cert-file --client-key=fake-key-seefile kubectl config --kubeconfig=config-demo set-credentials experimenter --username=exp --password=some-password"}
{"_id":"q-en-website-639dea367b8ef09de28b52be732d75a781f06354d322d95c474dc5b3ecd2ba65","text":"nssm set kube-proxy DependOnService kubelet nssm start kube-proxy <del> # Register kube-proxy.exe (overlay / vxlan) </del> <ins> # kube-proxy.exeを登録する (overlay / vxlan) </ins> nssm install kube-proxy C:kkube-proxy.exe nssm set kube-proxy AppDirectory c:k nssm set kube-proxy AppParameters --v=4 --proxy-mode=kernelspace --feature-gates=\"WinOverlay=true\" --hostname-override=<hostname> --kubeconfig=c:kconfig --network-name=vxlan0 --source-vip=<source-vip> --enable-dsr=false --log-dir=<log directory> --logtostderr=false"}
{"_id":"q-en-website-6560712ed39b37103eb90523b6c38cef5a9e0917fcee487f18a432c4f3cc3849","text":"[plugin](/docs/concepts/storage/volumes/#types-of-volumes). The following broad classes of Kubernetes volume plugins are supported on Windows: <del> * [`FlexVolume plugins`](/docs/concepts/storage/volumes/#flexVolume) </del> <ins> * [`FlexVolume plugins`](/docs/concepts/storage/volumes/#flexvolume-deprecated) </ins> * Please note that FlexVolumes have been deprecated as of 1.23 * [`CSI Plugins`](/docs/concepts/storage/volumes/#csi)"}
{"_id":"q-en-website-666ddff055617ca0d22a2b9777f56bf21f88a7a74c942a865fabca723e3aac24","text":"<!-- NEW RELEASE NOTES ENTRY --> <del> # v1.19.0 </del> <ins> # v1.20.0 </ins> [문서](https://docs.k8s.io) <del> ## v1.19.0 다운로드 </del> <ins> ## v1.20.0 다운로드 </ins> 파일명 | sha512 해시 -------- | ----------- <del> [kubernetes.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes.tar.gz) | `448b941e973a519a500eb24786f6deb7eebd0e1ecb034941e382790ff69dfc2838715a222cfc53bea7b75f2c6aedc7425eded4aad69bf88773393155c737f9c0` [kubernetes-src.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-src.tar.gz) | `47d253e6eb1f6da730f4f3885e205e6bfde88ffe66d92915465108c9eaf8e3c5d1ef515f8bf804a726db057433ecd25008ecdef624ee68ad9c103d1c7a615aad` </del> <ins> [kubernetes.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes.tar.gz) | `ebfe49552bbda02807034488967b3b62bf9e3e507d56245e298c4c19090387136572c1fca789e772a5e8a19535531d01dcedb61980e42ca7b0461d3864df2c14` [kubernetes-src.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-src.tar.gz) | `bcbd67ed0bb77840828c08c6118ad0c9bf2bcda16763afaafd8731fd6ce735be654feef61e554bcc34c77c65b02a25dae565adc5e1dc49a2daaa0d115bf1efe6` </ins> ### 클라이언트 바이너리 파일명 | sha512 해시 -------- | ----------- <del> [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-client-darwin-amd64.tar.gz) | `7093a34298297e46bcd1ccb77a9c83ca93b8ccb63ce2099d3d8cd8911ccc384470ac202644843406f031c505a8960d247350a740d683d8910ca70a0b58791a1b` [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-client-linux-386.tar.gz) | `891569cff7906732a42b20b86d1bf20a9fe873f87b106e717a5c0f80728b5823c2a00c7ccea7ec368382509f095735089ddd582190bc51dcbbcef6b8ebdbd5cc` [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-client-linux-amd64.tar.gz) | `1590d4357136a71a70172e32820c4a68430d1b94cf0ac941ea17695fbe0c5440d13e26e24a2e9ebdd360c231d4cd16ffffbbe5b577c898c78f7ebdc1d8d00fa3` [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-client-linux-arm.tar.gz) | `bc0fb19fb6af47f591adc64b5a36d3dffcadc35fdfd77a4a222e037dbd2ee53fafb84f13c4e307910cfa36b3a46704063b42a14ceaad902755ec14c492ccd51d` [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-client-linux-arm64.tar.gz) | `6ff47f4fdfb3b5f2bfe18fd792fe9bfc747f06bf52de062ee803cda87ac4a98868d8e1211742e32dd443a4bdb770018bbdde704dae6abfc6d80c02bdfb4e0311` [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-client-linux-ppc64le.tar.gz) | `d8816518adc3a7fc00f996f23ff84e6782a3ebbba7ef37ba44def47b0e6506fefeeaf37d0e197cecf0deb5bd1a8f9dd1ba82af6c29a6b9d21b8e62af965b6b81` [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-client-linux-s390x.tar.gz) | `662fd4618f2b747d2b0951454b9148399f6cd25d3ca7c40457b6e02cb20df979138cad8cccd18fc8b265d9426c90828d3f0b2a6b40d9cd1a1bdc17219e35ed33` [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-client-windows-386.tar.gz) | `d90cb92eb33ecbfab7a0e3a2da60ab10fc59132e4bc9abe0a1461a13222b5016704a7cfe0bf9bcf5d4ec55f505ffbbf53162dfe570e8f210e3f68b0d3a6bf7e3` [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-client-windows-amd64.tar.gz) | `6ec32a8a62b69363a524c4f8db765ff4bd16ea7e5b0eb04aa5a667f8653eda18c357a97513d9e12f0ba1612516acb150deffb6e3608633c62b97a15b6efa7cc0` </del> <ins> [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-client-darwin-amd64.tar.gz) | `3609f6483f4244676162232b3294d7a2dc40ae5bdd86a842a05aa768f5223b8f50e1d6420fd8afb2d0ce19de06e1d38e5e5b10154ba0cb71a74233e6dc94d5a0` [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-client-linux-386.tar.gz) | `e06c08016a08137d39804383fdc33a40bb2567aa77d88a5c3fd5b9d93f5b581c635b2c4faaa718ed3bb2d120cb14fe91649ed4469ba72c3a3dda1e343db545ed` [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-client-linux-amd64.tar.gz) | `081472833601aa4fa78e79239f67833aa4efcb4efe714426cd01d4ddf6f36fbf304ef7e1f5373bff0fdff44a845f7560165c093c108bd359b5ab4189f36b1f2f` [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-client-linux-arm.tar.gz) | `037f84a2f29fe62d266cab38ac5600d058cce12cbc4851bcf062fafba796c1fbe23a0c2939cd15784854ca7cd92383e5b96a11474fc71fb614b47dbf98a477d9` [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-client-linux-arm64.tar.gz) | `275727e1796791ca3cbe52aaa713a2660404eab6209466fdc1cfa8559c9b361fe55c64c6bcecbdeba536b6d56213ddf726e58adc60f959b6f77e4017834c5622` [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-client-linux-ppc64le.tar.gz) | `7a9965293029e9fcdb2b7387467f022d2026953b8461e6c84182abf35c28b7822d2389a6d8e4d8e532d2ea5d5d67c6fee5fb6c351363cb44c599dc8800649b04` [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-client-linux-s390x.tar.gz) | `85fc449ce1980f5f030cc32e8c8e2198c1cc91a448e04b15d27debc3ca56aa85d283f44b4f4e5fed26ac96904cc12808fa3e9af3d8bf823fc928befb9950d6f5` [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-client-windows-386.tar.gz) | `4c0a27dba1077aaee943e0eb7a787239dd697e1d968e78d1933c1e60b02d5d233d58541d5beec59807a4ffe3351d5152359e11da120bf64cacb3ee29fbc242e6` [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-client-windows-amd64.tar.gz) | `29336faf7c596539b8329afbbdceeddc843162501de4afee44a40616278fa1f284d8fc48c241fc7d52c65dab70f76280cc33cec419c8c5dbc2625d9175534af8` </ins> ### 서버 바이너리 파일명 | sha512 해시 -------- | ----------- <del> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-server-linux-amd64.tar.gz) | `7c268bd58e67d3c5016f3fcc9f4b6d2da7558af5a2c708ff3baf767b39e847e3d35d4fd2fa0f640bedbfb09a445036cafbe2f04357a88dada405cfc2ded76972` [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-server-linux-arm.tar.gz) | `fcbf8d9004f1cd244a82b685abaf81f9638c3cc1373d78e705050042cfa6a004f8eed92f4721539dcd169c55b662d10416af19cff7537a8dfef802dc41b4088b` [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-server-linux-arm64.tar.gz) | `e21f54a35ff29e919e98fe81758f654ea735983d5a9d08dab9484598b116843830a86ceb5cf0a23d27b7f9aba77e5f0aa107c171a0837ba781d508ebbea76f55` [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-server-linux-ppc64le.tar.gz) | `c7014c782683f8f612c7805654b632aab4c5dce895ee8f9ef24360616e24240ce59ddf3cf27c3170df5450d8fe14fbca3fb7cddfc9b74ae37943081f0fa4b6b3` [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-server-linux-s390x.tar.gz) | `3ac2d6b273e5b650f63260aae164fc6781ad5760f63cca911f5db9652c4bf32e7e7b25728987befc6dfda89c5c56969681b75f12b17141527d4e1d12f3d41f3c` </del> <ins> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-server-linux-amd64.tar.gz) | `fb56486a55dbf7dbacb53b1aaa690bae18d33d244c72a1e2dc95fb0fcce45108c44ba79f8fa04f12383801c46813dc33d2d0eb2203035cdce1078871595e446e` [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-server-linux-arm.tar.gz) | `735ed9993071fe35b292bf06930ee3c0f889e3c7edb983195b1c8e4d7113047c12c0f8281fe71879fc2fcd871e1ee587f03b695a03c8512c873abad444997a19` [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-server-linux-arm64.tar.gz) | `ffab155531d5a9b82487ee1abf4f6ef49626ea58b2de340656a762e46cf3e0f470bdbe7821210901fe1114224957c44c1d9cc1e32efb5ee24e51fe63990785b2` [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-server-linux-ppc64le.tar.gz) | `9d5730d35c4ddfb4c5483173629fe55df35d1e535d96f02459468220ac2c97dc01b995f577432a6e4d1548b6edbfdc90828dc9c1f7cf7464481af6ae10aaf118` [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-server-linux-s390x.tar.gz) | `6e4c165306940e8b99dd6e590f8542e31aed23d2c7a6808af0357fa425cec1a57016dd66169cf2a95f8eb8ef70e1f29e2d500533aae889e2e3d9290d04ab8721` </ins> ### 노드 바이너리 파일명 | sha512 해시 -------- | ----------- <del> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-node-linux-amd64.tar.gz) | `d5e21432a4ab019f00cd1a52bbbdb00feb3db2ce96b41a58b1ee27d8847c485f5d0efe13036fd1155469d6d15f5873a5a892ecc0198f1bae1bf5b586a0129e75` [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-node-linux-arm.tar.gz) | `bd57adf060813b06be2b33439d6f60d13630c0251ef96ba473274073200ea118f5622ec31ed714cc57bd9da410655e958a7700a5742ae7e4b6406ab12fbf21f3` [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-node-linux-arm64.tar.gz) | `3ee70abc0a5cbf1ef5dde0d27055f4d17084585c36a2cf41e3fd925d206df0b583f50dc1c118472f198788b65b2c447aa40ad41646b88791659d2dfb69b3890b` [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-node-linux-ppc64le.tar.gz) | `0f4368f229c082b2a75e7089a259e487d60b20bc8edf650dd7ca0fe23c51632397c2ef24c9c6cef078c95fce70d9229a5b4ff682c34f65a44bc4be3329c8ccde` [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-node-linux-s390x.tar.gz) | `8f0b6839fc0ad51300221fa7f32134f8c687073715cc0839f7aacb21a075c66dab113369707d03e9e0e53be62ca2e1bdf04d4b26cff805ae9c7a5a4b864e3eae` [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0/kubernetes-node-windows-amd64.tar.gz) | `587651158c9999e64e06186ef2e65fe14d46ffdae28c5d8ee6261193bfe4967717f997ebe13857fa1893bbf492e1cc1f816bce86a94c6df9b7a0264848391397` </del> <ins> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-node-linux-amd64.tar.gz) | `3e6c90561dd1c27fa1dff6953c503251c36001f7e0f8eff3ec918c74ae2d9aa25917d8ac87d5b4224b8229f620b1830442e6dce3b2a497043f8497eee3705696` [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-node-linux-arm.tar.gz) | `26db385d9ae9a97a1051a638e7e3de22c4bbff389d5a419fe40d5893f9e4fa85c8b60a2bd1d370fd381b60c3ca33c5d72d4767c90898caa9dbd4df6bd116a247` [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-node-linux-arm64.tar.gz) | `5b8b63f617e248432b7eb913285a8ef8ba028255216332c05db949666c3f9e9cb9f4c393bbd68d00369bda77abf9bfa2da254a5c9fe0d79ffdad855a77a9d8ed` [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-node-linux-ppc64le.tar.gz) | `60da7715996b4865e390640525d6e98593ba3cd45c6caeea763aa5355a7f989926da54f58cc5f657f614c8134f97cd3894b899f8b467d100dca48bc22dd4ff63` [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-node-linux-s390x.tar.gz) | `9407dc55412bd04633f84fcefe3a1074f3eaa772a7cb9302242b8768d6189b75d37677a959f91130e8ad9dc590f9ba8408ba6700a0ceff6827315226dd5ee1e6` [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0/kubernetes-node-windows-amd64.tar.gz) | `9d4261af343cc330e6359582f80dbd6efb57d41f882747a94bbf47b4f93292d43dd19a86214d4944d268941622dfbc96847585e6fec15fddc4dbd93d17015fa8` </ins> <del> ## v1.18.0 이후 체인지로그 </del> <ins> ## v1.19.0 이후 변경로그(Changelog) </ins> <del> ## 새로운 소식 (주요 테마) </del> <ins> ## 새로운 소식(주요 테마) </ins> <del> ### 사용 중단 경고 </del> <ins> ### Dockershim 사용 중단(deprecation) </ins> <del> SIG API Machinery는 `kubectl` 사용자 및 API 사용자에게 표시되는 [사용 중단된 API 사용 시 경고](https://kubernetes.io/docs/reference/using-api/deprecation-policy/#rest-resources-aka-api-objects)와 클러스터 관리자에게 표시되는 메트릭을 구현하였다. 사용 중단된 API에 대한 요청은 대상 제거 릴리스 및 대체 API를 포함하는 경고와 함께 반환된다. 경고는 [어드미션 웹훅](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/#admissionreview-response-warning)에서도 반환될 수 있으며, [사용자 정의 리소스의 사용 중단된 버전](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/#version-deprecation)에 대해 지정된다. </del> <ins> Docker as an underlying runtime is being deprecated. Docker-produced images will continue to work in your cluster with all runtimes, as they always have. The Kubernetes community [has written a blog post about this in detail](https://blog.k8s.io/2020/12/02/dont-panic-kubernetes-and-docker/) with [a dedicated FAQ page for it](https://blog.k8s.io/2020/12/02/dockershim-faq/). </ins> <del> ### 영구적인 베타(beta) 회피하기 </del> <ins> ### client-go를 위한 외부 자격증명(credential) 제공자 </ins> <del> 쿠버네티스 1.20에서부터, SIG Architecture는 9개월 이내에 모든 REST API들을 베타에서 안정 버전으로 전환하는 새로운 정책을 구현한다. 새로운 정책의 이면에 있는 아이디어는 기능이 오랫동안 베타 상태로 유지되는 것을 피하기 위함이다. 일단 새로운 API가 베타 단계에 진입하면, 9개월 동안 다음 중 하나를 수행하게 된다. </del> <ins> The client-go credential plugins can now be passed in the current cluster information via the `KUBERNETES_EXEC_INFO` environment variable. Learn more about this on [client-go credential plugins documentation](https://docs.k8s.io/reference/access-authn-authz/authentication/#client-go-credential-plugins/). </ins> <del> - GA에 도달하여, 베타 지원 중단 혹은 - 새로운 베타 버전을 보유 _(및 이전 베타 지원 중단)_. </del> <ins> ### 기능 게이트(feature gate)를 통해 크론잡(CronJob) 컨트롤러 v2 활성화 가능 </ins> <del> REST API가 9개월의 카운트 다운이 끝나면, 다음 쿠버네티스 릴리스에서 해당 API 버전이 사용 중단된다. 더 자세한 내용은 [쿠버네티스 블로그](https://kubernetes.io/blog/2020/08/21/moving-forward-from-beta/)에서 확인할 수 있다. </del> <ins> An alternative implementation of `CronJob` controller is now available as an alpha feature in this release, which has experimental performance improvement by using informers instead of polling. While this will be the default behavior in the future, you can [try them in this release through a feature gate](https://docs.k8s.io/concepts/workloads/controllers/cron-jobs/). </ins> <del> ### 워크로드 및 노드 디버깅을 위한 확장된 CLI 지원 </del> <ins> ### PID 제한(PID Limits)이 안정 기능(General Availability)으로 전환 </ins> <del> SIG CLI는 `kubectl` 로 디버깅을 확장하여, 다음의 두 가지 새로운 디버깅 워크플로(workflows)를 지원한다. 복사본을 생성하여 워크로드를 디버깅하고, 호스트 네임스페이스에 컨테이너를 생성하여 노드를 디버깅한다. 이는 아래의 작업을 할 때 유용하다. - 임시(Ephemeral) 컨테이너가 활성화되지 않은 클러스터에서 디버그 컨테이너 삽입 - busybox와 같은 이미지나 `sleep 1d` 와 같은 명령어를 변경하여 쉽게 디버깅할 수 있도록, 손상된 컨테이너를 수정하여 `kubectl exec` 를 사용할 수 있는 시간 확보 - 노드의 호스트 파일시스템에서 구성 파일 검사 </del> <ins> PID Limits features are now generally available on both `SupportNodePidsLimit` (node-to-pod PID isolation) and `SupportPodPidsLimit` (ability to limit PIDs per pod), after being enabled-by-default in beta stage for a year. </ins> <del> 이러한 새로운 워크플로에는 신규 클러스터 기능이 필요하지 않으므로, `kubectl alpha debug` 를 통해 기존 클러스터로 테스트할 수 있다. `kubectl` 을 사용한 디버깅에 대해 사용자의 의견을 기대한다. 이슈를 열거나, [#sig-cli](https://kubernetes.slack.com/messages/sig-cli)를 방문하거나 기능 개선에 대한 이슈 [#1441](https://features.k8s.io/1441)에 코멘트를 남겨서 SIG CLI와 연락할 수 있다. </del> <ins> ### API 우선순위 및 공정성(API Priority and Fairness)이 베타 단계로 전환 </ins> <del> ### 구조화된 로깅 </del> <ins> Initially introduced in 1.18, Kubernetes 1.20 now enables API Priority and Fairness (APF) by default. This allows `kube-apiserver` to [categorize incoming requests by priority levels](https://docs.k8s.io/concepts/cluster-administration/flow-control/). </ins> <del> SIG Instrumentation은 로그 메시지의 구조와 쿠버네티스 오브젝트에 대한 참조를 표준화했다. 구조화된 로깅을 사용하면 로그를 더 쉽게 구문 분석, 처리, 저장, 질의 및 분석할 수 있다. klog 라이브러리의 새 메소드는 로그 메시지 구조를 강제 적용한다. </del> <ins> ### IPv4/IPv6이 작동 </ins> <del> ### 엔드포인트슬라이스(EndpointSlices)가 기본적으로 활성화 </del> <ins> IPv4/IPv6 dual-stack has been reimplemented for 1.20 to support dual-stack Services, based on user and community feedback. If your cluster has dual-stack enabled, you can create Services which can use IPv4, IPv6, or both, and you can change this setting for existing Services. Details are available in updated [IPv4/IPv6 dual-stack docs](https://docs.k8s.io/concepts/services-networking/dual-stack/), which cover the nuanced array of options. </ins> <del> 엔드포인트슬라이스는 엔드포인트(EndPoint) API에 대한 스케일 및 확장 가능한 대안을 제공하는 훌륭한 신규 API이다. 엔드포인트슬라이스는 서비스를 지원하는 파드에 대한 IP 주소, 포트, 준비성 게이트(readiness gate) 상태 및 토폴로지 정보를 추적한다. </del> <ins> We expect this implementation to progress from alpha to beta and GA in coming releases, so we’re eager to have you comment about your dual-stack experiences in [#k8s-dual-stack](https://kubernetes.slack.com/messages/k8s-dual-stack) or in [enhancements #563](https://features.k8s.io/563). </ins> <del> 쿠버네티스 1.19에서 이 기능은, 엔드포인트 대신 엔드포인트슬라이스에서 읽는 kube-proxy와 함께 기본적으로 활성화된다. 이는 대부분 눈에 띄지 않는 변경이지만, 대규모 클러스터에서는 눈에 띄게 확장성이 향상된다. 또한 토폴로지 인식 라우팅과 같은 향후 쿠버네티스 릴리스에서 중요한 신규 기능을 사용할 수 있다. </del> <ins> ### go1.15.5 </ins> <del> ### 인그레스(ingress)를 안정 기능(General Availability)으로 전환 </del> <ins> go1.15.5 has been integrated to Kubernets project as of this release, [including other infrastructure related updates on this effort](https://github.com/kubernetes/kubernetes/pull/95776). </ins> <del> SIG Network는 널리 사용되고 있는 [인그레스 API](https://kubernetes.io/ko/docs/concepts/services-networking/ingress/)를 쿠버네티스 1.19의 안정 기능으로 전환했다. 이 변경은 쿠버네티스 기여자들의 수 년간의 노력을 인정하고, 쿠버네티스의 향후 네트워킹 API에 대한 추가 작업을 위한 기반을 마련한다. </del> <ins> ### CSI 볼륨 스냅샷(CSI Volume Snapshot)이 안정 기능으로 전환 </ins> <del> ### seccomp를 안정 기능으로 전환 </del> <ins> CSI Volume Snapshot moves to GA in the 1.20 release. This feature provides a standard way to trigger volume snapshot operations in Kubernetes and allows Kubernetes users to incorporate snapshot operations in a portable manner on any Kubernetes environment regardless of supporting underlying storage providers. Additionally, these Kubernetes snapshot primitives act as basic building blocks that unlock the ability to develop advanced, enterprise grade, storage administration features for Kubernetes: including application or cluster level backup solutions. Note that snapshot support will require Kubernetes distributors to bundle the Snapshot controller, Snapshot CRDs, and validation webhook. In addition, a CSI driver supporting the snapshot functionality must also be deployed on the cluster. </ins> <del> 쿠버네티스에 대한 seccomp(보안 컴퓨팅 모드) 지원이 안정 기능(GA)로 전환되었다. 이 기능은 파드(모든 컨테이너에 적용) 또는 단일 컨테이너에 대한 시스템 호출을 제한하여 워크로드 보안을 강화하는 데 사용될 수 있다. </del> <ins> ### 비재귀적 볼륨 소유(Non-recursive Volume Ownership (FSGroup))가 베타 단계로 전환 </ins> <del> 기술적으로 이것은 일급 객체(first class)인 `seccompProfile` 필드가 파드 및 컨테이너 `securityContext` 오브젝트에 추가되었음을 의미한다. </del> <ins> By default, the `fsgroup` setting, if specified, recursively updates permissions for every file in a volume on every mount. This can make mount, and pod startup, very slow if the volume has many files. This setting enables a pod to specify a `PodFSGroupChangePolicy` that indicates that volume ownership and permissions will be changed only when permission and ownership of the root directory does not match with expected permissions on the volume. </ins> <del> ```yaml securityContext: seccompProfile: type: RuntimeDefault|Localhost|Unconfined # 셋 중 하나를 선택 localhostProfile: my-profiles/profile-allow.json # type == Localhost 일때만 필요 ``` </del> <ins> ### FSGroup를 위한 CSIDriver 정책이 베타 단계로 전환 </ins> <del> `seccomp.security.alpha.kubernetes.io/pod` 및 `container.seccomp.security.alpha.kubernetes.io/...` 어노테이션에 대한 지원은 이제 사용 중단되었으며, 쿠버네티스 v1.22.0에서 제거된다. 현재 자동 버전 차이(skew)에 대한 처리는 새로운 필드를 어노테이션으로 변환하며 그 반대의 경우도 동일하게 동작한다. 즉, 클러스터의 기존 워크로드를 변환하는데 별도의 조치가 필요하지 않다. </del> <ins> The FSGroup's CSIDriver Policy is now beta in 1.20. This allows CSIDrivers to explicitly indicate if they want Kubernetes to manage permissions and ownership for their volumes via `fsgroup`. </ins> <del> 새로운 [Kubernetes.io의 문서 페이지][seccomp-docs]에서 seccomp로 컨테이너 시스템 호출을 제한하는 방법에 대한 자세한 정보를 찾을 수 있다. </del> <ins> ### CSI 드라이버의 보안성 향상(알파) </ins> <del> [seccomp-docs]: https://kubernetes.io/docs/tutorials/clusters/seccomp/ </del> <ins> In 1.20, we introduce a new alpha feature `CSIServiceAccountToken`. This feature allows CSI drivers to impersonate the pods that they mount the volumes for. This improves the security posture in the mounting process where the volumes are ACL’ed on the pods’ service account without handing out unnecessary permissions to the CSI drivers’ service account. This feature is especially important for secret-handling CSI drivers, such as the secrets-store-csi-driver. Since these tokens can be rotated and short-lived, this feature also provides a knob for CSI drivers to receive `NodePublishVolume` RPC calls periodically with the new token. This knob is also useful when volumes are short-lived, e.g. certificates. ### 그레이스풀 노드 종료(Graceful Node Shutdown) 기능 소개(알파) </ins> <del> ### 운영용 이미지가 커뮤니티 제어로 이동 </del> <ins> The `GracefulNodeShutdown` feature is now in Alpha. This allows kubelet to be aware of node system shutdowns, enabling graceful termination of pods during a system shutdown. This feature can be [enabled through feature gate](https://docs.k8s.io/concepts/architecture/nodes/#graceful-node-shutdown). </ins> <del> 쿠버네티스 v1.19부터 쿠버네티스 컨테이너 이미지는 `{asia,eu,us}.gcr.io/k8s-artifacts-prod` 에 있는 커뮤니티 제어 기반의 스토리지 버킷에 저장된다. `k8s.gcr.io` 가상 도메인(vanity domain)이 새 버킷으로 업데이트되었다. 이는 커뮤니티 제어 하에 운영 아티팩트(production artifacts)를 가져온다. </del> <ins> ### 런타임 로그 관리(sanitation) </ins> <del> ### KubeSchedulerConfiguration를 베타로 전환 </del> <ins> Logs can now be configured to use runtime protection from leaking sensitive data. [Details for this experimental feature is available in documentation](https://docs.k8s.io/concepts/cluster-administration/system-logs/#log-sanitization). </ins> <del> SIG Scheduling은 `KubeSchedulerConfiguration` 를 베타로 전환했다. [KubeSchedulerConfiguration](https://kubernetes.io/docs/reference/scheduling/config) 기능을 사용하면 kube-scheduler의 알고리즘 및 기타 설정을 조정할 수 있다. 남은 구성을 다시 작성하지 않고도, 선택한 일정 단계에서 특정 기능(플러그인에 포함된)을 쉽게 활성화하거나 비활성화할 수 있다. 또한 단일 kube-scheduler 인스턴스는 프로파일이라고 불리는 다양한 구성을 제공한다. 파드는 `.spec.schedulerName` 필드를 통해 스케줄링하려는 프로파일을 선택할 수 있다. </del> <ins> ### 파드 리소스 메트릭 </ins> <del> ### CSI 마이그레이션 - AzureDisk 및 vSphere (베타) 인-트리(In-tree) 볼륨 플러그인 및 모든 클라우드 공급자의 의존성이 쿠버네티스 코어 밖으로 이동된다. CSI 마이그레이션 기능을 사용하면 모든 볼륨 작업을 해당 CSI 드라이버로 라우팅하여 코드가 제거된 경우에도 레거시 API를 사용하는 기존 볼륨이 계속 동작할 수 있다. 이 기능의 AzureDisk 및 vSphere 구현이 베타로 승격되었다. </del> <ins> On-demand metrics calculation is now available through `/metrics/resources`. [When enabled]( https://docs.k8s.io/concepts/cluster-administration/system-metrics#kube-scheduler-metrics), the endpoint will report the requested resources and the desired limits of all running pods. </ins> <del> ### 스토리지 용량 추적 </del> <ins> ### `RootCAConfigMap` 소개 </ins> <del> 전통적으로 쿠버네티스 스케줄러는 추가 퍼시스턴트 스토리지가 클러스터의 모든 곳에서 사용할 수 있고 그 용량이 무한하다고 가정했다. 토폴로지 제약 사항은 첫 번째 요점을 다루었지만, 남은 스토리지 용량이 새 파드를 시작하기에 충분하지 않을 수 있다는 점을 고려하지 않은 채로 파드 스케줄링이 수행되었다. 새로운 알파(alpha) 기능인 [스토리지 용량 추적](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1472-storage-capacity-tracking)은 CSI 드라이버에 API를 추가하여, 스토리지 용량을 전달하고 파드의 노드를 선택할 때 쿠버네티스 스케줄러에서 해당 정보를 사용한다. 이 기능은 용량이 더 제한된 로컬 볼륨 및 기타 볼륨 유형에 대한 동적 프로비저닝을 지원하기 위한 디딤돌 역할이다. </del> <ins> `RootCAConfigMap` graduates to Beta, seperating from `BoundServiceAccountTokenVolume`. The `kube-root-ca.crt` ConfigMap is now available to every namespace, by default. It contains the Certificate Authority bundle for verify kube-apiserver connections. </ins> <del> ### CSI 볼륨 상태 모니터링 </del> <ins> ### `kubectl debug` 이 베타 단계로 전환 </ins> <del> CSI 상태 모니터링의 알파 버전은 쿠버네티스 1.19와 함께 릴리스된다. 이 기능을 사용하면 CSI 드라이버가 기본 스토리지 시스템의 비정상적인 볼륨 조건을 쿠버네티스와 공유하여 PVC 또는 파드의 이벤트를 전달할 수 있다. 이 기능은 쿠버네티스 개별 볼륨 상태 문제를 프로그래밍 방식으로 감지하고 해결하기 위한 디딤돌 역할이다. </del> <ins> `kubectl alpha debug` graduates from alpha to beta in 1.20, becoming `kubectl debug`. `kubectl debug` provides support for common debugging workflows directly from kubectl. Troubleshooting scenarios supported in this release of `kubectl` include: Troubleshoot workloads that crash on startup by creating a copy of the pod that uses a different container image or command. Troubleshoot distroless containers by adding a new container with debugging tools, either in a new copy of the pod or using an ephemeral container. (Ephemeral containers are an alpha feature that are not enabled by default.) Troubleshoot on a node by creating a container running in the host namespaces and with access to the host’s filesystem. Note that as a new builtin command, `kubectl debug` takes priority over any `kubectl` plugin named “debug”. You will need to rename the affected plugin. Invocations using `kubectl alpha debug` are now deprecated and will be removed in a subsequent release. Update your scripts to use `kubectl debug` instead of `kubectl alpha debug`! For more information about kubectl debug, see Debugging Running Pods on the Kubernetes website, kubectl help debug, or reach out to SIG CLI by visiting #sig-cli or commenting on [enhancement #1441](https://features.k8s.io/1441). </ins> <del> ### 일반적인 임시 볼륨 </del> <ins> ### kubeadm에서 사용 중단된 플래그 삭제 </ins> <del> 쿠버네티스는 라이프사이클이 파드에 연결되어 있고 스크래치 공간(예: 기본 제공되는 \"empty dir\" 볼륨 타입)으로 사용되거나 일부 데이터를 파드에 로드(예: 기본 제공되는 컨피그맵(ConfigMap) 및 시크릿(Secret) 볼륨 유형 또는 \"CSI 인라인 볼륨\")할 수 있는 볼륨 플러그인을 제공한다. 새로운 [일반적인 임시 볼륨](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1698-generic-ephemeral-volumes) 알파 기능은 동적 프로비저닝을 지원하는 기존 스토리지 드라이버를 볼륨의 라이프사이클이 포함된 파드에 바인딩된 임시 볼륨으로 사용한다. - 예를 들어 퍼시스턴트 메모리나 해당 노드의 별도 로컬 디스크와 같은, 루트 디스크와는 다른 스크래치 스토리지를 제공하는데 사용 - 볼륨 프로비저닝을 위한 모든 스토리지클래스(StorageClass) 파라미터 지원 - 스토리지 용량 추적, 스냅샷 및 복원, 볼륨 크기 조정과 같이 퍼시스턴트볼륨클레임(PersistentVolumeClaim)에서 지원하는 모든 기능을 지원 </del> <ins> `kubeadm` applies a number of deprecations and removals of deprecated features in this release. More details are available in the Urgent Upgrade Notes and Kind / Deprecation sections. </ins> <del> ### 변경할 수 없는(immutable) 시크릿 및 컨피그맵 (베타) </del> <ins> ### 파드의 호스트네임을 FQDN으로 사용하는 것이 베타 단계로 전환 </ins> <del> 시크릿 및 컨피그맵 볼륨은 immutable로 표시될 수 있으므로, 클러스터에 시크릿 및 컨피그맵 볼륨이 많은 경우 API 서버의 로드가 크게 줄어든다. 자세한 내용은 [컨피그맵](https://kubernetes.io/ko/docs/concepts/configuration/configmap/) 및 [시크릿](https://kubernetes.io/ko/docs/concepts/configuration/secret/)을 참고한다. </del> <ins> Previously introduced in 1.19 behind a feature gate, `SetHostnameAsFQDN` is now enabled by default. More details on this behavior is available in [documentation for DNS for Services and Pods](https://docs.k8s.io/concepts/services-networking/dns-pod-service/#pod-sethostnameasfqdn-field) </ins> <del> ### 윈도우에 대한 CSI 프록시 </del> <ins> ### `TokenRequest` / `TokenRequestProjection` 이 안정 기능으로 전환 </ins> <del> 윈도우용 CSI 프록시는 1.19 릴리스와 함께 베타로 승격되었다. 이 CSI 프록시를 사용하면 윈도우의 컨테이너가 권한 있는 스토리지 작업을 수행할 수 있도록 CSI 드라이버를 윈도우에서 실행할 수 있다. 베타에서 윈도우용 CSI 프록시는 직접 연결된 디스크 및 SMB를 사용하는 스토리지 드라이버를 지원한다. </del> <ins> Service account tokens bound to pod is now a stable feature. The feature gates will be removed in 1.21 release. For more information, refer to notes below on the changelogs. </ins> <del> ### 대시보드 v2 </del> <ins> ### 런타임클래스(RuntimeClass)가 안정 기능으로 전환 </ins> <del> SIG UI는 쿠버네티스 대시보드 애드온 v2를 릴리스했다. [쿠버네티스/대시보드](https://github.com/kubernetes/dashboard/releases) 리포지터리에서 최신 릴리스를 찾을 수 있다. 쿠버네티스 대시보드에는 이제 CRD 지원, 새로운 번역 및 AngularJS의 업데이트된 버전이 포함된다. </del> <ins> The `node.k8s.io` API groups are promoted from `v1beta1` to `v1`. `v1beta1` is now deprecated and will be removed in a future release, please start using `v1`. ([#95718](https://github.com/kubernetes/kubernetes/pull/95718), [@SergeyKanzhelev](https://github.com/SergeyKanzhelev)) [SIG Apps, Auth, Node, Scheduling and Testing] </ins> <del> ### 윈도우 컨테이너 지원을 베타로 전환 </del> <ins> ### 클라우드 컨트롤러 관리자(Cloud Controller Manager)가 이제 각 클라우드 공급자를 통해서만 제공 </ins> <del> 쿠버네티스 1.18에서 처음 도입된 윈도우 컨테이너 지원이 이번 릴리스에서 베타로 전환된다. 여기에는 윈도우 서버 버전 2004에 대한 추가 지원이 포함된다(전체 버전 호환성은 [윈도우용 문서](https://kubernetes.io/docs/setup/production-environment/windows/intro-windows-in-kubernetes/#cri-containerd)에서 찾을 수 있다). SIG Windows는 이번 릴리스에 대한 몇 가지 추가 사항도 포함한다. - DSR(Direct Server Return) 모드 지원으로 많은 서비스를 효율적으로 확장 가능 - 윈도우 컨테이너가 CPU 한계를 준수 - 메트릭 및 요약 모음에 대한 성능 개선 ### 쿠버네티스 지원 기간을 1년으로 늘림 쿠버네티스 1.19부터, 쿠버네티스 마이너(minor) 릴리스에 대한 패치 릴리스를 통한 버그 수정 지원이 9개월에서 1년으로 늘었다. 2019년 초에 워킹그룹(WG) 장기 지원(LTS)에서 실시한 설문 조사에 따르면 쿠버네티스 최종 사용자의 상당 부분이 이전 9개월 지원 기간 내에 업그레이드에 실패한 것으로 보인다. 연간 지원 기간은 최종 사용자가 원하는 대로 '추가적인 기간(쿠션)'을 제공하며, 이러한 방식을 통해 연간 계획 주기와도 더 적절하게 어울린다. </del> <ins> Kubernetes will no longer ship an instance of the Cloud Controller Manager binary. Each Cloud Provider is expected to ship their own instance of this binary. Details for a Cloud Provider to create an instance of such a binary can be found under [here](https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/cloud-provider/sample). Anyone with questions on building a Cloud Controller Manager should reach out to SIG Cloud Provider. Questions about the Cloud Controller Manager on a Managed Kubernetes solution should go to the relevant Cloud Provider. Questions about the Cloud Controller Manager on a non managed solution can be brought up with SIG Cloud Provider. </ins> ## 알려진 이슈 <del> 새로운 스토리지 용량 추적 알파 기능은 WaitForFirstConsumer 볼륨 바인딩 모드 제한의 영향을 받는 것으로 알려져 있다. [#94217](https://github.com/kubernetes/kubernetes/issues/94217) </del> <ins> ### kubelet의 요약(Summary) API는 가속기(accelerator) 메트릭을 가지고 있지 않음 Currently, cadvisor_stats_provider provides AcceleratorStats but cri_stats_provider does not. As a result, when using cri_stats_provider, kubelet's Summary API does not have accelerator metrics. [There is an open work in progress to fix this](https://github.com/kubernetes/kubernetes/pull/96873). </ins> ## 긴급 업그레이드 노트 <del> ### (업그레이드 전에 반드시 읽어야 함) - 조치 필요: 코어 마스터 기본 이미지(kube-controller-manager)를 debian에서 distroless로 전환한다. 스크립트를 사용하여 Flex 볼륨 지원이 필요한 경우 필요한 패키지(bash와 같은)로 자체 이미지를 빌드하라. ([#91329](https://github.com/kubernetes/kubernetes/pull/91329), [@dims](https://github.com/dims)) [SIG Cloud Provider, Release, Storage 및 Testing] - 조치 필요: --basic-auth-file 플래그를 통한 기본 인증 지원이 제거되었다. 사용자는 유사한 기능을 위해 --token-auth-file 플래그로 마이그레이션해야 한다. ([#89069](https://github.com/kubernetes/kubernetes/pull/89069), [@enj](https://github.com/enj)) [SIG API Machinery] - Azure blob 디스크 기능(`kind`: `Shared`, `Dedicated`)이 더 이상 사용되지 않는다. `kubernetes.io/azure-disk` 스토리지 클래스에 있는 `kind`: `Managed` 를 사용해야 한다. ([#92905](https://github.com/kubernetes/kubernetes/pull/92905), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider 및 Storage] - CVE-2020-8559(Medium): 손상된 노드에서 클러스터로 권한 상승. 자세한 내용은 https://github.com/kubernetes/kubernetes/issues/92914 를 참고한다. API 서버는 더이상 업그레이드 요청에 대해 101이 아닌 응답을 프록시하지 않는다. 이로 인해 101이 아닌 응답 코드로 업그레이드 요청에 응답하는 프록시된 백엔드(확장 API 서버와 같은)가 손상될 수 있다. ([#92941](https://github.com/kubernetes/kubernetes/pull/92941), [@tallclair](https://github.com/tallclair)) [SIG API Machinery] - Kubeadm은 /var/lib/kubelet/kubeadm-flags.env에서 사용 중단된 '--cgroup-driver' 플래그를 설정하지 않으며, kubelet의 config.yaml 파일에 설정한다. /var/lib/kubelet/kubeadm-flags.env 파일이나 /etc/default/kubelet 파일에 (RPM의 경우 /etc/sysconfig/kubelet) 이 플래그가 있는 경우 제거 후에 KubeletConfiguration을 사용하여 값을 지정해야 한다. ([#90513](https://github.com/kubernetes/kubernetes/pull/90513), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle] - Kubeadm은 이제 ClusterConfiguration에서 사용자가 지정한 etcd 버전을 준수하고 올바르게 사용한다. 사용자가 ClusterConfiguration에 지정된 버전을 유지하지 않으려면, kubeadm-config 컨피그맵을 편집하고 삭제해야 한다. ([#89588](https://github.com/kubernetes/kubernetes/pull/89588), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - Kubeadm은 systemd-resolved 서비스가 활성화된 경우에도 사용자가 설정한 resolvConfg 값을 따른다. kubeadm은 더이상 /var/lib/kubelet/kubeadm-flags.env 파일에 있는 '--resolv-conf' 플래그를 설정하지 않는다. /var/lib/kubelet/kubeadm-flags.env 파일이나 /etc/default/kubelet 파일에(RPM의 경우 /etc/sysconfig/kubelet) 이 플래그가 있는 경우 제거 후에 KubeletConfiguration을 사용하여 값을 지정해야 한다. ([#90394](https://github.com/kubernetes/kubernetes/pull/90394), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle] - Kubeadm: \"kubeadm init 단계: kubelet-start\"가 \"kubeconfig\" 단계 이후인, 초기화 워크 플로의 후반부로 이동한다. 이렇게 하면 kubeadm이 KubeletConfiguration 구성 설정 파일이 생성된 후에만 kubelet을 시작하고, OpenRC와 같은 초기화 시스템이 kubelet 서비스를 크래시루프(crashloop)할 수 없는 문제가 해결된다. - 'kubeadm config upload' 명령어는 전체 GA 사용 중단 주기 후에 최종적으로 제거되었다. 만약 그래도 사용해야 할 경우, 대안으로 'kubeadm init phase upload-config'를 사용한다. ([#92610](https://github.com/kubernetes/kubernetes/pull/92610), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - kubescheduler.config.k8s.io/v1alpha2를 kubescheduler.config.k8s.io/v1beta1로 업그레이드 - `.bindTimeoutSeconds` 가 `VolumeBinding` 에 대한 플러그인 인수의 일부로 이동되었으며, [프로파일](&#35;profiles)별로 별도 구성할 수 있다. - `.extenders` 가 API 표준을 충족하도록 업데이트되었다. 다음을 참고한다. - `.extenders` 디코딩은 대소문자를 구분한다. 모든 필드가 영향을 받는다. - `.extenders[*].httpTimeout` 은 `metav1.Duration` 유형이다. - `.extenders[*].enableHttps` 가 `.extenders[*].enableHTTPS` 로 이름이 변경되었다. - `RequestedToCapacityRatio` 인수 디코딩은 대소문자를 구분한다. 모든 필드가 영향을 받는다. - `DefaultPodTopologySpread` [플러그인](&#35;scheduling-plugins)이 `SelectorSpread` 로 이름이 변경되었다. - `Unreserve` 익스텐션 포인트가 프로파일 정의에서 제거되었다. 모든 `Reserve` 플러그인은 `Unreserve` 호출을 구현한다. - `.disablePreemption` 이 제거되었다. 사용자는 \"DefaultPreemption\" PostFilter 플러그인을 비활성화하여 선점에 대해 비활성화할 수 있다. ([#91420](https://github.com/kubernetes/kubernetes/pull/91420), [@pancernik](https://github.com/pancernik)) [SIG Scheduling] ## 종류(Kind)별 변경 </del> <ins> ### (주의. 업그레이드 전에 반드시 읽어야 함) - A bug was fixed in kubelet where exec probe timeouts were not respected. This may result in unexpected behavior since the default timeout (if not specified) is `1s` which may be too small for some exec probes. Ensure that pods relying on this behavior are updated to correctly handle probe timeouts. See [configure probe](https://docs.k8s.io/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#configure-probes) section of the documentation for more details. - This change in behavior may be unexpected for some clusters and can be disabled by turning off the `ExecProbeTimeout` feature gate. This gate will be locked and removed in future releases so that exec probe timeouts are always respected. ([#94115](https://github.com/kubernetes/kubernetes/pull/94115), [@andrewsykim](https://github.com/andrewsykim)) [SIG Node and Testing] - RuntimeClass feature graduates to General Availability. Promote `node.k8s.io` API groups from `v1beta1` to `v1`. `v1beta1` is now deprecated and will be removed in a future release, please start using `v1`. ([#95718](https://github.com/kubernetes/kubernetes/pull/95718), [@SergeyKanzhelev](https://github.com/SergeyKanzhelev)) [SIG Apps, Auth, Node, Scheduling and Testing] - API priority and fairness graduated to beta. 1.19 servers with APF turned on should not be run in a multi-server cluster with 1.20+ servers. ([#96527](https://github.com/kubernetes/kubernetes/pull/96527), [@adtac](https://github.com/adtac)) [SIG API Machinery and Testing] - For CSI drivers, kubelet no longer creates the target_path for NodePublishVolume in accordance with the CSI spec. Kubelet also no longer checks if staging and target paths are mounts or corrupted. CSI drivers need to be idempotent and do any necessary mount verification. ([#88759](https://github.com/kubernetes/kubernetes/pull/88759), [@andyzhangx](https://github.com/andyzhangx)) [SIG Storage] - Kubeadm: http://git.k8s.io/enhancements/keps/sig-cluster-lifecycle/kubeadm/2067-rename-master-label-taint/README.md ([#95382](https://github.com/kubernetes/kubernetes/pull/95382), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - The label applied to control-plane nodes \"node-role.kubernetes.io/master\" is now deprecated and will be removed in a future release after a GA deprecation period. - Introduce a new label \"node-role.kubernetes.io/control-plane\" that will be applied in parallel to \"node-role.kubernetes.io/master\" until the removal of the \"node-role.kubernetes.io/master\" label. - Make \"kubeadm upgrade apply\" add the \"node-role.kubernetes.io/control-plane\" label on existing nodes that only have the \"node-role.kubernetes.io/master\" label during upgrade. - Please adapt your tooling built on top of kubeadm to use the \"node-role.kubernetes.io/control-plane\" label. - The taint applied to control-plane nodes \"node-role.kubernetes.io/master:NoSchedule\" is now deprecated and will be removed in a future release after a GA deprecation period. - Apply toleration for a new, future taint \"node-role.kubernetes.io/control-plane:NoSchedule\" to the kubeadm CoreDNS / kube-dns managed manifests. Note that this taint is not yet applied to kubeadm control-plane nodes. - Please adapt your workloads to tolerate the same future taint preemptively. - Kubeadm: improve the validation of serviceSubnet and podSubnet. ServiceSubnet has to be limited in size, due to implementation details, and the mask can not allocate more than 20 bits. PodSubnet validates against the corresponding cluster \"--node-cidr-mask-size\" of the kube-controller-manager, it fail if the values are not compatible. kubeadm no longer sets the node-mask automatically on IPv6 deployments, you must check that your IPv6 service subnet mask is compatible with the default node mask /64 or set it accordenly. Previously, for IPv6, if the podSubnet had a mask lower than /112, kubeadm calculated a node-mask to be multiple of eight and splitting the available bits to maximise the number used for nodes. ([#95723](https://github.com/kubernetes/kubernetes/pull/95723), [@aojea](https://github.com/aojea)) [SIG Cluster Lifecycle] - The deprecated flag --experimental-kustomize is now removed from kubeadm commands. Use --experimental-patches instead, which was introduced in 1.19. Migration infromation available in --help description for --exprimental-patches. ([#94871](https://github.com/kubernetes/kubernetes/pull/94871), [@neolit123](https://github.com/neolit123)) - Windows hyper-v container featuregate is deprecated in 1.20 and will be removed in 1.21 ([#95505](https://github.com/kubernetes/kubernetes/pull/95505), [@wawa0210](https://github.com/wawa0210)) [SIG Node and Windows] - The kube-apiserver ability to serve on an insecure port, deprecated since v1.10, has been removed. The insecure address flags `--address` and `--insecure-bind-address` have no effect in kube-apiserver and will be removed in v1.24. The insecure port flags `--port` and `--insecure-port` may only be set to 0 and will be removed in v1.24. ([#95856](https://github.com/kubernetes/kubernetes/pull/95856), [@knight42](https://github.com/knight42), [SIG API Machinery, Node, Testing]) - Add dual-stack Services (alpha).  This is a BREAKING CHANGE to an alpha API. It changes the dual-stack API wrt Service from a single ipFamily field to 3 fields: ipFamilyPolicy (SingleStack, PreferDualStack, RequireDualStack), ipFamilies (a list of families assigned), and clusterIPs (inclusive of clusterIP).  Most users do not need to set anything at all, defaulting will handle it for them.  Services are single-stack unless the user asks for dual-stack.  This is all gated by the \"IPv6DualStack\" feature gate. ([#91824](https://github.com/kubernetes/kubernetes/pull/91824), [@khenidak](https://github.com/khenidak)) [SIG API Machinery, Apps, CLI, Network, Node, Scheduling and Testing] - `TokenRequest` and `TokenRequestProjection` are now GA features. The following flags are required by the API server: - `--service-account-issuer`, should be set to a URL identifying the API server that will be stable over the cluster lifetime. - `--service-account-key-file`, set to one or more files containing one or more public keys used to verify tokens. - `--service-account-signing-key-file`, set to a file containing a private key to use to sign service account tokens. Can be the same file given to `kube-controller-manager` with `--service-account-private-key-file`. ([#95896](https://github.com/kubernetes/kubernetes/pull/95896), [@zshihang](https://github.com/zshihang)) [SIG API Machinery, Auth, Cluster Lifecycle] - kubeadm: make the command \"kubeadm alpha kubeconfig user\" accept a \"--config\" flag and remove the following flags: - apiserver-advertise-address / apiserver-bind-port: use either localAPIEndpoint from InitConfiguration or controlPlaneEndpoint from ClusterConfiguration. - cluster-name: use clusterName from ClusterConfiguration - cert-dir: use certificatesDir from ClusterConfiguration ([#94879](https://github.com/kubernetes/kubernetes/pull/94879), [@knight42](https://github.com/knight42)) [SIG Cluster Lifecycle] - Resolves non-deterministic behavior of the garbage collection controller when ownerReferences with incorrect data are encountered. Events with a reason of `OwnerRefInvalidNamespace` are recorded when namespace mismatches between child and owner objects are detected. The [kubectl-check-ownerreferences](https://github.com/kubernetes-sigs/kubectl-check-ownerreferences) tool can be run prior to upgrading to locate existing objects with invalid ownerReferences. - A namespaced object with an ownerReference referencing a uid of a namespaced kind which does not exist in the same namespace is now consistently treated as though that owner does not exist, and the child object is deleted. - A cluster-scoped object with an ownerReference referencing a uid of a namespaced kind is now consistently treated as though that owner is not resolvable, and the child object is ignored by the garbage collector. ([#92743](https://github.com/kubernetes/kubernetes/pull/92743), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Apps and Testing] ## 종류(Kind)별 변경 사항 </ins> ### 사용 중단 <del> - vSphere CSI 드라이버로의 vSphere 인-트리 볼륨 마이그레이션에 대한 지원이 추가되었다. 인-트리 vSphere 볼륨 플러그인은 더이상 사용되지 않으며, 향후 릴리스에서 제거된다. vSphere에 쿠버네티스를 자체 배포하는 사용자는 CSIMigration + CSIMigrationSphere 기능을 활성화하고 vSphere CSI 드라이버(https://github.com/kubernetes-sigs/vsphere-csi-driver)를 설치하여 기존 파드 및 PVC 오브젝트에 대한 중단을 방지해야 한다. 사용자는 새 볼륨에 대해 vSphere CSI 드라이버를 직접 사용하기 시작해야 한다. vSphere 볼륨용 CSI 마이그레이션 기능을 사용하려면 최소 vSphere vCenter/ESXi 버전이 7.0u1이고 최소 HW 버전이 VM 버전 15여야 한다. vSAN 원시 정책 파라미터는 인-트리 vSphere 볼륨 플러그인에서 더이상 사용되지 않으며 향후 릴리스에서 제거될 예정이다. ([#90911](https://github.com/kubernetes/kubernetes/pull/90911), [@divyenpatel](https://github.com/divyenpatel)) [SIG API Machinery, Node 및 Storage] - Apiextensions.k8s.io/v1beta1은 사용 중단되었으며, apiextensions.k8s.io/v1을 사용한다. ([#90673](https://github.com/kubernetes/kubernetes/pull/90673), [@deads2k](https://github.com/deads2k)) [SIG API Machinery] - Apiregistration.k8s.io/v1beta1은 사용 중단되었으며, apiregistration.k8s.io/v1을 사용한다. ([#90672](https://github.com/kubernetes/kubernetes/pull/90672), [@deads2k](https://github.com/deads2k)) [SIG API Machinery] - Authentication.k8s.io/v1beta1 및 authorization.k8s.io/v1beta1은 1.19에서 사용 중단되었으며, v1 level을 사용하고, 1.22에서 제거될 예정이다. ([#90458](https://github.com/kubernetes/kubernetes/pull/90458), [@deads2k](https://github.com/deads2k)) [SIG API Machinery 및 Auth] - Autoscaling/v2beta1은 사용 중단되었으며, autoscaling/v2beta2를 사용한다. ([#90463](https://github.com/kubernetes/kubernetes/pull/90463), [@deads2k](https://github.com/deads2k)) [SIG Autoscaling] - Coordination.k8s.io/v1beta1은 1.19에서 사용 중단되어, 1.22에서 제거될 예정이며, 대신 v1을 사용한다. ([#90559](https://github.com/kubernetes/kubernetes/pull/90559), [@deads2k](https://github.com/deads2k)) [SIG Scalability] - nodeExpansion CSI 호출에 볼륨 기능 및 스테이징 대상 필드가 있는지 확인해야 한다. NodeStage 및 NodePublish 간에 호출되는 NodeExpandVolume의 동작은 CSI 볼륨에 대해 사용 중단된다. CSI 드라이버는 노드 EXPAND_VOLUME 기능이 있는 경우 NodePublish 후 NodeExpandVolume 호출을 지원해야 한다. ([#86968](https://github.com/kubernetes/kubernetes/pull/86968), [@gnufied](https://github.com/gnufied)) [SIG Storage] - 기능: azure 디스크 마이그레이션이 1.19에서 베타 버전으로 변경된다. 기능 게이트 CSIMigration이 베타(기본적으로 설정되는)로 전환되며, CSIMigrationAzureDisk가 베타(AzureDisk CSI 드라이버가 설치되야 하므로 기본적으로 설정되어 있지 않은)로 전환된다. 인-트리 AzureDisk 플러그인 \"kubernetes.io/azure-disk\"는 이제 사용 중단되며, 1.23에서 제거된다. 사용자는 CSIMigration + CSIMigrationAzureDisk 기능을 사용하도록 설정하고 AzureDisk CSI 드라이버(https://github.com/kubernetes-sigs/azuredisk-csi-driver)를 설치하여 해당 시점에 기존 파드 및 PVC 오브젝트가 중단되지 않도록 해야 한다. 사용자는 모든 새 볼륨에 대해 AzureDisk CSI 드라이버를 직접 사용해야 한다. ([#90896](https://github.com/kubernetes/kubernetes/pull/90896), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider 및 Storage] - Kube-apiserver: componentstatus API가 사용 중단된다. 이 API는 etcd, kube-scheduler 및 kube-controller-manager 컴포넌트의 상태를 제공했지만, 해당 컴포넌트가 API 서버에 대해 로컬이며, kube-scheduler 및 kube-controller-manager가 보안되지 않은 상태의 엔드포인트를 노출한 경우에만 동작했다. 이 API 대신 etcd의 상태 확인은 kube-apiserver의 상태 확인에 포함되고, kube-scheduler/kube-controller-manager 상태 확인은 해당 컴포넌트의 상태 엔드포인트에 대해 직접 수행될 수 있다. ([#93570](https://github.com/kubernetes/kubernetes/pull/93570), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Apps 및 Cluster Lifecycle] - Kubeadm: `kubeadm config view` 명령은 사용 중단되며, 기능 릴리스에서 제거될 예정이다. `kubectl get cm -o yaml -n kube-system kubeadm-config` 를 사용하여 kubeadm 설정을 직접 가져와야 한다. ([#92740](https://github.com/kubernetes/kubernetes/pull/92740), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle] - Kubeadm: \"kubeadm alpha kubelet config enable-dynamic\" 명령이 사용 중단된다. 이 기능을 계속 사용하려면 k8s.io에서 \"동적 Kubelet 구성\"을 참조한다. ([#92881](https://github.com/kubernetes/kubernetes/pull/92881), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: `--experimental-kustomize` 기능이 사용 중단되며, 대신 `--experimental-patches` 기능을 사용한다. 지원되는 패치 형식은 \"kubectl patch\"와 동일하다. 디렉터리에서 파일로 읽히며, 초기화/조인/업그레이드 도중에 kubeadm 컴포넌트에 적용될 수 있다. 당분간은 정적 파드의 패치만 지원된다. ([#92017](https://github.com/kubernetes/kubernetes/pull/92017), [@neolit123](https://github.com/neolit123)) - Kubeadm: \"kubeadm alpha certs renew\" 명령어에 대해 사용 중단된 \"--use-api\"  플래그가 제거되었다. ([#90143](https://github.com/kubernetes/kubernetes/pull/90143), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - 쿠버네티스는 더이상 hyperkube 이미지 빌드를 지원하지 않는다. ([#88676](https://github.com/kubernetes/kubernetes/pull/88676), [@dims](https://github.com/dims)) [SIG Cluster Lifecycle 및 Release] - kubectl get 명령어에서 --export 플래그가 제거되었다. ([#88649](https://github.com/kubernetes/kubernetes/pull/88649), [@oke-py](https://github.com/oke-py)) [SIG CLI 및 Testing] - 스케줄러의 알파 기능인 'ResourceLimitsPriorityFunction'은 사용을 많이 하지 않아 완전히 제거되었다. ([#91883](https://github.com/kubernetes/kubernetes/pull/91883), [@SataQiu](https://github.com/SataQiu)) [SIG Scheduling 및 Testing] - Storage.k8s.io/v1beta1은 사용 중단되었으며, 대신 storage.k8s.io/v1이 사용된다. ([#90671](https://github.com/kubernetes/kubernetes/pull/90671), [@deads2k](https://github.com/deads2k)) [SIG Storage] </del> <ins> - Docker support in the kubelet is now deprecated and will be removed in a future release. The kubelet uses a module called \"dockershim\" which implements CRI support for Docker and it has seen maintenance issues in the Kubernetes community. We encourage you to evaluate moving to a container runtime that is a full-fledged implementation of CRI (v1alpha1 or v1 compliant) as they become available. ([#94624](https://github.com/kubernetes/kubernetes/pull/94624), [@dims](https://github.com/dims)) [SIG Node] - Kubeadm: deprecate self-hosting support. The experimental command \"kubeadm alpha self-hosting\" is now deprecated and will be removed in a future release. ([#95125](https://github.com/kubernetes/kubernetes/pull/95125), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: graduate the \"kubeadm alpha certs\" command to a parent command \"kubeadm certs\". The command \"kubeadm alpha certs\" is deprecated and will be removed in a future release. Please migrate. ([#94938](https://github.com/kubernetes/kubernetes/pull/94938), [@yagonobre](https://github.com/yagonobre)) [SIG Cluster Lifecycle] - Kubeadm: remove the deprecated \"kubeadm alpha kubelet config enable-dynamic\" command. To continue using the feature please defer to the guide for \"Dynamic Kubelet Configuration\" at k8s.io. This change also removes the parent command \"kubeadm alpha kubelet\" as there are no more sub-commands under it for the time being. ([#94668](https://github.com/kubernetes/kubernetes/pull/94668), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: remove the deprecated --kubelet-config flag for the command \"kubeadm upgrade node\" ([#94869](https://github.com/kubernetes/kubernetes/pull/94869), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubectl: deprecate --delete-local-data ([#95076](https://github.com/kubernetes/kubernetes/pull/95076), [@dougsland](https://github.com/dougsland)) [SIG CLI, Cloud Provider and Scalability] - Kubelet's deprecated endpoint `metrics/resource/v1alpha1` has been removed, please adopt `metrics/resource`. ([#94272](https://github.com/kubernetes/kubernetes/pull/94272), [@RainbowMango](https://github.com/RainbowMango)) [SIG Instrumentation and Node] - Removes deprecated scheduler metrics DeprecatedSchedulingDuration, DeprecatedSchedulingAlgorithmPredicateEvaluationSecondsDuration, DeprecatedSchedulingAlgorithmPriorityEvaluationSecondsDuration ([#94884](https://github.com/kubernetes/kubernetes/pull/94884), [@arghya88](https://github.com/arghya88)) [SIG Instrumentation and Scheduling] - Scheduler alpha metrics binding_duration_seconds and scheduling_algorithm_preemption_evaluation_seconds are deprecated, Both of those metrics are now covered as part of framework_extension_point_duration_seconds, the former as a PostFilter the latter and a Bind plugin. The plan is to remove both in 1.21 ([#95001](https://github.com/kubernetes/kubernetes/pull/95001), [@arghya88](https://github.com/arghya88)) [SIG Instrumentation and Scheduling] - Support 'controlplane' as a valid EgressSelection type in the EgressSelectorConfiguration API. 'Master' is deprecated and will be removed in v1.22. ([#95235](https://github.com/kubernetes/kubernetes/pull/95235), [@andrewsykim](https://github.com/andrewsykim)) [SIG API Machinery] - The v1alpha1 PodPreset API and admission plugin has been removed with no built-in replacement. Admission webhooks can be used to modify pods on creation. ([#94090](https://github.com/kubernetes/kubernetes/pull/94090), [@deads2k](https://github.com/deads2k)) [SIG API Machinery, Apps, CLI, Cloud Provider, Scalability and Testing] </ins> ### API 변경 <del> - CSI드라이버(CSIDriver)가 볼륨 소유권 및 권한 수정을 지원하는지 여부를 지정할 수 있도록, 새로운 알파 수준의 필드인, `SupportsFsGroup` 가 도입되었다. 이 필드를 사용하려면 `CSIVolumeSupportFSGroup` 기능 게이트를 활성화해야 한다. ([#92001](https://github.com/kubernetes/kubernetes/pull/92001), [@huffmanca](https://github.com/huffmanca)) [SIG API Machinery, CLI 및 Storage] - 사용 중단된 어노테이션을 신규 API 서버의 필드와 동기화하기 위해 seccomp 프로파일에 대한 파드 버전 비대칭 전략이 추가되었다. 자세한 설명은 [KEP의](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/20190717-seccomp-ga.md&#35;version-skew-strategy) 해당 섹션을 참고한다. ([#91408](https://github.com/kubernetes/kubernetes/pull/91408), [@saschagrunert](https://github.com/saschagrunert)) [SIG Apps, Auth, CLI 및 Node] - Kubelet에서 수집한 가속기/GPU 메트릭을 비활성화하는 기능이 추가되었다. ([#91930](https://github.com/kubernetes/kubernetes/pull/91930), [@RenaudWasTaken](https://github.com/RenaudWasTaken)) [SIG Node] - 이제 어드미션 웹훅은 어드미션 리뷰 응답의 `.response.warnings` 필드를 사용하여 API 클라이언트에 표시되는 경고 메시지를 반환할 수 있다. ([#92667](https://github.com/kubernetes/kubernetes/pull/92667), [@liggitt](https://github.com/liggitt)) [SIG API Machinery 및 Testing] - CertificateSigningRequest API의 조건이 업데이트되었다. - `status` 필드가 추가되었다. 이 필드의 기본값은 `True` 이며 `Approved`, `Denied` 및 `Failed` 조건에 대해서만 `True` 로 설정될 수 있다. - `lastTransitionTime` 필드가 추가되었다. - 서명자가 영구적인 실패를 표시할 수 있도록 `Failed` 조건 유형이 추가되었다. 이 조건은 `certificatesigningrequests/status` 하위 리소스를 통해 추가될 수 있다. - `Approved` 및 `Denied` 조건은 상호 배타적이다. - `Approved`, `Denied` , `Failed` 조건은 더이상 CSR에서 제거할 수 없다. ([#90191](https://github.com/kubernetes/kubernetes/pull/90191), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Apps, Auth, CLI 및 Node] - 클러스터 관리자는 이제 kubelet 구성 파일에서 enableSystemLogHandler를 false로 설정하여 kubelet에서 /logs 엔드포인트를 끌 수 있다. enableSystemLogHandler는 오직 enableDebuggingHandlers도 true로 설정된 경우에만 true로 설정할 수 있다. ([#87273](https://github.com/kubernetes/kubernetes/pull/87273), [@SaranBalaji90](https://github.com/SaranBalaji90)) [SIG Node] - 사용자 정의 엔드포인트는 이제 새로운 EndpointSliceMirroring 컨트롤러에 의해 엔드포인트슬라이스에 미러링된다. ([#91637](https://github.com/kubernetes/kubernetes/pull/91637), [@robscott](https://github.com/robscott)) [SIG API Machinery, Apps, Auth, Cloud Provider, Instrumentation, Network 및 Testing] - CustomResourceDefinitions은 `spec.versions[*].deprecated` 를 `true` 로 설정하여 버전을 사용 중단됨으로 표시하고, 선택적으로 `spec.versions[*].deprecationWarning` 필드로 기본 지원 중단 경고를 재정의할 수 있도록 지원한다.  ([#92329](https://github.com/kubernetes/kubernetes/pull/92329), [@liggitt](https://github.com/liggitt)) [SIG API Machinery] - EnvVarSource api 문서의 버그가 수정되었다. ([#91194](https://github.com/kubernetes/kubernetes/pull/91194), [@wawa0210](https://github.com/wawa0210)) [SIG Apps] - \"Too large resource version\" 오류에서 복구할 수 없는 리플렉터(reflector)의 버그를 수정하였다. ([#92537](https://github.com/kubernetes/kubernetes/pull/92537), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery] - 고침: 이제 로그 타임스탬프에 고정 너비를 유지하기 위해 후행에 0이 포함된다. ([#91207](https://github.com/kubernetes/kubernetes/pull/91207), [@iamchuckss](https://github.com/iamchuckss)) [SIG Apps 및 Node] - `GenericEphemeralVolume` 기능 게이트의 새로운 알파 기능인 일반 임시 볼륨은 `EmptyDir` 볼륨에 대한 보다 유연한 대안을 제공한다. `EmptyDir` 과 마찬가지로 쿠버네티스에 의해 각 파드에 대한 볼륨이 자동으로 생성되고 삭제된다. 그러나 일반적인 프로비저닝 프로세스(`PersistentVolumeClaim`)를 사용하기 때문에, 스토리지는 타사 스토리지 공급 업체에서 제공할 수 있으며, 일반적인 모든 볼륨 기능이 작동한다. 볼륨은 비워둘 필요가 없다. 예를 들어, 스냅샷으로부터의 복원이 지원된다. ([#92784](https://github.com/kubernetes/kubernetes/pull/92784), [@pohly](https://github.com/pohly)) [SIG API Machinery, Apps, Auth, CLI, Instrumentation, Node, Scheduling, Storage 및 Testing] - 이제 쿠버네티스 빌드를 위하여 최소 Go1.14.4 이상의 버전이 필요하다. ([#92438](https://github.com/kubernetes/kubernetes/pull/92438), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Auth, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Network, Node, Release, Storage 및 Testing] - kubectl edit 명령어에서 managedFields가 숨겨졌다. ([#91946](https://github.com/kubernetes/kubernetes/pull/91946), [@soltysh](https://github.com/soltysh)) [SIG CLI] - K8s.io/apimachinery - scheme.Convert()는 이제 명시적으로 등록된 변환만을 사용한다. 기본 리플렉션 기반 변환은 더이상 사용할 수 없다. `+k8s:conversion-gen` 태그는 `k8s.io/code-generator` 컴포넌트와 함께 사용하여 변환을 생성할 수 있다. ([#90018](https://github.com/kubernetes/kubernetes/pull/90018), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery, Apps 및 Testing] - Kube-proxy: 포트 바인딩 실패를 치명적인 오류로 처리하기 위해 `--bind-address-hard-fail` 플래그가 추가되었다. ([#89350](https://github.com/kubernetes/kubernetes/pull/89350), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle 및 Network] - Kubebuilder 유효성 검사 태그는 CRD 생성을 위해 metav1.Condition에 설정된다. ([#92660](https://github.com/kubernetes/kubernetes/pull/92660), [@damemi](https://github.com/damemi)) [SIG API Machinery] - Kubelet의 --runonce 옵션은 이제 Kubelet의 설정 파일에서 `runOnce` 로도 사용할 수 있다. ([#89128](https://github.com/kubernetes/kubernetes/pull/89128), [@vincent178](https://github.com/vincent178)) [SIG Node] - Kubelet: 구조화된 로깅을 지원하기 위해 '--logging-format' 플래그가 추가되었다. ([#91532](https://github.com/kubernetes/kubernetes/pull/91532), [@afrouzMashaykhi](https://github.com/afrouzMashaykhi)) [SIG API Machinery, Cluster Lifecycle, Instrumentation 및 Node] - 쿠버네티스는 이제 golang 1.15.0-rc.1로 빌드된다. - 주체 대체 이름(Subject Alternative Names)이 없을 때, 인증서를 제공하는 X.509의 CommonName 필드를 호스트 이름으로 처리하는, 더이상 사용되지 않는 레거시 동작은 이제 기본적으로 비활성화된다. GODEBUG 환경 변수에 x509ignoreCN=0 값을 추가하여 일시적으로 다시 활성화할 수도 있다. ([#93264](https://github.com/kubernetes/kubernetes/pull/93264), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery, Auth, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Network, Node, Release, Scalability, Storage 및 Testing] - 변경할 수 없는 시크릿/컨피그맵 기능을 베타로 승격하고 기본적으로 기능이 활성화된다. 이를 통해 시크릿 또는 컨피그맵 오브젝트의 `Immutable` 필드를 설정하여 내용을 immutable로 표시할 수 있다. ([#89594](https://github.com/kubernetes/kubernetes/pull/89594), [@wojtek-t](https://github.com/wojtek-t)) [SIG Apps 및 Testing] - 스케줄 구성 `KubeSchedulerConfiguration` 에서 `BindTimeoutSeconds` 가 제거되었다. ([#91580](https://github.com/kubernetes/kubernetes/pull/91580), [@cofyc](https://github.com/cofyc)) [SIG Scheduling 및 Testing] - kubescheduler.config.k8s.io/v1alpha1이 제거되었다. ([#89298](https://github.com/kubernetes/kubernetes/pull/89298), [@gavinfish](https://github.com/gavinfish)) [SIG Scheduling] - 예약에 실패한 예약 플러그인은 예약 해제 익스텐션 포인트를 트리거하게 된다. ([#92391](https://github.com/kubernetes/kubernetes/pull/92391), [@adtac](https://github.com/adtac)) [SIG Scheduling 및 Testing] - 예전 API 클라이언트가 제출한 업데이트/패치 요청에서 처리하는 `metadata.managedFields` 의 회귀 문제가 해결되었다. ([#91748](https://github.com/kubernetes/kubernetes/pull/91748), [@apelisse](https://github.com/apelisse)) - 스케줄러: 바인딩되지 않은 볼륨이 있는 파드를 예약하기 전에 선택적으로 사용 가능한 스토리지 용량을 확인한다. (신규 기능 게이트인 `CSIStorageCapacity` 가 있는 알파 기능, CSI 드라이버에서만 작동하며, CSI 드라이버 배포의 기능 지원에 따라 상이하다.) ([#92387](https://github.com/kubernetes/kubernetes/pull/92387), [@pohly](https://github.com/pohly)) [SIG API Machinery, Apps, Auth, Scheduling, Storage 및 Testing] - Seccomp 지원이 GA로 전환되었다. 새로운 `seccompProfile` 필드가 파드 및 컨테이너의 securityContext 오브젝트에 추가된다. `seccomp.security.alpha.kubernetes.io/pod` 및 `container.seccomp.security.alpha.kubernetes.io/...` 어노테이션에 대한 지원은 사용 중단되며, v1.22에서 제거된다. ([#91381](https://github.com/kubernetes/kubernetes/pull/91381), [@pjbgf](https://github.com/pjbgf)) [SIG Apps, Auth, Node, Release, Scheduling 및 Testing] - ServiceAppProtocol 기능 게이트는 이제 베타 버전이며 기본적으로 활성화되어 서비스 및 엔드포인트에 새 AppProtocol 필드를 추가한다. ([#90023](https://github.com/kubernetes/kubernetes/pull/90023), [@robscott](https://github.com/robscott)) [SIG Apps 및 Network] - SetHostnameAsFQDN은 PodSpec의 새 필드이다. true로 설정하면, 파드의 정규화된 도메인 이름(FQDN)이 해당 컨테이너의 호스트 이름으로 설정된다. 리눅스 컨테이너에서 이는 커널의 hostname 필드(utsname 구조체의 nodename 필드)에 FQDN을 설정하는 것을 의미한다. 윈도우 컨테이너에서 이는 레지스트리 키 HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters에 대한 호스트 이름의 레지스트리 값을 FQDN으로 설정하는 것을 의미한다. 파드에 FQDN이 없는 경우에는 아무런 효과가 없다. ([#91699](https://github.com/kubernetes/kubernetes/pull/91699), [@javidiaz](https://github.com/javidiaz)) [SIG Apps, Network, Node 및 Testing] - The CertificateSigningRequest API는 다음의 변경 사항과 함께 certificates.k8s.io/v1로 승격되었다. - 이제 `spec.signerName` 이 필요하며, `certificates.k8s.io/v1` API를 통해 `kubernetes.io/legacy-unknown` 요청을 생성하는것이 허용되지 않는다. - `spec.usages` 가 필요하며, 중복값을 포함할 수 없으며, 알려진 사용법만 포함해야 한다. - `status.conditions` 는 중복 유형을 포함할 수 없다. - `status.conditions[*].status` 가 필요하다. - `status.certificate` 는 PEM으로 반드시 인코딩되어야 하며, CERTIFICATE 블록만을 포함해야 한다. ([#91685](https://github.com/kubernetes/kubernetes/pull/91685), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Architecture, Auth, CLI 및 Testing] - 이제 HugePageStorageMediumSize 기능 게이트는 기본적으로 켜져 있으며, 컨테이너 수준에서 여러 크기의 huge page 리소스를 사용할 수 있다. ([#90592](https://github.com/kubernetes/kubernetes/pull/90592), [@bart0sh](https://github.com/bart0sh)) [SIG Node] - Kubelet의 --node-status-max-images 옵션은 이제 Kubelet 구성 파일의 nodeStatusMaxImage 필드를 통해 사용할 수 있다. ([#91275](https://github.com/kubernetes/kubernetes/pull/91275), [@knabben](https://github.com/knabben)) [SIG Node] - Kubelet의 --seccomp-profile-root 옵션은 사용 중단된 것으로 표시된다. ([#91182](https://github.com/kubernetes/kubernetes/pull/91182), [@knabben](https://github.com/knabben)) [SIG Node] - Kubelet의 `--bootstrap-checkpoint-path` 옵션이 제거되었다. ([#91577](https://github.com/kubernetes/kubernetes/pull/91577), [@knabben](https://github.com/knabben)) [SIG Apps 및 Node] - Kubelet의 `--cloud-provider` 및 `--cloud-config` 옵션은 사용 중단된 것으로 표시된다. ([#90408](https://github.com/kubernetes/kubernetes/pull/90408), [@knabben](https://github.com/knabben)) [SIG Cloud Provider 및 Node] - Kubelet의 `--enable-server` 및 `--provider-id` 옵션은 이제 각각 Kubelet 구성 파일의 `enableServer` 및 `providerID` 필드를 통해 사용할 수 있다. ([#90494](https://github.com/kubernetes/kubernetes/pull/90494), [@knabben](https://github.com/knabben)) [SIG Node] - Kubelet의 `--kernel-memcg-notification` 옵션은 이제 Kubelet 구성 파일의 kernelMemcgNotification 필드를 통해 사용할 수 있다. ([#91863](https://github.com/kubernetes/kubernetes/pull/91863), [@knabben](https://github.com/knabben)) [SIG Cloud Provider, Node 및 Testing] - Kubelet의 `--really-crash-for-testing` 및 `--chaos-chance` 옵션은 사용 중단된 것으로 표시된다. ([#90499](https://github.com/kubernetes/kubernetes/pull/90499), [@knabben](https://github.com/knabben)) [SIG Node] - Kubelet의 `--volume-plugin-dir` 옵션은 이제 Kubelet 구성 파일의 `VolumePluginDir` 필드를 통해 사용할 수 있다. ([#88480](https://github.com/kubernetes/kubernetes/pull/88480), [@savitharaghunathan](https://github.com/savitharaghunathan)) [SIG Node] - `DefaultIngressClass` 기능은 이제 GA로 전환되었다. `--feature-gate` 파라미터는 1.20에서 제거된다. ([#91957](https://github.com/kubernetes/kubernetes/pull/91957), [@cmluciano](https://github.com/cmluciano)) [SIG API Machinery, Apps, Network 및 Testing] - 알파 `DynamicAuditing` 기능 게이트 및 `auditregistration.k8s.io/v1alpha1` API가 제거되었으며 더이상 지원되지 않는다. ([#91502](https://github.com/kubernetes/kubernetes/pull/91502), [@deads2k](https://github.com/deads2k)) [SIG API Machinery, Auth 및 Testing] - kube-controller-manager 관리 서명자는 이제 고유한 서명 인증서와 키를 소유할 수 있다. `--cluster-signing-[signer-name]-{cert,key}-file` 에 대한 도움말을 참고한다. `--cluster-signing-{cert,key}-file` 는 여전히 기본값이다. ([#90822](https://github.com/kubernetes/kubernetes/pull/90822), [@deads2k](https://github.com/deads2k)) [SIG API Machinery, Apps 및 Auth] - v1.14부터 사용 중단된, 사용하지 않는 `series.state` 필드는 `events.k8s.io/v1beta1` 및 `v1` 이벤트 유형에서 삭제되었다. ([#90449](https://github.com/kubernetes/kubernetes/pull/90449), [@wojtek-t](https://github.com/wojtek-t)) [SIG Apps] - 스케줄러 플러그인에 대한 예약 해제 익스텐션 포인트가 예약 익스텐션 포인트로 병합되었다. ([#92200](https://github.com/kubernetes/kubernetes/pull/92200), [@adtac](https://github.com/adtac)) [SIG Scheduling 및 Testing] - Golang 버전이 v1.14.4로 변경되었다. ([#88638](https://github.com/kubernetes/kubernetes/pull/88638), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery, Cloud Provider, Release 및 Testing] - Service.Spec.IPFamily에 대한 API 문서를 변경하여, 이중 스택 기능이 GA 되기 전에 정확한 의미가 변경될 수 있으며, 사용자는 기존 서비스가 IPv4, IPv6 혹은 이중 스택인지 확인하기 위해 IPFamily가 아닌 ClusterIP 또는 엔드포인트를 살펴봐야 한다. ([#91527](https://github.com/kubernetes/kubernetes/pull/91527), [@danwinship](https://github.com/danwinship)) [SIG Apps 및 Network] - 사용자는 리소스 그룹을 무시하도록 리소스 접두사를 구성할 수 있다. ([#88842](https://github.com/kubernetes/kubernetes/pull/88842), [@angao](https://github.com/angao)) [SIG Node 및 Scheduling] - `Ingress` 및 `IngressClass` 리소스가 `networking.k8s.io/v1` 로 변경되었다. `extensions/v1beta1` 및 `networking.k8s.io/v1beta1` API 버전의 인그레스 및 인그레스클래스 유형은 사용 중단되었으며, 더이상 1.22 이상에서 제공되지 않는다. 지속형 오브젝트는 `networking.k8s.io/v1` API를 통해 접근할 수 있다. v1 인그레스 오브젝트의 주목할만한 변경 사항은 다음과 같다. (v1beta1 필드 이름은 변경되지 않았다.) - `spec.backend` -> `spec.defaultBackend` - `serviceName` -> `service.name` - `servicePort` -> `service.port.name` (string 값에 대하여) - `servicePort` -> `service.port.number` (numeric 값에 대하여) - `pathType` 은 더이상 v1에서 기본값을 갖지 않는다. \"Exact\", \"Prefix\" 또는 \"ImplementationSpecific\" 중에서 지정되어야 한다. 기타 인그레스 API 변경 사항: - 백엔드는 이제 리소스 또는 서비스 백엔드가 될 수 있다. - `path` 는 더이상 유효한 정규 표현식이 아니어도 된다. ([#89778](https://github.com/kubernetes/kubernetes/pull/89778), [@cmluciano](https://github.com/cmluciano)) [SIG API Machinery, Apps, CLI, Network 및 Testing] - `NodeResourcesLeastAllocated` 및 `NodeResourcesMostAllocated` 플러그인은 이제 CPU 및 메모리에 대한 사용자 정의 가중치를 지원한다. [#90544](https://github.com/kubernetes/kubernetes/pull/90544), [@chendave](https://github.com/chendave)) [SIG Scheduling] - v1beta1 버전의 스케줄러 구성 설정 API에 `PostFilter` 유형이 추가되었다. ([#91547](https://github.com/kubernetes/kubernetes/pull/91547), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling] - `RequestedToCapacityRatioArgs` 인코딩은 이제 엄격하게 작동한다. ([#91603](https://github.com/kubernetes/kubernetes/pull/91603), [@pancernik](https://github.com/pancernik)) [SIG Scheduling] - `v1beta1` 스케줄러의 `Extender` 인코딩은 대소문자를 구분하며(`v1alpha1`/`v1alpha2` 는 대소문자를 구분하지 않았다.), `httpTimeout` 필드는 기간 인코딩을 사용하며(예를 들어, 1초는 `\"1s\"` 로 지정된다.), `v1alpha1`/`v1alpha2` 의 `enableHttps` 필드 이름이 `enableHTTPS` 로 변경되었다. ([#91625](https://github.com/kubernetes/kubernetes/pull/91625), [@pancernik](https://github.com/pancernik)) [SIG Scheduling] ### 기능 - defaultpreemption 플러그인은 기존 하드코딩된 파드 선점 로직을 대체하는 스케줄러에 등록되고 활성화된다. ([#92049](https://github.com/kubernetes/kubernetes/pull/92049), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling 및 Testing] - 스케줄링 필터 실패를 해결하기 위해, 필터 단계 후에 실행되는 스케줄러 프레임워크에 새로운 익스텐션 포인트인 `PostFilter` 가 도입되었다. 전형적인 구현은 선점 로직을 실행하는 것이다. ([#91314](https://github.com/kubernetes/kubernetes/pull/91314), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling 및 Testing] - 조치 필요: CoreDNS v1.7.0에서, [메트릭의 이름이 변경되어](https://github.com/coredns/coredns/blob/master/notes/coredns-1.7.0.md&#35;metric-changes) 이전 메트릭의 이름을 사용하는 기존 리포팅 공식과 역호환(backward incompatible)되지 않는다. 업그레이드하기 전에 공식을 새 이름으로 조정해야 한다. Kubeadm은 이제 CoreDNS 버전 v1.7.0이 포함된다. 주요 변경 사항은 다음과 같다. -  CoreDNS가 서비스 기록 업데이트를 중단할 수 있는 버그가 수정되었다. -  어떤 정책이 설정되어 있어도 항상 첫 번째 업스트림 서버만 선택되는 포워드 플러그인의 버그가 수정되었다. -  쿠버네티스 플러그인에서 이미 사용 중단된 `resyncperiod` 및 `upstream` 이 제거되었다. -  프로메테우스(Prometheus) 메트릭 이름 변경을 포함한다. (표준 프로메테우스 메트릭 명명 규칙에 맞게 변경). 이전 메트릭의 이름을 사용하는 기존 리포팅 공식과 역호환된다. -  페더레이션 플러그인(v1 쿠버네티스 페더레이션을 허용)이 제거되었다. 자세한 내용은 https://coredns.io/2020/06/15/coredns-1.7.0-release/ 에서 확인할 수 있다. ([#92651](https://github.com/kubernetes/kubernetes/pull/92651), [@rajansandeep](https://github.com/rajansandeep)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle 및 Instrumentation] - 사용 중단된 버전에 대한 API 요청은 이제 API 응답에서 경고 헤더를 수신하고, 사용 중단된 API의 사용을 나타내는 메트릭이 표시되도록 한다. - `kubectl` 은 표준 에러 출력으로 경고를 출력하며, `--warnings-as-errors` 옵션을 허용하여 경고를 치명적인 오류로 처리한다. - `k8s.io/client-go` 은 기본적으로 표준 에러 출력에 경고를 출력한다. `config.WarningHandler` 를 설정하여 클라이언트 별로 재정의하거나, `rest.SetDefaultWarningHandler()` 로 프로세스별로 재정의한다. - `kube-apiserver` 는 요청된, 사용 중단된 API에 대해 `group`, `version`, `resource`, `subresource` 및 `removed_release` 레이블을 표시하고 `apiserver_requested_deprecated_apis` 게이지 메트릭을 `1` 로 설정한다. ([#73032](https://github.com/kubernetes/kubernetes/pull/73032), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, CLI, Instrumentation 및 Testing] - component-base에 --logging-format 플래그가 추가되었다. 기본값은 변경되지 않은 klog를 사용하는 \"text\"이다. ([#89683](https://github.com/kubernetes/kubernetes/pull/89683), [@yuzhiquan](https://github.com/yuzhiquan)) [SIG Instrumentation] - kubectl create deployment 명령어에 --port 플래그가 추가되었다. ([#91113](https://github.com/kubernetes/kubernetes/pull/91113), [@soltysh](https://github.com/soltysh)) [SIG CLI 및 Testing] - cmd/cloud-controller-manager에 .import-restrictions 파일이 추가되었다. ([#90630](https://github.com/kubernetes/kubernetes/pull/90630), [@nilo19](https://github.com/nilo19)) [SIG API Machinery 및 Cloud Provider] - CRI-API ImageSpec 오브젝트에 어노테이션이 추가되었다. ([#90061](https://github.com/kubernetes/kubernetes/pull/90061), [@marosset](https://github.com/marosset)) [SIG Node 및 Windows] - 스케줄러의 PodSchedulingDuration 메트릭에 시도(attempts)에 대한 레이블이 추가되었다. ([#92650](https://github.com/kubernetes/kubernetes/pull/92650), [@ahg-g](https://github.com/ahg-g)) [SIG Instrumentation 및 Scheduling] - kubectl scale 명령어에 클라이언트측과 서버측에 대한 드라이런(dry-run) 지원이 추가되었다. ([#89666](https://github.com/kubernetes/kubernetes/pull/89666), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG CLI 및 Testing] - kubectl diff에 셀렉터가 추가되었다. ([#90857](https://github.com/kubernetes/kubernetes/pull/90857), [@sethpollack](https://github.com/sethpollack)) [SIG CLI] - cgroups v2 노드의 유효성 검사에 대한 지원이 추가되었다. ([#89901](https://github.com/kubernetes/kubernetes/pull/89901), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle  및 Node] - 노드 수준에서, 다른 크기로 사전 할당된 huge page에 대한 지원이 추가되었다. ([#89252](https://github.com/kubernetes/kubernetes/pull/89252), [@odinuge](https://github.com/odinuge)) [SIG Apps 및 Node] - Azure 파일 드라이버에 대한 태그 지원이 추가되었다. ([#92825](https://github.com/kubernetes/kubernetes/pull/92825), [@ZeroMagic](https://github.com/ZeroMagic)) [SIG Cloud Provider 및 Storage] - azure 디스크 드라이버에 대한 태그 지원이 추가되었다. ([#92356](https://github.com/kubernetes/kubernetes/pull/92356), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider 및 Storage] - kubectl run 명령어에 --privileged 플래그가 추가되었다. ([#90569](https://github.com/kubernetes/kubernetes/pull/90569), [@brianpursley](https://github.com/brianpursley)) [SIG CLI] - `v1beta1` 장비 플러그인 API에 새로운 `GetPreferredAllocation()` 호출이 추가되었다. ([#92665](https://github.com/kubernetes/kubernetes/pull/92665), [@klueska](https://github.com/klueska)) [SIG Node 및 Testing] - 쿠버네티스 서비스의 세션 어피니티를 설정하기 위해 윈도우에 대한 기능 지원이 추가되었다. 필요: [윈도우 서버 vNext Insider Preview Build 19551](https://blogs.windows.com/windowsexperience/2020/01/28/announcing-windows-server-vnext-insider-preview-build-19551/)(또는 그 이상) ([#91701](https://github.com/kubernetes/kubernetes/pull/91701), [@elweb9858](https://github.com/elweb9858)) [SIG Network 및 Windows] - kube-apiserver 메트릭 추가: apiserver_current_inflight_request_measures. (API 우선순위(Priority) 및 공정성(Fairness)이 활성화된 경우, windowed_request_stats). ([#91177](https://github.com/kubernetes/kubernetes/pull/91177), [@MikeSpreitzer](https://github.com/MikeSpreitzer)) [SIG API Machinery, Instrumentation 및 Testing] - AWS 로드밸런서 서비스의 대상 노드에 service.beta.kubernetes.io/aws-load-balancer-target-node-labels 어노테이션이 추가되었다. ([#90943](https://github.com/kubernetes/kubernetes/pull/90943), [@foobarfran](https://github.com/foobarfran)) [SIG Cloud Provider] - 서로 다른 세분성을 갖는 흐름-제어 시스템의 내부 상태를 덤프하기 위해 접두사 \"/debug/flowcontrol/*\" 아래에 디버깅 엔드포인트 집합이 추가되었다. ([#90967](https://github.com/kubernetes/kubernetes/pull/90967), [@yue9944882](https://github.com/yue9944882)) [SIG API Machinery] - kube-scheduler의 메트릭인 framework_extension_point_duration_seconds에 프로파일 레이블이 추가되었다.([#92268](https://github.com/kubernetes/kubernetes/pull/92268), [@alculquicondor](https://github.com/alculquicondor)) [SIG Instrumentation 및 Scheduling] - kube-scheduler의 메트릭인 schedule_attempts_total에 프로파일 레이블이 추가되었다. - e2e_scheduling_duration_seconds에 결과 및 프로파일 레이블이 추가되었다. 이제 스케줄링 불가능 및 오류 시도 횟수가 기록된다. ([#92202](https://github.com/kubernetes/kubernetes/pull/92202), [@alculquicondor](https://github.com/alculquicondor)) [SIG Instrumentation 및 Scheduling] - 사용 중단된 API 버전에 대한 API 요청의 감사(audit) 이벤트는 이제 `\"k8s.io/deprecated\": \"true\"` 감사 어노테이션을 포함한다. 대상에 대한 제거 릴리스(removal release)가 식별되면, 해당 감사 이벤트는 `\"k8s.io/removal-release\": \"<majorVersion>.<minorVersion>\"` 감사 어노테이션도 포함한다. ([#92842](https://github.com/kubernetes/kubernetes/pull/92842), [@liggitt](https://github.com/liggitt)) [SIG API Machinery 및 Instrumentation] - 대시보드가 v2.0.1로 격상되었다. ([#91526](https://github.com/kubernetes/kubernetes/pull/91526), [@maciaszczykm](https://github.com/maciaszczykm)) [SIG Cloud Provider] - 클라우드 노드-컨트롤러는 InstancesV2를 사용한다. ([#91319](https://github.com/kubernetes/kubernetes/pull/91319), [@gongguan](https://github.com/gongguan)) [SIG Apps, Cloud Provider, Scalability 및 Storage] - 의존성: Golang 버전이 1.13.9로 변경되었다. - 빌드: kube-cross 이미지 빌드가 제거되었다. ([#89275](https://github.com/kubernetes/kubernetes/pull/89275), [@justaugustus](https://github.com/justaugustus)) [SIG Release 및 Testing] - 세부 스케줄러 점수 결과는 레벨(verbose) 10에서 표시된다. ([#89384](https://github.com/kubernetes/kubernetes/pull/89384), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling] - E2e.test는 클러스터가 적합하다고 평가되기 위해, 통과해야 하는 적합성 테스트 목록을 표시할 수 있다. ([#88924](https://github.com/kubernetes/kubernetes/pull/88924), [@dims](https://github.com/dims)) [SIG Architecture 및 Testing] - PodTopologySpread 플러그인을 사용하여 defaultspreading을 수행하려면 DefaultPodTopologySpread 기능 게이트를 활성화해야 한다. 이렇게 하면, 레거시 DefaultPodTopologySpread 플러그인이 비활성화된다. ([#91793](https://github.com/kubernetes/kubernetes/pull/91793), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - EndpointSlice 컨트롤러가 실패한 동기화를 재시도하기 위해 더 오래 대기하게 된다. ([#89438](https://github.com/kubernetes/kubernetes/pull/89438), [@robscott](https://github.com/robscott)) [SIG Apps 및 Network] - 로컬 영역(AWS local zone)을 지원하기 위해, AWS azToRegion 메서드가 확장된다. ([#90874](https://github.com/kubernetes/kubernetes/pull/90874), [@Jeffwan](https://github.com/Jeffwan)) [SIG Cloud Provider] - 기능: azure 공유 디스크 지원이 추가되었다. ([#89511](https://github.com/kubernetes/kubernetes/pull/89511), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider 및 Storage] - 기능: azure 디스크 api-version이 변경되었다. ([#89250](https://github.com/kubernetes/kubernetes/pull/89250), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider 및 Storage] - 기능: [Azure 공유 디스크](https://docs.microsoft.com/ko-kr/azure/virtual-machines/disks-shared-enable?tabs=azure-cli)를 지원하며, azure 디스크 스토리지 클래스에 새로운 필드(`maxShares`)가 추가되었다. kind: StorageClass apiVersion: storage.k8s.io/v1 metadata: name: shared-disk provisioner: kubernetes.io/azure-disk parameters: skuname: Premium_LRS  &#35; 현재는 프리미엄 SSD만 사용 가능하다. cachingMode: None  &#35; 읽기전용 호스트 캐싱은 maxShares>1 인 프리미엄 SSD에 사용할 수 없다. maxShares: 2 ([#89328](https://github.com/kubernetes/kubernetes/pull/89328), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider 및 Storage] - 가상 서버 주소가 이미 바인딩되지 않은 경우, `EnsureDummyInterface` 만 실행하여 IPVS 프록시 성능을 향상시킬 수 있다. ([#92609](https://github.com/kubernetes/kubernetes/pull/92609), [@andrewsykim](https://github.com/andrewsykim)) [SIG Network] - 이제 Kube-Proxy는 EndpointSliceProxying 기능 게이트를 통해 윈도우에서 엔드포인트슬라이스를 지원한다. ([#90909](https://github.com/kubernetes/kubernetes/pull/90909), [@kumarvin123](https://github.com/kumarvin123)) [SIG Network 및 Windows] - 이제 Kube-Proxy는 IPv6DualStack 기능 게이트를 사용하여 윈도우에서 IPv6DualStack 기능을 지원한다. ([#90853](https://github.com/kubernetes/kubernetes/pull/90853), [@kumarvin123](https://github.com/kumarvin123)) [SIG Network, Node 및 Windows] - Kube-addon-manager가 v9.1.1로 변경되어, 허용된 리소스의 기본 목록을 재정의할 수 있다. (https://github.com/kubernetes/kubernetes/pull/91018) ([#91240](https://github.com/kubernetes/kubernetes/pull/91240), [@tosi3k](https://github.com/tosi3k)) [SIG Cloud Provider, Scalability 및 Testing] - etcd3에서 지원하는 Kube-apiserver는 데이터베이스 파일 크기를 표시하는 메트릭을 추출할 수 있다. ([#89151](https://github.com/kubernetes/kubernetes/pull/89151), [@jingyih](https://github.com/jingyih)) [SIG API Machinery] - Kube-apiserver, kube-scheduler 및 kube-controller manager는 이제 유닉스 시스템에서 실행되는 경우 --bind-address 및 --secure-port 플래그로 정의된 주소에서 수신 대기할 때, SO_REUSEPORT 소켓 옵션을 사용한다(윈도우는 지원되지 않는다). 이를 통해 동일한 구성으로 단일 호스트에서 이러한 프로세스의 여러 인스턴스를 실행할 수 있으므로, 다운타임 없이 정상적으로 변경/재시작이 가능하다. ([#88893](https://github.com/kubernetes/kubernetes/pull/88893), [@invidian](https://github.com/invidian)) [SIG API Machinery, Scheduling 및 Testing] - Kube-apiserver: NodeRestriction 어드미션 플러그인은 이제 새 노드를 만들 때, kubelet이 설정할 수 있는 노드 레이블을 1.16 이상에서 kubelet이 허용하는, `--node-labels` 파라미터로 제한한다. ([#90307](https://github.com/kubernetes/kubernetes/pull/90307), [@liggitt](https://github.com/liggitt)) [SIG Auth 및 Node] - Kube-controller-manager: 구조화된 로깅을 지원하기 위해 '--logging-format' 플래그가 추가되었다. ([#91521](https://github.com/kubernetes/kubernetes/pull/91521), [@SataQiu](https://github.com/SataQiu)) [SIG API Machinery 및 Instrumentation] - Kube-controller-manager: `--experimental-cluster-signing-duration` 플래그는 v1.22에서 사용 중단된 것으로 표시되며, `--cluster-signing-duration` 으로 대체된다. ([#91154](https://github.com/kubernetes/kubernetes/pull/91154), [@liggitt](https://github.com/liggitt)) [SIG Auth 및 Cloud Provider] - 이제 Kube-proxy는 리눅스에서 기본적으로 엔드포인트 대신 엔드포인트슬라이스를 사용한다. 새로운 알파 `WindowsEndpointSliceProxying` 기능 게이트를 통해 윈도우에서 기능을 활성화할 수 있다. ([#92736](https://github.com/kubernetes/kubernetes/pull/92736), [@robscott](https://github.com/robscott)) [SIG Network] - Kube-scheduler: 구조화된 로깅을 지원하기 위해 '--logging-format' 플래그가 추가되었다. ([#91522](https://github.com/kubernetes/kubernetes/pull/91522), [@SataQiu](https://github.com/SataQiu)) [SIG API Machinery, Cluster Lifecycle, Instrumentation 및 Scheduling] - Kubeadm은 이제 생성된 컴포넌트와 사용자 제공 컴포넌트의 설정을 구분하여, 구성 업그레이드가 필요한 경우 이전 컴포넌트를 다시 생성한다. ([#86070](https://github.com/kubernetes/kubernetes/pull/86070), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - Kubeadm: 수동으로 업그레이드된 컴포넌트의 설정이, 업그레이드 계획 및 적용 중에 --config 옵션을 통해 YAML 파일에서 적용될 수 있다.  클러스터에 저장된 모든 것을 덮어쓰는 kubeadm 구성 및 컴포넌트의 설정이 보존되는 기존의 --config 동작도 유지된다. --config와 함께 사용되는 동작은 이제 kubeadm 설정 API 오브젝트(API group \"kubeadm.kubernetes.io\")가 파일에 제공되었는지의 여부에 따라 결정된다. ([#91980](https://github.com/kubernetes/kubernetes/pull/91980), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - Kubeadm: 구동이 느린 컨테이너를 보호하기 위해 정적 파드에 대한 시작 프로브가 추가되었다. ([#91179](https://github.com/kubernetes/kubernetes/pull/91179), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle] - Kubeadm: \"kubeadm init phase certs\" 하위 명령어의 \"--csr-only\" 및 \"--csr-dir\" 플래그는 사용 중단되었다. 대신 \"kubeadm alpha certs generate-csr\" 를 사용해야 한다. 이 신규 명령어를 사용하면 모든 컨트롤 플레인 컴포넌트에 대한 새로운 개인키 및 인증서 서명 요청을 생성할 수 있으므로, 외부 CA로 인증서에 서명할 수 있다. ([#92183](https://github.com/kubernetes/kubernetes/pull/92183), [@wallrj](https://github.com/wallrj)) [SIG Cluster Lifecycle] - Kubeadm: 'upgrade apply' 도중에, kube-proxy 컨피그맵이 누락된 경우, kube-proxy가 업그레이드되지 않아야 한다고 가정한다. DNS 서버 애드온에서 kube-dns/coredns 컨피그맵이 누락된 경우에도 동일하게 적용된다. 이는 'upgrade apply' 지원 단계까지의 일시적인 해결 방법이다. 해당 단계가 지원되면, kube-proxy/dns 수동으로 넘겨져야 한다. ([#89593](https://github.com/kubernetes/kubernetes/pull/89593), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: 컨트롤-플레인 정적 파드는 \"시스템-노드-크리티컬\" 우선순위 클래스로 전환되었다. ([#90063](https://github.com/kubernetes/kubernetes/pull/90063), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: upgrade plan은 이제 업그레이드 전에, 알려진 컴포넌트의 설정 상태를 나타내는 표를 출력한다. ([#88124](https://github.com/kubernetes/kubernetes/pull/88124), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - Kubectl 명령어는 지정하지 않고(전체 리소스 이름을 입력할 필요 없음) 바로 taint no와 같이 사용할 수 있다. ([#88723](https://github.com/kubernetes/kubernetes/pull/88723), [@wawa0210](https://github.com/wawa0210)) [SIG CLI] - Kubelet: 다음의 메트릭 이름이 변경되었다. kubelet_running_container_count --> kubelet_running_containers kubelet_running_pod_count --> kubelet_running_pods ([#92407](https://github.com/kubernetes/kubernetes/pull/92407), [@RainbowMango](https://github.com/RainbowMango)) [SIG API Machinery, Cluster Lifecycle, Instrumentation 및 Node] - 클라이언트 인증서를 교체하도록 설정된 kubelet은 이제 인증서 만료까지 남은 시간(초)을 나타내는 `certificate_manager_server_ttl_seconds` 게이지 메트릭을 표시한다. ([#91148](https://github.com/kubernetes/kubernetes/pull/91148), [@liggitt](https://github.com/liggitt)) [SIG Auth 및 Node] - PodTopologySpreading이 더 잘 확산될 수 있도록 새로운 점수 계산 함수가 도입되었다. ([#90475](https://github.com/kubernetes/kubernetes/pull/90475), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - 유틸리티 라이브러리가 소폭 향상되었으며, 별도의 조치가 필요하진 않다. ([#92440](https://github.com/kubernetes/kubernetes/pull/92440), [@luigibk](https://github.com/luigibk)) [SIG Network] - PodTolerationRestriction: 에러에서 네임스페이스 허용 목록이 표시된다. ([#87582](https://github.com/kubernetes/kubernetes/pull/87582), [@mrueg](https://github.com/mrueg)) [SIG Scheduling] - 공급자별 참고 사항: vsphere: vsphere.conf - 성능 문제를 위해 자격증명 시크릿 관리를 비활성화하는 새로운 옵션 ([#90836](https://github.com/kubernetes/kubernetes/pull/90836), [@Danil-Grigorev](https://github.com/Danil-Grigorev)) [SIG Cloud Provider] - pod_preemption_metrics의 이름이 preemption_metrics로 변경되었다. ([#93256](https://github.com/kubernetes/kubernetes/pull/93256), [@ahg-g](https://github.com/ahg-g)) [SIG Instrumentation 및 Scheduling] - Rest.Config는 이제, 이전에는 환경 변수를 통해서만 구성할 수 있었던 프록시 구성을 재정의하는 플래그를 지원한다. ([#81443](https://github.com/kubernetes/kubernetes/pull/81443), [@mikedanese](https://github.com/mikedanese)) [SIG API Machinery 및 Node] - PodTopologySpreading의 점수는 maxSkew가 증가함에 따라 차이가 감소되었다. ([#90820](https://github.com/kubernetes/kubernetes/pull/90820), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - 적용된 구성으로부터 필드가 제거된 경우 서버측 적용 동작이 정규화되었다. 다른 소유자가 없는 제거된 필드는 생성된 오브젝트에서 제거되거나 기본값이 있는 경우, 기본값으로 재설정된다. 기본값으로 재설정하지 않고 HPA로 `replicas` 필드를 이전하는 것과 같은 안전한 소유권 이전은 [소유권 이전](https://kubernetes.io/docs/reference/using-api/api-concepts/&#35;transferring-ownership)에 설명되어 있다. ([#92661](https://github.com/kubernetes/kubernetes/pull/92661), [@jpbetz](https://github.com/jpbetz)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation 및 Testing] - 서비스 컨트롤러: 노드의 관련 필드가 변경될 때에만 LB 노드 풀이 동기화된다. ([#90769](https://github.com/kubernetes/kubernetes/pull/90769), [@andrewsykim](https://github.com/andrewsykim)) [SIG Apps 및 Network] - CSIMigrationvSphere 기능 게이트가 베타로 전환되었다. 사용자는 CSIMigration + CSIMigrationvSphere 기능을 활성화하고 vSphere CSI 드라이버(https://github.com/kubernetes-sigs/vsphere-csi-driver)를 설치하여 인-트리 vSphere 플러그인 \"kubernetes.io/vsphere-volume\" 에서 vSphere CSI 드라이버로 워크로드를 이동해야 한다. 요구사항: vSphere vCenter/ESXi 버전: 7.0u1, HW 버전: VM 버전 15 ([#92816](https://github.com/kubernetes/kubernetes/pull/92816), [@divyenpatel](https://github.com/divyenpatel)) [SIG Cloud Provider 및 Storage] - `kubectl create deployment` 명령에 대하여 --replicas 플래그가 지원된다. ([#91562](https://github.com/kubernetes/kubernetes/pull/91562), [@zhouya0](https://github.com/zhouya0)) - 클라이언트측 적용에서 서버측 적용으로의 원활한 업그레이드를 지원하며, 해당하는 다운그레이드 또한 지원한다. ([#90187](https://github.com/kubernetes/kubernetes/pull/90187), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG API Machinery 및 Testing] - VMSS의 비동기식 생성/변경을 지원한다. ([#89248](https://github.com/kubernetes/kubernetes/pull/89248), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - cgroups v2 통합 모드를 사용하는 호스트에서의 실행을 지원한다. ([#85218](https://github.com/kubernetes/kubernetes/pull/85218), [@giuseppe](https://github.com/giuseppe)) [SIG Node] - 코어 마스터 베이스 이미지(kube-apiserver, kube-scheduler)를 debian에서 distroless로 전환하였다. ([#90674](https://github.com/kubernetes/kubernetes/pull/90674), [@dims](https://github.com/dims)) [SIG Cloud Provider, Release 및 Scalability] - etcd 이미지(마이그레이션 스크립트 포함)를 debian에서 distroless로 전환하였다. ([#91171](https://github.com/kubernetes/kubernetes/pull/91171), [@dims](https://github.com/dims)) [SIG API Machinery 및 Cloud Provider] - RotateKubeletClientCertificate 기능 게이트가 GA로 승격되었으며, kubelet --feature-gate RotateKubeletClientCertificate 파라미터는 1.20에서 제거된다. ([#91780](https://github.com/kubernetes/kubernetes/pull/91780), [@liggitt](https://github.com/liggitt)) [SIG Auth 및 Node] - SCTPSupport 기능이 기본적으로 활성화된다. ([#88932](https://github.com/kubernetes/kubernetes/pull/88932), [@janosi](https://github.com/janosi)) [SIG Network] - `certificatesigningrequests/approval` 하위 리소스는 이제 패치 API 요청을 지원한다. ([#91558](https://github.com/kubernetes/kubernetes/pull/91558), [@liggitt](https://github.com/liggitt)) [SIG Auth 및 Testing] - `kubernetes_build_info` 의 메트릭 레이블 이름이 `camel case` 에서 `snake case` 로 변경되었다. - gitVersion --> git_version - gitCommit --> git_commit - gitTreeState --> git_tree_state - buildDate --> build_date - goVersion --> go_version 이 변경 사항은 `kube-apiserver`、`kube-scheduler`、`kube-proxy` 및 `kube-controller-manager` 에서 발생한다. ([#91805](https://github.com/kubernetes/kubernetes/pull/91805), [@RainbowMango](https://github.com/RainbowMango)) [SIG API Machinery, Cluster Lifecycle 및 Instrumentation] - apiserver 로그의 추적 출력이 더 체계적이고 포괄적으로 변경되었다. 추적은 중첩되며, 오래 실행되지 않은 모든 요청 엔드포인트에 대해 전체 필터 체인이 계측된다(예: 인증 확인이 포함된다.). ([#88936](https://github.com/kubernetes/kubernetes/pull/88936), [@jpbetz](https://github.com/jpbetz)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation 및 Scheduling] - 시간 초과 직전에 감시 북마크를 보내는 것 외에도, 주기적으로(요청된 경우) 보내도록 변경되었다. ([#90560](https://github.com/kubernetes/kubernetes/pull/90560), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery] - cri-tools이 v1.18.0으로 변경되었다. ([#89720](https://github.com/kubernetes/kubernetes/pull/89720), [@saschagrunert](https://github.com/saschagrunert)) [SIG Cloud Provider, Cluster Lifecycle, Release 및 Scalability] - etcd 클라이언트측이 v3.4.4로 변경되었다. ([#89169](https://github.com/kubernetes/kubernetes/pull/89169), [@jingyih](https://github.com/jingyih)) [SIG API Machinery 및 Cloud Provider] - etcd 클라이언트측이 v3.4.7로 변경되었다. ([#89822](https://github.com/kubernetes/kubernetes/pull/89822), [@jingyih](https://github.com/jingyih)) [SIG API Machinery 및 Cloud Provider] - etcd 클라이언트측이 v3.4.9로 변경되었다. ([#92075](https://github.com/kubernetes/kubernetes/pull/92075), [@jingyih](https://github.com/jingyih)) [SIG API Machinery, Cloud Provider 및 Instrumentation] - azure-sdk가 v40.2.0으로 변경되었다. ([#89105](https://github.com/kubernetes/kubernetes/pull/89105), [@andyzhangx](https://github.com/andyzhangx)) [SIG CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Storage 및 Testing] - 이제 `kubectl port-forward` 가 UDP를 지원하지 않음을 사용자에게 경고하게 된다. ([#91616](https://github.com/kubernetes/kubernetes/pull/91616), [@knight42](https://github.com/knight42)) [SIG CLI] - PodTopologySpread의 가중치 확산 스케줄링 점수가 2배로 늘어났다. ([#91258](https://github.com/kubernetes/kubernetes/pull/91258), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - `EventRecorder()` 는 `FrameworkHandle` 인터페이스에 노출되어 스케줄러 플러그인 개발자가 클러스터 수준 이벤트를 기록하도록 선택할 수 있다. ([#92010](https://github.com/kubernetes/kubernetes/pull/92010), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling] - `kubectl alpha debug` 명령어는 이제 원본을 복사하여 파드 디버깅을 지원한다. ([#90094](https://github.com/kubernetes/kubernetes/pull/90094), [@aylei](https://github.com/aylei)) [SIG CLI] - `kubectl alpha debug` 명령어는 이제 노드의 호스트 네임스페이스에서 실행되는 디버깅 컨테이너를 생성하여 노드를 디버깅하는 방식을 지원한다. ([#92310](https://github.com/kubernetes/kubernetes/pull/92310), [@verb](https://github.com/verb)) [SIG CLI] - `local-up-cluster.sh` 는 이제 기본적으로 CSI snapshotter를 설치하며, `ENABLE_CSI_SNAPSHOTTER=false` 로 비활성화할 수 있다. ([#91504](https://github.com/kubernetes/kubernetes/pull/91504), [@pohly](https://github.com/pohly)) - `ImageLocality` 플러그인의 `maxThreshold` 는 이제 파드의 이미지 수에 따라 크기가 조정되어, 여러 이미지가 있는 파드의 노드 우선순위를 구분하는데 도움을 줄 수 있다. ([#91138](https://github.com/kubernetes/kubernetes/pull/91138), [@chendave](https://github.com/chendave)) [SIG Scheduling] </del> <ins> - `TokenRequest` and `TokenRequestProjection` features have been promoted to GA. This feature allows generating service account tokens that are not visible in Secret objects and are tied to the lifetime of a Pod object. See https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#service-account-token-volume-projection for details on configuring and using this feature. The `TokenRequest` and `TokenRequestProjection` feature gates will be removed in v1.21. - kubeadm's kube-apiserver Pod manifest now includes the following flags by default \"--service-account-key-file\", \"--service-account-signing-key-file\", \"--service-account-issuer\". ([#93258](https://github.com/kubernetes/kubernetes/pull/93258), [@zshihang](https://github.com/zshihang)) [SIG API Machinery, Auth, Cluster Lifecycle, Storage and Testing] - A new `nofuzz` go build tag now disables gofuzz support. Release binaries enable this. ([#92491](https://github.com/kubernetes/kubernetes/pull/92491), [@BenTheElder](https://github.com/BenTheElder)) [SIG API Machinery] - Add WindowsContainerResources and Annotations to CRI-API UpdateContainerResourcesRequest ([#95741](https://github.com/kubernetes/kubernetes/pull/95741), [@katiewasnothere](https://github.com/katiewasnothere)) [SIG Node] - Add a `serving` and `terminating` condition to the EndpointSlice API. `serving` tracks the readiness of endpoints regardless of their terminating state. This is distinct from `ready` since `ready` is only true when pods are not terminating. `terminating` is true when an endpoint is terminating. For pods this is any endpoint with a deletion timestamp. ([#92968](https://github.com/kubernetes/kubernetes/pull/92968), [@andrewsykim](https://github.com/andrewsykim)) [SIG Apps and Network] - Add dual-stack Services (alpha).  This is a BREAKING CHANGE to an alpha API. It changes the dual-stack API wrt Service from a single ipFamily field to 3 fields: ipFamilyPolicy (SingleStack, PreferDualStack, RequireDualStack), ipFamilies (a list of families assigned), and clusterIPs (inclusive of clusterIP).  Most users do not need to set anything at all, defaulting will handle it for them.  Services are single-stack unless the user asks for dual-stack.  This is all gated by the \"IPv6DualStack\" feature gate. ([#91824](https://github.com/kubernetes/kubernetes/pull/91824), [@khenidak](https://github.com/khenidak)) [SIG API Machinery, Apps, CLI, Network, Node, Scheduling and Testing] - Add support for hugepages to downward API ([#86102](https://github.com/kubernetes/kubernetes/pull/86102), [@derekwaynecarr](https://github.com/derekwaynecarr)) [SIG API Machinery, Apps, CLI, Network, Node, Scheduling and Testing] - Adds kubelet alpha feature, `GracefulNodeShutdown` which makes kubelet aware of node system shutdowns and result in graceful termination of pods during a system shutdown. ([#96129](https://github.com/kubernetes/kubernetes/pull/96129), [@bobbypage](https://github.com/bobbypage)) [SIG Node] - AppProtocol is now GA for Endpoints and Services. The ServiceAppProtocol feature gate will be deprecated in 1.21. ([#96327](https://github.com/kubernetes/kubernetes/pull/96327), [@robscott](https://github.com/robscott)) [SIG Apps and Network] - Automatic allocation of NodePorts for services with type LoadBalancer can now be disabled by setting the (new) parameter Service.spec.allocateLoadBalancerNodePorts=false. The default is to allocate NodePorts for services with type LoadBalancer which is the existing behavior. ([#92744](https://github.com/kubernetes/kubernetes/pull/92744), [@uablrek](https://github.com/uablrek)) [SIG Apps and Network] - Certain fields on  Service objects will be automatically cleared when changing the service's `type` to a mode that does not need those fields.  For example, changing from type=LoadBalancer to type=ClusterIP will clear the NodePort assignments, rather than forcing the user to clear them. ([#95196](https://github.com/kubernetes/kubernetes/pull/95196), [@thockin](https://github.com/thockin)) [SIG API Machinery, Apps, Network and Testing] - Document that ServiceTopology feature is required to use `service.spec.topologyKeys`. ([#96528](https://github.com/kubernetes/kubernetes/pull/96528), [@andrewsykim](https://github.com/andrewsykim)) [SIG Apps] - EndpointSlice has a new NodeName field guarded by the EndpointSliceNodeName feature gate. - EndpointSlice topology field will be deprecated in an upcoming release. - EndpointSlice \"IP\" address type is formally removed after being deprecated in Kubernetes 1.17. - The discovery.k8s.io/v1alpha1 API is deprecated and will be removed in Kubernetes 1.21. ([#96440](https://github.com/kubernetes/kubernetes/pull/96440), [@robscott](https://github.com/robscott)) [SIG API Machinery, Apps and Network] - External facing API podresources is now available under k8s.io/kubelet/pkg/apis/ ([#92632](https://github.com/kubernetes/kubernetes/pull/92632), [@RenaudWasTaken](https://github.com/RenaudWasTaken)) [SIG Node and Testing] - Fewer candidates are enumerated for preemption to improve performance in large clusters. ([#94814](https://github.com/kubernetes/kubernetes/pull/94814), [@adtac](https://github.com/adtac)) - Fix conversions for custom metrics. ([#94481](https://github.com/kubernetes/kubernetes/pull/94481), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery and Instrumentation] - GPU metrics provided by kubelet are now disabled by default. ([#95184](https://github.com/kubernetes/kubernetes/pull/95184), [@RenaudWasTaken](https://github.com/RenaudWasTaken)) - If BoundServiceAccountTokenVolume is enabled, cluster admins can use metric `serviceaccount_stale_tokens_total` to monitor workloads that are depending on the extended tokens. If there are no such workloads, turn off extended tokens by starting `kube-apiserver` with flag `--service-account-extend-token-expiration=false` ([#96273](https://github.com/kubernetes/kubernetes/pull/96273), [@zshihang](https://github.com/zshihang)) [SIG API Machinery and Auth] - Introduce alpha support for exec-based container registry credential provider plugins in the kubelet. ([#94196](https://github.com/kubernetes/kubernetes/pull/94196), [@andrewsykim](https://github.com/andrewsykim)) [SIG Node and Release] - Introduces a metric source for HPAs which allows scaling based on container resource usage. ([#90691](https://github.com/kubernetes/kubernetes/pull/90691), [@arjunrn](https://github.com/arjunrn)) [SIG API Machinery, Apps, Autoscaling and CLI] - Kube-apiserver now deletes expired kube-apiserver Lease objects: - The feature is under feature gate `APIServerIdentity`. - A flag is added to kube-apiserver: `identity-lease-garbage-collection-check-period-seconds` ([#95895](https://github.com/kubernetes/kubernetes/pull/95895), [@roycaihw](https://github.com/roycaihw)) [SIG API Machinery, Apps, Auth and Testing] - Kube-controller-manager: volume plugins can be restricted from contacting local and loopback addresses by setting `--volume-host-allow-local-loopback=false`, or from contacting specific CIDR ranges by setting `--volume-host-cidr-denylist` (for example, `--volume-host-cidr-denylist=127.0.0.1/28,feed::/16`) ([#91785](https://github.com/kubernetes/kubernetes/pull/91785), [@mattcary](https://github.com/mattcary)) [SIG API Machinery, Apps, Auth, CLI, Network, Node, Storage and Testing] - Migrate scheduler, controller-manager and cloud-controller-manager to use LeaseLock ([#94603](https://github.com/kubernetes/kubernetes/pull/94603), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery, Apps, Cloud Provider and Scheduling] - Modify DNS-1123 error messages to indicate that RFC 1123 is not followed exactly ([#94182](https://github.com/kubernetes/kubernetes/pull/94182), [@mattfenwick](https://github.com/mattfenwick)) [SIG API Machinery, Apps, Auth, Network and Node] - Move configurable fsgroup change policy for pods to beta ([#96376](https://github.com/kubernetes/kubernetes/pull/96376), [@gnufied](https://github.com/gnufied)) [SIG Apps and Storage] - New flag is introduced, i.e. --topology-manager-scope=container|pod. The default value is the \"container\" scope. ([#92967](https://github.com/kubernetes/kubernetes/pull/92967), [@cezaryzukowski](https://github.com/cezaryzukowski)) [SIG Instrumentation, Node and Testing] - New parameter `defaultingType` for `PodTopologySpread` plugin allows to use k8s defined or user provided default constraints ([#95048](https://github.com/kubernetes/kubernetes/pull/95048), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - NodeAffinity plugin can be configured with AddedAffinity. ([#96202](https://github.com/kubernetes/kubernetes/pull/96202), [@alculquicondor](https://github.com/alculquicondor)) [SIG Node, Scheduling and Testing] - Promote RuntimeClass feature to GA. Promote node.k8s.io API groups from v1beta1 to v1. ([#95718](https://github.com/kubernetes/kubernetes/pull/95718), [@SergeyKanzhelev](https://github.com/SergeyKanzhelev)) [SIG Apps, Auth, Node, Scheduling and Testing] - Reminder: The labels \"failure-domain.beta.kubernetes.io/zone\" and \"failure-domain.beta.kubernetes.io/region\" are deprecated in favor of \"topology.kubernetes.io/zone\" and \"topology.kubernetes.io/region\" respectively.  All users of the \"failure-domain.beta...\" labels should switch to the \"topology...\" equivalents. ([#96033](https://github.com/kubernetes/kubernetes/pull/96033), [@thockin](https://github.com/thockin)) [SIG API Machinery, Apps, CLI, Cloud Provider, Network, Node, Scheduling, Storage and Testing] - Server Side Apply now treats LabelSelector fields as atomic (meaning the entire selector is managed by a single writer and updated together), since they contain interrelated and inseparable fields that do not merge in intuitive ways. ([#93901](https://github.com/kubernetes/kubernetes/pull/93901), [@jpbetz](https://github.com/jpbetz)) [SIG API Machinery, Auth, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Network, Node, Storage and Testing] - Services will now have a `clusterIPs` field to go with `clusterIP`.  `clusterIPs[0]` is a synonym for `clusterIP` and will be syncronized on create and update operations. ([#95894](https://github.com/kubernetes/kubernetes/pull/95894), [@thockin](https://github.com/thockin)) [SIG Network] - The ServiceAccountIssuerDiscovery feature gate is now Beta and enabled by default. ([#91921](https://github.com/kubernetes/kubernetes/pull/91921), [@mtaufen](https://github.com/mtaufen)) [SIG Auth] - The status of v1beta1 CRDs without \"preserveUnknownFields:false\" now shows a violation, \"spec.preserveUnknownFields: Invalid value: true: must be false\". ([#93078](https://github.com/kubernetes/kubernetes/pull/93078), [@vareti](https://github.com/vareti)) - The usage of mixed protocol values in the same LoadBalancer Service is possible if the new feature gate MixedProtocolLBService is enabled. The feature gate is disabled by default. The user has to enable it for the API Server. ([#94028](https://github.com/kubernetes/kubernetes/pull/94028), [@janosi](https://github.com/janosi)) [SIG API Machinery and Apps] - This PR will introduce a feature gate CSIServiceAccountToken with two additional fields in `CSIDriverSpec`. ([#93130](https://github.com/kubernetes/kubernetes/pull/93130), [@zshihang](https://github.com/zshihang)) [SIG API Machinery, Apps, Auth, CLI, Network, Node, Storage and Testing] - Users can try the cronjob controller v2 using the feature gate. This will be the default controller in future releases. ([#93370](https://github.com/kubernetes/kubernetes/pull/93370), [@alaypatel07](https://github.com/alaypatel07)) [SIG API Machinery, Apps, Auth and Testing] - VolumeSnapshotDataSource moves to GA in 1.20 release ([#95282](https://github.com/kubernetes/kubernetes/pull/95282), [@xing-yang](https://github.com/xing-yang)) [SIG Apps] - WinOverlay feature graduated to beta ([#94807](https://github.com/kubernetes/kubernetes/pull/94807), [@ksubrmnn](https://github.com/ksubrmnn)) [SIG Windows] ### 기능(feature) - **Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.**: - A new metric `apiserver_request_filter_duration_seconds` has been introduced that measures request filter latency in seconds. ([#95207](https://github.com/kubernetes/kubernetes/pull/95207), [@tkashem](https://github.com/tkashem)) [SIG API Machinery and Instrumentation] - A new set of alpha metrics are reported by the Kubernetes scheduler under the `/metrics/resources` endpoint that allow administrators to easily see the resource consumption (requests and limits for all resources on the pods) and compare it to actual pod usage or node capacity. ([#94866](https://github.com/kubernetes/kubernetes/pull/94866), [@smarterclayton](https://github.com/smarterclayton)) [SIG API Machinery, Instrumentation, Node and Scheduling] - Add --experimental-logging-sanitization flag enabling runtime protection from leaking sensitive data in logs ([#96370](https://github.com/kubernetes/kubernetes/pull/96370), [@serathius](https://github.com/serathius)) [SIG API Machinery, Cluster Lifecycle and Instrumentation] - Add a StorageVersionAPI feature gate that makes API server update storageversions before serving certain write requests. This feature allows the storage migrator to manage storage migration for built-in resources. Enabling internal.apiserver.k8s.io/v1alpha1 API and APIServerIdentity feature gate are required to use this feature. ([#93873](https://github.com/kubernetes/kubernetes/pull/93873), [@roycaihw](https://github.com/roycaihw)) [SIG API Machinery, Auth and Testing] - Add a metric for time taken to perform recursive permission change ([#95866](https://github.com/kubernetes/kubernetes/pull/95866), [@JornShen](https://github.com/JornShen)) [SIG Instrumentation and Storage] - Add a new `vSphere` metric: `cloudprovider_vsphere_vcenter_versions`. It's content show `vCenter` hostnames with the associated server version. ([#94526](https://github.com/kubernetes/kubernetes/pull/94526), [@Danil-Grigorev](https://github.com/Danil-Grigorev)) [SIG Cloud Provider and Instrumentation] - Add a new flag to set priority for the kubelet on Windows nodes so that workloads cannot overwhelm the node there by disrupting kubelet process. ([#96051](https://github.com/kubernetes/kubernetes/pull/96051), [@ravisantoshgudimetla](https://github.com/ravisantoshgudimetla)) [SIG Node and Windows] - Add feature to size memory backed volumes ([#94444](https://github.com/kubernetes/kubernetes/pull/94444), [@derekwaynecarr](https://github.com/derekwaynecarr)) [SIG Storage and Testing] - Add foreground cascading deletion to kubectl with the new `kubectl delete foreground|background|orphan` option. ([#93384](https://github.com/kubernetes/kubernetes/pull/93384), [@zhouya0](https://github.com/zhouya0)) - Add metrics for azure service operations (route and loadbalancer). ([#94124](https://github.com/kubernetes/kubernetes/pull/94124), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider and Instrumentation] - Add network rule support in Azure account creation. ([#94239](https://github.com/kubernetes/kubernetes/pull/94239), [@andyzhangx](https://github.com/andyzhangx)) - Add node_authorizer_actions_duration_seconds metric that can be used to estimate load to node authorizer. ([#92466](https://github.com/kubernetes/kubernetes/pull/92466), [@mborsz](https://github.com/mborsz)) [SIG API Machinery, Auth and Instrumentation] - Add pod_ based CPU and memory metrics to Kubelet's  /metrics/resource endpoint ([#95839](https://github.com/kubernetes/kubernetes/pull/95839), [@egernst](https://github.com/egernst)) [SIG Instrumentation, Node and Testing] - Added `get-users` and `delete-user` to the `kubectl config` subcommand ([#89840](https://github.com/kubernetes/kubernetes/pull/89840), [@eddiezane](https://github.com/eddiezane)) [SIG CLI] - Added counter metric \"apiserver_request_self\" to count API server self-requests with labels for verb, resource, and subresource. ([#94288](https://github.com/kubernetes/kubernetes/pull/94288), [@LogicalShark](https://github.com/LogicalShark)) [SIG API Machinery, Auth, Instrumentation and Scheduling] - Added new k8s.io/component-helpers repository providing shared helper code for (core) components. ([#92507](https://github.com/kubernetes/kubernetes/pull/92507), [@ingvagabund](https://github.com/ingvagabund)) [SIG Apps, Node, Release and Scheduling] - Adds `create ingress` command to `kubectl` ([#78153](https://github.com/kubernetes/kubernetes/pull/78153), [@amimof](https://github.com/amimof)) [SIG CLI and Network] - Adds a headless service on node-local-cache addon. ([#88412](https://github.com/kubernetes/kubernetes/pull/88412), [@stafot](https://github.com/stafot)) [SIG Cloud Provider and Network] - Allow cross compilation of kubernetes on different platforms. ([#94403](https://github.com/kubernetes/kubernetes/pull/94403), [@bnrjee](https://github.com/bnrjee)) [SIG Release] - Azure: Support multiple services sharing one IP address ([#94991](https://github.com/kubernetes/kubernetes/pull/94991), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - CRDs: For structural schemas, non-nullable null map fields will now be dropped and defaulted if a default is available. null items in list will continue being preserved, and fail validation if not nullable. ([#95423](https://github.com/kubernetes/kubernetes/pull/95423), [@apelisse](https://github.com/apelisse)) [SIG API Machinery] - Changed: default \"Accept: */*\" header added to HTTP probes. See https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#http-probes (https://github.com/kubernetes/website/pull/24756) ([#95641](https://github.com/kubernetes/kubernetes/pull/95641), [@fonsecas72](https://github.com/fonsecas72)) [SIG Network and Node] - Client-go credential plugins can now be passed in the current cluster information via the KUBERNETES_EXEC_INFO environment variable. ([#95489](https://github.com/kubernetes/kubernetes/pull/95489), [@ankeesler](https://github.com/ankeesler)) [SIG API Machinery and Auth] - Command to start network proxy changes from 'KUBE_ENABLE_EGRESS_VIA_KONNECTIVITY_SERVICE ./cluster/kube-up.sh' to 'KUBE_ENABLE_KONNECTIVITY_SERVICE=true ./hack/kube-up.sh' ([#92669](https://github.com/kubernetes/kubernetes/pull/92669), [@Jefftree](https://github.com/Jefftree)) [SIG Cloud Provider] - Configure AWS LoadBalancer health check protocol via service annotations. ([#94546](https://github.com/kubernetes/kubernetes/pull/94546), [@kishorj](https://github.com/kishorj)) - DefaultPodTopologySpread graduated to Beta. The feature gate is enabled by default. ([#95631](https://github.com/kubernetes/kubernetes/pull/95631), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling and Testing] - E2e test for PodFsGroupChangePolicy ([#96247](https://github.com/kubernetes/kubernetes/pull/96247), [@saikat-royc](https://github.com/saikat-royc)) [SIG Storage and Testing] - Ephemeral containers now apply the same API defaults as initContainers and containers ([#94896](https://github.com/kubernetes/kubernetes/pull/94896), [@wawa0210](https://github.com/wawa0210)) [SIG Apps and CLI] - Gradudate the Pod Resources API to G.A Introduces the pod_resources_endpoint_requests_total metric which tracks the total number of requests to the pod resources API ([#92165](https://github.com/kubernetes/kubernetes/pull/92165), [@RenaudWasTaken](https://github.com/RenaudWasTaken)) [SIG Instrumentation, Node and Testing] - In dual-stack bare-metal clusters, you can now pass dual-stack IPs to `kubelet --node-ip`. eg: `kubelet --node-ip 10.1.0.5,fd01::0005`. This is not yet supported for non-bare-metal clusters. In dual-stack clusters where nodes have dual-stack addresses, hostNetwork pods will now get dual-stack PodIPs. ([#95239](https://github.com/kubernetes/kubernetes/pull/95239), [@danwinship](https://github.com/danwinship)) [SIG Network and Node] - Introduce api-extensions category which will return: mutating admission configs, validating admission configs, CRDs and APIServices when used in kubectl get, for example. ([#95603](https://github.com/kubernetes/kubernetes/pull/95603), [@soltysh](https://github.com/soltysh)) [SIG API Machinery] - Introduces a new GCE specific cluster creation variable KUBE_PROXY_DISABLE. When set to true, this will skip over the creation of kube-proxy (whether the daemonset or static pod). This can be used to control the lifecycle of kube-proxy separately from the lifecycle of the nodes. ([#91977](https://github.com/kubernetes/kubernetes/pull/91977), [@varunmar](https://github.com/varunmar)) [SIG Cloud Provider] - Kube-apiserver now maintains a Lease object to identify itself: - The feature is under feature gate `APIServerIdentity`. - Two flags are added to kube-apiserver: `identity-lease-duration-seconds`, `identity-lease-renew-interval-seconds` ([#95533](https://github.com/kubernetes/kubernetes/pull/95533), [@roycaihw](https://github.com/roycaihw)) [SIG API Machinery] - Kube-apiserver: The timeout used when making health check calls to etcd can now be configured with `--etcd-healthcheck-timeout`. The default timeout is 2 seconds, matching the previous behavior. ([#93244](https://github.com/kubernetes/kubernetes/pull/93244), [@Sh4d1](https://github.com/Sh4d1)) [SIG API Machinery] - Kube-apiserver: added support for compressing rotated audit log files with `--audit-log-compress` ([#94066](https://github.com/kubernetes/kubernetes/pull/94066), [@lojies](https://github.com/lojies)) [SIG API Machinery and Auth] - Kubeadm now prints warnings instead of throwing errors if the current system time is outside of the NotBefore and NotAfter bounds of a loaded certificate.  ([#94504](https://github.com/kubernetes/kubernetes/pull/94504), [@neolit123](https://github.com/neolit123)) - Kubeadm: Add a preflight check that the control-plane node has at least 1700MB of RAM ([#93275](https://github.com/kubernetes/kubernetes/pull/93275), [@xlgao-zju](https://github.com/xlgao-zju)) [SIG Cluster Lifecycle] - Kubeadm: add the \"--cluster-name\" flag to the \"kubeadm alpha kubeconfig user\" to allow configuring the cluster name in the generated kubeconfig file ([#93992](https://github.com/kubernetes/kubernetes/pull/93992), [@prabhu43](https://github.com/prabhu43)) [SIG Cluster Lifecycle] - Kubeadm: add the \"--kubeconfig\" flag to the \"kubeadm init phase upload-certs\" command to allow users to pass a custom location for a kubeconfig file. ([#94765](https://github.com/kubernetes/kubernetes/pull/94765), [@zhanw15](https://github.com/zhanw15)) [SIG Cluster Lifecycle] - Kubeadm: make etcd pod request 100m CPU, 100Mi memory and 100Mi ephemeral_storage by default ([#94479](https://github.com/kubernetes/kubernetes/pull/94479), [@knight42](https://github.com/knight42)) [SIG Cluster Lifecycle] - Kubeadm: make the command \"kubeadm alpha kubeconfig user\" accept a \"--config\" flag and remove the following flags: - apiserver-advertise-address / apiserver-bind-port: use either localAPIEndpoint from InitConfiguration or controlPlaneEndpoint from ClusterConfiguration. - cluster-name: use clusterName from ClusterConfiguration - cert-dir: use certificatesDir from ClusterConfiguration ([#94879](https://github.com/kubernetes/kubernetes/pull/94879), [@knight42](https://github.com/knight42)) [SIG Cluster Lifecycle] - Kubectl create now supports creating ingress objects. ([#94327](https://github.com/kubernetes/kubernetes/pull/94327), [@rikatz](https://github.com/rikatz)) [SIG CLI and Network] - Kubectl rollout history sts/sts-name --revision=some-revision will start showing the detailed view of  the sts on that specified revision ([#86506](https://github.com/kubernetes/kubernetes/pull/86506), [@dineshba](https://github.com/dineshba)) [SIG CLI] - Kubectl: Previously users cannot provide arguments to a external diff tool via KUBECTL_EXTERNAL_DIFF env. This release now allow users to specify args to KUBECTL_EXTERNAL_DIFF env. ([#95292](https://github.com/kubernetes/kubernetes/pull/95292), [@dougsland](https://github.com/dougsland)) [SIG CLI] - Kubemark now supports both real and hollow nodes in a single cluster. ([#93201](https://github.com/kubernetes/kubernetes/pull/93201), [@ellistarn](https://github.com/ellistarn)) [SIG Scalability] - Kubernetes E2E test image manifest lists now contain Windows images. ([#77398](https://github.com/kubernetes/kubernetes/pull/77398), [@claudiubelu](https://github.com/claudiubelu)) [SIG Testing and Windows] - Kubernetes is now built using go1.15.2 - build: Update to k/repo-infra@v0.1.1 (supports go1.15.2) - build: Use go-runner:buster-v2.0.1 (built using go1.15.1) - bazel: Replace --features with Starlark build settings flag - hack/lib/util.sh: some bash cleanups - switched one spot to use kube::logging - make kube::util::find-binary return an error when it doesn't find anything so that hack scripts fail fast instead of with '' binary not found errors. - this required deleting some genfeddoc stuff. the binary no longer exists in k/k repo since we removed federation/, and I don't see it in https://github.com/kubernetes-sigs/kubefed/ either. I'm assuming that it's gone for good now. - bazel: output go_binary rule directly from go_binary_conditional_pure From: [@mikedanese](https://github.com/mikedanese): Instead of aliasing. Aliases are annoying in a number of ways. This is specifically bugging me now because they make the action graph harder to analyze programmatically. By using aliases here, we would need to handle potentially aliased go_binary targets and dereference to the effective target. The comment references an issue with `pure = select(...)` which appears to be resolved considering this now builds. - make kube::util::find-binary not dependent on bazel-out/ structure Implement an aspect that outputs go_build_mode metadata for go binaries, and use that during binary selection. ([#94449](https://github.com/kubernetes/kubernetes/pull/94449), [@justaugustus](https://github.com/justaugustus)) [SIG Architecture, CLI, Cluster Lifecycle, Node, Release and Testing] - Kubernetes is now built using go1.15.5 - build: Update to k/repo-infra@v0.1.2 (supports go1.15.5) ([#95776](https://github.com/kubernetes/kubernetes/pull/95776), [@justaugustus](https://github.com/justaugustus)) [SIG Cloud Provider, Instrumentation, Release and Testing] - New default scheduling plugins order reduces scheduling and preemption latency when taints and node affinity are used ([#95539](https://github.com/kubernetes/kubernetes/pull/95539), [@soulxu](https://github.com/soulxu)) [SIG Scheduling] - Only update Azure data disks when attach/detach ([#94265](https://github.com/kubernetes/kubernetes/pull/94265), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Promote SupportNodePidsLimit to GA to provide node-to-pod PID isolation. Promote SupportPodPidsLimit to GA to provide ability to limit PIDs per pod. ([#94140](https://github.com/kubernetes/kubernetes/pull/94140), [@derekwaynecarr](https://github.com/derekwaynecarr)) - SCTP support in API objects (Pod, Service, NetworkPolicy) is now GA. Note that this has no effect on whether SCTP is enabled on nodes at the kernel level, and note that some cloud platforms and network plugins do not support SCTP traffic. ([#95566](https://github.com/kubernetes/kubernetes/pull/95566), [@danwinship](https://github.com/danwinship)) [SIG Apps and Network] - Scheduler now ignores Pod update events if the resourceVersion of old and new Pods are identical. ([#96071](https://github.com/kubernetes/kubernetes/pull/96071), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling] - Scheduling Framework: expose Run[Pre]ScorePlugins functions to PreemptionHandle which can be used in PostFilter extention point. ([#93534](https://github.com/kubernetes/kubernetes/pull/93534), [@everpeace](https://github.com/everpeace)) [SIG Scheduling and Testing] - SelectorSpreadPriority maps to PodTopologySpread plugin when DefaultPodTopologySpread feature is enabled ([#95448](https://github.com/kubernetes/kubernetes/pull/95448), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - Send GCE node startup scripts logs to console and journal. ([#95311](https://github.com/kubernetes/kubernetes/pull/95311), [@karan](https://github.com/karan)) - SetHostnameAsFQDN has been graduated to Beta and therefore it is enabled by default. ([#95267](https://github.com/kubernetes/kubernetes/pull/95267), [@javidiaz](https://github.com/javidiaz)) [SIG Node] - Support [service.beta.kubernetes.io/azure-pip-ip-tags] annotations to allow customers to specify ip-tags to influence public-ip creation in Azure [Tag1=Value1, Tag2=Value2, etc.] ([#94114](https://github.com/kubernetes/kubernetes/pull/94114), [@MarcPow](https://github.com/MarcPow)) [SIG Cloud Provider] - Support custom tags for cloud provider managed resources ([#96450](https://github.com/kubernetes/kubernetes/pull/96450), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - Support customize load balancer health probe protocol and request path ([#96338](https://github.com/kubernetes/kubernetes/pull/96338), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - Support for Windows container images (OS Versions: 1809, 1903, 1909, 2004) was added the pause:3.4 image. ([#91452](https://github.com/kubernetes/kubernetes/pull/91452), [@claudiubelu](https://github.com/claudiubelu)) [SIG Node, Release and Windows] - Support multiple standard load balancers in one cluster ([#96111](https://github.com/kubernetes/kubernetes/pull/96111), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - The beta `RootCAConfigMap` feature gate is enabled by default and causes kube-controller-manager to publish a \"kube-root-ca.crt\" ConfigMap to every namespace. This ConfigMap contains a CA bundle used for verifying connections to the kube-apiserver. ([#96197](https://github.com/kubernetes/kubernetes/pull/96197), [@zshihang](https://github.com/zshihang)) [SIG API Machinery, Apps, Auth and Testing] - The kubelet_runtime_operations_duration_seconds metric buckets were set to 0.005 0.0125 0.03125 0.078125 0.1953125 0.48828125 1.220703125 3.0517578125 7.62939453125 19.073486328125 47.6837158203125 119.20928955078125 298.0232238769531 and 745.0580596923828 seconds ([#96054](https://github.com/kubernetes/kubernetes/pull/96054), [@alvaroaleman](https://github.com/alvaroaleman)) [SIG Instrumentation and Node] - There is a new pv_collector_total_pv_count metric that counts persistent volumes by the volume plugin name and volume mode. ([#95719](https://github.com/kubernetes/kubernetes/pull/95719), [@tsmetana](https://github.com/tsmetana)) [SIG Apps, Instrumentation, Storage and Testing] - Volume snapshot e2e test to validate PVC and VolumeSnapshotContent finalizer ([#95863](https://github.com/kubernetes/kubernetes/pull/95863), [@RaunakShah](https://github.com/RaunakShah)) [SIG Cloud Provider, Storage and Testing] - Warns user when executing kubectl apply/diff to resource currently being deleted. ([#95544](https://github.com/kubernetes/kubernetes/pull/95544), [@SaiHarshaK](https://github.com/SaiHarshaK)) [SIG CLI] - `kubectl alpha debug` has graduated to beta and is now `kubectl debug`. ([#96138](https://github.com/kubernetes/kubernetes/pull/96138), [@verb](https://github.com/verb)) [SIG CLI and Testing] - `kubectl debug` gains support for changing container images when copying a pod for debugging, similar to how `kubectl set image` works. See `kubectl help debug` for more information. ([#96058](https://github.com/kubernetes/kubernetes/pull/96058), [@verb](https://github.com/verb)) [SIG CLI] </ins> ### 문서 <del> - 샘플 앱 배포 지침이 변경되었다. ([#82785](https://github.com/kubernetes/kubernetes/pull/82785), [@ashish-billore](https://github.com/ashish-billore)) [SIG API Machinery] </del> <ins> - Fake dynamic client: document that List does not preserve TypeMeta in UnstructuredList ([#95117](https://github.com/kubernetes/kubernetes/pull/95117), [@andrewsykim](https://github.com/andrewsykim)) [SIG API Machinery] - Kubelet: remove alpha warnings for CNI flags. ([#94508](https://github.com/kubernetes/kubernetes/pull/94508), [@andrewsykim](https://github.com/andrewsykim)) [SIG Network and Node] - Updates docs and guidance on cloud provider InstancesV2 and Zones interface for external cloud providers: - removes experimental warning for InstancesV2 - document that implementation of InstancesV2 will disable calls to Zones - deprecate Zones in favor of InstancesV2 ([#96397](https://github.com/kubernetes/kubernetes/pull/96397), [@andrewsykim](https://github.com/andrewsykim)) [SIG Cloud Provider] </ins> ### 실패 테스트 <del> - Kube-proxy iptables min-sync-period 의 기본값은 1초로 변경되었다. (이전 값은 0 이다.) ([#92836](https://github.com/kubernetes/kubernetes/pull/92836), [@aojea](https://github.com/aojea)) [SIG Network] ### 버그 또는 회귀(Regression) - 인-트리 소스의 PV 집합은 CSIPersistentVolumeSource로 변환될 때 노드 어피니티에서 주문된 요구사항 값을 갖는다. ([#88987](https://github.com/kubernetes/kubernetes/pull/88987), [@jiahuif](https://github.com/jiahuif)) [SIG Storage] - `informer-sync` 헬스 체커로 인한 apiserver의 패닉이 수정되었다. ([#93600](https://github.com/kubernetes/kubernetes/pull/93600), [@ialidzhikov](https://github.com/ialidzhikov)) [SIG API Machinery] - 이제 GCP cloud-controller-manager 가 클러스터 외부에서 실행되어 새 노드를 초기화하지 못하는 문제가 수정되었다. ([#90057](https://github.com/kubernetes/kubernetes/pull/90057), [@ialidzhikov](https://github.com/ialidzhikov)) [SIG Apps 및 Cloud Provider] - Kubelets 용 GCE CloudProvider를 초기화 할 때 GCE API 호출을 하지 않는다. ([#90218](https://github.com/kubernetes/kubernetes/pull/90218), [@wojtek-t](https://github.com/wojtek-t)) [SIG Cloud Provider 및 Scalability] - IP 별칭을 추가하거나 GCE 클라우드 제공 업체의 노드 객체에 반영할 때, 불필요한 GCE API 호출을 하지 않는다. ([#90242](https://github.com/kubernetes/kubernetes/pull/90242), [@wojtek-t](https://github.com/wojtek-t)) [SIG Apps, Cloud Provider 및 Network] - 파드가 스케줄 되는 동안, 어노테이션이 변경될 때 불필요한 스케줄링 변동을 방지한다. ([#90373](https://github.com/kubernetes/kubernetes/pull/90373), [@fabiokung](https://github.com/fabiokung)) [SIG Scheduling] - kubectl 용 Azure 인증 모듈은 이제 갱신 토큰이 만료된 후에 로그인을 요청한다. ([#86481](https://github.com/kubernetes/kubernetes/pull/86481), [@tdihp](https://github.com/tdihp)) [SIG API Machinery 및 Auth] - Azure: lb 생성시 발생하는 동시성 해결 ([#89604](https://github.com/kubernetes/kubernetes/pull/89604), [@aramase](https://github.com/aramase)) [SIG Cloud Provider] - Azure: 연결된 VMSS 가 많은 클러스터에서 스로틀링(throttling)을 방지하기 위해 전역 VMSS VMs 캐시를 VMSS 별 VM 캐시로 전환하였다. ([#93107](https://github.com/kubernetes/kubernetes/pull/93107), [@bpineau](https://github.com/bpineau)) [SIG Cloud Provider] - Azure: IPv6 인바운드 보안 규칙에 대한 대상 접두사 및 포트를 설정하였다. ([#91831](https://github.com/kubernetes/kubernetes/pull/91831), [@aramase](https://github.com/aramase)) [SIG Cloud Provider] - 베이스-이미지: kube-cross:v1.13.9-5 으로 업데이트 되었다. ([#90963](https://github.com/kubernetes/kubernetes/pull/90963), [@justaugustus](https://github.com/justaugustus)) [SIG Release 및 Testing] - 기존 servicePort의 nodePort가 수동으로 변경된 경우 AWS NLB 서비스에 대한 버그가 수정되었다. ([#89562](https://github.com/kubernetes/kubernetes/pull/89562), [@M00nF1sh](https://github.com/M00nF1sh)) [SIG Cloud Provider] - APIServer에 연결할 수 없거나 kubelet에 아직 올바른 자격증명이 없는 경우, CSINode 초기화는 시작할때 kubelet을 중단하지 않는다. ([#89589](https://github.com/kubernetes/kubernetes/pull/89589), [@jsafrane](https://github.com/jsafrane)) [SIG Storage] - CVE-2020-8557 (Medium): 컨테이너의 /etc/hosts 파일을 통한 노드-로컬 간 서비스 거부. 자세한 내용은 https://github.com/kubernetes/kubernetes/issues/93032 을 참조한다. ([#92916](https://github.com/kubernetes/kubernetes/pull/92916), [@joelsmith](https://github.com/joelsmith)) [SIG Node] - Client-go: watch를 재구성하는 대신 타임아웃이 발생하면, 정보 제공자가 전체 목록 요청으로 돌아가는 문제가 해결되었다. ([#89652](https://github.com/kubernetes/kubernetes/pull/89652), [@liggitt](https://github.com/liggitt)) [SIG API Machinery 및 Testing] - CloudNodeLifecycleController는 노드 모니터링을 할 때, 셧다운 상태 전에 노드의 존재 상태를 확인하게 된다. ([#90737](https://github.com/kubernetes/kubernetes/pull/90737), [@jiahuif](https://github.com/jiahuif)) [SIG Apps 및 Cloud Provider] - `startupProbe` 는 지정하지만 `readinessProbe` 는 지정하지 않은 컨테이너는 이전에는 `startupProbe` 가 완료되기 전에 \"준비(ready)\"된 것으로 간주되었지만 이제는 \"준비되지 않은(not-ready)\" 것으로 간주된다. ([#92196](https://github.com/kubernetes/kubernetes/pull/92196), [@thockin](https://github.com/thockin)) [SIG Node] - 이제 Cordon 된 노드가 AWS 대상 그룹에서 등록 취소된다. ([#85920](https://github.com/kubernetes/kubernetes/pull/85920), [@hoelzro](https://github.com/hoelzro)) [SIG Cloud Provider] - kubernetes.azure.com/managed=false 레이블이 지정된 노드를 로드 밸런서의 백엔드 풀에 추가하지 않는다. ([#93034](https://github.com/kubernetes/kubernetes/pull/93034), [@matthias50](https://github.com/matthias50)) [SIG Cloud Provider] - CSI 드라이버가 FailedPrecondition 오류를 반환하는 경우 볼륨 확장을 재시도 하지 않는다. ([#92986](https://github.com/kubernetes/kubernetes/pull/92986), [@gnufied](https://github.com/gnufied)) [SIG Node 및 Storage] - Dockershim 보안: 이제 파드 샌드박스가 항상 `no-new-privileges` 및 `runtime/default` seccomp 프로필로 실행된다. dockershim seccomp: 이제 파드 수준에서 설정할 때 사용자 지정 프로필이 더 작은 seccomp 프로필을 가질 수 있다. ([#90948](https://github.com/kubernetes/kubernetes/pull/90948), [@pjbgf](https://github.com/pjbgf)) [SIG Node] - 이중-스택: 서비스 clusterIP가 지정된 ipFamily를 따르지 않는 버그가 수정되었다. ([#89612](https://github.com/kubernetes/kubernetes/pull/89612), [@SataQiu](https://github.com/SataQiu)) [SIG Network] - EndpointSliceMirroring 컨트롤러는 이제 엔드포인트에서 엔드포인트슬라이스로 레이블을 복사한다. ([#93442](https://github.com/kubernetes/kubernetes/pull/93442), [@robscott](https://github.com/robscott)) [SIG Apps 및 Network] - Azure 가용성 영역(availability zone)이 항상 소문자인지 확인한다. ([#89722](https://github.com/kubernetes/kubernetes/pull/89722), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - DeletionTimestamp가 0이 아닌 파드에 대한 축출 요청이 항상 성공하게 된다. ([#91342](https://github.com/kubernetes/kubernetes/pull/91342), [@michaelgugino](https://github.com/michaelgugino)) [SIG Apps] - 리소스 이름이 내장 오브젝트와 동일한 CRD를 설명한다. ([#89505](https://github.com/kubernetes/kubernetes/pull/89505), [@knight42](https://github.com/knight42)) [SIG API Machinery, CLI 및 Testing] - 내부 정보가 동기화 되었는지를 확인하는 새로운 \"informer-sync\" 검사로 kube-apiserver의 /readyz 를 확장한다. ([#92644](https://github.com/kubernetes/kubernetes/pull/92644), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery 및 Testing] - winkernel kube-proxy 에 있는 DSR 로드밸런서 버전이 HNS 버전 9.3-9.max, 10.2+ 로 확장되었다. ([#93080](https://github.com/kubernetes/kubernetes/pull/93080), [@elweb9858](https://github.com/elweb9858)) [SIG Network] - 필수 어피니티 용어가 있는 첫번째 파드는 토폴로지 키가 일치하는 노드에서만 예약할 수 있게 된다. ([#91168](https://github.com/kubernetes/kubernetes/pull/91168), [@ahg-g](https://github.com/ahg-g)) [SIG Scheduling] - 연결 해제된 상태의 CIDR이 존재하는 경우에 대한 AWS 로드밸런서 VPC CIDR 계산이 수정되었다. ([#92227](https://github.com/kubernetes/kubernetes/pull/92227), [@M00nF1sh](https://github.com/M00nF1sh)) [SIG Cloud Provider] - 관리되지 않는 노드에 대한 InstanceMetadataByProviderID 가 수정되었다. ([#92572](https://github.com/kubernetes/kubernetes/pull/92572), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - 고객이 VMSS orchestrationMode를 설정한 경우 `VirtualMachineScaleSets.virtualMachines.GET` 이 허용되지 않았던 문제가 수정되었다. ([#91097](https://github.com/kubernetes/kubernetes/pull/91097), [@feiskyer](https://github.com/feiskyer)) - 앞에 0이 있는 IPv6 주소 사용을 허용하지 않던 버그가 수정되었다. ([#89341](https://github.com/kubernetes/kubernetes/pull/89341), [@aojea](https://github.com/aojea)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle 및 Instrumentation] - ExternalTrafficPolicy 가 ExternalIPs 서비스에 적용되지 않던 버그를 수정하였다. ([#90537](https://github.com/kubernetes/kubernetes/pull/90537), [@freehan](https://github.com/freehan)) [SIG Network] - VMSS 캐시에서 nil VM 항목이 만료될 때의 조건이 수정되었다. ([#92681](https://github.com/kubernetes/kubernetes/pull/92681), [@ArchangelSDY](https://github.com/ArchangelSDY)) [SIG Cloud Provider] - 스케줄러가 불필요한 스케줄 시도를 수행할 수 있는 레이싱(racing) 이슈가 수정되었다. ([#90660](https://github.com/kubernetes/kubernetes/pull/90660), [@Huang-Wei](https://github.com/Huang-Wei)) - 수정된 컨피그맵 또는 시크릿 하위 경로(subpath)의 볼륨 마운트를 사용하여 컨테이너가 다시 시작되는 문제가 수정되었다. ([#89629](https://github.com/kubernetes/kubernetes/pull/89629), [@fatedier](https://github.com/fatedier)) [SIG Architecture, Storage 및 Testing] - 다중 마스터 HA 클러스터에서 정적으로 할당 된 portNumber가 있는 NodePort 생성이 충돌하는 포트 할당 로직 버그가 수정되었다. ([#89937](https://github.com/kubernetes/kubernetes/pull/89937), [@aojea](https://github.com/aojea)) [SIG Network 및 Testing] - xfs_repair가 xfs 마운트를 중지하는 버그가 수정되었다. ([#89444](https://github.com/kubernetes/kubernetes/pull/89444), [@gnufied](https://github.com/gnufied)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation 및 Storage] - 클러스터 덤프 정보에 대한 네임스페이스 플래그가 작동하지 않는 문제가 수정되었다. ([#91890](https://github.com/kubernetes/kubernetes/pull/91890), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - OOM 으로 컨테이너가 손상된 경우, SystemOOM 감지에 대한 버그가 수정되었다. ([#88871](https://github.com/kubernetes/kubernetes/pull/88871), [@dashpole](https://github.com/dashpole)) [SIG Node] - 이미지 파일 시스템 감지, devicemapper에 대한 디스크 메트릭, 5.0+ 리눅스 커널에서 OOM Kill 감지에 대한 버그가 수정되었다. ([#92919](https://github.com/kubernetes/kubernetes/pull/92919), [@dashpole](https://github.com/dashpole)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation 및 Node] - etcd 이미지에서 etcd 버전 마이그레이션 스크립트가 수정되었다. ([#91925](https://github.com/kubernetes/kubernetes/pull/91925), [@wenjiaswe](https://github.com/wenjiaswe)) [SIG API Machinery] - Azure 파일 CSI 번역의 결함이 수정되었다. ([#90162](https://github.com/kubernetes/kubernetes/pull/90162), [@rfranzke](https://github.com/rfranzke)) [SIG Release 및 Storage] - 짧은 시간에 Azure 노드를 다시 만들 경우, 인스턴스를 찾을 수 없는 문제가 수정되었다. ([#93316](https://github.com/kubernetes/kubernetes/pull/93316), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - 지원되는 거대 페이지의 크기를 변경할 시 발생하는 문제가 수정되었다. ([#80831](https://github.com/kubernetes/kubernetes/pull/80831), [@odinuge](https://github.com/odinuge)) [SIG Node 및 Testing] - 준비 상태(readiness)를 보고하기 전까지 APIServices가 HTTP 핸들러에 설치될 때까지 기다리도록 kube-apiserver 시작 작업이 수정되었다. ([#89147](https://github.com/kubernetes/kubernetes/pull/89147), [@sttts](https://github.com/sttts)) [SIG API Machinery] - kubectl create --dryrun 클라이언트가 네임스페이스를 무시하는 문제가 수정되었다. ([#90502](https://github.com/kubernetes/kubernetes/pull/90502), [@zhouya0](https://github.com/zhouya0)) - kubectl create secret docker-registry 명령어의 --from-file 플래그를 사용할 수 없는 문제가 수정되었다. ([#90960](https://github.com/kubernetes/kubernetes/pull/90960), [@zhouya0](https://github.com/zhouya0)) [SIG CLI 및 Testing] - kubectl describe CSINode 명령어의 nil pointer 에러가 수정되었다. ([#89646](https://github.com/kubernetes/kubernetes/pull/89646), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - 리스(Lease) 정보에 접근할 수 없는 사용자를 위해 kubectl describe node 명령어가 수정되었다. ([#90469](https://github.com/kubernetes/kubernetes/pull/90469), [@uthark](https://github.com/uthark)) [SIG CLI] - 빈 어노테이션에 대한 kubectl describe 명령어의 출력 형식이 수정되었다. ([#91405](https://github.com/kubernetes/kubernetes/pull/91405), [@iyashu](https://github.com/iyashu)) [SIG CLI] - 실제로 패치를 지속하지 않도록 kubectl diff 명령어가 수정되었다. ([#89795](https://github.com/kubernetes/kubernetes/pull/89795), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG CLI 및 Testing] - kubectl run 명령어의 --dry-run=client 플래그가 네임스페이스를 무시하는 문제가 수정되었다. ([#90785](https://github.com/kubernetes/kubernetes/pull/90785), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - kubectl version 명령이 설정 파일 없이 버전 정보를 표시하도록 변경되었다. ([#89913](https://github.com/kubernetes/kubernetes/pull/89913), [@zhouya0](https://github.com/zhouya0)) [SIG API Machinery 및 CLI] - `kubectl alpha debug` 명령어의 `--container` 플래그에 대하여 `-c` 축약표현이 누락된 문제가 수정되었다. ([#89674](https://github.com/kubernetes/kubernetes/pull/89674), [@superbrothers](https://github.com/superbrothers)) [SIG CLI] - 오브젝트의 평균 값이 무시되어 출력되는 문제가 수정되었다. ([#89142](https://github.com/kubernetes/kubernetes/pull/89142), [@zhouya0](https://github.com/zhouya0)) [SIG API Machinery] - Azure VMs에 공용 IP를 할당 한 후 공용 IP가 표시되지 않는 문제가 수정되었다. ([#90886](https://github.com/kubernetes/kubernetes/pull/90886), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - 파드보다 먼저 노드를 제거할 때 스케줄러의 충돌이 일어나는 문제를 수정하였다. ([#89908](https://github.com/kubernetes/kubernetes/pull/89908), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - 로드밸런서 backendPools 에 대해 Azure VMSS를 업데이트 할 때 VMSS 이름 및 리소스 그룹의 이름 수정에 대한 버그가 수정되었다. ([#89337](https://github.com/kubernetes/kubernetes/pull/89337), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Azure VM 컴퓨터 이름의 접두사가 VMSS 이름과 다른 경우의 스로틀링 문제가 해결되었다. ([#92793](https://github.com/kubernetes/kubernetes/pull/92793), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - 수정: Azure 할당 해제 노드가 종료된 것으로 간주 ([#92257](https://github.com/kubernetes/kubernetes/pull/92257), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - 수정: azure 디스크 PV에 대한 GetLabelsForVolume 패닉 문제 ([#92166](https://github.com/kubernetes/kubernetes/pull/92166), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - 수정: 어노테이션 지원에 Azure 파일 마이그레이션 지원 추가 ([#91093](https://github.com/kubernetes/kubernetes/pull/91093), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider 및 Node] - 수정: API 스로틀링(throttling)을 유발할 수 있는 Azure 디스크 댕글링(dangling) 연결 문제 ([#90749](https://github.com/kubernetes/kubernetes/pull/90749), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - 수정: ip 제품군을 기반으로 올바른 ip 결정 ([#93043](https://github.com/kubernetes/kubernetes/pull/93043), [@aramase](https://github.com/aramase)) [SIG Cloud Provider] - 수정: 비어있는 경우 도커 구성 캐시를 사용하지 않음 ([#92330](https://github.com/kubernetes/kubernetes/pull/92330), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - 수정: Azure 디스크 스토리지 클래스 마이그레이션에서 토폴로지 문제 수정 ([#91196](https://github.com/kubernetes/kubernetes/pull/91196), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - 수정: 최대 개수 테이블에 항목이 누락되어 디스크 연결 오류 발생 ([#89768](https://github.com/kubernetes/kubernetes/pull/89768), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider 및 Storage] - 수정: 잘못된 최대 Azure 디스크 최대 개수 ([#92331](https://github.com/kubernetes/kubernetes/pull/92331), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider 및 Storage] - 수정: Azure 디스크 및 파일 마운트 시 초기 지연 ([#93052](https://github.com/kubernetes/kubernetes/pull/93052), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider 및 Storage] - 수정: Azure에서 삭제된 비 VMSS 인스턴스에 의해 지원되는 노드 제거 지원 ([#91184](https://github.com/kubernetes/kubernetes/pull/91184), [@bpineau](https://github.com/bpineau)) [SIG Cloud Provider] - 수정: Azure 디스크에 강제 분리 사용 ([#91948](https://github.com/kubernetes/kubernetes/pull/91948), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - wait.Forever에서 첫 번째 반복에서 백오프 기간을 건너 뛰는 1.18 회귀 문제가 수정되었다. ([#90476](https://github.com/kubernetes/kubernetes/pull/90476), [@zhan849](https://github.com/zhan849)) [SIG API Machinery] - 엔드포인트 슬라이스 업데이트에서 newObj 를 oldObj 로 잘못 사용하는 버그가 수정되었다. ([#92339](https://github.com/kubernetes/kubernetes/pull/92339), [@fatkun](https://github.com/fatkun)) [SIG Apps 및 Network] - 중첩 범위가 있는 jsonpath 출력 표현식으로 kubectl 명령을 실행하면, 중첩 범위 다음의 표현식이 무시되는 버그가 수정되었다. ([#88464](https://github.com/kubernetes/kubernetes/pull/88464), [@brianpursley](https://github.com/brianpursley)) [SIG API Machinery] - TopologyManager가 활성화 되었을 때, 재사용 가능한 CPU 및 장치 할당이 적용되지 않는 버그가 수정되었다. ([#93189](https://github.com/kubernetes/kubernetes/pull/93189), [@klueska](https://github.com/klueska)) [SIG Node] - 깊이 중첩된 오브젝트에 json 패치를 적용하는 성능 문제가 수정되었다. ([#92069](https://github.com/kubernetes/kubernetes/pull/92069), [@tapih](https://github.com/tapih)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle 및 Instrumentation] - RBAC 역할 및 바인딩 오브젝트의 가비지 수집을 방지하는 회귀 문제가 수정되었다. ([#90534](https://github.com/kubernetes/kubernetes/pull/90534), [@apelisse](https://github.com/apelisse)) [SIG Auth] - kubeconfig 파일이 없을 때 --local 또는 --dry-run 플래그를 사용하여 kubectl 명령을 실행하는 회귀 문제가 수정되었다. ([#90243](https://github.com/kubernetes/kubernetes/pull/90243), [@soltysh](https://github.com/soltysh)) [SIG API Machinery, CLI 및 Testing] - 베어러 토큰(kubectl --token=..)과 exec 자격증명 플러그인이 동일한 컨텍스트로 구성되었을 때 모호하게 동작하는 문제가 수정되었다. 이제 전달자 토큰이 우선하게 된다. ([#91745](https://github.com/kubernetes/kubernetes/pull/91745), [@anderseknert](https://github.com/anderseknert)) [SIG API Machinery, Auth 및 Testing] - 이름에 `.` 문자가 포함된 서비스 어카운트의 사용자 인증 정보 마운트 문제가 수정되었다. ([#89696](https://github.com/kubernetes/kubernetes/pull/89696), [@nabokihms](https://github.com/nabokihms)) [SIG Auth] - 노드 삭제 시 파드의 nominatedNodeName을 지울 수 없는 문제가 수정되었다. ([#91750](https://github.com/kubernetes/kubernetes/pull/91750), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling 및 Testing] - zsh 완료가 성공적으로 초기화되었지만 zsh 완료를 초기화 할때 0이 아닌 종료 코드가 반환되는 버그가 수정되었다. ([#88165](https://github.com/kubernetes/kubernetes/pull/88165), [@brianpursley](https://github.com/brianpursley)) [SIG CLI] - endpointSliceTracker의 메모리 누수 문제가 수정되었다. ([#92838](https://github.com/kubernetes/kubernetes/pull/92838), [@tnqn](https://github.com/tnqn)) [SIG Apps 및 Network] - iSCSI 및 FibreChannel 볼륨 플러그인의 고정 마운트 옵션이 수정되었다. ([#89172](https://github.com/kubernetes/kubernetes/pull/89172), [@jsafrane](https://github.com/jsafrane)) [SIG Storage] - 영역 전체의 노드 수에 불균형이 있는 클러스터의 kube-scheduler 에서 손실된 노드 데이터에 대한 문제가 수정되었다. ([#93355](https://github.com/kubernetes/kubernetes/pull/93355), [@maelk](https://github.com/maelk)) - IPv6DualStack 기능 게이트가 활성화된 클러스터에서 서비스를 생성하거나 변경할 때 IPFamily 필드와 관련된 몇 가지 버그가 수정되었다. IPFamily 필드의 동작이 이상하고 일관성이 없으며, 이중-스택 기능이 GA가 되기 전에 변경될 가능성이 있다. 사용자는 현재 이 필드를 \"쓰기 전용\" 으로 취급해야 하며 현재 IPFamily 값을 기반으로 서비스에 대한 어떤 가정도 하지 않아야 한다. ([#91400](https://github.com/kubernetes/kubernetes/pull/91400), [@danwinship](https://github.com/danwinship)) [SIG Apps 및 Network] - OwnerReferencesPermissionEnforcement 유효성 검사 승인 플러그인이 활성화된 클러스터에서 엔드포인트슬라이스 컨트롤러가 오류없이 실행되도록 수정되었다. ([#89741](https://github.com/kubernetes/kubernetes/pull/89741), [@marun](https://github.com/marun)) [SIG Auth 및 Networking] - IPv6-전용 파드에 대한 엔드포인트를 올바르게 생성하도록 엔드포인트슬라이스컨트롤러가 수정되었다. IPv6DualStack 기능 게이트가 활성화된 경우 서비스에서 `ipFamily: IPv6` 을 지정하여 IPv6 헤드리스 서비스를 허용하도록 엔드포인트컨트롤러가 수정되었다. (이것은 이미 엔드포인트슬라이스컨트롤러와 함께 작동되었다.) ([#91399](https://github.com/kubernetes/kubernetes/pull/91399), [@danwinship](https://github.com/danwinship)) [SIG Apps 및 Network] - 여러 파드에서 읽기 전용 iSCSI 볼륨을 사용할 때 발생하는 문제가 수정되었다. ([#91738](https://github.com/kubernetes/kubernetes/pull/91738), [@jsafrane](https://github.com/jsafrane)) [SIG Storage 및 Testing] - 정보제공자(informer)를 사용하는 CSI 볼륨 첨부 스케일링의 문제가 수정되었다. ([#91307](https://github.com/kubernetes/kubernetes/pull/91307), [@yuga711](https://github.com/yuga711)) [SIG API Machinery, Apps, Node, Storage 및 Testing] - 스케일 하위리소스가 활성화된 사용자 지정 리소스 정의의 복제본 필드에 대한 기본값을 수정하는 버그가 수정되었다. ([#89833](https://github.com/kubernetes/kubernetes/pull/89833), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle 및 Instrumentation] - 디렉토리가 아닌 hostpath 타입이 HostPathFile로 인식될 수 있는 버그가 수정되었으며, HostPathType에 대한 e2e 테스트가 추가되었다. ([#64829](https://github.com/kubernetes/kubernetes/pull/64829), [@dixudx](https://github.com/dixudx)) [SIG Apps, Storage 및 Testing] - 1.16 에서 처음 널리 알려졌던, 일부 VXLAN-기반 네트워크 플러그인에서 63-초 또는 1-초 연결 지연 문제가 수정되었다. (일부 사용자는 특정 네트워크 플러그인에서 이 문제를 더 일찍 확인했다.) 이전에 ethtool 을 사용하여 기본 네트워크 인터페이스에서 체크섬 오프로드를 비활성화한 경우 이제 그 작업을 중지할 수 있다. ([#92035](https://github.com/kubernetes/kubernetes/pull/92035), [@danwinship](https://github.com/danwinship)) [SIG Network 및 Node] - API 요청에서 캐시-제어 헤더가 삭제된 1.17 의 회귀문제가 수정되었다. ([#90468](https://github.com/kubernetes/kubernetes/pull/90468), [@liggitt](https://github.com/liggitt)) [SIG API Machinery 및 Testing] - 잘못된 주석이 있는 HorizontalPodAutoscaler 오브젝트의 변환 오류가 수정되었다. ([#89963](https://github.com/kubernetes/kubernetes/pull/89963), [@liggitt](https://github.com/liggitt)) [SIG Autoscaling] - 오류가 발생했을 경우, 중지하는 대신 올바르게 빌드된 모든 오브젝트에 적용하도록 kubectl 이 수정되었다. ([#89848](https://github.com/kubernetes/kubernetes/pull/89848), [@seans3](https://github.com/seans3)) [SIG CLI 및 Testing] - 부정확한 시간에 독점 CPU를 해제하는 CPUManager 의 회귀 문제가 수정되었다. ([#90377](https://github.com/kubernetes/kubernetes/pull/90377), [@cbf123](https://github.com/cbf123)) [SIG Cloud Provider 및 Node] - 초기화(init) 컨테이너로부터 상속된 앱 컨테이너에서 독점 CPU를 해제할 가능성이 거의 없는 CPUManager 의 회귀 문제가 수정되었다. ([#90419](https://github.com/kubernetes/kubernetes/pull/90419), [@klueska](https://github.com/klueska)) [SIG Node] - 로컬 및 원격 포트를 지정할 때 `kubectl port-forward` 에서 v1.18.0-rc.1 로의 회귀문제가 수정되었다. ([#89401](https://github.com/kubernetes/kubernetes/pull/89401), [@liggitt](https://github.com/liggitt)) - 엔드포인트슬라이스 컨트롤러 가비지 수집에 대한 경합(race) 조건이 수정되었다. ([#91311](https://github.com/kubernetes/kubernetes/pull/91311), [@robscott](https://github.com/robscott)) [SIG Apps, Network 및 Testing] - GCE 클러스터 공급자의 경우, 단일 영역에서 노드가 1000 개 이상인 클러스터에 대해 내부 유형의 로드 밸런서를 만들수 없는 버그가 수정되었다. ([#89902](https://github.com/kubernetes/kubernetes/pull/89902), [@wojtek-t](https://github.com/wojtek-t)) [SIG Cloud Provider, Network 및 Scalability] - 외부 스토리지 e2e 테스트 스위트(suite) 의 경우, VolumeSnapshotClass가 입력으로 명시적으로 제공되는 경우, VolumeSnapshotClass에서 스냅샷 프로비저닝 도구를 선택하도록 외부 드라이버가 변경되었다. ([#90878](https://github.com/kubernetes/kubernetes/pull/90878), [@saikat-royc](https://github.com/saikat-royc)) [SIG Storage 및 Testing] - Get-kube.sh: 올바른 버킷에서 바이너리를 가져오도록 순서가 수정되었다. ([#91635](https://github.com/kubernetes/kubernetes/pull/91635), [@cpanato](https://github.com/cpanato)) [SIG Release] - firstTimestamp가 설정되지 않은 경우 이벤트를 출력할 때, eventTime 을 사용하도록 수정되었다. ([#89999](https://github.com/kubernetes/kubernetes/pull/89999), [@soltysh](https://github.com/soltysh)) [SIG CLI] - 파라미터 cgroupPerQos=false 및 cgroupRoot=/docker 를 설정하면 이 함수는 nodeAllocatableRoot=/docker/kubepods 를 반환하는데 이는 옳지 않다. 올바른 반환은 /docker.cm.NodeAllocatableRoot(s.CgroupRoot, s.CgroupDriver) 이어야 한다. kubeDeps.CAdvisorInterface, err = cadvisor.New(imageFsInfoProvider, s.RootDirectory, cgroupRoots, cadvisor.UsingLegacyCadvisorStats(s.ContainerRuntime, s.RemoteRuntimeEndpoint)) 위 함수는 cgroupRoots를 사용하여 cadvisor 인터페이스를 만들 때, 잘못된 파라미터 cgroupRoots 로 인해 제거 관리자가 /docker 에서 메트릭을 수집하지 않도록 유도하고 kubelet은 이러한 오류를 자주 표시하게된다. E0303 17:25:03.436781 63839 summary_sys_containers.go:47] Failed to get system container stats for \"/docker\": failed to get cgroup stats for \"/docker\": failed to get container info for \"/docker\": unknown container \"/docker\" E0303 17:25:03.436809 63839 helpers.go:680] eviction manager: failed to construct signal: \"allocatableMemory.available\" error: system container \"pods\" not found in metrics ([#88970](https://github.com/kubernetes/kubernetes/pull/88970), [@mysunshine92](https://github.com/mysunshine92)) [SIG Node] - HA 환경에서, 대기 스케줄러가 API 서버와의 연결이 끊어진 기간 동안 파드를 삭제하고 다시 생성한 후 대기 스케줄러가 마스터가 되면 스케줄러 캐시가 손상될 수 있다. 이 PR은 이 문제를 해결한다. ([#91126](https://github.com/kubernetes/kubernetes/pull/91126), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling] - /metrics/resource 의 kubelet 리소스 메트릭 엔드포인트에서 다음 메트릭의 이름이 변경되었다. - node_cpu_usage_seconds --> node_cpu_usage_seconds_total - container_cpu_usage_seconds --> container_cpu_usage_seconds_total 이것은 1.18.0에서 추가된 &#35;86282의 부분적인 되돌리기이며, 처음에는 _total 접미사가 제거되었다. ([#89540](https://github.com/kubernetes/kubernetes/pull/89540), [@dashpole](https://github.com/dashpole)) [SIG Instrumentation 및 Node] - Ipvs: 지원되는 커널에서만 sysctlconnreuse 설정을 시도한다. ([#88541](https://github.com/kubernetes/kubernetes/pull/88541), [@cmluciano](https://github.com/cmluciano)) [SIG Network] - kubectl/client-go의 Jsonpath 지원은 복잡한 유형(맵/슬라이스/구조체)을 Go-구문 대신 json으로 직렬화 한다. ([#89660](https://github.com/kubernetes/kubernetes/pull/89660), [@pjferrell](https://github.com/pjferrell)) [SIG API Machinery, CLI 및 Cluster Lifecycle] - Kube-aggregator 인증서는 디스크에서 변경시 동적으로 로드된다. ([#92791](https://github.com/kubernetes/kubernetes/pull/92791), [@p0lyn0mial](https://github.com/p0lyn0mial)) [SIG API Machinery] - Kube-apiserver: 불필요한 409 충돌 오류를 클라이언트에 반환하지 않도록 스케일 하위 리소스 패치 처리가 수정되었다. ([#90342](https://github.com/kubernetes/kubernetes/pull/90342), [@liggitt](https://github.com/liggitt)) [SIG Apps, Autoscaling 및 Testing] - Kube-apiserver: 연속적인 재귀 하강 연산자가 있는 jsonpath 표현식은 더 이상 사용자 정의 리소스 표시 열에 대해 해석되지 않는다. ([#93408](https://github.com/kubernetes/kubernetes/pull/93408), [@joelsmith](https://github.com/joelsmith)) [SIG API Machinery] - Kube-apiserver: 단일 X-Stream-Protocol-Version 헤더의 여러 쉼표로 구분된 프로토콜이 이제 RFC2616을 준수하는 여러 헤더와 함께 인식된다. ([#89857](https://github.com/kubernetes/kubernetes/pull/89857), [@tedyu](https://github.com/tedyu)) [SIG API Machinery] - Kube-proxy IP 군은 프록시가 사용하는 nodeIP에 의해 결정된다. 우선순위는: 1. 바인드 주소가 0.0.0.0 또는 ::가 아닌 경우 구성된 --bind-address 의 값 2. 설정된 경우, 노드 개체의 기본 IP 3. IP를 찾을 수 없는 경우, NodeIP 의 기본값은 127.0.0.1 이며 IP 군은 IPv4 이다. ([#91725](https://github.com/kubernetes/kubernetes/pull/91725), [@aojea](https://github.com/aojea)) [SIG Network] - 이중-스택 모드에서 Kube-proxy는 `Service.Spec.IPFamily` 필드를 사용하는 대신 ClusterIP에서 서비스 IP 계열을 유추한다. ([#91357](https://github.com/kubernetes/kubernetes/pull/91357), [@aojea](https://github.com/aojea)) - 이제 Kube-up에 CoreDNS 버전 v1.7.0이 포함된다. 주요 변경 사항은 다음과 같다. -  CoreDNS가 서비스 기록 업데이트를 중단할 수 있는 버그가 수정되었다. -  어떤 정책이 설정되어도 항상 첫 번째 업스트림 서버만 선택되는 포워드 플러그인의 버그가 수정되었다. -  쿠버네티스 플러그인에서 이미 사용 중단된 옵션 `resyncperiod` 및 `upstream` 가 제거되었다. -  Prometheus 메트릭 이름 변경을 포함한다(표준 Prometheus 메트릭 명명 규칙에 맞게 변경). 이전 메트릭의 이름을 사용하는 기존 보고 공식과 역호환 된다. -  페더레이션 플러그인 (v1 쿠버네티스 페더레이션 허용) 이 제거되었다. 자세한 내용은 https://coredns.io/2020/06/15/coredns-1.7.0-release/ 에서 확인할 수 있다. ([#92718](https://github.com/kubernetes/kubernetes/pull/92718), [@rajansandeep](https://github.com/rajansandeep)) [SIG Cloud Provider] - Kube-up: 승인 웹훅 자격증명 구성의 확인 설정이 수정되었다. ([#91995](https://github.com/kubernetes/kubernetes/pull/91995), [@liggitt](https://github.com/liggitt)) [SIG Cloud Provider 및 Cluster Lifecycle] - Kubeadm의 TLS 부트스트랩 프로세스가 조인 시 완료되는 시간 제한이 5 분으로 증가하였다. ([#89735](https://github.com/kubernetes/kubernetes/pull/89735), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - Kubeadm: 이 작업을 반복 재시도 함으로써, 업데이트 상태를 보다 탄력적으로 만들기 위하여, join / UpdateStatus에 대한 재시도를 추가하였다. ([#91952](https://github.com/kubernetes/kubernetes/pull/91952), [@xlgao-zju](https://github.com/xlgao-zju)) [SIG Cluster Lifecycle] - Kubeadm: 안전하지 않은 서비스를 비활성화하기 위하여 사용 중단된 플래그인 --port=0 을 kube-controller-manager 및 kube-scheduler 매니페스트에 추가하였다. 이 플래그가 없으면 기본적으로 구성 요소(예: /metrics)가 (--adress에 의해 제어되는)기본노드 인터페이스에서 안전하지 않게 제공된다. 이 동작을 재정의하고 안전하지 않은 서비스를 활성화하려는 사용자의 경우, 이러한 구성 요소에 대한 kubeadm의 \"extraArgs\" 메커니즘을 통해 사용자 정의 포트로 --port=X 를 전달할 수 있다. ([#92720](https://github.com/kubernetes/kubernetes/pull/92720), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: \"조인\" 과정에서, 이미 클러스터에 존재하는 경우 etcd 구성원을 다시 추가하지 않는다. ([#92118](https://github.com/kubernetes/kubernetes/pull/92118), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: \"리셋\" 과정에서, 클러스터에 남아서 쌓여있는 etcd 멤버만 제거하지 않고, 로컬 etcd 스토리지의 정리를 계속 진행한다. ([#91145](https://github.com/kubernetes/kubernetes/pull/91145), [@tnqn](https://github.com/tnqn)) [SIG Cluster Lifecycle] - Kubeadm: 조인 중에 동일한 이름의 노드가 클러스터에 이미 존재하는지 확인하는 경우 NodeReady 조건이 올바르게 검증되었는지를 확인한다. ([#89602](https://github.com/kubernetes/kubernetes/pull/89602), [@kvaps](https://github.com/kvaps)) [SIG Cluster Lifecycle] - Kubeadm: 업그레이드 단계에서 `image-pull-timeout` 플래그가 준수되었는지 확인한다. ([#90328](https://github.com/kubernetes/kubernetes/pull/90328), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle] - Kubeadm: 1.18.x로 업그레이드 후 RBAC 누락으로 인해 노드가 클러스터에 조인할 수 없는 버그가 수정되었다. ([#89537](https://github.com/kubernetes/kubernetes/pull/89537), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: 'kubeadm join'에서 컨트롤 플레인과 관련된 플래그 전달에 대한 잘못된 경고가 수정되었다. ([#89596](https://github.com/kubernetes/kubernetes/pull/89596), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: 느린 설정에서 etcd 멤버를 추가할 때 \"kubeadm join\" 에 대한 견고성이 향상되었다. ([#90645](https://github.com/kubernetes/kubernetes/pull/90645), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: 생성된 인증서에서 중복된 DNS 이름 및 IP 주소가 제거된다. ([#92753](https://github.com/kubernetes/kubernetes/pull/92753), [@QianChenglong](https://github.com/QianChenglong)) [SIG Cluster Lifecycle] - Kubectl azure 인증: 1.18.0에서 \"spn:\" 접두사가 예기치 않게 kubeconfig 파일의 `apiserver-id` 구성에 추가되는 회귀현상을 수정하였다. ([#89706](https://github.com/kubernetes/kubernetes/pull/89706), [@weinong](https://github.com/weinong)) [SIG API Machinery 및 Auth] - Kubectl: 오토스케일이 '--name' 플래그를 따르지 않던 버그가 수정되었다. ([#91855](https://github.com/kubernetes/kubernetes/pull/91855), [@SataQiu](https://github.com/SataQiu)) [SIG CLI] - Kubectl: kubectl scale이 '--timeout' 플래그를 따르지 않던 버그가 수정되었다. ([#91858](https://github.com/kubernetes/kubernetes/pull/91858), [@SataQiu](https://github.com/SataQiu)) [SIG CLI] - Kubelet: kubelet 도움말 정보가 올바른 유형의 플래그를 표시할 수 없던 버그가 수정되었다. ([#88515](https://github.com/kubernetes/kubernetes/pull/88515), [@SataQiu](https://github.com/SataQiu)) [SIG Docs 및 Node] - Kuberuntime 보안: 파드 샌드박스는 이제 항상 `runtime/default` seccomp 프로필로 실행된다. kuberuntime seccomp: 사용자 정의 프로필은 이제 파드 수준에서 설정할 때 더 작은 seccomp 프로필을 가질 수 있다. ([#90949](https://github.com/kubernetes/kubernetes/pull/90949), [@pjbgf](https://github.com/pjbgf)) [SIG Node] - Kubelet 부트 스트랩 인증서 신호를 인식하게 되었다. ([#92786](https://github.com/kubernetes/kubernetes/pull/92786), [@answer1991](https://github.com/answer1991)) [SIG API Machinery, Auth 및 Node] - 노드 ([#89677](https://github.com/kubernetes/kubernetes/pull/89677), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - 여러 네트워크 인터페이스가 있는 AWS 노드에서, kubelet은 이제 보조 인터페이스의 주소를 보다 안정적으로 보고해야 한다. ([#91889](https://github.com/kubernetes/kubernetes/pull/91889), [@anguslees](https://github.com/anguslees)) [SIG Cloud Provider] - 리스케줄링 시도를 위한 파드의 조건 업데이트는 생략된다. ([#91252](https://github.com/kubernetes/kubernetes/pull/91252), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - 이제 이전에 지정된 노드가 예약 및 확인할 수 없게 된 후 파드를 선점 대상으로 고려할 수 있게 된다. ([#92604](https://github.com/kubernetes/kubernetes/pull/92604), [@soulxu](https://github.com/soulxu)) - 볼륨을 확장하거나 생성할 때 PVC 요청크기에 대한 오버플로를 방지한다. ([#90907](https://github.com/kubernetes/kubernetes/pull/90907), [@gnufied](https://github.com/gnufied)) [SIG Cloud Provider 및 Storage] - 프라이빗 Azure 클라우드의 클러스터가 동일한 클라우드의 ACR에 인증할 수 있도록 수정을 허용한다. ([#90425](https://github.com/kubernetes/kubernetes/pull/90425), [@DavidParks8](https://github.com/DavidParks8)) [SIG Cloud Provider] - AWS 로드밸런서 워커 노드의 SG 규칙 논리를 결정적으로 변경하였다. ([#92224](https://github.com/kubernetes/kubernetes/pull/92224), [@M00nF1sh](https://github.com/M00nF1sh)) [SIG Cloud Provider] - 서버측 적용을 사용하지 않는 생성/업데이트/패치 요청에서 처리되는 metadata.managedFields의 회귀 문제가 해결되었다. ([#91690](https://github.com/kubernetes/kubernetes/pull/91690), [@apelisse](https://github.com/apelisse)) [SIG API Machinery 및 Testing] - 윈도우 볼륨을 마운트하는 v1.18.0-rc.1의 회귀 문제가 해결되었다. ([#89319](https://github.com/kubernetes/kubernetes/pull/89319), [@mboersma](https://github.com/mboersma)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation 및 Storage] - v1 CSR API를 제공하는 서버에 대해 `kubectl certificate approve/deny` 를 사용하는 문제가 해결되었다. ([#91691](https://github.com/kubernetes/kubernetes/pull/91691), [@liggitt](https://github.com/liggitt)) [SIG Auth 및 CLI] - --namespace 플래그 없이 `kubectl apply --prune` 기능이 복원되었다. 1.17부터 `kubectl apply --prune` 은 기본 네임스페이스(또는 kubeconfig에서) 또는 명령줄 플래그에 명시적으로 지정된 리소스만 제거하였다. 그러나 이것은 구성 파일의 모든 네임스페이스에서 리소스를 제거할 수 있는 kubectl 1.16의 변경사항을 호환되지 않는다. 이 패치는 kubectl 1.16 의 동작을 복원한다. ([#89551](https://github.com/kubernetes/kubernetes/pull/89551), [@tatsuhiro-t](https://github.com/tatsuhiro-t)) [SIG CLI 및 Testing] - 클러스터/gce/매니페스트의 컨트롤 플레인 매니페스트에서 정적 컨트롤 플레인 파드의 우선순위를 복원한다. ([#89970](https://github.com/kubernetes/kubernetes/pull/89970), [@liggitt](https://github.com/liggitt)) [SIG Cluster Lifecycle 및 Node] - 1.19-rc1에 추가된, 윈도우 노드를 위한 devicemanager 가 복귀되었다. ([#93263](https://github.com/kubernetes/kubernetes/pull/93263), [@liggitt](https://github.com/liggitt)) Node 및 Windows] - 스케줄러 v1 정책 구성 또는 알고리즘 제공 업체 설정을 v1beta1 컴포넌트컨피그(ComponentConfig)와 함께 전달하여 정책에서 CC로의 전환을 지원한다. ([#92531](https://github.com/kubernetes/kubernetes/pull/92531), [@damemi](https://github.com/damemi)) [SIG Scheduling] - 사용 가능한 노드가 없어서 발생하는 스케줄링 실패의 경우 이제 ```schedule_attempts_total``` 메트릭 하위에 스케줄링 불가능으로 보고된다. ([#90989](https://github.com/kubernetes/kubernetes/pull/90989), [@ahg-g](https://github.com/ahg-g)) [SIG Scheduling] - 이제 파드에 바인딩 된 서비스 어카운트 토큰을 파드 삭제 유예 기간 동안 사용할 수 있다. ([#89583](https://github.com/kubernetes/kubernetes/pull/89583), [@liggitt](https://github.com/liggitt)) [SIG Auth] - 서비스 로드 밸런서는 더 이상 스케줄링 불가능으로 표시된 노드를 후보 노드에서 제외하지 않는다. 대신 서비스 로드 밸런서 제외 레이블을 사용해야 한다. 코돈(cordon) 노드를 보유하고 있는 1.18 클러스터에서 업그레이드 하려는 사용자는, 해당 노드가 서비스 로드 밸런서에서 제외시키려 할 경우, 업그레이드 하기 전에 영향을 받는 노드에 `node.kubernetes.io/exclude-from-external-load-balancers` 레이블을 설정해야 한다. ([#90823](https://github.com/kubernetes/kubernetes/pull/90823), [@smarterclayton](https://github.com/smarterclayton)) [SIG Apps, Cloud Provider 및 Network] - kubectl annotate 명령어의 --list 옵션이 지원된다. ([#92576](https://github.com/kubernetes/kubernetes/pull/92576), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - 노드 추가/삭제 이벤트에서 서비스 `Type=LoadBalancer`에 대한 LB 백엔드 노드를 동기화한다. ([#81185](https://github.com/kubernetes/kubernetes/pull/81185), [@andrewsykim](https://github.com/andrewsykim)) - 비어있지 않고, 인수가 필요하지 않는 다음의 구성요소는 이제 인수가 지정된 경우 오류 메세지를 출력하고 종료된다. cloud-controller-manager, kube-apiserver, kube-controller-manager, kube-proxy, kubeadm {alpha|config|token|version}, kubemark. 플래그는 짦은 형식의 경우 단일 대시 \"-\" (0x45), 긴 형식의 경우 이중 대시 \"--\"로 시작해야 한다. 이 변경 이전에는 잘못된 플래그 (예를 들어, 0x8211: \"–\" 와 같은 아스키가 아닌 대시문자로 시작)가 위치 인수로 처리되고 무시되었다. ([#91349](https://github.com/kubernetes/kubernetes/pull/91349), [@neolit123](https://github.com/neolit123)) [SIG API Machinery, Cloud Provider, Cluster Lifecycle, Network 및 Scheduling] - 파드 사양의 terminationGracePeriodSeconds가 미러 파드에 적용된다. ([#92442](https://github.com/kubernetes/kubernetes/pull/92442), [@tedyu](https://github.com/tedyu)) [SIG Node 및 Testing] - 이전 커널과의 IPVS 호환성 문제를 해결하기 위해 github.com/moby/ipvs를 v1.0.1로 변경하였다. ([#90555](https://github.com/kubernetes/kubernetes/pull/90555), [@andrewsykim](https://github.com/andrewsykim)) [SIG Network] - status 하위 리소스를 경유하는 파드의 상태 업데이트는 이제 `status.podIP` 및 `status.podIPs` 필드의 형식이 올바른지 확인한다. ([#90628](https://github.com/kubernetes/kubernetes/pull/90628), [@liggitt](https://github.com/liggitt)) [SIG 앱 및 Node] - 준비상태(readiness)를 보고하기 전에 모든 CRD는 디스커버리 엔드포인트가 확인될 때까지 기다린다. ([#89145](https://github.com/kubernetes/kubernetes/pull/89145), [@sttts](https://github.com/sttts)) [SIG API Machinery] - 파드를 제거할 때, PDB를 확인하지 않고 Pending 상태의 파드가 제거된다. ([#83906](https://github.com/kubernetes/kubernetes/pull/83906), [@michaelgugino](https://github.com/michaelgugino)) [SIG API Machinery, Apps, Node 및 Scheduling] - [보안] golang.org/x/text/encoding/unicode 의 취약성 ([#92219](https://github.com/kubernetes/kubernetes/pull/92219), [@voor](https://github.com/voor)) Cloud Provider, Cluster Lifecycle, Instrumentation 및 Node ### 기타 (정리(Cleanup) or Flake(플레이크)) - --cache-dir은 http 및 디스커버리 모두에 대해 캐시 디렉토리를 설정하며 기본값은 $HOME/.kube/cache이다. ([#92910](https://github.com/kubernetes/kubernetes/pull/92910), [@soltysh](https://github.com/soltysh)) [SIG API Machinery 및 CLI] - 이미지 로그에 `pod.Namespace` 가 추가되었다. ([#91945](https://github.com/kubernetes/kubernetes/pull/91945), [@zhipengzuo](https://github.com/zhipengzuo)) - DISABLE_KUBECONFIG_LOCK 환경 변수를 통해 kubeconfig 파일 잠금을 비활성화 하는 기능이 추가되었다. ([#92513](https://github.com/kubernetes/kubernetes/pull/92513), [@soltysh](https://github.com/soltysh)) [SIG API Machinery 및 CLI] - udp 파드의 conntrack 모듈이 정리되었는지 확인하기 위한 별도의 테스트가 추가되었다. ([#90180](https://github.com/kubernetes/kubernetes/pull/90180), [@JacobTanenbaum](https://github.com/JacobTanenbaum)) [SIG Architecture, Network 및 Testing] - fsType이 지정되지 않은 경우, cinder 값의 fsType 을 `ext4` 로 조정한다. ([#90608](https://github.com/kubernetes/kubernetes/pull/90608), [@huffmanca](https://github.com/huffmanca)) [SIG Storage] - 베이스-이미지(base-image): debian-base:v2.1.0를 사용한다. ([#90697](https://github.com/kubernetes/kubernetes/pull/90697), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery 및 Release] - 베이스-이미지: debian-iptables:v12.1.0를 사용한다. ([#90782](https://github.com/kubernetes/kubernetes/pull/90782), [@justaugustus](https://github.com/justaugustus)) [SIG Release] - Beta.kubernetes.io/arch는 v1.14 이후 이미 사용 중단되었으며, v1.18은 제거 대상이다. ([#89462](https://github.com/kubernetes/kubernetes/pull/89462), [@wawa0210](https://github.com/wawa0210)) [SIG Testing] - 빌드: debian-base@v2.1.2 및 debian-iptables@v12.1.1로 변경되었다. ([#93667](https://github.com/kubernetes/kubernetes/pull/93667), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery, Release 및 Testing] - beta.kubernetes.io/os를 kubernetes.io/os로 변경하였다. ([#89460](https://github.com/kubernetes/kubernetes/pull/89460), [@wawa0210](https://github.com/wawa0210)) [SIG Testing 및 Windows] - beta.kubernetes.io/os를 kubernetes.io/os로 변경하였다. ([#89461](https://github.com/kubernetes/kubernetes/pull/89461), [@wawa0210](https://github.com/wawa0210)) [SIG Cloud Provider 및 Cluster Lifecycle] - `kubectl get` 을 사용하여 네임스페이스가 지정되지 않는 리소스를 검색할 때, 리소스가 없을 때의 출력 메세지가 변경되었다. ([#89861](https://github.com/kubernetes/kubernetes/pull/89861), [@rccrdpccl](https://github.com/rccrdpccl)) [SIG CLI] - CoreDNS는 더 이상 kube-dns 컨피그맵에 대한 페더레이션 데이터 변환을 지원하지 않는다. ([#92716](https://github.com/kubernetes/kubernetes/pull/92716), [@rajansandeep](https://github.com/rajansandeep)) [SIG Cluster Lifecycle] - 힙스터와 관련된 kubectl top 명령어의 플래그가 사용 중단 되었다. kubectl top 에서 힙스터 지원이 중단 되었다. ([#87498](https://github.com/kubernetes/kubernetes/pull/87498), [@serathius](https://github.com/serathius)) [SIG CLI] - 더 이상 사용되지 않는 `--target-ram-md` 플래그가 사용 중단되었다. ([#91818](https://github.com/kubernetes/kubernetes/pull/91818), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery] - Kubelet API에 직접 의존하는 일부 적합성 테스트가 삭제되었다. ([#90615](https://github.com/kubernetes/kubernetes/pull/90615), [@dims](https://github.com/dims)) [SIG Architecture, Network, Release 및 Testing] - 바인딩 되지 않은 PVC가 지연 바인딩 모드에 있지만 파드에서 사용하는 경우, `WaitingForPodScheduled` 이벤트를 보내게 된다. ([#91455](https://github.com/kubernetes/kubernetes/pull/91455), [@cofyc](https://github.com/cofyc)) [SIG Storage] - 수정: blob 디스크 기능의 라이선스 문제 ([#92824](https://github.com/kubernetes/kubernetes/pull/92824), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - 전용 kubectl 하위명령어의 필드 관리자를 설정하여 서버측 적용의 충돌 오류를 개선하였다. ([#88885](https://github.com/kubernetes/kubernetes/pull/88885), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG CLI 및 Testing] - IsFullyQualifiedDomainName()은 IsDNS1123Label을 기반으로 각 레이블의 유효성을 검사한다. ([#90172](https://github.com/kubernetes/kubernetes/pull/90172), [@nak3](https://github.com/nak3)) [SIG API Machinery 및 Network] - 이제 서비스 어노테이션 `cloud.google.com/network-tier: Standard` 을 사용하여 GCE 로드밸런서의 네트워크 등급을 구성할 수 있다. ([#88532](https://github.com/kubernetes/kubernetes/pull/88532), [@zioproto](https://github.com/zioproto)) [SIG Cloud Provider, Network 및 Testing] - Kube-aggregator: aggregator_unavailable_apiservice_count 메트릭의 이름을 aggregator_unavailable_apiservice_total로 변경하였다. ([#88156](https://github.com/kubernetes/kubernetes/pull/88156), [@p0lyn0mial](https://github.com/p0lyn0mial)) [SIG API Machinery] - Kube-apiserver: 사용자 정의 리소스 용으로 게시된 openapi 스키마는 이제 표준 ListMeta 스키마 정의를 참조한다. ([#92546](https://github.com/kubernetes/kubernetes/pull/92546), [@liggitt](https://github.com/liggitt)) [SIG API Machinery] - Kube-proxy는 kube-proxy에 대한 변경 사항이 적용되기 위해 대기열에 마지막으로 대기한 시간을 나타내는 새로운 메트릭인, `kubeproxy_sync_proxy_rules_last_queued_timestamp_seconds` 를 노출해야 한다. ([#90175](https://github.com/kubernetes/kubernetes/pull/90175), [@squeed](https://github.com/squeed)) [SIG Instrumentation 및 Network] - Kube-scheduler: 메트릭 항목 `scheduler_total_preemption_attempts` 의 이름이 `scheduler_preemption_attempts_total` 로 변경되었다. ([#91448](https://github.com/kubernetes/kubernetes/pull/91448), [@RainbowMango](https://github.com/RainbowMango)) [SIG API Machinery, Cluster Lifecycle, Instrumentation 및 Scheduling] - Kube-up: 1.17 이전의 동작과 일치하도록 중요 파드를 kube-system 네임스페이스로 기본적으로 제한한다. ([#93121](https://github.com/kubernetes/kubernetes/pull/93121), [@liggitt](https://github.com/liggitt)) [SIG Cloud Provider 및 Scheduling] - Kubeadm은 이제 kubelet 명령줄 대신 kubelet 구성 요소 설정을 사용하여 IPv6DualStack 기능 게이트를 전달한다. ([#90840](https://github.com/kubernetes/kubernetes/pull/90840), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - Kubeadm: \"kubeadm upgrade apply\" 중에 컨트롤 플레인 이미지를 미리 가져오기 위하여 데몬셋(DaemonSet)을 사용하지 않는다. 개별 노드의 업그레이드는 이제 사전 구동 검사를 하여 필요한 이미지를 가져온다. \"kubeadm upgrade apply\" 에 대한 \"--image-pull-timeout\" 플래그는 이제 사용 중단되었으며, GA 지원 중단 정책에 따라 향후 릴리스에서 제거된다. ([#90788](https://github.com/kubernetes/kubernetes/pull/90788), [@xlgao-zju](https://github.com/xlgao-zju)) [SIG Cluster Lifecycle] - Kubeadm: /healthz 를 사용하는 대신 kube-apiserver의 스태틱(static) 파드에 대해 /livez 및 /readyz 에 대해 두 개의 개별 검사를 사용한다. ([#90970](https://github.com/kubernetes/kubernetes/pull/90970), [@johscheuer](https://github.com/johscheuer)) [SIG Cluster Lifecycle] - 없음 ([#91597](https://github.com/kubernetes/kubernetes/pull/91597), [@elmiko](https://github.com/elmiko)) [SIG Autoscaling 및 Testing] - Openapi-controller: 등급 제한 메트릭 `APIServiceOpenAPIAggregationControllerQueue1` 에서 후행의 `1` 문자리터럴을 제거하고, 프로메테우스의 모범 사례를 준수하도록 이름을 `open_api_aggregation_controller` 로 변경하였다. ([#77979](https://github.com/kubernetes/kubernetes/pull/77979), [@s-urbaniak](https://github.com/s-urbaniak)) [SIG API Machinery] - 볼륨 작동 오류시 이벤트 스팸이 감소하였다. ([#89794](https://github.com/kubernetes/kubernetes/pull/89794), [@msau42](https://github.com/msau42)) [SIG Storage] - 로컬 nodeipam 범위 할당자를 리팩토링하고 다음의 메트릭을 사용하여, 할당된 CIDR을 저장하는데 사용된 cidr집합을 계측한다. \"cidrset_cidrs_allocations_total\", \"cidrset_cidrs_releases_total\", \"cidrset_usage_cidrs\", \"cidrset_allocation_tries_per_request\", ([#90288](https://github.com/kubernetes/kubernetes/pull/90288), [@aojea](https://github.com/aojea)) [SIG 앱, Instrumentation, Network 및 확장성] - kubectl apply 명령어에서 사용 중단된 --server-dry-run 플래그가 제거되었다. ([#91308](https://github.com/kubernetes/kubernetes/pull/91308), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG CLI 및 Testing] - 기능 게이트 DefaultPodTopologySpread와의 이름 충돌을 피하기 위해 DefaultPodTopologySpread 플러그인의 이름을 SelectorSpread 플러그인으로 변경하였다. ([#92501](https://github.com/kubernetes/kubernetes/pull/92501), [@rakeshreddybandi](https://github.com/rakeshreddybandi)) [SIG Release, Scheduling 및 Testing] - framework.Failf가 ExpectNoError로 변경되었다. ([#91811](https://github.com/kubernetes/kubernetes/pull/91811), [@lixiaobing1](https://github.com/lixiaobing1)) [SIG Instrumentation, Storage 및 Testing] - 필터링 된 노드가 하나 이하인 경우, 스케줄러 PreScore 플러그인이 실행되지 않는다. ([#89370](https://github.com/kubernetes/kubernetes/pull/89370), [@ahg-g](https://github.com/ahg-g)) [SIG Scheduling] - \"HostPath는 볼륨에 올바른 모드를 제공해야 한다.\"는 이제 적합성 테스트에서 제외된다. ([#90861](https://github.com/kubernetes/kubernetes/pull/90861), [@dims](https://github.com/dims)) [SIG Architecture 및 Testing] - Kubelet의 `--experimental-allocatable-ignore-eviction` 옵션은 이제 사용 중단된 것으로 표시된다. ([#91578](https://github.com/kubernetes/kubernetes/pull/91578), [@knabben](https://github.com/knabben)) [SIG Node] - Kubelet의 `--experimental-mounter-path` 및 `--experimental-check-node-capabilities-before-mount` 옵션은 이제 사용 중단된 것으로 표시된다. ([#91373](https://github.com/kubernetes/kubernetes/pull/91373), [@knabben](https://github.com/knabben)) - PR은 PV 또는 PVC 처리에서 특정 실패가 발생할 때 이벤트를 생성하는 기능을 추가한다. 이 이벤트는 사용자가 사용 실패 이유를 파악하여 필요한 복구 조치를 취할 수 있도록 도와준다. ([#89845](https://github.com/kubernetes/kubernetes/pull/89845), [@yuga711](https://github.com/yuga711)) [SIG Apps] - PodShareProcessNamespace 기능 게이트가 제거되고, PodShareProcessNamespace 는 항상 활성화된다. ([#90099](https://github.com/kubernetes/kubernetes/pull/90099), [@tanjunchen](https://github.com/tanjunchen)) [SIG Node] - kube-apiserver의 `--kubelet-https` 플래그가 사용 중단 된다. kubelet에 대한 kube-apiserver의 연결은 이제 항상 `https` 를 사용한다. (kubelet은 v1.0 이전부터 apiserver가 통신하는 엔드포인트를 제공하기 위해 언제나 `https` 를 사용하였다.) ([#91630](https://github.com/kubernetes/kubernetes/pull/91630), [@liggitt](https://github.com/liggitt)) [SIG API Machinery 및 Node] - CNI가 v0.8.6로 변경되었다. ([#91370](https://github.com/kubernetes/kubernetes/pull/91370), [@justaugustus](https://github.com/justaugustus)) [SIG Cloud Provider, Network, Release 및 Testing] - Golang이 v1.14.5로 변경되었다. - Update repo-infra to 0.0.7 (go1.14.5 및 go1.13.13을 지원하기 위해) - 포함: - bazelbuild/bazel-toolchains@3.3.2 - bazelbuild/rules_go@v0.22.7 ([#93088](https://github.com/kubernetes/kubernetes/pull/93088), [@justaugustus](https://github.com/justaugustus)) [SIG Release 및 Testing] - Golang이 v1.14.6로 변경되었다. - repo-infra가 0.0.8로 변경되었다. (go1.14.6 및 go1.13.14을 지원하기 위해) - 포함: - bazelbuild/bazel-toolchains@3.4.0 - bazelbuild/rules_go@v0.22.8 ([#93198](https://github.com/kubernetes/kubernetes/pull/93198), [@justaugustus](https://github.com/justaugustus)) [SIG Release 및 Testing] - corefile-migration 라이브러리가 1.0.8로 변경되었다. ([#91856](https://github.com/kubernetes/kubernetes/pull/91856), [@wawa0210](https://github.com/wawa0210)) [SIG Node] - 기본 etcd 서버 버전이 3.4.4로 변경되었다. ([#89214](https://github.com/kubernetes/kubernetes/pull/89214), [@jingyih](https://github.com/jingyih)) [SIG API Machinery, Cluster Lifecycle 및 Testing] - 기본 etcd 서버 버전이 3.4.7로 변경되었다. ([#89895](https://github.com/kubernetes/kubernetes/pull/89895), [@jingyih](https://github.com/jingyih)) [SIG API Machinery, Cluster Lifecycle 및 Testing] - 기본 etcd 서버 버전이 3.4.9로 변경되었다. ([#92349](https://github.com/kubernetes/kubernetes/pull/92349), [@jingyih](https://github.com/jingyih)) [SIG API Machinery, Cloud Provider, Cluster Lifecycle 및 Testing] - go.etcd.io/bbolt가 v1.3.5로 변경되었다. ([#92350](https://github.com/kubernetes/kubernetes/pull/92350), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery 및 Cloud Provider] - opencontainers/runtime-spec 의존성이 v1.0.2로 변경되었다. ([#89644](https://github.com/kubernetes/kubernetes/pull/89644), [@saschagrunert](https://github.com/saschagrunert)) [SIG Node] - `beta.kubernetes.io/os` 및 `beta.kubernetes.io/arch` 노드 레이블은 사용 중단되었다. `kubernetes.io/os` 및 `kubernetes.io/arch` 를 사용하도록 노드 셀렉터를 변경해야한다. ([#91046](https://github.com/kubernetes/kubernetes/pull/91046), [@wawa0210](https://github.com/wawa0210)) [SIG Apps 및 Node] - `kubectl config view` 는 이제 클라이언트 인증서와 유사하게 기본적으로 베어러 토큰을 수정한다. `--raw` 플래그는 여전히 전체 컨텐츠를 출력하는데 사용될 수 있다. ([#88985](https://github.com/kubernetes/kubernetes/pull/88985), [@puerco](https://github.com/puerco)) </del> <ins> - Resolves an issue running Ingress conformance tests on clusters which use finalizers on Ingress objects to manage releasing load balancer resources ([#96742](https://github.com/kubernetes/kubernetes/pull/96742), [@spencerhance](https://github.com/spencerhance)) [SIG Network and Testing] - The Conformance test \"validates that there is no conflict between pods with same hostPort but different hostIP and protocol\" now validates the connectivity to each hostPort, in addition to the functionality. ([#96627](https://github.com/kubernetes/kubernetes/pull/96627), [@aojea](https://github.com/aojea)) [SIG Scheduling and Testing] ### 버그 또는 회귀(regression) - Add kubectl wait  --ignore-not-found flag ([#90969](https://github.com/kubernetes/kubernetes/pull/90969), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - Added support to kube-proxy for externalTrafficPolicy=Local setting via Direct Server Return (DSR) load balancers on Windows. ([#93166](https://github.com/kubernetes/kubernetes/pull/93166), [@elweb9858](https://github.com/elweb9858)) [SIG Network] - Alter wording to describe pods using a pvc ([#95635](https://github.com/kubernetes/kubernetes/pull/95635), [@RaunakShah](https://github.com/RaunakShah)) [SIG CLI] - An issues preventing volume expand controller to annotate the PVC with `volume.kubernetes.io/storage-resizer` when the PVC StorageClass is already updated to the out-of-tree provisioner is now fixed. ([#94489](https://github.com/kubernetes/kubernetes/pull/94489), [@ialidzhikov](https://github.com/ialidzhikov)) [SIG API Machinery, Apps and Storage] - Azure ARM client: don't segfault on empty response and http error ([#94078](https://github.com/kubernetes/kubernetes/pull/94078), [@bpineau](https://github.com/bpineau)) [SIG Cloud Provider] - Azure armclient backoff step defaults to 1 (no retry). ([#94180](https://github.com/kubernetes/kubernetes/pull/94180), [@feiskyer](https://github.com/feiskyer)) - Azure: fix a bug that kube-controller-manager would panic if wrong Azure VMSS name is configured ([#94306](https://github.com/kubernetes/kubernetes/pull/94306), [@knight42](https://github.com/knight42)) [SIG Cloud Provider] - Both apiserver_request_duration_seconds metrics and RequestReceivedTimestamp fields of an audit event now take into account the time a request spends in the apiserver request filters. ([#94903](https://github.com/kubernetes/kubernetes/pull/94903), [@tkashem](https://github.com/tkashem)) - Build/lib/release: Explicitly use '--platform' in building server images When we switched to go-runner for building the apiserver, controller-manager, and scheduler server components, we no longer reference the individual architectures in the image names, specifically in the 'FROM' directive of the server image Dockerfiles. As a result, server images for non-amd64 images copy in the go-runner amd64 binary instead of the go-runner that matches that architecture. This commit explicitly sets the '--platform=linux/${arch}' to ensure we're pulling the correct go-runner arch from the manifest list. Before: `FROM ${base_image}` After: `FROM --platform=linux/${arch} ${base_image}` ([#94552](https://github.com/kubernetes/kubernetes/pull/94552), [@justaugustus](https://github.com/justaugustus)) [SIG Release] - Bump node-problem-detector version to v0.8.5 to fix OOM detection in with Linux kernels 5.1+ ([#96716](https://github.com/kubernetes/kubernetes/pull/96716), [@tosi3k](https://github.com/tosi3k)) [SIG Cloud Provider, Scalability and Testing] - CSIDriver object can be deployed during volume attachment. ([#93710](https://github.com/kubernetes/kubernetes/pull/93710), [@Jiawei0227](https://github.com/Jiawei0227)) [SIG Apps, Node, Storage and Testing] - Ceph RBD volume expansion now works even when ceph.conf was not provided. ([#92027](https://github.com/kubernetes/kubernetes/pull/92027), [@juliantaylor](https://github.com/juliantaylor)) - Change plugin name in fsgroupapplymetrics of csi and flexvolume to distinguish different driver ([#95892](https://github.com/kubernetes/kubernetes/pull/95892), [@JornShen](https://github.com/JornShen)) [SIG Instrumentation, Storage and Testing] - Change the calculation of pod UIDs so that static pods get a unique value - will cause all containers to be killed and recreated after in-place upgrade. ([#87461](https://github.com/kubernetes/kubernetes/pull/87461), [@bboreham](https://github.com/bboreham)) [SIG Node] - Change the mount way from systemd to normal mount except ceph and glusterfs intree-volume. ([#94916](https://github.com/kubernetes/kubernetes/pull/94916), [@smileusd](https://github.com/smileusd)) [SIG Apps, Cloud Provider, Network, Node, Storage and Testing] - Changes to timeout parameter handling in 1.20.0-beta.2 have been reverted to avoid breaking backwards compatibility with existing clients. ([#96727](https://github.com/kubernetes/kubernetes/pull/96727), [@liggitt](https://github.com/liggitt)) [SIG API Machinery and Testing] - Clear UDP conntrack entry on endpoint changes when using nodeport ([#71573](https://github.com/kubernetes/kubernetes/pull/71573), [@JacobTanenbaum](https://github.com/JacobTanenbaum)) [SIG Network] - Cloud node controller: handle empty providerID from getProviderID ([#95342](https://github.com/kubernetes/kubernetes/pull/95342), [@nicolehanjing](https://github.com/nicolehanjing)) [SIG Cloud Provider] - Disable watchcache for events ([#96052](https://github.com/kubernetes/kubernetes/pull/96052), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery] - Disabled `LocalStorageCapacityIsolation` feature gate is honored during scheduling. ([#96092](https://github.com/kubernetes/kubernetes/pull/96092), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling] - Do not fail sorting empty elements. ([#94666](https://github.com/kubernetes/kubernetes/pull/94666), [@soltysh](https://github.com/soltysh)) [SIG CLI] - Dual-stack: make nodeipam compatible with existing single-stack clusters when dual-stack feature gate become enabled by default ([#90439](https://github.com/kubernetes/kubernetes/pull/90439), [@SataQiu](https://github.com/SataQiu)) [SIG API Machinery] - Duplicate owner reference entries in create/update/patch requests now get deduplicated by the API server. The client sending the request now receives a warning header in the API response. Clients should stop sending requests with duplicate owner references. The API server may reject such requests as early as 1.24. ([#96185](https://github.com/kubernetes/kubernetes/pull/96185), [@roycaihw](https://github.com/roycaihw)) [SIG API Machinery and Testing] - Endpoint slice controller now mirrors parent's service label to its corresponding endpoint slices. ([#94443](https://github.com/kubernetes/kubernetes/pull/94443), [@aojea](https://github.com/aojea)) - Ensure getPrimaryInterfaceID not panic when network interfaces for Azure VMSS are null ([#94355](https://github.com/kubernetes/kubernetes/pull/94355), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Exposes and sets a default timeout for the SubjectAccessReview client for DelegatingAuthorizationOptions ([#95725](https://github.com/kubernetes/kubernetes/pull/95725), [@p0lyn0mial](https://github.com/p0lyn0mial)) [SIG API Machinery and Cloud Provider] - Exposes and sets a default timeout for the TokenReview client for DelegatingAuthenticationOptions ([#96217](https://github.com/kubernetes/kubernetes/pull/96217), [@p0lyn0mial](https://github.com/p0lyn0mial)) [SIG API Machinery and Cloud Provider] - Fix CVE-2020-8555 for Quobyte client connections. ([#95206](https://github.com/kubernetes/kubernetes/pull/95206), [@misterikkit](https://github.com/misterikkit)) [SIG Storage] - Fix IP fragmentation of UDP and TCP packets not supported issues on LoadBalancer rules ([#96464](https://github.com/kubernetes/kubernetes/pull/96464), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - Fix a bug that DefaultPreemption plugin is disabled when using (legacy) scheduler policy. ([#96439](https://github.com/kubernetes/kubernetes/pull/96439), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling and Testing] - Fix a bug where loadbalancer deletion gets stuck because of missing resource group. ([#93962](https://github.com/kubernetes/kubernetes/pull/93962), [@phiphi282](https://github.com/phiphi282)) - Fix a concurrent map writes error in kubelet ([#93773](https://github.com/kubernetes/kubernetes/pull/93773), [@knight42](https://github.com/knight42)) [SIG Node] - Fix a panic in `kubectl debug` when a pod has multiple init or ephemeral containers. ([#94580](https://github.com/kubernetes/kubernetes/pull/94580), [@kiyoshim55](https://github.com/kiyoshim55)) - Fix a regression where kubeadm bails out with a fatal error when an optional version command line argument is supplied to the \"kubeadm upgrade plan\" command ([#94421](https://github.com/kubernetes/kubernetes/pull/94421), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - Fix azure disk attach failure for disk size bigger than 4TB ([#95463](https://github.com/kubernetes/kubernetes/pull/95463), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix azure disk data loss issue on Windows when unmount disk ([#95456](https://github.com/kubernetes/kubernetes/pull/95456), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Fix azure file migration panic ([#94853](https://github.com/kubernetes/kubernetes/pull/94853), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix bug in JSON path parser where an error occurs when a range is empty ([#95933](https://github.com/kubernetes/kubernetes/pull/95933), [@brianpursley](https://github.com/brianpursley)) [SIG API Machinery] - Fix client-go prometheus metrics to correctly present the API path accessed in some environments. ([#74363](https://github.com/kubernetes/kubernetes/pull/74363), [@aanm](https://github.com/aanm)) [SIG API Machinery] - Fix detach azure disk issue when vm not exist ([#95177](https://github.com/kubernetes/kubernetes/pull/95177), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix etcd_object_counts metric reported by kube-apiserver ([#94773](https://github.com/kubernetes/kubernetes/pull/94773), [@tkashem](https://github.com/tkashem)) [SIG API Machinery] - Fix incorrectly reported verbs for kube-apiserver metrics for CRD objects ([#93523](https://github.com/kubernetes/kubernetes/pull/93523), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery and Instrumentation] - Fix k8s.io/apimachinery/pkg/api/meta.SetStatusCondition to update ObservedGeneration ([#95961](https://github.com/kubernetes/kubernetes/pull/95961), [@KnicKnic](https://github.com/KnicKnic)) [SIG API Machinery] - Fix kubectl SchemaError on CRDs with schema using x-kubernetes-preserve-unknown-fields on array types. ([#94888](https://github.com/kubernetes/kubernetes/pull/94888), [@sttts](https://github.com/sttts)) [SIG API Machinery] - Fix memory leak in kube-apiserver when underlying time goes forth and back. ([#96266](https://github.com/kubernetes/kubernetes/pull/96266), [@chenyw1990](https://github.com/chenyw1990)) [SIG API Machinery] - Fix missing csi annotations on node during parallel csinode update. ([#94389](https://github.com/kubernetes/kubernetes/pull/94389), [@pacoxu](https://github.com/pacoxu)) [SIG Storage] - Fix network_programming_latency metric reporting for Endpoints/EndpointSlice deletions, where we don't have correct timestamp ([#95363](https://github.com/kubernetes/kubernetes/pull/95363), [@wojtek-t](https://github.com/wojtek-t)) [SIG Network and Scalability] - Fix paging issues when Azure API returns empty values with non-empty nextLink ([#96211](https://github.com/kubernetes/kubernetes/pull/96211), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Fix pull image error from multiple ACRs using azure managed identity ([#96355](https://github.com/kubernetes/kubernetes/pull/96355), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix race condition on timeCache locks. ([#94751](https://github.com/kubernetes/kubernetes/pull/94751), [@auxten](https://github.com/auxten)) - Fix regression on `kubectl portforward` when TCP and UCP services were configured on the same port. ([#94728](https://github.com/kubernetes/kubernetes/pull/94728), [@amorenoz](https://github.com/amorenoz)) - Fix scheduler cache snapshot when a Node is deleted before its Pods ([#95130](https://github.com/kubernetes/kubernetes/pull/95130), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - Fix the `cloudprovider_azure_api_request_duration_seconds` metric buckets to correctly capture the latency metrics. Previously, the majority of the calls would fall in the \"+Inf\" bucket. ([#94873](https://github.com/kubernetes/kubernetes/pull/94873), [@marwanad](https://github.com/marwanad)) [SIG Cloud Provider and Instrumentation] - Fix vSphere volumes that could be erroneously attached to wrong node ([#96224](https://github.com/kubernetes/kubernetes/pull/96224), [@gnufied](https://github.com/gnufied)) [SIG Cloud Provider and Storage] - Fix verb & scope reporting for kube-apiserver metrics (LIST reported instead of GET) ([#95562](https://github.com/kubernetes/kubernetes/pull/95562), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery and Testing] - Fix vsphere detach failure for static PVs ([#95447](https://github.com/kubernetes/kubernetes/pull/95447), [@gnufied](https://github.com/gnufied)) [SIG Cloud Provider and Storage] - Fix: azure disk resize error if source does not exist ([#93011](https://github.com/kubernetes/kubernetes/pull/93011), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix: detach azure disk broken on Azure Stack ([#94885](https://github.com/kubernetes/kubernetes/pull/94885), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix: resize Azure disk issue when it's in attached state ([#96705](https://github.com/kubernetes/kubernetes/pull/96705), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix: smb valid path error ([#95583](https://github.com/kubernetes/kubernetes/pull/95583), [@andyzhangx](https://github.com/andyzhangx)) [SIG Storage] - Fix: use sensitiveOptions on Windows mount ([#94126](https://github.com/kubernetes/kubernetes/pull/94126), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Fixed a bug causing incorrect formatting of `kubectl describe ingress`. ([#94985](https://github.com/kubernetes/kubernetes/pull/94985), [@howardjohn](https://github.com/howardjohn)) [SIG CLI and Network] - Fixed a bug in client-go where new clients with customized `Dial`, `Proxy`, `GetCert` config may get stale HTTP transports. ([#95427](https://github.com/kubernetes/kubernetes/pull/95427), [@roycaihw](https://github.com/roycaihw)) [SIG API Machinery] - Fixed a bug that prevents kubectl to validate CRDs with schema using x-kubernetes-preserve-unknown-fields on object fields. ([#96369](https://github.com/kubernetes/kubernetes/pull/96369), [@gautierdelorme](https://github.com/gautierdelorme)) [SIG API Machinery and Testing] - Fixed a bug that prevents the use of ephemeral containers in the presence of a validating admission webhook. ([#94685](https://github.com/kubernetes/kubernetes/pull/94685), [@verb](https://github.com/verb)) [SIG Node and Testing] - Fixed a bug where aggregator_unavailable_apiservice metrics were reported for deleted apiservices. ([#96421](https://github.com/kubernetes/kubernetes/pull/96421), [@dgrisonnet](https://github.com/dgrisonnet)) [SIG API Machinery and Instrumentation] - Fixed a bug where improper storage and comparison of endpoints led to excessive API traffic from the endpoints controller ([#94112](https://github.com/kubernetes/kubernetes/pull/94112), [@damemi](https://github.com/damemi)) [SIG Apps, Network and Testing] - Fixed a regression which prevented pods with `docker/default` seccomp annotations from being created in 1.19 if a PodSecurityPolicy was in place which did not allow `runtime/default` seccomp profiles. ([#95985](https://github.com/kubernetes/kubernetes/pull/95985), [@saschagrunert](https://github.com/saschagrunert)) [SIG Auth] - Fixed bug in reflector that couldn't recover from \"Too large resource version\" errors with API servers 1.17.0-1.18.5 ([#94316](https://github.com/kubernetes/kubernetes/pull/94316), [@janeczku](https://github.com/janeczku)) [SIG API Machinery] - Fixed bug where kubectl top pod output is not sorted when --sort-by and --containers flags are used together ([#93692](https://github.com/kubernetes/kubernetes/pull/93692), [@brianpursley](https://github.com/brianpursley)) [SIG CLI] - Fixed kubelet creating extra sandbox for pods with RestartPolicyOnFailure after all containers succeeded ([#92614](https://github.com/kubernetes/kubernetes/pull/92614), [@tnqn](https://github.com/tnqn)) [SIG Node and Testing] - Fixes an issue proxying to ipv6 pods without specifying a port ([#94834](https://github.com/kubernetes/kubernetes/pull/94834), [@liggitt](https://github.com/liggitt)) [SIG API Machinery and Network] - Fixes code generation for non-namespaced create subresources fake client test. ([#96586](https://github.com/kubernetes/kubernetes/pull/96586), [@Doude](https://github.com/Doude)) [SIG API Machinery] - Fixes high CPU usage in kubectl drain ([#95260](https://github.com/kubernetes/kubernetes/pull/95260), [@amandahla](https://github.com/amandahla)) [SIG CLI] - For vSphere Cloud Provider, If VM of worker node is deleted, the node will also be deleted by node controller ([#92608](https://github.com/kubernetes/kubernetes/pull/92608), [@lubronzhan](https://github.com/lubronzhan)) [SIG Cloud Provider] - Gracefully delete nodes when their parent scale set went missing ([#95289](https://github.com/kubernetes/kubernetes/pull/95289), [@bpineau](https://github.com/bpineau)) [SIG Cloud Provider] - HTTP/2 connection health check is enabled by default in all Kubernetes clients. The feature should work out-of-the-box. If needed, users can tune the feature via the HTTP2_READ_IDLE_TIMEOUT_SECONDS and HTTP2_PING_TIMEOUT_SECONDS environment variables. The feature is disabled if HTTP2_READ_IDLE_TIMEOUT_SECONDS is set to 0. ([#95981](https://github.com/kubernetes/kubernetes/pull/95981), [@caesarxuchao](https://github.com/caesarxuchao)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation and Node] - If the user specifies an invalid timeout in the request URL, the request will be aborted with an HTTP 400. - If the user specifies a timeout in the request URL that exceeds the maximum request deadline allowed by the apiserver, the request will be aborted with an HTTP 400. ([#96061](https://github.com/kubernetes/kubernetes/pull/96061), [@tkashem](https://github.com/tkashem)) [SIG API Machinery, Network and Testing] - If we set SelectPolicy MinPolicySelect on scaleUp behavior or scaleDown behavior,Horizontal Pod Autoscaler doesn`t automatically scale the number of pods correctly ([#95647](https://github.com/kubernetes/kubernetes/pull/95647), [@JoshuaAndrew](https://github.com/JoshuaAndrew)) [SIG Apps and Autoscaling] - Ignore apparmor for non-linux operating systems ([#93220](https://github.com/kubernetes/kubernetes/pull/93220), [@wawa0210](https://github.com/wawa0210)) [SIG Node and Windows] - Ignore root user check when windows pod starts ([#92355](https://github.com/kubernetes/kubernetes/pull/92355), [@wawa0210](https://github.com/wawa0210)) [SIG Node and Windows] - Improve error messages related to nodePort endpoint changes conntrack entries cleanup. ([#96251](https://github.com/kubernetes/kubernetes/pull/96251), [@ravens](https://github.com/ravens)) [SIG Network] - In dual-stack clusters, kubelet will now set up both IPv4 and IPv6 iptables rules, which may fix some problems, eg with HostPorts. ([#94474](https://github.com/kubernetes/kubernetes/pull/94474), [@danwinship](https://github.com/danwinship)) [SIG Network and Node] - Increase maximum IOPS of AWS EBS io1 volume to current maximum (64,000). ([#90014](https://github.com/kubernetes/kubernetes/pull/90014), [@jacobmarble](https://github.com/jacobmarble)) - Ipvs: ensure selected scheduler kernel modules are loaded ([#93040](https://github.com/kubernetes/kubernetes/pull/93040), [@cmluciano](https://github.com/cmluciano)) [SIG Network] - K8s.io/apimachinery: runtime.DefaultUnstructuredConverter.FromUnstructured now handles converting integer fields to typed float values ([#93250](https://github.com/kubernetes/kubernetes/pull/93250), [@liggitt](https://github.com/liggitt)) [SIG API Machinery] - Kube-proxy now trims extra spaces found in loadBalancerSourceRanges to match Service validation. ([#94107](https://github.com/kubernetes/kubernetes/pull/94107), [@robscott](https://github.com/robscott)) [SIG Network] - Kubeadm ensures \"kubeadm reset\" does not unmount the root \"/var/lib/kubelet\" directory if it is mounted by the user. ([#93702](https://github.com/kubernetes/kubernetes/pull/93702), [@thtanaka](https://github.com/thtanaka)) - Kubeadm now makes sure the etcd manifest is regenerated upon upgrade even when no etcd version change takes place ([#94395](https://github.com/kubernetes/kubernetes/pull/94395), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle] - Kubeadm now warns (instead of error out) on missing \"ca.key\" files for root CA, front-proxy CA and etcd CA, during \"kubeadm join --control-plane\" if the user has provided all certificates, keys and kubeconfig files which require signing with the given CA keys. ([#94988](https://github.com/kubernetes/kubernetes/pull/94988), [@neolit123](https://github.com/neolit123)) - Kubeadm: add missing \"--experimental-patches\" flag to \"kubeadm init phase control-plane\" ([#95786](https://github.com/kubernetes/kubernetes/pull/95786), [@Sh4d1](https://github.com/Sh4d1)) [SIG Cluster Lifecycle] - Kubeadm: avoid a panic when determining if the running version of CoreDNS is supported during upgrades ([#94299](https://github.com/kubernetes/kubernetes/pull/94299), [@zouyee](https://github.com/zouyee)) [SIG Cluster Lifecycle] - Kubeadm: ensure the etcd data directory is created with 0700 permissions during control-plane init and join ([#94102](https://github.com/kubernetes/kubernetes/pull/94102), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: fix coredns migration should be triggered when there are newdefault configs during kubeadm upgrade ([#96907](https://github.com/kubernetes/kubernetes/pull/96907), [@pacoxu](https://github.com/pacoxu)) [SIG Cluster Lifecycle] - Kubeadm: fix the bug that kubeadm tries to call 'docker info' even if the CRI socket was for another CR ([#94555](https://github.com/kubernetes/kubernetes/pull/94555), [@SataQiu](https://github.com/SataQiu)) [SIG Cluster Lifecycle] - Kubeadm: for Docker as the container runtime, make the \"kubeadm reset\" command stop containers before removing them ([#94586](https://github.com/kubernetes/kubernetes/pull/94586), [@BedivereZero](https://github.com/BedivereZero)) [SIG Cluster Lifecycle] - Kubeadm: make the kubeconfig files for the kube-controller-manager and kube-scheduler use the LocalAPIEndpoint instead of the ControlPlaneEndpoint. This makes kubeadm clusters more reseliant to version skew problems during immutable upgrades: https://kubernetes.io/docs/setup/release/version-skew-policy/#kube-controller-manager-kube-scheduler-and-cloud-controller-manager ([#94398](https://github.com/kubernetes/kubernetes/pull/94398), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: relax the validation of kubeconfig server URLs. Allow the user to define custom kubeconfig server URLs without erroring out during validation of existing kubeconfig files (e.g. when using external CA mode). ([#94816](https://github.com/kubernetes/kubernetes/pull/94816), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubectl: print error if users place flags before plugin name ([#92343](https://github.com/kubernetes/kubernetes/pull/92343), [@knight42](https://github.com/knight42)) [SIG CLI] - Kubelet: assume that swap is disabled when `/proc/swaps` does not exist ([#93931](https://github.com/kubernetes/kubernetes/pull/93931), [@SataQiu](https://github.com/SataQiu)) [SIG Node] - New Azure instance types do now have correct max data disk count information. ([#94340](https://github.com/kubernetes/kubernetes/pull/94340), [@ialidzhikov](https://github.com/ialidzhikov)) [SIG Cloud Provider and Storage] - Port mapping now allows the same `containerPort` of different containers to different `hostPort` without naming the mapping explicitly. ([#94494](https://github.com/kubernetes/kubernetes/pull/94494), [@SergeyKanzhelev](https://github.com/SergeyKanzhelev)) - Print go stack traces at -v=4 and not -v=2 ([#94663](https://github.com/kubernetes/kubernetes/pull/94663), [@soltysh](https://github.com/soltysh)) [SIG CLI] - Recreate EndpointSlices on rapid Service creation. ([#94730](https://github.com/kubernetes/kubernetes/pull/94730), [@robscott](https://github.com/robscott)) - Reduce volume name length for vsphere volumes ([#96533](https://github.com/kubernetes/kubernetes/pull/96533), [@gnufied](https://github.com/gnufied)) [SIG Storage] - Remove ready file and its directory (which is created during volume SetUp) during emptyDir volume TearDown. ([#95770](https://github.com/kubernetes/kubernetes/pull/95770), [@jingxu97](https://github.com/jingxu97)) [SIG Storage] - Reorganized iptables rules to fix a performance issue ([#95252](https://github.com/kubernetes/kubernetes/pull/95252), [@tssurya](https://github.com/tssurya)) [SIG Network] - Require feature flag CustomCPUCFSQuotaPeriod if setting a non-default cpuCFSQuotaPeriod in kubelet config. ([#94687](https://github.com/kubernetes/kubernetes/pull/94687), [@karan](https://github.com/karan)) [SIG Node] - Resolves a regression in 1.19+ with workloads targeting deprecated beta os/arch labels getting stuck in NodeAffinity status on node startup. ([#96810](https://github.com/kubernetes/kubernetes/pull/96810), [@liggitt](https://github.com/liggitt)) [SIG Node] - Resolves non-deterministic behavior of the garbage collection controller when ownerReferences with incorrect data are encountered. Events with a reason of `OwnerRefInvalidNamespace` are recorded when namespace mismatches between child and owner objects are detected. The [kubectl-check-ownerreferences](https://github.com/kubernetes-sigs/kubectl-check-ownerreferences) tool can be run prior to upgrading to locate existing objects with invalid ownerReferences. - A namespaced object with an ownerReference referencing a uid of a namespaced kind which does not exist in the same namespace is now consistently treated as though that owner does not exist, and the child object is deleted. - A cluster-scoped object with an ownerReference referencing a uid of a namespaced kind is now consistently treated as though that owner is not resolvable, and the child object is ignored by the garbage collector. ([#92743](https://github.com/kubernetes/kubernetes/pull/92743), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Apps and Testing] - Skip [k8s.io/kubernetes@v1.19.0/test/e2e/storage/testsuites/base.go:162]: Driver azure-disk doesn't support snapshot type DynamicSnapshot -- skipping skip [k8s.io/kubernetes@v1.19.0/test/e2e/storage/testsuites/base.go:185]: Driver azure-disk doesn't support ntfs -- skipping ([#96144](https://github.com/kubernetes/kubernetes/pull/96144), [@qinpingli](https://github.com/qinpingli)) [SIG Storage and Testing] - StatefulSet Controller now waits for PersistentVolumeClaim deletion before creating pods. ([#93457](https://github.com/kubernetes/kubernetes/pull/93457), [@ymmt2005](https://github.com/ymmt2005)) - StreamWatcher now calls HandleCrash at appropriate sequence. ([#93108](https://github.com/kubernetes/kubernetes/pull/93108), [@lixiaobing1](https://github.com/lixiaobing1)) - Support the node label `node.kubernetes.io/exclude-from-external-load-balancers` ([#95542](https://github.com/kubernetes/kubernetes/pull/95542), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - The AWS network load balancer attributes can now be specified during service creation ([#95247](https://github.com/kubernetes/kubernetes/pull/95247), [@kishorj](https://github.com/kishorj)) [SIG Cloud Provider] - The `/debug/api_priority_and_fairness/dump_requests` path at an apiserver will no longer return a phantom line for each exempt priority level. ([#93406](https://github.com/kubernetes/kubernetes/pull/93406), [@MikeSpreitzer](https://github.com/MikeSpreitzer)) [SIG API Machinery] - The kube-apiserver will no longer serve APIs that should have been deleted in GA non-alpha levels.  Alpha levels will continue to serve the removed APIs so that CI doesn't immediately break. ([#96525](https://github.com/kubernetes/kubernetes/pull/96525), [@deads2k](https://github.com/deads2k)) [SIG API Machinery] - The kubelet recognizes the --containerd-namespace flag to configure the namespace used by cadvisor. ([#87054](https://github.com/kubernetes/kubernetes/pull/87054), [@changyaowei](https://github.com/changyaowei)) [SIG Node] - Unhealthy pods covered by PDBs can be successfully evicted if enough healthy pods are available. ([#94381](https://github.com/kubernetes/kubernetes/pull/94381), [@michaelgugino](https://github.com/michaelgugino)) [SIG Apps] - Update Calico to v3.15.2 ([#94241](https://github.com/kubernetes/kubernetes/pull/94241), [@lmm](https://github.com/lmm)) [SIG Cloud Provider] - Update default etcd server version to 3.4.13 ([#94287](https://github.com/kubernetes/kubernetes/pull/94287), [@jingyih](https://github.com/jingyih)) [SIG API Machinery, Cloud Provider, Cluster Lifecycle and Testing] - Update max azure data disk count map ([#96308](https://github.com/kubernetes/kubernetes/pull/96308), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Update the PIP when it is not in the Succeeded provisioning state during the LB update. ([#95748](https://github.com/kubernetes/kubernetes/pull/95748), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - Update the frontend IP config when the service's `pipName` annotation is changed ([#95813](https://github.com/kubernetes/kubernetes/pull/95813), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - Update the route table tag in the route reconcile loop ([#96545](https://github.com/kubernetes/kubernetes/pull/96545), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - Use NLB Subnet CIDRs instead of VPC CIDRs in Health Check SG Rules ([#93515](https://github.com/kubernetes/kubernetes/pull/93515), [@t0rr3sp3dr0](https://github.com/t0rr3sp3dr0)) [SIG Cloud Provider] - Users will see increase in time for deletion of pods and also guarantee that removal of pod from api server  would mean deletion of all the resources from container runtime. ([#92817](https://github.com/kubernetes/kubernetes/pull/92817), [@kmala](https://github.com/kmala)) [SIG Node] - Very large patches may now be specified to `kubectl patch` with the `--patch-file` flag instead of including them directly on the command line. The `--patch` and `--patch-file` flags are mutually exclusive. ([#93548](https://github.com/kubernetes/kubernetes/pull/93548), [@smarterclayton](https://github.com/smarterclayton)) [SIG CLI] - Volume binding: report UnschedulableAndUnresolvable status instead of an error when bound PVs not found ([#95541](https://github.com/kubernetes/kubernetes/pull/95541), [@cofyc](https://github.com/cofyc)) [SIG Apps, Scheduling and Storage] - Warn instead of fail when creating Roles and ClusterRoles with custom verbs via kubectl ([#92492](https://github.com/kubernetes/kubernetes/pull/92492), [@eddiezane](https://github.com/eddiezane)) [SIG CLI] - When creating a PVC with the volume.beta.kubernetes.io/storage-provisioner annotation already set, the PV controller might have incorrectly deleted the newly provisioned PV instead of binding it to the PVC, depending on timing and system load. ([#95909](https://github.com/kubernetes/kubernetes/pull/95909), [@pohly](https://github.com/pohly)) [SIG Apps and Storage] - [kubectl] Fail when local source file doesn't exist ([#90333](https://github.com/kubernetes/kubernetes/pull/90333), [@bamarni](https://github.com/bamarni)) [SIG CLI] ### 기타 (정리 또는 플레이크(flake)) - **Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.**: <!-- This section can be blank if this pull request does not require a release note. When adding links which point to resources within git repositories, like KEPs or supporting documentation, please reference a specific commit and avoid linking directly to the master branch. This ensures that links reference a specific point in time, rather than a document that may change over time. See here for guidance on getting permanent links to files: https://help.github.com/en/articles/getting-permanent-links-to-files Please use the following format for linking documentation: - [KEP]: <link> - [Usage]: <link> - [Other doc]: <link> --> ([#96443](https://github.com/kubernetes/kubernetes/pull/96443), [@alaypatel07](https://github.com/alaypatel07)) [SIG Apps] - --redirect-container-streaming is no longer functional. The flag will be removed in v1.22 ([#95935](https://github.com/kubernetes/kubernetes/pull/95935), [@tallclair](https://github.com/tallclair)) [SIG Node] - A new metric `requestAbortsTotal` has been introduced that counts aborted requests for each `group`, `version`, `verb`, `resource`, `subresource` and `scope`. ([#95002](https://github.com/kubernetes/kubernetes/pull/95002), [@p0lyn0mial](https://github.com/p0lyn0mial)) [SIG API Machinery, Cloud Provider, Instrumentation and Scheduling] - API priority and fairness metrics use snake_case in label names ([#96236](https://github.com/kubernetes/kubernetes/pull/96236), [@adtac](https://github.com/adtac)) [SIG API Machinery, Cluster Lifecycle, Instrumentation and Testing] - Add fine grained debugging to intra-pod conformance test to troubleshoot networking issues for potentially unhealthy nodes when running conformance or sonobuoy tests. ([#93837](https://github.com/kubernetes/kubernetes/pull/93837), [@jayunit100](https://github.com/jayunit100)) - Add the following metrics: - network_plugin_operations_total - network_plugin_operations_errors_total ([#93066](https://github.com/kubernetes/kubernetes/pull/93066), [@AnishShah](https://github.com/AnishShah)) - Adds a bootstrapping ClusterRole, ClusterRoleBinding and group for /metrics, /livez/*, /readyz/*, & /healthz/- endpoints. ([#93311](https://github.com/kubernetes/kubernetes/pull/93311), [@logicalhan](https://github.com/logicalhan)) [SIG API Machinery, Auth, Cloud Provider and Instrumentation] - AdmissionReview objects sent for the creation of Namespace API objects now populate the `namespace` attribute consistently (previously the `namespace` attribute was empty for Namespace creation via POST requests, and populated for Namespace creation via server-side-apply PATCH requests) ([#95012](https://github.com/kubernetes/kubernetes/pull/95012), [@nodo](https://github.com/nodo)) [SIG API Machinery and Testing] - Applies translations on all command descriptions ([#95439](https://github.com/kubernetes/kubernetes/pull/95439), [@HerrNaN](https://github.com/HerrNaN)) [SIG CLI] - Base-images: Update to debian-iptables:buster-v1.3.0 - Uses iptables 1.8.5 - base-images: Update to debian-base:buster-v1.2.0 - cluster/images/etcd: Build etcd:3.4.13-1 image - Uses debian-base:buster-v1.2.0 ([#94733](https://github.com/kubernetes/kubernetes/pull/94733), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery, Release and Testing] - Changed: default \"Accept-Encoding\" header removed from HTTP probes. See https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#http-probes ([#96127](https://github.com/kubernetes/kubernetes/pull/96127), [@fonsecas72](https://github.com/fonsecas72)) [SIG Network and Node] - Client-go header logging (at verbosity levels >= 9) now masks `Authorization` header contents ([#95316](https://github.com/kubernetes/kubernetes/pull/95316), [@sfowl](https://github.com/sfowl)) [SIG API Machinery] - Decrease warning message frequency on setting volume ownership for configmap/secret. ([#92878](https://github.com/kubernetes/kubernetes/pull/92878), [@jvanz](https://github.com/jvanz)) - Enhance log information of verifyRunAsNonRoot, add pod, container information ([#94911](https://github.com/kubernetes/kubernetes/pull/94911), [@wawa0210](https://github.com/wawa0210)) [SIG Node] - Fix func name NewCreateCreateDeploymentOptions ([#91931](https://github.com/kubernetes/kubernetes/pull/91931), [@lixiaobing1](https://github.com/lixiaobing1)) [SIG CLI] - Fix kubelet to properly log when a container is started. Previously, kubelet may log that container is dead and was restarted when it was actually started for the first time. This behavior only happened on pods with initContainers and regular containers. ([#91469](https://github.com/kubernetes/kubernetes/pull/91469), [@rata](https://github.com/rata)) - Fixes the message about no auth for metrics in scheduler. ([#94035](https://github.com/kubernetes/kubernetes/pull/94035), [@zhouya0](https://github.com/zhouya0)) [SIG Scheduling] - Generators for services are removed from kubectl ([#95256](https://github.com/kubernetes/kubernetes/pull/95256), [@Git-Jiro](https://github.com/Git-Jiro)) [SIG CLI] - Introduce kubectl-convert plugin. ([#96190](https://github.com/kubernetes/kubernetes/pull/96190), [@soltysh](https://github.com/soltysh)) [SIG CLI and Testing] - Kube-scheduler now logs processed component config at startup ([#96426](https://github.com/kubernetes/kubernetes/pull/96426), [@damemi](https://github.com/damemi)) [SIG Scheduling] - Kubeadm: Separate argument key/value in log msg ([#94016](https://github.com/kubernetes/kubernetes/pull/94016), [@mrueg](https://github.com/mrueg)) [SIG Cluster Lifecycle] - Kubeadm: remove the CoreDNS check for known image digests when applying the addon ([#94506](https://github.com/kubernetes/kubernetes/pull/94506), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Kubeadm: update the default pause image version to 1.4.0 on Windows. With this update the image supports Windows versions 1809 (2019LTS), 1903, 1909, 2004 ([#95419](https://github.com/kubernetes/kubernetes/pull/95419), [@jsturtevant](https://github.com/jsturtevant)) [SIG Cluster Lifecycle and Windows] - Kubectl: the `generator` flag of `kubectl autoscale` has been deprecated and has no effect, it will be removed in a feature release ([#92998](https://github.com/kubernetes/kubernetes/pull/92998), [@SataQiu](https://github.com/SataQiu)) [SIG CLI] - Lock ExternalPolicyForExternalIP to default, this feature gate will be removed in 1.22. ([#94581](https://github.com/kubernetes/kubernetes/pull/94581), [@knabben](https://github.com/knabben)) [SIG Network] - Mask ceph RBD adminSecrets in logs when logLevel >= 4. ([#95245](https://github.com/kubernetes/kubernetes/pull/95245), [@sfowl](https://github.com/sfowl)) - Remove offensive words from kubectl cluster-info command. ([#95202](https://github.com/kubernetes/kubernetes/pull/95202), [@rikatz](https://github.com/rikatz)) - Remove support for \"ci/k8s-master\" version label in kubeadm, use \"ci/latest\" instead. See [kubernetes/test-infra#18517](https://github.com/kubernetes/test-infra/pull/18517). ([#93626](https://github.com/kubernetes/kubernetes/pull/93626), [@vikkyomkar](https://github.com/vikkyomkar)) - Remove the dependency of csi-translation-lib module on apiserver/cloud-provider/controller-manager ([#95543](https://github.com/kubernetes/kubernetes/pull/95543), [@wawa0210](https://github.com/wawa0210)) [SIG Release] - Scheduler framework interface moved from pkg/scheduler/framework/v1alpha to pkg/scheduler/framework ([#95069](https://github.com/kubernetes/kubernetes/pull/95069), [@farah](https://github.com/farah)) [SIG Scheduling, Storage and Testing] - Service.beta.kubernetes.io/azure-load-balancer-disable-tcp-reset is removed.  All Standard load balancers will always enable tcp resets. ([#94297](https://github.com/kubernetes/kubernetes/pull/94297), [@MarcPow](https://github.com/MarcPow)) [SIG Cloud Provider] - Stop propagating SelfLink (deprecated in 1.16) in kube-apiserver ([#94397](https://github.com/kubernetes/kubernetes/pull/94397), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery and Testing] - Strip unnecessary security contexts on Windows ([#93475](https://github.com/kubernetes/kubernetes/pull/93475), [@ravisantoshgudimetla](https://github.com/ravisantoshgudimetla)) [SIG Node, Testing and Windows] - To ensure the code be strong,  add unit test for GetAddressAndDialer ([#93180](https://github.com/kubernetes/kubernetes/pull/93180), [@FreeZhang61](https://github.com/FreeZhang61)) [SIG Node] - UDP and SCTP protocols can left stale connections that need to be cleared to avoid services disruption, but they can cause problems that are hard to debug. Kubernetes components using a loglevel greater or equal than 4 will log the conntrack operations and its output, to show the entries that were deleted. ([#95694](https://github.com/kubernetes/kubernetes/pull/95694), [@aojea](https://github.com/aojea)) [SIG Network] - Update CNI plugins to v0.8.7 ([#94367](https://github.com/kubernetes/kubernetes/pull/94367), [@justaugustus](https://github.com/justaugustus)) [SIG Cloud Provider, Network, Node, Release and Testing] - Update cri-tools to [v1.19.0](https://github.com/kubernetes-sigs/cri-tools/releases/tag/v1.19.0) ([#94307](https://github.com/kubernetes/kubernetes/pull/94307), [@xmudrii](https://github.com/xmudrii)) [SIG Cloud Provider] - Update etcd client side to v3.4.13 ([#94259](https://github.com/kubernetes/kubernetes/pull/94259), [@jingyih](https://github.com/jingyih)) [SIG API Machinery and Cloud Provider] - Users will now be able to configure all supported values for AWS NLB health check interval and thresholds for new resources. ([#96312](https://github.com/kubernetes/kubernetes/pull/96312), [@kishorj](https://github.com/kishorj)) [SIG Cloud Provider] - V1helpers.MatchNodeSelectorTerms now accepts just a Node and a list of Terms ([#95871](https://github.com/kubernetes/kubernetes/pull/95871), [@damemi](https://github.com/damemi)) [SIG Apps, Scheduling and Storage] - Vsphere: improve logging message on node cache refresh event ([#95236](https://github.com/kubernetes/kubernetes/pull/95236), [@andrewsykim](https://github.com/andrewsykim)) [SIG Cloud Provider] - `MatchNodeSelectorTerms` function moved to `k8s.io/component-helpers` ([#95531](https://github.com/kubernetes/kubernetes/pull/95531), [@damemi](https://github.com/damemi)) [SIG Apps, Scheduling and Storage] - `kubectl api-resources` now prints the API version (as 'API group/version', same as output of `kubectl api-versions`). The column APIGROUP is now APIVERSION ([#95253](https://github.com/kubernetes/kubernetes/pull/95253), [@sallyom](https://github.com/sallyom)) [SIG CLI] - `kubectl get ingress` now prefers the `networking.k8s.io/v1` over `extensions/v1beta1` (deprecated since v1.14). To explicitly request the deprecated version, use `kubectl get ingress.v1beta1.extensions`. ([#94309](https://github.com/kubernetes/kubernetes/pull/94309), [@liggitt](https://github.com/liggitt)) [SIG API Machinery and CLI] </ins> ## 의존성 ### 추가 <del> - cloud.google.com/go/bigquery: v1.0.1 - cloud.google.com/go/datastore: v1.0.0 - cloud.google.com/go/pubsub: v1.0.1 - cloud.google.com/go/storage: v1.0.0 - dmitri.shuralyov.com/gpu/mtl: 666a987 - github.com/cespare/xxhash/v2: [v2.1.1](https://github.com/cespare/xxhash/v2/tree/v2.1.1) - github.com/checkpoint-restore/go-criu/v4: [v4.0.2](https://github.com/checkpoint-restore/go-criu/v4/tree/v4.0.2) - github.com/chzyer/logex: [v1.1.10](https://github.com/chzyer/logex/tree/v1.1.10) - github.com/chzyer/readline: [2972be2](https://github.com/chzyer/readline/tree/2972be2) - github.com/chzyer/test: [a1ea475](https://github.com/chzyer/test/tree/a1ea475) - github.com/containerd/cgroups: [0dbf7f0](https://github.com/containerd/cgroups/tree/0dbf7f0) - github.com/containerd/continuity: [aaeac12](https://github.com/containerd/continuity/tree/aaeac12) - github.com/containerd/fifo: [a9fb20d](https://github.com/containerd/fifo/tree/a9fb20d) - github.com/containerd/go-runc: [5a6d9f3](https://github.com/containerd/go-runc/tree/5a6d9f3) - github.com/containerd/ttrpc: [v1.0.0](https://github.com/containerd/ttrpc/tree/v1.0.0) - github.com/coreos/bbolt: [v1.3.2](https://github.com/coreos/bbolt/tree/v1.3.2) - github.com/coreos/go-systemd/v22: [v22.1.0](https://github.com/coreos/go-systemd/v22/tree/v22.1.0) - github.com/cpuguy83/go-md2man/v2: [v2.0.0](https://github.com/cpuguy83/go-md2man/v2/tree/v2.0.0) - github.com/docopt/docopt-go: [ee0de3b](https://github.com/docopt/docopt-go/tree/ee0de3b) - github.com/go-gl/glfw/v3.3/glfw: [12ad95a](https://github.com/go-gl/glfw/v3.3/glfw/tree/12ad95a) - github.com/go-ini/ini: [v1.9.0](https://github.com/go-ini/ini/tree/v1.9.0) - github.com/godbus/dbus/v5: [v5.0.3](https://github.com/godbus/dbus/v5/tree/v5.0.3) - github.com/ianlancetaylor/demangle: [5e5cf60](https://github.com/ianlancetaylor/demangle/tree/5e5cf60) - github.com/ishidawataru/sctp: [7c296d4](https://github.com/ishidawataru/sctp/tree/7c296d4) - github.com/moby/ipvs: [v1.0.1](https://github.com/moby/ipvs/tree/v1.0.1) - github.com/moby/sys/mountinfo: [v0.1.3](https://github.com/moby/sys/mountinfo/tree/v0.1.3) - github.com/moby/term: [672ec06](https://github.com/moby/term/tree/672ec06) - github.com/russross/blackfriday/v2: [v2.0.1](https://github.com/russross/blackfriday/v2/tree/v2.0.1) - github.com/shurcooL/sanitized_anchor_name: [v1.0.0](https://github.com/shurcooL/sanitized_anchor_name/tree/v1.0.0) - github.com/ugorji/go: [v1.1.4](https://github.com/ugorji/go/tree/v1.1.4) - github.com/yuin/goldmark: [v1.1.27](https://github.com/yuin/goldmark/tree/v1.1.27) - google.golang.org/protobuf: v1.24.0 - gotest.tools/v3: v3.0.2 - k8s.io/klog/v2: v2.2.0 </del> <ins> - cloud.google.com/go/firestore: v1.1.0 - github.com/Azure/go-autorest: [v14.2.0+incompatible](https://github.com/Azure/go-autorest/tree/v14.2.0) - github.com/armon/go-metrics: [f0300d1](https://github.com/armon/go-metrics/tree/f0300d1) - github.com/armon/go-radix: [7fddfc3](https://github.com/armon/go-radix/tree/7fddfc3) - github.com/bketelsen/crypt: [5cbc8cc](https://github.com/bketelsen/crypt/tree/5cbc8cc) - github.com/form3tech-oss/jwt-go: [v3.2.2+incompatible](https://github.com/form3tech-oss/jwt-go/tree/v3.2.2) - github.com/fvbommel/sortorder: [v1.0.1](https://github.com/fvbommel/sortorder/tree/v1.0.1) - github.com/hashicorp/consul/api: [v1.1.0](https://github.com/hashicorp/consul/api/tree/v1.1.0) - github.com/hashicorp/consul/sdk: [v0.1.1](https://github.com/hashicorp/consul/sdk/tree/v0.1.1) - github.com/hashicorp/errwrap: [v1.0.0](https://github.com/hashicorp/errwrap/tree/v1.0.0) - github.com/hashicorp/go-cleanhttp: [v0.5.1](https://github.com/hashicorp/go-cleanhttp/tree/v0.5.1) - github.com/hashicorp/go-immutable-radix: [v1.0.0](https://github.com/hashicorp/go-immutable-radix/tree/v1.0.0) - github.com/hashicorp/go-msgpack: [v0.5.3](https://github.com/hashicorp/go-msgpack/tree/v0.5.3) - github.com/hashicorp/go-multierror: [v1.0.0](https://github.com/hashicorp/go-multierror/tree/v1.0.0) - github.com/hashicorp/go-rootcerts: [v1.0.0](https://github.com/hashicorp/go-rootcerts/tree/v1.0.0) - github.com/hashicorp/go-sockaddr: [v1.0.0](https://github.com/hashicorp/go-sockaddr/tree/v1.0.0) - github.com/hashicorp/go-uuid: [v1.0.1](https://github.com/hashicorp/go-uuid/tree/v1.0.1) - github.com/hashicorp/go.net: [v0.0.1](https://github.com/hashicorp/go.net/tree/v0.0.1) - github.com/hashicorp/logutils: [v1.0.0](https://github.com/hashicorp/logutils/tree/v1.0.0) - github.com/hashicorp/mdns: [v1.0.0](https://github.com/hashicorp/mdns/tree/v1.0.0) - github.com/hashicorp/memberlist: [v0.1.3](https://github.com/hashicorp/memberlist/tree/v0.1.3) - github.com/hashicorp/serf: [v0.8.2](https://github.com/hashicorp/serf/tree/v0.8.2) - github.com/jmespath/go-jmespath/internal/testify: [v1.5.1](https://github.com/jmespath/go-jmespath/internal/testify/tree/v1.5.1) - github.com/mitchellh/cli: [v1.0.0](https://github.com/mitchellh/cli/tree/v1.0.0) - github.com/mitchellh/go-testing-interface: [v1.0.0](https://github.com/mitchellh/go-testing-interface/tree/v1.0.0) - github.com/mitchellh/gox: [v0.4.0](https://github.com/mitchellh/gox/tree/v0.4.0) - github.com/mitchellh/iochan: [v1.0.0](https://github.com/mitchellh/iochan/tree/v1.0.0) - github.com/pascaldekloe/goe: [57f6aae](https://github.com/pascaldekloe/goe/tree/57f6aae) - github.com/posener/complete: [v1.1.1](https://github.com/posener/complete/tree/v1.1.1) - github.com/ryanuber/columnize: [9b3edd6](https://github.com/ryanuber/columnize/tree/9b3edd6) - github.com/sean-/seed: [e2103e2](https://github.com/sean-/seed/tree/e2103e2) - github.com/subosito/gotenv: [v1.2.0](https://github.com/subosito/gotenv/tree/v1.2.0) - github.com/willf/bitset: [d5bec33](https://github.com/willf/bitset/tree/d5bec33) - gopkg.in/ini.v1: v1.51.0 - gopkg.in/yaml.v3: 9f266ea - rsc.io/quote/v3: v3.1.0 - rsc.io/sampler: v1.3.0 </ins> ### 변경 <del> - cloud.google.com/go: v0.38.0 → v0.51.0 - github.com/Azure/azure-sdk-for-go: [v35.0.0+incompatible → v43.0.0+incompatible](https://github.com/Azure/azure-sdk-for-go/compare/v35.0.0...v43.0.0) - github.com/Azure/go-autorest/autorest/adal: [v0.5.0 → v0.8.2](https://github.com/Azure/go-autorest/autorest/adal/compare/v0.5.0...v0.8.2) - github.com/Azure/go-autorest/autorest/date: [v0.1.0 → v0.2.0](https://github.com/Azure/go-autorest/autorest/date/compare/v0.1.0...v0.2.0) - github.com/Azure/go-autorest/autorest/mocks: [v0.2.0 → v0.3.0](https://github.com/Azure/go-autorest/autorest/mocks/compare/v0.2.0...v0.3.0) - github.com/Azure/go-autorest/autorest: [v0.9.0 → v0.9.6](https://github.com/Azure/go-autorest/autorest/compare/v0.9.0...v0.9.6) - github.com/GoogleCloudPlatform/k8s-cloud-provider: [27a4ced → 7901bc8](https://github.com/GoogleCloudPlatform/k8s-cloud-provider/compare/27a4ced...7901bc8) - github.com/Microsoft/go-winio: [v0.4.14 → fc70bd9](https://github.com/Microsoft/go-winio/compare/v0.4.14...fc70bd9) - github.com/Microsoft/hcsshim: [672e52e → 5eafd15](https://github.com/Microsoft/hcsshim/compare/672e52e...5eafd15) - github.com/alecthomas/template: [a0175ee → fb15b89](https://github.com/alecthomas/template/compare/a0175ee...fb15b89) - github.com/alecthomas/units: [2efee85 → c3de453](https://github.com/alecthomas/units/compare/2efee85...c3de453) - github.com/beorn7/perks: [v1.0.0 → v1.0.1](https://github.com/beorn7/perks/compare/v1.0.0...v1.0.1) - github.com/cilium/ebpf: [95b36a5 → 1c8d4c9](https://github.com/cilium/ebpf/compare/95b36a5...1c8d4c9) - github.com/containerd/console: [84eeaae → v1.0.0](https://github.com/containerd/console/compare/84eeaae...v1.0.0) - github.com/containerd/containerd: [v1.0.2 → v1.3.3](https://github.com/containerd/containerd/compare/v1.0.2...v1.3.3) - github.com/containerd/typeurl: [2a93cfd → v1.0.0](https://github.com/containerd/typeurl/compare/2a93cfd...v1.0.0) - github.com/containernetworking/cni: [v0.7.1 → v0.8.0](https://github.com/containernetworking/cni/compare/v0.7.1...v0.8.0) - github.com/coredns/corefile-migration: [v1.0.6 → v1.0.10](https://github.com/coredns/corefile-migration/compare/v1.0.6...v1.0.10) - github.com/coreos/pkg: [97fdf19 → 399ea9e](https://github.com/coreos/pkg/compare/97fdf19...399ea9e) - github.com/docker/docker: [be7ac8b → aa6a989](https://github.com/docker/docker/compare/be7ac8b...aa6a989) - github.com/docker/go-connections: [v0.3.0 → v0.4.0](https://github.com/docker/go-connections/compare/v0.3.0...v0.4.0) - github.com/evanphx/json-patch: [v4.2.0+incompatible → e83c0a1](https://github.com/evanphx/json-patch/compare/v4.2.0...e83c0a1) - github.com/fsnotify/fsnotify: [v1.4.7 → v1.4.9](https://github.com/fsnotify/fsnotify/compare/v1.4.7...v1.4.9) - github.com/go-kit/kit: [v0.8.0 → v0.9.0](https://github.com/go-kit/kit/compare/v0.8.0...v0.9.0) - github.com/go-logfmt/logfmt: [v0.3.0 → v0.4.0](https://github.com/go-logfmt/logfmt/compare/v0.3.0...v0.4.0) - github.com/go-logr/logr: [v0.1.0 → v0.2.0](https://github.com/go-logr/logr/compare/v0.1.0...v0.2.0) - github.com/golang/groupcache: [02826c3 → 215e871](https://github.com/golang/groupcache/compare/02826c3...215e871) - github.com/golang/protobuf: [v1.3.2 → v1.4.2](https://github.com/golang/protobuf/compare/v1.3.2...v1.4.2) - github.com/google/cadvisor: [v0.35.0 → v0.37.0](https://github.com/google/cadvisor/compare/v0.35.0...v0.37.0) - github.com/google/go-cmp: [v0.3.0 → v0.4.0](https://github.com/google/go-cmp/compare/v0.3.0...v0.4.0) - github.com/google/pprof: [3ea8567 → d4f498a](https://github.com/google/pprof/compare/3ea8567...d4f498a) - github.com/googleapis/gax-go/v2: [v2.0.4 → v2.0.5](https://github.com/googleapis/gax-go/v2/compare/v2.0.4...v2.0.5) - github.com/googleapis/gnostic: [v0.1.0 → v0.4.1](https://github.com/googleapis/gnostic/compare/v0.1.0...v0.4.1) - github.com/gorilla/mux: [v1.7.0 → v1.7.3](https://github.com/gorilla/mux/compare/v1.7.0...v1.7.3) - github.com/json-iterator/go: [v1.1.8 → v1.1.10](https://github.com/json-iterator/go/compare/v1.1.8...v1.1.10) - github.com/jstemmer/go-junit-report: [af01ea7 → v0.9.1](https://github.com/jstemmer/go-junit-report/compare/af01ea7...v0.9.1) - github.com/konsorten/go-windows-terminal-sequences: [v1.0.1 → v1.0.3](https://github.com/konsorten/go-windows-terminal-sequences/compare/v1.0.1...v1.0.3) - github.com/kr/pretty: [v0.1.0 → v0.2.0](https://github.com/kr/pretty/compare/v0.1.0...v0.2.0) - github.com/mattn/go-isatty: [v0.0.9 → v0.0.4](https://github.com/mattn/go-isatty/compare/v0.0.9...v0.0.4) - github.com/matttproud/golang_protobuf_extensions: [v1.0.1 → c182aff](https://github.com/matttproud/golang_protobuf_extensions/compare/v1.0.1...c182aff) - github.com/mistifyio/go-zfs: [v2.1.1+incompatible → f784269](https://github.com/mistifyio/go-zfs/compare/v2.1.1...f784269) - github.com/mrunalp/fileutils: [7d4729f → abd8a0e](https://github.com/mrunalp/fileutils/compare/7d4729f...abd8a0e) - github.com/opencontainers/runc: [v1.0.0-rc10 → 819fcc6](https://github.com/opencontainers/runc/compare/v1.0.0-rc10...819fcc6) - github.com/opencontainers/runtime-spec: [v1.0.0 → 237cc4f](https://github.com/opencontainers/runtime-spec/compare/v1.0.0...237cc4f) - github.com/opencontainers/selinux: [5215b18 → v1.5.2](https://github.com/opencontainers/selinux/compare/5215b18...v1.5.2) - github.com/pkg/errors: [v0.8.1 → v0.9.1](https://github.com/pkg/errors/compare/v0.8.1...v0.9.1) - github.com/prometheus/client_golang: [v1.0.0 → v1.7.1](https://github.com/prometheus/client_golang/compare/v1.0.0...v1.7.1) - github.com/prometheus/common: [v0.4.1 → v0.10.0](https://github.com/prometheus/common/compare/v0.4.1...v0.10.0) - github.com/prometheus/procfs: [v0.0.2 → v0.1.3](https://github.com/prometheus/procfs/compare/v0.0.2...v0.1.3) - github.com/rubiojr/go-vhd: [0bfd3b3 → 02e2102](https://github.com/rubiojr/go-vhd/compare/0bfd3b3...02e2102) - github.com/sirupsen/logrus: [v1.4.2 → v1.6.0](https://github.com/sirupsen/logrus/compare/v1.4.2...v1.6.0) - github.com/spf13/cobra: [v0.0.5 → v1.0.0](https://github.com/spf13/cobra/compare/v0.0.5...v1.0.0) - github.com/spf13/viper: [v1.3.2 → v1.4.0](https://github.com/spf13/viper/compare/v1.3.2...v1.4.0) - github.com/tmc/grpc-websocket-proxy: [89b8d40 → 0ad062e](https://github.com/tmc/grpc-websocket-proxy/compare/89b8d40...0ad062e) - github.com/urfave/cli: [v1.20.0 → v1.22.2](https://github.com/urfave/cli/compare/v1.20.0...v1.22.2) - github.com/vishvananda/netlink: [v1.0.0 → v1.1.0](https://github.com/vishvananda/netlink/compare/v1.0.0...v1.1.0) - github.com/vishvananda/netns: [be1fbed → 52d707b](https://github.com/vishvananda/netns/compare/be1fbed...52d707b) - go.etcd.io/bbolt: v1.3.3 → v1.3.5 - go.etcd.io/etcd: 3cf2f69 → 18dfb9c - go.opencensus.io: v0.21.0 → v0.22.2 - go.uber.org/atomic: v1.3.2 → v1.4.0 - golang.org/x/crypto: bac4c82 → 75b2880 - golang.org/x/exp: 4b39c73 → da58074 - golang.org/x/image: 0694c2d → cff245a - golang.org/x/lint: 959b441 → fdd1cda - golang.org/x/mobile: d3739f8 → d2bd2a2 - golang.org/x/mod: 4bf6d31 → v0.3.0 - golang.org/x/net: 13f9640 → ab34263 - golang.org/x/oauth2: 0f29369 → 858c2ad - golang.org/x/sys: fde4db3 → ed371f2 - golang.org/x/text: v0.3.2 → v0.3.3 - golang.org/x/time: 9d24e82 → 555d28b - golang.org/x/tools: 65e3620 → c1934b7 - golang.org/x/xerrors: a985d34 → 9bdfabe - google.golang.org/api: 5213b80 → v0.15.1 - google.golang.org/appengine: v1.5.0 → v1.6.5 - google.golang.org/genproto: 24fa4b2 → cb27e3a - google.golang.org/grpc: v1.26.0 → v1.27.0 - gopkg.in/check.v1: 788fd78 → 41f04d3 - honnef.co/go/tools: v0.0.1-2019.2.2 → v0.0.1-2019.2.3 - k8s.io/gengo: 36b2048 → 8167cfd - k8s.io/kube-openapi: bf4fb3b → 656914f - k8s.io/system-validators: v1.0.4 → v1.1.2 - k8s.io/utils: 0a110f9 → d5654de - sigs.k8s.io/apiserver-network-proxy/konnectivity-client: v0.0.7 → v0.0.9 - sigs.k8s.io/structured-merge-diff/v3: v3.0.0 → 43c19bb </del> <ins> - cloud.google.com/go/bigquery: v1.0.1 → v1.4.0 - cloud.google.com/go/datastore: v1.0.0 → v1.1.0 - cloud.google.com/go/pubsub: v1.0.1 → v1.2.0 - cloud.google.com/go/storage: v1.0.0 → v1.6.0 - cloud.google.com/go: v0.51.0 → v0.54.0 - github.com/Azure/go-autorest/autorest/adal: [v0.8.2 → v0.9.5](https://github.com/Azure/go-autorest/autorest/adal/compare/v0.8.2...v0.9.5) - github.com/Azure/go-autorest/autorest/date: [v0.2.0 → v0.3.0](https://github.com/Azure/go-autorest/autorest/date/compare/v0.2.0...v0.3.0) - github.com/Azure/go-autorest/autorest/mocks: [v0.3.0 → v0.4.1](https://github.com/Azure/go-autorest/autorest/mocks/compare/v0.3.0...v0.4.1) - github.com/Azure/go-autorest/autorest: [v0.9.6 → v0.11.1](https://github.com/Azure/go-autorest/autorest/compare/v0.9.6...v0.11.1) - github.com/Azure/go-autorest/logger: [v0.1.0 → v0.2.0](https://github.com/Azure/go-autorest/logger/compare/v0.1.0...v0.2.0) - github.com/Azure/go-autorest/tracing: [v0.5.0 → v0.6.0](https://github.com/Azure/go-autorest/tracing/compare/v0.5.0...v0.6.0) - github.com/Microsoft/go-winio: [fc70bd9 → v0.4.15](https://github.com/Microsoft/go-winio/compare/fc70bd9...v0.4.15) - github.com/aws/aws-sdk-go: [v1.28.2 → v1.35.24](https://github.com/aws/aws-sdk-go/compare/v1.28.2...v1.35.24) - github.com/blang/semver: [v3.5.0+incompatible → v3.5.1+incompatible](https://github.com/blang/semver/compare/v3.5.0...v3.5.1) - github.com/checkpoint-restore/go-criu/v4: [v4.0.2 → v4.1.0](https://github.com/checkpoint-restore/go-criu/v4/compare/v4.0.2...v4.1.0) - github.com/containerd/containerd: [v1.3.3 → v1.4.1](https://github.com/containerd/containerd/compare/v1.3.3...v1.4.1) - github.com/containerd/ttrpc: [v1.0.0 → v1.0.2](https://github.com/containerd/ttrpc/compare/v1.0.0...v1.0.2) - github.com/containerd/typeurl: [v1.0.0 → v1.0.1](https://github.com/containerd/typeurl/compare/v1.0.0...v1.0.1) - github.com/coreos/etcd: [v3.3.10+incompatible → v3.3.13+incompatible](https://github.com/coreos/etcd/compare/v3.3.10...v3.3.13) - github.com/docker/docker: [aa6a989 → bd33bbf](https://github.com/docker/docker/compare/aa6a989...bd33bbf) - github.com/go-gl/glfw/v3.3/glfw: [12ad95a → 6f7a984](https://github.com/go-gl/glfw/v3.3/glfw/compare/12ad95a...6f7a984) - github.com/golang/groupcache: [215e871 → 8c9f03a](https://github.com/golang/groupcache/compare/215e871...8c9f03a) - github.com/golang/mock: [v1.3.1 → v1.4.1](https://github.com/golang/mock/compare/v1.3.1...v1.4.1) - github.com/golang/protobuf: [v1.4.2 → v1.4.3](https://github.com/golang/protobuf/compare/v1.4.2...v1.4.3) - github.com/google/cadvisor: [v0.37.0 → v0.38.5](https://github.com/google/cadvisor/compare/v0.37.0...v0.38.5) - github.com/google/go-cmp: [v0.4.0 → v0.5.2](https://github.com/google/go-cmp/compare/v0.4.0...v0.5.2) - github.com/google/pprof: [d4f498a → 1ebb73c](https://github.com/google/pprof/compare/d4f498a...1ebb73c) - github.com/google/uuid: [v1.1.1 → v1.1.2](https://github.com/google/uuid/compare/v1.1.1...v1.1.2) - github.com/gorilla/mux: [v1.7.3 → v1.8.0](https://github.com/gorilla/mux/compare/v1.7.3...v1.8.0) - github.com/gorilla/websocket: [v1.4.0 → v1.4.2](https://github.com/gorilla/websocket/compare/v1.4.0...v1.4.2) - github.com/jmespath/go-jmespath: [c2b33e8 → v0.4.0](https://github.com/jmespath/go-jmespath/compare/c2b33e8...v0.4.0) - github.com/karrick/godirwalk: [v1.7.5 → v1.16.1](https://github.com/karrick/godirwalk/compare/v1.7.5...v1.16.1) - github.com/opencontainers/go-digest: [v1.0.0-rc1 → v1.0.0](https://github.com/opencontainers/go-digest/compare/v1.0.0-rc1...v1.0.0) - github.com/opencontainers/runc: [819fcc6 → v1.0.0-rc92](https://github.com/opencontainers/runc/compare/819fcc6...v1.0.0-rc92) - github.com/opencontainers/runtime-spec: [237cc4f → 4d89ac9](https://github.com/opencontainers/runtime-spec/compare/237cc4f...4d89ac9) - github.com/opencontainers/selinux: [v1.5.2 → v1.6.0](https://github.com/opencontainers/selinux/compare/v1.5.2...v1.6.0) - github.com/prometheus/procfs: [v0.1.3 → v0.2.0](https://github.com/prometheus/procfs/compare/v0.1.3...v0.2.0) - github.com/quobyte/api: [v0.1.2 → v0.1.8](https://github.com/quobyte/api/compare/v0.1.2...v0.1.8) - github.com/spf13/cobra: [v1.0.0 → v1.1.1](https://github.com/spf13/cobra/compare/v1.0.0...v1.1.1) - github.com/spf13/viper: [v1.4.0 → v1.7.0](https://github.com/spf13/viper/compare/v1.4.0...v1.7.0) - github.com/storageos/go-api: [343b3ef → v2.2.0+incompatible](https://github.com/storageos/go-api/compare/343b3ef...v2.2.0) - github.com/stretchr/testify: [v1.4.0 → v1.6.1](https://github.com/stretchr/testify/compare/v1.4.0...v1.6.1) - github.com/vishvananda/netns: [52d707b → db3c7e5](https://github.com/vishvananda/netns/compare/52d707b...db3c7e5) - go.etcd.io/etcd: 17cef6e → dd1b699 - go.opencensus.io: v0.22.2 → v0.22.3 - golang.org/x/crypto: 75b2880 → 7f63de1 - golang.org/x/exp: da58074 → 6cc2880 - golang.org/x/lint: fdd1cda → 738671d - golang.org/x/net: ab34263 → 69a7880 - golang.org/x/oauth2: 858c2ad → bf48bf1 - golang.org/x/sys: ed371f2 → 5cba982 - golang.org/x/text: v0.3.3 → v0.3.4 - golang.org/x/time: 555d28b → 3af7569 - golang.org/x/xerrors: 9bdfabe → 5ec99f8 - google.golang.org/api: v0.15.1 → v0.20.0 - google.golang.org/genproto: cb27e3a → 8816d57 - google.golang.org/grpc: v1.27.0 → v1.27.1 - google.golang.org/protobuf: v1.24.0 → v1.25.0 - honnef.co/go/tools: v0.0.1-2019.2.3 → v0.0.1-2020.1.3 - k8s.io/gengo: 8167cfd → 83324d8 - k8s.io/klog/v2: v2.2.0 → v2.4.0 - k8s.io/kube-openapi: 6aeccd4 → d219536 - k8s.io/system-validators: v1.1.2 → v1.2.0 - k8s.io/utils: d5654de → 67b214c - sigs.k8s.io/apiserver-network-proxy/konnectivity-client: v0.0.9 → v0.0.14 - sigs.k8s.io/structured-merge-diff/v4: v4.0.1 → v4.0.2 </ins> ### 제거 <del> - github.com/OpenPeeDeeP/depguard: [v1.0.1](https://github.com/OpenPeeDeeP/depguard/tree/v1.0.1) - github.com/Rican7/retry: [v0.1.0](https://github.com/Rican7/retry/tree/v0.1.0) - github.com/StackExchange/wmi: [5d04971](https://github.com/StackExchange/wmi/tree/5d04971) - github.com/anmitsu/go-shlex: [648efa6](https://github.com/anmitsu/go-shlex/tree/648efa6) - github.com/bazelbuild/bazel-gazelle: [70208cb](https://github.com/bazelbuild/bazel-gazelle/tree/70208cb) - github.com/bazelbuild/buildtools: [69366ca](https://github.com/bazelbuild/buildtools/tree/69366ca) - github.com/bazelbuild/rules_go: [6dae44d](https://github.com/bazelbuild/rules_go/tree/6dae44d) - github.com/bradfitz/go-smtpd: [deb6d62](https://github.com/bradfitz/go-smtpd/tree/deb6d62) - github.com/cespare/prettybench: [03b8cfe](https://github.com/cespare/prettybench/tree/03b8cfe) - github.com/checkpoint-restore/go-criu: [17b0214](https://github.com/checkpoint-restore/go-criu/tree/17b0214) - github.com/client9/misspell: [v0.3.4](https://github.com/client9/misspell/tree/v0.3.4) - github.com/coreos/go-etcd: [v2.0.0+incompatible](https://github.com/coreos/go-etcd/tree/v2.0.0) - github.com/cpuguy83/go-md2man: [v1.0.10](https://github.com/cpuguy83/go-md2man/tree/v1.0.10) - github.com/docker/libnetwork: [c8a5fca](https://github.com/docker/libnetwork/tree/c8a5fca) - github.com/gliderlabs/ssh: [v0.1.1](https://github.com/gliderlabs/ssh/tree/v0.1.1) - github.com/go-critic/go-critic: [1df3008](https://github.com/go-critic/go-critic/tree/1df3008) - github.com/go-lintpack/lintpack: [v0.5.2](https://github.com/go-lintpack/lintpack/tree/v0.5.2) - github.com/go-ole/go-ole: [v1.2.1](https://github.com/go-ole/go-ole/tree/v1.2.1) - github.com/go-toolsmith/astcast: [v1.0.0](https://github.com/go-toolsmith/astcast/tree/v1.0.0) - github.com/go-toolsmith/astcopy: [v1.0.0](https://github.com/go-toolsmith/astcopy/tree/v1.0.0) - github.com/go-toolsmith/astequal: [v1.0.0](https://github.com/go-toolsmith/astequal/tree/v1.0.0) - github.com/go-toolsmith/astfmt: [v1.0.0](https://github.com/go-toolsmith/astfmt/tree/v1.0.0) - github.com/go-toolsmith/astinfo: [9809ff7](https://github.com/go-toolsmith/astinfo/tree/9809ff7) - github.com/go-toolsmith/astp: [v1.0.0](https://github.com/go-toolsmith/astp/tree/v1.0.0) - github.com/go-toolsmith/pkgload: [v1.0.0](https://github.com/go-toolsmith/pkgload/tree/v1.0.0) - github.com/go-toolsmith/strparse: [v1.0.0](https://github.com/go-toolsmith/strparse/tree/v1.0.0) - github.com/go-toolsmith/typep: [v1.0.0](https://github.com/go-toolsmith/typep/tree/v1.0.0) - github.com/gobwas/glob: [v0.2.3](https://github.com/gobwas/glob/tree/v0.2.3) - github.com/godbus/dbus: [2ff6f7f](https://github.com/godbus/dbus/tree/2ff6f7f) - github.com/golangci/check: [cfe4005](https://github.com/golangci/check/tree/cfe4005) - github.com/golangci/dupl: [3e9179a](https://github.com/golangci/dupl/tree/3e9179a) - github.com/golangci/errcheck: [ef45e06](https://github.com/golangci/errcheck/tree/ef45e06) - github.com/golangci/go-misc: [927a3d8](https://github.com/golangci/go-misc/tree/927a3d8) - github.com/golangci/go-tools: [e32c541](https://github.com/golangci/go-tools/tree/e32c541) - github.com/golangci/goconst: [041c5f2](https://github.com/golangci/goconst/tree/041c5f2) - github.com/golangci/gocyclo: [2becd97](https://github.com/golangci/gocyclo/tree/2becd97) - github.com/golangci/gofmt: [0b8337e](https://github.com/golangci/gofmt/tree/0b8337e) - github.com/golangci/golangci-lint: [v1.18.0](https://github.com/golangci/golangci-lint/tree/v1.18.0) - github.com/golangci/gosec: [66fb7fc](https://github.com/golangci/gosec/tree/66fb7fc) - github.com/golangci/ineffassign: [42439a7](https://github.com/golangci/ineffassign/tree/42439a7) - github.com/golangci/lint-1: [ee948d0](https://github.com/golangci/lint-1/tree/ee948d0) - github.com/golangci/maligned: [b1d8939](https://github.com/golangci/maligned/tree/b1d8939) - github.com/golangci/misspell: [950f5d1](https://github.com/golangci/misspell/tree/950f5d1) - github.com/golangci/prealloc: [215b22d](https://github.com/golangci/prealloc/tree/215b22d) - github.com/golangci/revgrep: [d9c87f5](https://github.com/golangci/revgrep/tree/d9c87f5) - github.com/golangci/unconvert: [28b1c44](https://github.com/golangci/unconvert/tree/28b1c44) - github.com/google/go-github: [v17.0.0+incompatible](https://github.com/google/go-github/tree/v17.0.0) - github.com/google/go-querystring: [v1.0.0](https://github.com/google/go-querystring/tree/v1.0.0) - github.com/gostaticanalysis/analysisutil: [v0.0.3](https://github.com/gostaticanalysis/analysisutil/tree/v0.0.3) - github.com/jellevandenhooff/dkim: [f50fe3d](https://github.com/jellevandenhooff/dkim/tree/f50fe3d) - github.com/klauspost/compress: [v1.4.1](https://github.com/klauspost/compress/tree/v1.4.1) - github.com/logrusorgru/aurora: [a7b3b31](https://github.com/logrusorgru/aurora/tree/a7b3b31) - github.com/mattn/go-shellwords: [v1.0.5](https://github.com/mattn/go-shellwords/tree/v1.0.5) - github.com/mattn/goveralls: [v0.0.2](https://github.com/mattn/goveralls/tree/v0.0.2) - github.com/mesos/mesos-go: [v0.0.9](https://github.com/mesos/mesos-go/tree/v0.0.9) - github.com/mitchellh/go-ps: [4fdf99a](https://github.com/mitchellh/go-ps/tree/4fdf99a) - github.com/mozilla/tls-observatory: [8791a20](https://github.com/mozilla/tls-observatory/tree/8791a20) - github.com/nbutton23/zxcvbn-go: [eafdab6](https://github.com/nbutton23/zxcvbn-go/tree/eafdab6) - github.com/pquerna/ffjson: [af8b230](https://github.com/pquerna/ffjson/tree/af8b230) - github.com/quasilyte/go-consistent: [c6f3937](https://github.com/quasilyte/go-consistent/tree/c6f3937) - github.com/ryanuber/go-glob: [256dc44](https://github.com/ryanuber/go-glob/tree/256dc44) - github.com/shirou/gopsutil: [c95755e](https://github.com/shirou/gopsutil/tree/c95755e) - github.com/shirou/w32: [bb4de01](https://github.com/shirou/w32/tree/bb4de01) - github.com/shurcooL/go-goon: [37c2f52](https://github.com/shurcooL/go-goon/tree/37c2f52) - github.com/shurcooL/go: [9e1955d](https://github.com/shurcooL/go/tree/9e1955d) - github.com/sourcegraph/go-diff: [v0.5.1](https://github.com/sourcegraph/go-diff/tree/v0.5.1) - github.com/tarm/serial: [98f6abe](https://github.com/tarm/serial/tree/98f6abe) - github.com/timakin/bodyclose: [87058b9](https://github.com/timakin/bodyclose/tree/87058b9) - github.com/ugorji/go/codec: [d75b2dc](https://github.com/ugorji/go/codec/tree/d75b2dc) - github.com/ultraware/funlen: [v0.0.2](https://github.com/ultraware/funlen/tree/v0.0.2) - github.com/valyala/bytebufferpool: [v1.0.0](https://github.com/valyala/bytebufferpool/tree/v1.0.0) - github.com/valyala/fasthttp: [v1.2.0](https://github.com/valyala/fasthttp/tree/v1.2.0) - github.com/valyala/quicktemplate: [v1.1.1](https://github.com/valyala/quicktemplate/tree/v1.1.1) - github.com/valyala/tcplisten: [ceec8f9](https://github.com/valyala/tcplisten/tree/ceec8f9) - go4.org: 417644f - golang.org/x/build: 2835ba2 - golang.org/x/perf: 6e6d33e - gopkg.in/airbrake/gobrake.v2: v2.0.9 - gopkg.in/gemnasium/logrus-airbrake-hook.v2: v2.1.2 - gotest.tools/gotestsum: v0.3.5 - grpc.go4.org: 11d0a25 - k8s.io/klog: v1.0.0 - k8s.io/repo-infra: v0.0.1-alpha.1 - mvdan.cc/interfacer: c200402 - mvdan.cc/lint: adc824a - mvdan.cc/unparam: fbb5962 - sourcegraph.com/sqs/pbtypes: d3ebe8f </del> <ins> - github.com/armon/consul-api: [eb2c6b5](https://github.com/armon/consul-api/tree/eb2c6b5) - github.com/go-ini/ini: [v1.9.0](https://github.com/go-ini/ini/tree/v1.9.0) - github.com/ugorji/go: [v1.1.4](https://github.com/ugorji/go/tree/v1.1.4) - github.com/xlab/handysort: [fb3537e](https://github.com/xlab/handysort/tree/fb3537e) - github.com/xordataexchange/crypt: [b2862e3](https://github.com/xordataexchange/crypt/tree/b2862e3) - vbom.ml/util: db5cfe1 </ins> ## 의존성 ### 추가 <del> - cloud.google.com/go/bigquery: v1.0.1 - cloud.google.com/go/datastore: v1.0.0 - cloud.google.com/go/pubsub: v1.0.1 - cloud.google.com/go/storage: v1.0.0 - dmitri.shuralyov.com/gpu/mtl: 666a987 - github.com/cespare/xxhash/v2: [v2.1.1](https://github.com/cespare/xxhash/v2/tree/v2.1.1) - github.com/checkpoint-restore/go-criu/v4: [v4.0.2](https://github.com/checkpoint-restore/go-criu/v4/tree/v4.0.2) - github.com/chzyer/logex: [v1.1.10](https://github.com/chzyer/logex/tree/v1.1.10) - github.com/chzyer/readline: [2972be2](https://github.com/chzyer/readline/tree/2972be2) - github.com/chzyer/test: [a1ea475](https://github.com/chzyer/test/tree/a1ea475) - github.com/containerd/cgroups: [0dbf7f0](https://github.com/containerd/cgroups/tree/0dbf7f0) - github.com/containerd/continuity: [aaeac12](https://github.com/containerd/continuity/tree/aaeac12) - github.com/containerd/fifo: [a9fb20d](https://github.com/containerd/fifo/tree/a9fb20d) - github.com/containerd/go-runc: [5a6d9f3](https://github.com/containerd/go-runc/tree/5a6d9f3) - github.com/containerd/ttrpc: [v1.0.0](https://github.com/containerd/ttrpc/tree/v1.0.0) - github.com/coreos/bbolt: [v1.3.2](https://github.com/coreos/bbolt/tree/v1.3.2) - github.com/coreos/go-systemd/v22: [v22.1.0](https://github.com/coreos/go-systemd/v22/tree/v22.1.0) - github.com/cpuguy83/go-md2man/v2: [v2.0.0](https://github.com/cpuguy83/go-md2man/v2/tree/v2.0.0) - github.com/docopt/docopt-go: [ee0de3b](https://github.com/docopt/docopt-go/tree/ee0de3b) - github.com/go-gl/glfw/v3.3/glfw: [12ad95a](https://github.com/go-gl/glfw/v3.3/glfw/tree/12ad95a) - github.com/go-ini/ini: [v1.9.0](https://github.com/go-ini/ini/tree/v1.9.0) - github.com/godbus/dbus/v5: [v5.0.3](https://github.com/godbus/dbus/v5/tree/v5.0.3) - github.com/ianlancetaylor/demangle: [5e5cf60](https://github.com/ianlancetaylor/demangle/tree/5e5cf60) - github.com/ishidawataru/sctp: [7c296d4](https://github.com/ishidawataru/sctp/tree/7c296d4) - github.com/moby/ipvs: [v1.0.1](https://github.com/moby/ipvs/tree/v1.0.1) - github.com/moby/sys/mountinfo: [v0.1.3](https://github.com/moby/sys/mountinfo/tree/v0.1.3) - github.com/moby/term: [672ec06](https://github.com/moby/term/tree/672ec06) - github.com/russross/blackfriday/v2: [v2.0.1](https://github.com/russross/blackfriday/v2/tree/v2.0.1) - github.com/shurcooL/sanitized_anchor_name: [v1.0.0](https://github.com/shurcooL/sanitized_anchor_name/tree/v1.0.0) - github.com/ugorji/go: [v1.1.4](https://github.com/ugorji/go/tree/v1.1.4) - github.com/yuin/goldmark: [v1.1.27](https://github.com/yuin/goldmark/tree/v1.1.27) - google.golang.org/protobuf: v1.24.0 - gotest.tools/v3: v3.0.2 - k8s.io/klog/v2: v2.2.0 - sigs.k8s.io/structured-merge-diff/v4: v4.0.1 </del> <ins> - cloud.google.com/go/firestore: v1.1.0 - github.com/Azure/go-autorest: [v14.2.0+incompatible](https://github.com/Azure/go-autorest/tree/v14.2.0) - github.com/armon/go-metrics: [f0300d1](https://github.com/armon/go-metrics/tree/f0300d1) - github.com/armon/go-radix: [7fddfc3](https://github.com/armon/go-radix/tree/7fddfc3) - github.com/bketelsen/crypt: [5cbc8cc](https://github.com/bketelsen/crypt/tree/5cbc8cc) - github.com/form3tech-oss/jwt-go: [v3.2.2+incompatible](https://github.com/form3tech-oss/jwt-go/tree/v3.2.2) - github.com/fvbommel/sortorder: [v1.0.1](https://github.com/fvbommel/sortorder/tree/v1.0.1) - github.com/hashicorp/consul/api: [v1.1.0](https://github.com/hashicorp/consul/api/tree/v1.1.0) - github.com/hashicorp/consul/sdk: [v0.1.1](https://github.com/hashicorp/consul/sdk/tree/v0.1.1) - github.com/hashicorp/errwrap: [v1.0.0](https://github.com/hashicorp/errwrap/tree/v1.0.0) - github.com/hashicorp/go-cleanhttp: [v0.5.1](https://github.com/hashicorp/go-cleanhttp/tree/v0.5.1) - github.com/hashicorp/go-immutable-radix: [v1.0.0](https://github.com/hashicorp/go-immutable-radix/tree/v1.0.0) - github.com/hashicorp/go-msgpack: [v0.5.3](https://github.com/hashicorp/go-msgpack/tree/v0.5.3) - github.com/hashicorp/go-multierror: [v1.0.0](https://github.com/hashicorp/go-multierror/tree/v1.0.0) - github.com/hashicorp/go-rootcerts: [v1.0.0](https://github.com/hashicorp/go-rootcerts/tree/v1.0.0) - github.com/hashicorp/go-sockaddr: [v1.0.0](https://github.com/hashicorp/go-sockaddr/tree/v1.0.0) - github.com/hashicorp/go-uuid: [v1.0.1](https://github.com/hashicorp/go-uuid/tree/v1.0.1) - github.com/hashicorp/go.net: [v0.0.1](https://github.com/hashicorp/go.net/tree/v0.0.1) - github.com/hashicorp/logutils: [v1.0.0](https://github.com/hashicorp/logutils/tree/v1.0.0) - github.com/hashicorp/mdns: [v1.0.0](https://github.com/hashicorp/mdns/tree/v1.0.0) - github.com/hashicorp/memberlist: [v0.1.3](https://github.com/hashicorp/memberlist/tree/v0.1.3) - github.com/hashicorp/serf: [v0.8.2](https://github.com/hashicorp/serf/tree/v0.8.2) - github.com/jmespath/go-jmespath/internal/testify: [v1.5.1](https://github.com/jmespath/go-jmespath/internal/testify/tree/v1.5.1) - github.com/mitchellh/cli: [v1.0.0](https://github.com/mitchellh/cli/tree/v1.0.0) - github.com/mitchellh/go-testing-interface: [v1.0.0](https://github.com/mitchellh/go-testing-interface/tree/v1.0.0) - github.com/mitchellh/gox: [v0.4.0](https://github.com/mitchellh/gox/tree/v0.4.0) - github.com/mitchellh/iochan: [v1.0.0](https://github.com/mitchellh/iochan/tree/v1.0.0) - github.com/pascaldekloe/goe: [57f6aae](https://github.com/pascaldekloe/goe/tree/57f6aae) - github.com/posener/complete: [v1.1.1](https://github.com/posener/complete/tree/v1.1.1) - github.com/ryanuber/columnize: [9b3edd6](https://github.com/ryanuber/columnize/tree/9b3edd6) - github.com/sean-/seed: [e2103e2](https://github.com/sean-/seed/tree/e2103e2) - github.com/subosito/gotenv: [v1.2.0](https://github.com/subosito/gotenv/tree/v1.2.0) - github.com/willf/bitset: [d5bec33](https://github.com/willf/bitset/tree/d5bec33) - gopkg.in/ini.v1: v1.51.0 - gopkg.in/yaml.v3: 9f266ea - rsc.io/quote/v3: v3.1.0 - rsc.io/sampler: v1.3.0 </ins> ### 변경 <del> - cloud.google.com/go: v0.38.0 → v0.51.0 - github.com/Azure/azure-sdk-for-go: [v35.0.0+incompatible → v43.0.0+incompatible](https://github.com/Azure/azure-sdk-for-go/compare/v35.0.0...v43.0.0) - github.com/Azure/go-autorest/autorest/adal: [v0.5.0 → v0.8.2](https://github.com/Azure/go-autorest/autorest/adal/compare/v0.5.0...v0.8.2) - github.com/Azure/go-autorest/autorest/date: [v0.1.0 → v0.2.0](https://github.com/Azure/go-autorest/autorest/date/compare/v0.1.0...v0.2.0) - github.com/Azure/go-autorest/autorest/mocks: [v0.2.0 → v0.3.0](https://github.com/Azure/go-autorest/autorest/mocks/compare/v0.2.0...v0.3.0) - github.com/Azure/go-autorest/autorest: [v0.9.0 → v0.9.6](https://github.com/Azure/go-autorest/autorest/compare/v0.9.0...v0.9.6) - github.com/GoogleCloudPlatform/k8s-cloud-provider: [27a4ced → 7901bc8](https://github.com/GoogleCloudPlatform/k8s-cloud-provider/compare/27a4ced...7901bc8) - github.com/Microsoft/go-winio: [v0.4.14 → fc70bd9](https://github.com/Microsoft/go-winio/compare/v0.4.14...fc70bd9) - github.com/Microsoft/hcsshim: [672e52e → 5eafd15](https://github.com/Microsoft/hcsshim/compare/672e52e...5eafd15) - github.com/alecthomas/template: [a0175ee → fb15b89](https://github.com/alecthomas/template/compare/a0175ee...fb15b89) - github.com/alecthomas/units: [2efee85 → c3de453](https://github.com/alecthomas/units/compare/2efee85...c3de453) - github.com/beorn7/perks: [v1.0.0 → v1.0.1](https://github.com/beorn7/perks/compare/v1.0.0...v1.0.1) - github.com/cilium/ebpf: [95b36a5 → 1c8d4c9](https://github.com/cilium/ebpf/compare/95b36a5...1c8d4c9) - github.com/containerd/console: [84eeaae → v1.0.0](https://github.com/containerd/console/compare/84eeaae...v1.0.0) - github.com/containerd/containerd: [v1.0.2 → v1.3.3](https://github.com/containerd/containerd/compare/v1.0.2...v1.3.3) - github.com/containerd/typeurl: [2a93cfd → v1.0.0](https://github.com/containerd/typeurl/compare/2a93cfd...v1.0.0) - github.com/containernetworking/cni: [v0.7.1 → v0.8.0](https://github.com/containernetworking/cni/compare/v0.7.1...v0.8.0) - github.com/coredns/corefile-migration: [v1.0.6 → v1.0.10](https://github.com/coredns/corefile-migration/compare/v1.0.6...v1.0.10) - github.com/coreos/pkg: [97fdf19 → 399ea9e](https://github.com/coreos/pkg/compare/97fdf19...399ea9e) - github.com/docker/docker: [be7ac8b → aa6a989](https://github.com/docker/docker/compare/be7ac8b...aa6a989) - github.com/docker/go-connections: [v0.3.0 → v0.4.0](https://github.com/docker/go-connections/compare/v0.3.0...v0.4.0) - github.com/evanphx/json-patch: [v4.2.0+incompatible → v4.9.0+incompatible](https://github.com/evanphx/json-patch/compare/v4.2.0...v4.9.0) - github.com/fsnotify/fsnotify: [v1.4.7 → v1.4.9](https://github.com/fsnotify/fsnotify/compare/v1.4.7...v1.4.9) - github.com/go-kit/kit: [v0.8.0 → v0.9.0](https://github.com/go-kit/kit/compare/v0.8.0...v0.9.0) - github.com/go-logfmt/logfmt: [v0.3.0 → v0.4.0](https://github.com/go-logfmt/logfmt/compare/v0.3.0...v0.4.0) - github.com/go-logr/logr: [v0.1.0 → v0.2.0](https://github.com/go-logr/logr/compare/v0.1.0...v0.2.0) - github.com/golang/groupcache: [02826c3 → 215e871](https://github.com/golang/groupcache/compare/02826c3...215e871) - github.com/golang/protobuf: [v1.3.2 → v1.4.2](https://github.com/golang/protobuf/compare/v1.3.2...v1.4.2) - github.com/google/cadvisor: [v0.35.0 → v0.37.0](https://github.com/google/cadvisor/compare/v0.35.0...v0.37.0) - github.com/google/go-cmp: [v0.3.0 → v0.4.0](https://github.com/google/go-cmp/compare/v0.3.0...v0.4.0) - github.com/google/pprof: [3ea8567 → d4f498a](https://github.com/google/pprof/compare/3ea8567...d4f498a) - github.com/googleapis/gax-go/v2: [v2.0.4 → v2.0.5](https://github.com/googleapis/gax-go/v2/compare/v2.0.4...v2.0.5) - github.com/googleapis/gnostic: [v0.1.0 → v0.4.1](https://github.com/googleapis/gnostic/compare/v0.1.0...v0.4.1) - github.com/gorilla/mux: [v1.7.0 → v1.7.3](https://github.com/gorilla/mux/compare/v1.7.0...v1.7.3) - github.com/json-iterator/go: [v1.1.8 → v1.1.10](https://github.com/json-iterator/go/compare/v1.1.8...v1.1.10) - github.com/jstemmer/go-junit-report: [af01ea7 → v0.9.1](https://github.com/jstemmer/go-junit-report/compare/af01ea7...v0.9.1) - github.com/konsorten/go-windows-terminal-sequences: [v1.0.1 → v1.0.3](https://github.com/konsorten/go-windows-terminal-sequences/compare/v1.0.1...v1.0.3) - github.com/kr/pretty: [v0.1.0 → v0.2.0](https://github.com/kr/pretty/compare/v0.1.0...v0.2.0) - github.com/mattn/go-isatty: [v0.0.9 → v0.0.4](https://github.com/mattn/go-isatty/compare/v0.0.9...v0.0.4) - github.com/matttproud/golang_protobuf_extensions: [v1.0.1 → c182aff](https://github.com/matttproud/golang_protobuf_extensions/compare/v1.0.1...c182aff) - github.com/mistifyio/go-zfs: [v2.1.1+incompatible → f784269](https://github.com/mistifyio/go-zfs/compare/v2.1.1...f784269) - github.com/mrunalp/fileutils: [7d4729f → abd8a0e](https://github.com/mrunalp/fileutils/compare/7d4729f...abd8a0e) - github.com/opencontainers/runc: [v1.0.0-rc10 → 819fcc6](https://github.com/opencontainers/runc/compare/v1.0.0-rc10...819fcc6) - github.com/opencontainers/runtime-spec: [v1.0.0 → 237cc4f](https://github.com/opencontainers/runtime-spec/compare/v1.0.0...237cc4f) - github.com/opencontainers/selinux: [5215b18 → v1.5.2](https://github.com/opencontainers/selinux/compare/5215b18...v1.5.2) - github.com/pkg/errors: [v0.8.1 → v0.9.1](https://github.com/pkg/errors/compare/v0.8.1...v0.9.1) - github.com/prometheus/client_golang: [v1.0.0 → v1.7.1](https://github.com/prometheus/client_golang/compare/v1.0.0...v1.7.1) - github.com/prometheus/common: [v0.4.1 → v0.10.0](https://github.com/prometheus/common/compare/v0.4.1...v0.10.0) - github.com/prometheus/procfs: [v0.0.2 → v0.1.3](https://github.com/prometheus/procfs/compare/v0.0.2...v0.1.3) - github.com/rubiojr/go-vhd: [0bfd3b3 → 02e2102](https://github.com/rubiojr/go-vhd/compare/0bfd3b3...02e2102) - github.com/sirupsen/logrus: [v1.4.2 → v1.6.0](https://github.com/sirupsen/logrus/compare/v1.4.2...v1.6.0) - github.com/spf13/cobra: [v0.0.5 → v1.0.0](https://github.com/spf13/cobra/compare/v0.0.5...v1.0.0) - github.com/spf13/viper: [v1.3.2 → v1.4.0](https://github.com/spf13/viper/compare/v1.3.2...v1.4.0) - github.com/tmc/grpc-websocket-proxy: [89b8d40 → 0ad062e](https://github.com/tmc/grpc-websocket-proxy/compare/89b8d40...0ad062e) - github.com/urfave/cli: [v1.20.0 → v1.22.2](https://github.com/urfave/cli/compare/v1.20.0...v1.22.2) - github.com/vishvananda/netlink: [v1.0.0 → v1.1.0](https://github.com/vishvananda/netlink/compare/v1.0.0...v1.1.0) - github.com/vishvananda/netns: [be1fbed → 52d707b](https://github.com/vishvananda/netns/compare/be1fbed...52d707b) - go.etcd.io/bbolt: v1.3.3 → v1.3.5 - go.etcd.io/etcd: 3cf2f69 → 17cef6e - go.opencensus.io: v0.21.0 → v0.22.2 - go.uber.org/atomic: v1.3.2 → v1.4.0 - golang.org/x/crypto: bac4c82 → 75b2880 - golang.org/x/exp: 4b39c73 → da58074 - golang.org/x/image: 0694c2d → cff245a - golang.org/x/lint: 959b441 → fdd1cda - golang.org/x/mobile: d3739f8 → d2bd2a2 - golang.org/x/mod: 4bf6d31 → v0.3.0 - golang.org/x/net: 13f9640 → ab34263 - golang.org/x/oauth2: 0f29369 → 858c2ad - golang.org/x/sys: fde4db3 → ed371f2 - golang.org/x/text: v0.3.2 → v0.3.3 - golang.org/x/time: 9d24e82 → 555d28b - golang.org/x/tools: 65e3620 → c1934b7 - golang.org/x/xerrors: a985d34 → 9bdfabe - google.golang.org/api: 5213b80 → v0.15.1 - google.golang.org/appengine: v1.5.0 → v1.6.5 - google.golang.org/genproto: 24fa4b2 → cb27e3a - google.golang.org/grpc: v1.26.0 → v1.27.0 - gopkg.in/check.v1: 788fd78 → 41f04d3 - honnef.co/go/tools: v0.0.1-2019.2.2 → v0.0.1-2019.2.3 - k8s.io/gengo: 36b2048 → 8167cfd - k8s.io/kube-openapi: bf4fb3b → 6aeccd4 - k8s.io/system-validators: v1.0.4 → v1.1.2 - k8s.io/utils: a9aa75a → d5654de - sigs.k8s.io/apiserver-network-proxy/konnectivity-client: v0.0.7 → v0.0.9 </del> <ins> - cloud.google.com/go/bigquery: v1.0.1 → v1.4.0 - cloud.google.com/go/datastore: v1.0.0 → v1.1.0 - cloud.google.com/go/pubsub: v1.0.1 → v1.2.0 - cloud.google.com/go/storage: v1.0.0 → v1.6.0 - cloud.google.com/go: v0.51.0 → v0.54.0 - github.com/Azure/go-autorest/autorest/adal: [v0.8.2 → v0.9.5](https://github.com/Azure/go-autorest/autorest/adal/compare/v0.8.2...v0.9.5) - github.com/Azure/go-autorest/autorest/date: [v0.2.0 → v0.3.0](https://github.com/Azure/go-autorest/autorest/date/compare/v0.2.0...v0.3.0) - github.com/Azure/go-autorest/autorest/mocks: [v0.3.0 → v0.4.1](https://github.com/Azure/go-autorest/autorest/mocks/compare/v0.3.0...v0.4.1) - github.com/Azure/go-autorest/autorest: [v0.9.6 → v0.11.1](https://github.com/Azure/go-autorest/autorest/compare/v0.9.6...v0.11.1) - github.com/Azure/go-autorest/logger: [v0.1.0 → v0.2.0](https://github.com/Azure/go-autorest/logger/compare/v0.1.0...v0.2.0) - github.com/Azure/go-autorest/tracing: [v0.5.0 → v0.6.0](https://github.com/Azure/go-autorest/tracing/compare/v0.5.0...v0.6.0) - github.com/Microsoft/go-winio: [fc70bd9 → v0.4.15](https://github.com/Microsoft/go-winio/compare/fc70bd9...v0.4.15) - github.com/aws/aws-sdk-go: [v1.28.2 → v1.35.24](https://github.com/aws/aws-sdk-go/compare/v1.28.2...v1.35.24) - github.com/blang/semver: [v3.5.0+incompatible → v3.5.1+incompatible](https://github.com/blang/semver/compare/v3.5.0...v3.5.1) - github.com/checkpoint-restore/go-criu/v4: [v4.0.2 → v4.1.0](https://github.com/checkpoint-restore/go-criu/v4/compare/v4.0.2...v4.1.0) - github.com/containerd/containerd: [v1.3.3 → v1.4.1](https://github.com/containerd/containerd/compare/v1.3.3...v1.4.1) - github.com/containerd/ttrpc: [v1.0.0 → v1.0.2](https://github.com/containerd/ttrpc/compare/v1.0.0...v1.0.2) - github.com/containerd/typeurl: [v1.0.0 → v1.0.1](https://github.com/containerd/typeurl/compare/v1.0.0...v1.0.1) - github.com/coreos/etcd: [v3.3.10+incompatible → v3.3.13+incompatible](https://github.com/coreos/etcd/compare/v3.3.10...v3.3.13) - github.com/docker/docker: [aa6a989 → bd33bbf](https://github.com/docker/docker/compare/aa6a989...bd33bbf) - github.com/go-gl/glfw/v3.3/glfw: [12ad95a → 6f7a984](https://github.com/go-gl/glfw/v3.3/glfw/compare/12ad95a...6f7a984) - github.com/golang/groupcache: [215e871 → 8c9f03a](https://github.com/golang/groupcache/compare/215e871...8c9f03a) - github.com/golang/mock: [v1.3.1 → v1.4.1](https://github.com/golang/mock/compare/v1.3.1...v1.4.1) - github.com/golang/protobuf: [v1.4.2 → v1.4.3](https://github.com/golang/protobuf/compare/v1.4.2...v1.4.3) - github.com/google/cadvisor: [v0.37.0 → v0.38.5](https://github.com/google/cadvisor/compare/v0.37.0...v0.38.5) - github.com/google/go-cmp: [v0.4.0 → v0.5.2](https://github.com/google/go-cmp/compare/v0.4.0...v0.5.2) - github.com/google/pprof: [d4f498a → 1ebb73c](https://github.com/google/pprof/compare/d4f498a...1ebb73c) - github.com/google/uuid: [v1.1.1 → v1.1.2](https://github.com/google/uuid/compare/v1.1.1...v1.1.2) - github.com/gorilla/mux: [v1.7.3 → v1.8.0](https://github.com/gorilla/mux/compare/v1.7.3...v1.8.0) - github.com/gorilla/websocket: [v1.4.0 → v1.4.2](https://github.com/gorilla/websocket/compare/v1.4.0...v1.4.2) - github.com/jmespath/go-jmespath: [c2b33e8 → v0.4.0](https://github.com/jmespath/go-jmespath/compare/c2b33e8...v0.4.0) - github.com/karrick/godirwalk: [v1.7.5 → v1.16.1](https://github.com/karrick/godirwalk/compare/v1.7.5...v1.16.1) - github.com/opencontainers/go-digest: [v1.0.0-rc1 → v1.0.0](https://github.com/opencontainers/go-digest/compare/v1.0.0-rc1...v1.0.0) - github.com/opencontainers/runc: [819fcc6 → v1.0.0-rc92](https://github.com/opencontainers/runc/compare/819fcc6...v1.0.0-rc92) - github.com/opencontainers/runtime-spec: [237cc4f → 4d89ac9](https://github.com/opencontainers/runtime-spec/compare/237cc4f...4d89ac9) - github.com/opencontainers/selinux: [v1.5.2 → v1.6.0](https://github.com/opencontainers/selinux/compare/v1.5.2...v1.6.0) - github.com/prometheus/procfs: [v0.1.3 → v0.2.0](https://github.com/prometheus/procfs/compare/v0.1.3...v0.2.0) - github.com/quobyte/api: [v0.1.2 → v0.1.8](https://github.com/quobyte/api/compare/v0.1.2...v0.1.8) - github.com/spf13/cobra: [v1.0.0 → v1.1.1](https://github.com/spf13/cobra/compare/v1.0.0...v1.1.1) - github.com/spf13/viper: [v1.4.0 → v1.7.0](https://github.com/spf13/viper/compare/v1.4.0...v1.7.0) - github.com/storageos/go-api: [343b3ef → v2.2.0+incompatible](https://github.com/storageos/go-api/compare/343b3ef...v2.2.0) - github.com/stretchr/testify: [v1.4.0 → v1.6.1](https://github.com/stretchr/testify/compare/v1.4.0...v1.6.1) - github.com/vishvananda/netns: [52d707b → db3c7e5](https://github.com/vishvananda/netns/compare/52d707b...db3c7e5) - go.etcd.io/etcd: 17cef6e → dd1b699 - go.opencensus.io: v0.22.2 → v0.22.3 - golang.org/x/crypto: 75b2880 → 7f63de1 - golang.org/x/exp: da58074 → 6cc2880 - golang.org/x/lint: fdd1cda → 738671d - golang.org/x/net: ab34263 → 69a7880 - golang.org/x/oauth2: 858c2ad → bf48bf1 - golang.org/x/sys: ed371f2 → 5cba982 - golang.org/x/text: v0.3.3 → v0.3.4 - golang.org/x/time: 555d28b → 3af7569 - golang.org/x/xerrors: 9bdfabe → 5ec99f8 - google.golang.org/api: v0.15.1 → v0.20.0 - google.golang.org/genproto: cb27e3a → 8816d57 - google.golang.org/grpc: v1.27.0 → v1.27.1 - google.golang.org/protobuf: v1.24.0 → v1.25.0 - honnef.co/go/tools: v0.0.1-2019.2.3 → v0.0.1-2020.1.3 - k8s.io/gengo: 8167cfd → 83324d8 - k8s.io/klog/v2: v2.2.0 → v2.4.0 - k8s.io/kube-openapi: 6aeccd4 → d219536 - k8s.io/system-validators: v1.1.2 → v1.2.0 - k8s.io/utils: d5654de → 67b214c - sigs.k8s.io/apiserver-network-proxy/konnectivity-client: v0.0.9 → v0.0.14 - sigs.k8s.io/structured-merge-diff/v4: v4.0.1 → v4.0.2 </ins> ### 제거 <del> - github.com/OpenPeeDeeP/depguard: [v1.0.1](https://github.com/OpenPeeDeeP/depguard/tree/v1.0.1) - github.com/Rican7/retry: [v0.1.0](https://github.com/Rican7/retry/tree/v0.1.0) - github.com/StackExchange/wmi: [5d04971](https://github.com/StackExchange/wmi/tree/5d04971) - github.com/anmitsu/go-shlex: [648efa6](https://github.com/anmitsu/go-shlex/tree/648efa6) - github.com/bazelbuild/bazel-gazelle: [70208cb](https://github.com/bazelbuild/bazel-gazelle/tree/70208cb) - github.com/bazelbuild/buildtools: [69366ca](https://github.com/bazelbuild/buildtools/tree/69366ca) - github.com/bazelbuild/rules_go: [6dae44d](https://github.com/bazelbuild/rules_go/tree/6dae44d) - github.com/bradfitz/go-smtpd: [deb6d62](https://github.com/bradfitz/go-smtpd/tree/deb6d62) - github.com/cespare/prettybench: [03b8cfe](https://github.com/cespare/prettybench/tree/03b8cfe) - github.com/checkpoint-restore/go-criu: [17b0214](https://github.com/checkpoint-restore/go-criu/tree/17b0214) - github.com/client9/misspell: [v0.3.4](https://github.com/client9/misspell/tree/v0.3.4) - github.com/coreos/go-etcd: [v2.0.0+incompatible](https://github.com/coreos/go-etcd/tree/v2.0.0) - github.com/cpuguy83/go-md2man: [v1.0.10](https://github.com/cpuguy83/go-md2man/tree/v1.0.10) - github.com/docker/libnetwork: [c8a5fca](https://github.com/docker/libnetwork/tree/c8a5fca) - github.com/gliderlabs/ssh: [v0.1.1](https://github.com/gliderlabs/ssh/tree/v0.1.1) - github.com/go-critic/go-critic: [1df3008](https://github.com/go-critic/go-critic/tree/1df3008) - github.com/go-lintpack/lintpack: [v0.5.2](https://github.com/go-lintpack/lintpack/tree/v0.5.2) - github.com/go-ole/go-ole: [v1.2.1](https://github.com/go-ole/go-ole/tree/v1.2.1) - github.com/go-toolsmith/astcast: [v1.0.0](https://github.com/go-toolsmith/astcast/tree/v1.0.0) - github.com/go-toolsmith/astcopy: [v1.0.0](https://github.com/go-toolsmith/astcopy/tree/v1.0.0) - github.com/go-toolsmith/astequal: [v1.0.0](https://github.com/go-toolsmith/astequal/tree/v1.0.0) - github.com/go-toolsmith/astfmt: [v1.0.0](https://github.com/go-toolsmith/astfmt/tree/v1.0.0) - github.com/go-toolsmith/astinfo: [9809ff7](https://github.com/go-toolsmith/astinfo/tree/9809ff7) - github.com/go-toolsmith/astp: [v1.0.0](https://github.com/go-toolsmith/astp/tree/v1.0.0) - github.com/go-toolsmith/pkgload: [v1.0.0](https://github.com/go-toolsmith/pkgload/tree/v1.0.0) - github.com/go-toolsmith/strparse: [v1.0.0](https://github.com/go-toolsmith/strparse/tree/v1.0.0) - github.com/go-toolsmith/typep: [v1.0.0](https://github.com/go-toolsmith/typep/tree/v1.0.0) - github.com/gobwas/glob: [v0.2.3](https://github.com/gobwas/glob/tree/v0.2.3) - github.com/godbus/dbus: [2ff6f7f](https://github.com/godbus/dbus/tree/2ff6f7f) - github.com/golangci/check: [cfe4005](https://github.com/golangci/check/tree/cfe4005) - github.com/golangci/dupl: [3e9179a](https://github.com/golangci/dupl/tree/3e9179a) - github.com/golangci/errcheck: [ef45e06](https://github.com/golangci/errcheck/tree/ef45e06) - github.com/golangci/go-misc: [927a3d8](https://github.com/golangci/go-misc/tree/927a3d8) - github.com/golangci/go-tools: [e32c541](https://github.com/golangci/go-tools/tree/e32c541) - github.com/golangci/goconst: [041c5f2](https://github.com/golangci/goconst/tree/041c5f2) - github.com/golangci/gocyclo: [2becd97](https://github.com/golangci/gocyclo/tree/2becd97) - github.com/golangci/gofmt: [0b8337e](https://github.com/golangci/gofmt/tree/0b8337e) - github.com/golangci/golangci-lint: [v1.18.0](https://github.com/golangci/golangci-lint/tree/v1.18.0) - github.com/golangci/gosec: [66fb7fc](https://github.com/golangci/gosec/tree/66fb7fc) - github.com/golangci/ineffassign: [42439a7](https://github.com/golangci/ineffassign/tree/42439a7) - github.com/golangci/lint-1: [ee948d0](https://github.com/golangci/lint-1/tree/ee948d0) - github.com/golangci/maligned: [b1d8939](https://github.com/golangci/maligned/tree/b1d8939) - github.com/golangci/misspell: [950f5d1](https://github.com/golangci/misspell/tree/950f5d1) - github.com/golangci/prealloc: [215b22d](https://github.com/golangci/prealloc/tree/215b22d) - github.com/golangci/revgrep: [d9c87f5](https://github.com/golangci/revgrep/tree/d9c87f5) - github.com/golangci/unconvert: [28b1c44](https://github.com/golangci/unconvert/tree/28b1c44) - github.com/google/go-github: [v17.0.0+incompatible](https://github.com/google/go-github/tree/v17.0.0) - github.com/google/go-querystring: [v1.0.0](https://github.com/google/go-querystring/tree/v1.0.0) - github.com/gostaticanalysis/analysisutil: [v0.0.3](https://github.com/gostaticanalysis/analysisutil/tree/v0.0.3) - github.com/jellevandenhooff/dkim: [f50fe3d](https://github.com/jellevandenhooff/dkim/tree/f50fe3d) - github.com/klauspost/compress: [v1.4.1](https://github.com/klauspost/compress/tree/v1.4.1) - github.com/logrusorgru/aurora: [a7b3b31](https://github.com/logrusorgru/aurora/tree/a7b3b31) - github.com/mattn/go-shellwords: [v1.0.5](https://github.com/mattn/go-shellwords/tree/v1.0.5) - github.com/mattn/goveralls: [v0.0.2](https://github.com/mattn/goveralls/tree/v0.0.2) - github.com/mesos/mesos-go: [v0.0.9](https://github.com/mesos/mesos-go/tree/v0.0.9) - github.com/mitchellh/go-ps: [4fdf99a](https://github.com/mitchellh/go-ps/tree/4fdf99a) - github.com/mozilla/tls-observatory: [8791a20](https://github.com/mozilla/tls-observatory/tree/8791a20) - github.com/nbutton23/zxcvbn-go: [eafdab6](https://github.com/nbutton23/zxcvbn-go/tree/eafdab6) - github.com/pquerna/ffjson: [af8b230](https://github.com/pquerna/ffjson/tree/af8b230) - github.com/quasilyte/go-consistent: [c6f3937](https://github.com/quasilyte/go-consistent/tree/c6f3937) - github.com/ryanuber/go-glob: [256dc44](https://github.com/ryanuber/go-glob/tree/256dc44) - github.com/shirou/gopsutil: [c95755e](https://github.com/shirou/gopsutil/tree/c95755e) - github.com/shirou/w32: [bb4de01](https://github.com/shirou/w32/tree/bb4de01) - github.com/shurcooL/go-goon: [37c2f52](https://github.com/shurcooL/go-goon/tree/37c2f52) - github.com/shurcooL/go: [9e1955d](https://github.com/shurcooL/go/tree/9e1955d) - github.com/sourcegraph/go-diff: [v0.5.1](https://github.com/sourcegraph/go-diff/tree/v0.5.1) - github.com/tarm/serial: [98f6abe](https://github.com/tarm/serial/tree/98f6abe) - github.com/timakin/bodyclose: [87058b9](https://github.com/timakin/bodyclose/tree/87058b9) - github.com/ugorji/go/codec: [d75b2dc](https://github.com/ugorji/go/codec/tree/d75b2dc) - github.com/ultraware/funlen: [v0.0.2](https://github.com/ultraware/funlen/tree/v0.0.2) - github.com/valyala/bytebufferpool: [v1.0.0](https://github.com/valyala/bytebufferpool/tree/v1.0.0) - github.com/valyala/fasthttp: [v1.2.0](https://github.com/valyala/fasthttp/tree/v1.2.0) - github.com/valyala/quicktemplate: [v1.1.1](https://github.com/valyala/quicktemplate/tree/v1.1.1) - github.com/valyala/tcplisten: [ceec8f9](https://github.com/valyala/tcplisten/tree/ceec8f9) - go4.org: 417644f - golang.org/x/build: 2835ba2 - golang.org/x/perf: 6e6d33e - gopkg.in/airbrake/gobrake.v2: v2.0.9 - gopkg.in/gemnasium/logrus-airbrake-hook.v2: v2.1.2 - gotest.tools/gotestsum: v0.3.5 - grpc.go4.org: 11d0a25 - k8s.io/klog: v1.0.0 - k8s.io/repo-infra: v0.0.1-alpha.1 - mvdan.cc/interfacer: c200402 - mvdan.cc/lint: adc824a - mvdan.cc/unparam: fbb5962 - sigs.k8s.io/structured-merge-diff/v3: v3.0.0 - sourcegraph.com/sqs/pbtypes: d3ebe8f </del> <ins> - github.com/armon/consul-api: [eb2c6b5](https://github.com/armon/consul-api/tree/eb2c6b5) - github.com/go-ini/ini: [v1.9.0](https://github.com/go-ini/ini/tree/v1.9.0) - github.com/ugorji/go: [v1.1.4](https://github.com/ugorji/go/tree/v1.1.4) - github.com/xlab/handysort: [fb3537e](https://github.com/xlab/handysort/tree/fb3537e) - github.com/xordataexchange/crypt: [b2862e3](https://github.com/xordataexchange/crypt/tree/b2862e3) - vbom.ml/util: db5cfe1 </ins> <del> # v1.19.0-rc.4 </del> <ins> # v1.20.0-rc.0 </ins> <del> ## Downloads for v1.19.0-rc.4 </del> <ins> ## Downloads for v1.20.0-rc.0 </ins> ### Source Code filename | sha512 hash -------- | ----------- <del> [kubernetes.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes.tar.gz) | 98bb6e2ac98a3176a9592982fec04b037d189de73cb7175d51596075bfd008c7ec0a2301b9511375626581f864ea74b5731e2ef2b4c70363f1860d11eb827de1 [kubernetes-src.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-src.tar.gz) | d4686f8d07fe6f324f46880a4dc5af9afa314a6b7dca82d0edb50290b769d25d18babcc5257a96a51a046052c7747e324b025a90a36ca5e62f67642bb03c44f6 </del> <ins> [kubernetes.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes.tar.gz) | acfee8658831f9503fccda0904798405434f17be7064a361a9f34c6ed04f1c0f685e79ca40cef5fcf34e3193bacbf467665e8dc277e0562ebdc929170034b5ae [kubernetes-src.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-src.tar.gz) | 9d962f8845e1fa221649cf0c0e178f0f03808486c49ea15ab5ec67861ec5aa948cf18bc0ee9b2067643c8332227973dd592e6a4457456a9d9d80e8ef28d5f7c3 </ins> ### Client binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-client-darwin-amd64.tar.gz) | e9184ceb37491764c1ea2ef0b1eca55f27109bb973c7ff7c78e83c5945840baf28fdead21ef861b0c5cb81f4dc39d0af86ed7b17ed6f087f211084d0033dad11 [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-client-linux-386.tar.gz) | c9f1ec4e8d9c6245f955b2132c0fae6d851a6a49a5b7a2333c01ba9fafa3c4e8a07c6462e525179c25e308520502544ab4dc570e1b9d0090d58b6d18bcfcba47 [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-client-linux-amd64.tar.gz) | d23858b03c3554ad12517ce5f7855ceccaa9425c2d19fbc9cf902c0e796a8182f8b0e8eeeeefff0f46e960dfee96b2a2033a04a3194ac34dfd2a32003775d060 [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-client-linux-arm.tar.gz) | a745b3a06fe992713e4d7f921e2f36c5b39222d7b1a3e13299d15925743dd99965c2bdf05b4deda30a6f6232a40588e154fdd83f40d9d260d7ac8f70b18cad48 [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-client-linux-arm64.tar.gz) | 719b1f30e4bbb05d638ee78cf0145003a1e783bbd0c2f0952fcb30702dd27dfd44c3bc85baaf9a776e490ed53c638327ed1c0e5a882dc93c24d7cac20e4f1dd0 [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-client-linux-ppc64le.tar.gz) | fba0794e9dc0f231da5a4e85e37c2d8260e5205574e0421f5122a7d60a05ca6546912519a28e8d6c241904617234e1b0b5c94f890853ad5ae4e329ef8085a092 [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-client-linux-s390x.tar.gz) | edce96e37e37fd2b60e34fe56240461094e5784985790453becdfe09011305fcbd8a50ee5bf6d82a70d208d660796d0ddf160bed0292271b6617049db800962f [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-client-windows-386.tar.gz) | 06c849b35d886bebedfd8d906ac37ccda10e05b06542fefe6440268c5e937f235915e53daafe35076b68e0af0d4ddeab4240da55b09ee52fa26928945f1a2ecd [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-client-windows-amd64.tar.gz) | a13e6ec70f76d6056d5668b678ba6f223e35756cded6c84dfb58e28b3741fecfa7cb5e6ae2239392d770028d1b55ca8eb520c0b24e13fc3bd38720134b472d53 </del> <ins> [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-client-darwin-amd64.tar.gz) | 062b57f1a450fe01d6184f104d81d376bdf5720010412821e315fd9b1b622a400ac91f996540daa66cee172006f3efade4eccc19265494f1a1d7cc9450f0b50a [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-client-linux-386.tar.gz) | 86e96d2c2046c5e62e02bef30a6643f25e01f1b3eba256cab7dd61252908540c26cb058490e9cecc5a9bad97d2b577f5968884e9f1a90237e302419f39e068bc [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-client-linux-amd64.tar.gz) | 619d3afb9ce902368390e71633396010e88e87c5fd848e3adc71571d1d4a25be002588415e5f83afee82460f8a7c9e0bd968335277cb8f8cb51e58d4bb43e64e [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-client-linux-arm.tar.gz) | 60965150a60ab3d05a248339786e0c7da4b89a04539c3719737b13d71302bac1dd9bcaa427d8a1f84a7b42d0c67801dce2de0005e9e47d21122868b32ac3d40f [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-client-linux-arm64.tar.gz) | 688e064f4ef6a17189dbb5af468c279b9de35e215c40500fb97b1d46692d222747023f9e07a7f7ba006400f9532a8912e69d7c5143f956b1dadca144c67ee711 [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-client-linux-ppc64le.tar.gz) | 47b8abc02b42b3b1de67da184921b5801d7e3cb09befac840c85913193fc5ac4e5e3ecfcb57da6b686ff21af9a3bd42ae6949d4744dbe6ad976794340e328b83 [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-client-linux-s390x.tar.gz) | 971b41d3169f30e6c412e0254c180636abb7ccc8dcee6641b0e9877b69752fc61aa30b76c19c108969df654fe385da3cb3a44dd59d3c28dc45561392d7e08874 [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-client-windows-386.tar.gz) | 2d34e8387e31531d9aca5655f2f0d18e75b01825dc1c39b7beb73a7b7b610e2ba429e5ca97d5c41a71b67e75e7096c86ab63fda9baab4c0878c1ccb3a1aefac8 [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-client-windows-amd64.tar.gz) | f909640f4140693bb871936f10a40e79b43502105d0adb318b35bb7a64a770ad9d05a3a732368ccd3d15d496d75454789165bd1f5c2571da9a00569b3e6c007c </ins> ### Server binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-server-linux-amd64.tar.gz) | ff7fbf211c29b94c19466337e6c142e733c8c0bac815a97906168e57d21ad1b2965e4b0033b525de8fed9a91ab943e3eb6d330f8095660e32be2791f8161a6a2 [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-server-linux-arm.tar.gz) | 218a35466ebcc0bc0e8eff9bbb2e58f0ac3bec6a75f45a7c1487aa4fc3e2bddb90b74e91a2b81bbbbb1eb1de2df310adab4c07c2a2c38a9973580b4f85734a1f [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-server-linux-arm64.tar.gz) | 8a81d727e63875d18336fda8bb6f570084553fc346b7e7df2fc3e1c04a8ef766f61d96d445537e4660ce2f46b170a04218a4d8a270b3ad373caa3f815c0fec93 [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-server-linux-ppc64le.tar.gz) | 9b5afa44ac2e1232cd0c54b3602a2027bc8a08b30809b3ef973f75793b35a596491e6056d7995e493a1e4f48d83389240ac2e609b9f76d2715b8e115e6648716 [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-server-linux-s390x.tar.gz) | f3034b2e88b5c1d362d84f78dfd1761d0fc21ada1cd6b1a6132a709c663a1206651df96c948534b3661f6b70b651e33021aced3a7574a0e5fc88ace73fff2a6f </del> <ins> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-server-linux-amd64.tar.gz) | 0ea4458ae34108c633b4d48f1f128c6274dbc82b613492e78b3e0a2f656ac0df0bb9a75124e15d67c8e81850adcecf19f4ab0234c17247ee7ddf84f2df3e5eaa [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-server-linux-arm.tar.gz) | aef6a4d457faa29936603370f29a8523bb274211c3cb5101bd31aaf469c91ba6bd149ea99a4ccdd83352cf37e4d6508c5ee475ec10292bccd2f77ceea31e1c28 [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-server-linux-arm64.tar.gz) | 4829f473e9d60f9929ad17c70fdc2b6b6509ed75418be0b23a75b28580949736cb5b0bd6382070f93aa0a2a8863f0b1596daf965186ca749996c29d03ef7d8b8 [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-server-linux-ppc64le.tar.gz) | 9ab0790d382a3e28df1c013762c09da0085449cfd09d176d80be932806c24a715ea829be0075c3e221a2ad9cf06e726b4c39ab41987c1fb0fee2563e48206763 [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-server-linux-s390x.tar.gz) | 98670b587e299856dd9821b7517a35f9a65835b915b153de08b66c54d82160438b66f774bf5306c07bc956d70ff709860bc23162225da5e89f995d3fdc1f0122 </ins> ### Node binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-node-linux-amd64.tar.gz) | 2061a8f5bc2060b071564c92b693950eda7768a9ceb874982f0e91aa78284fb477becb55ecf099acae73c447271240caecefc19b3b29024e9b818e0639c2fc70 [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-node-linux-arm.tar.gz) | c06b817b191ff9a4b05bf70fc14edcf01d4ded204e489966b1761dd68d45d054028870301e45ebba648c0be097c7c42120867c8b28fdd625c8eb5a5bc3ace71d [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-node-linux-arm64.tar.gz) | 21efb3bf23628546de97210074f48e928fec211b81215eff8b10c3f5f7e79bb5911c1393a66a8363a0183fe299bf98b316c0c2d77a13c8c5b798255c056bd806 [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-node-linux-ppc64le.tar.gz) | ce31dd65b9cbfaabdc3c93e8afee0ea5606c64e6bf4452078bee73b1d328d23ebdbc871a00edd16fa4e676406a707cf9113fdaec76489681c379c35c3fd6aeb0 [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-node-linux-s390x.tar.gz) | 523a8e1d6e0eff70810e846c171b7f74a4aaecb25237addf541a9f8adb3797402b6e57abf9030f62d5bb333d5f5e8960199a44fe48696a4da98f7ed7d993cde1 [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.4/kubernetes-node-windows-amd64.tar.gz) | a7fbcd11ea8b6427e7846e39b2fdeae41d484320faa8f3e9b6a777d87ba62e7399ad0ec6a33d9a4675001898881e444f336eebd5c97b3903dee803834a646f3d </del> <ins> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-node-linux-amd64.tar.gz) | 699e9c8d1837198312eade8eb6fec390f6a2fea9e08207d2f58e8bb6e3e799028aca69e4670aac0a4ba7cf0af683aee2c158bf78cc520c80edc876c8d94d521a [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-node-linux-arm.tar.gz) | f3b5eab0669490e3cd7e802693daf3555d08323dfff6e73a881fce00fed4690e8bdaf1610278d9de74036ca37631016075e5695a02158b7d3e7582b20ef7fa35 [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-node-linux-arm64.tar.gz) | e5012f77363561a609aaf791baaa17d09009819c4085a57132e5feb5366275a54640094e6ed1cba527f42b586c6d62999c2a5435edf5665ff0e114db4423c2ae [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-node-linux-ppc64le.tar.gz) | 2a6d6501620b1a9838dff05c66a40260cc22154a28027813346eb16e18c386bc3865298a46a0f08da71cd55149c5e7d07c4c4c431b4fd231486dd9d716548adb [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-node-linux-s390x.tar.gz) | 5eca02777519e31428a1e5842fe540b813fb8c929c341bbc71dcfd60d98deb89060f8f37352e8977020e21e053379eead6478eb2d54ced66fb9d38d5f3142bf0 [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0-rc.0/kubernetes-node-windows-amd64.tar.gz) | 8ace02e7623dff894e863a2e0fa7dfb916368431d1723170713fe82e334c0ae0481b370855b71e2561de0fb64fed124281be604761ec08607230b66fb9ed1c03 </ins> <del> ## Changelog since v1.19.0-rc.3 </del> <ins> ## Changelog since v1.20.0-beta.2 </ins> ## Changes by Kind <del> ### Deprecation </del> <ins> ### Feature </ins> <del> - Kube-apiserver: the componentstatus API is deprecated. This API provided status of etcd, kube-scheduler, and kube-controller-manager components, but only worked when those components were local to the API server, and when kube-scheduler and kube-controller-manager exposed unsecured health endpoints. Instead of this API, etcd health is included in the kube-apiserver health check and kube-scheduler/kube-controller-manager health checks can be made directly against those components' health endpoints. ([#93570](https://github.com/kubernetes/kubernetes/pull/93570), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Apps and Cluster Lifecycle] </del> <ins> - Kubernetes is now built using go1.15.5 - build: Update to k/repo-infra@v0.1.2 (supports go1.15.5) ([#95776](https://github.com/kubernetes/kubernetes/pull/95776), [@justaugustus](https://github.com/justaugustus)) [SIG Cloud Provider, Instrumentation, Release and Testing] </ins> <del> ### Bug or Regression </del> <ins> ### Failing Test </ins> <del> - A panic in the apiserver caused by the `informer-sync` health checker is now fixed. ([#93600](https://github.com/kubernetes/kubernetes/pull/93600), [@ialidzhikov](https://github.com/ialidzhikov)) [SIG API Machinery] - EndpointSliceMirroring controller now copies labels from Endpoints to EndpointSlices. ([#93442](https://github.com/kubernetes/kubernetes/pull/93442), [@robscott](https://github.com/robscott)) [SIG Apps and Network] - Kube-apiserver: jsonpath expressions with consecutive recursive descent operators are no longer evaluated for custom resource printer columns ([#93408](https://github.com/kubernetes/kubernetes/pull/93408), [@joelsmith](https://github.com/joelsmith)) [SIG API Machinery] </del> <ins> - Resolves an issue running Ingress conformance tests on clusters which use finalizers on Ingress objects to manage releasing load balancer resources ([#96742](https://github.com/kubernetes/kubernetes/pull/96742), [@spencerhance](https://github.com/spencerhance)) [SIG Network and Testing] - The Conformance test \"validates that there is no conflict between pods with same hostPort but different hostIP and protocol\" now validates the connectivity to each hostPort, in addition to the functionality. ([#96627](https://github.com/kubernetes/kubernetes/pull/96627), [@aojea](https://github.com/aojea)) [SIG Scheduling and Testing] </ins> <del> ### Other (Cleanup or Flake) </del> <ins> ### Bug or Regression </ins> <del> - Build: Update to debian-base@v2.1.0 and debian-iptables@v12.1.1 ([#93667](https://github.com/kubernetes/kubernetes/pull/93667), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery, Release and Testing] </del> <ins> - Bump node-problem-detector version to v0.8.5 to fix OOM detection in with Linux kernels 5.1+ ([#96716](https://github.com/kubernetes/kubernetes/pull/96716), [@tosi3k](https://github.com/tosi3k)) [SIG Cloud Provider, Scalability and Testing] - Changes to timeout parameter handling in 1.20.0-beta.2 have been reverted to avoid breaking backwards compatibility with existing clients. ([#96727](https://github.com/kubernetes/kubernetes/pull/96727), [@liggitt](https://github.com/liggitt)) [SIG API Machinery and Testing] - Duplicate owner reference entries in create/update/patch requests now get deduplicated by the API server. The client sending the request now receives a warning header in the API response. Clients should stop sending requests with duplicate owner references. The API server may reject such requests as early as 1.24. ([#96185](https://github.com/kubernetes/kubernetes/pull/96185), [@roycaihw](https://github.com/roycaihw)) [SIG API Machinery and Testing] - Fix: resize Azure disk issue when it's in attached state ([#96705](https://github.com/kubernetes/kubernetes/pull/96705), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fixed a bug where aggregator_unavailable_apiservice metrics were reported for deleted apiservices. ([#96421](https://github.com/kubernetes/kubernetes/pull/96421), [@dgrisonnet](https://github.com/dgrisonnet)) [SIG API Machinery and Instrumentation] - Fixes code generation for non-namespaced create subresources fake client test. ([#96586](https://github.com/kubernetes/kubernetes/pull/96586), [@Doude](https://github.com/Doude)) [SIG API Machinery] - HTTP/2 connection health check is enabled by default in all Kubernetes clients. The feature should work out-of-the-box. If needed, users can tune the feature via the HTTP2_READ_IDLE_TIMEOUT_SECONDS and HTTP2_PING_TIMEOUT_SECONDS environment variables. The feature is disabled if HTTP2_READ_IDLE_TIMEOUT_SECONDS is set to 0. ([#95981](https://github.com/kubernetes/kubernetes/pull/95981), [@caesarxuchao](https://github.com/caesarxuchao)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation and Node] - Kubeadm: fix coredns migration should be triggered when there are newdefault configs during kubeadm upgrade ([#96907](https://github.com/kubernetes/kubernetes/pull/96907), [@pacoxu](https://github.com/pacoxu)) [SIG Cluster Lifecycle] - Reduce volume name length for vsphere volumes ([#96533](https://github.com/kubernetes/kubernetes/pull/96533), [@gnufied](https://github.com/gnufied)) [SIG Storage] - Resolves a regression in 1.19+ with workloads targeting deprecated beta os/arch labels getting stuck in NodeAffinity status on node startup. ([#96810](https://github.com/kubernetes/kubernetes/pull/96810), [@liggitt](https://github.com/liggitt)) [SIG Node] </ins> ## Dependencies"}
{"_id":"q-en-website-6af046399189379bfea41a820b891fbcf65fd98a1e8f82cb228031a0b23bea95","text":"<ins> --- title: \"Secretの管理\" weight: 28 description: Secretを使用した機密設定データの管理 --- </ins>"}
{"_id":"q-en-website-6b5dabf432fc5bd11ee63f220ae4e8d3f219cb3e1ea30539d5f571a61442c9d1","text":"$($(CertUtil -hashfile .kubectl.exe SHA256)[1] -replace \" \", \"\") -eq $(type .kubectl.exe.sha256) ``` <del> 1. Append or prepend the kubectl binary folder to your `PATH` environment variable. </del> <ins> 1. Append or prepend the `kubectl` binary folder to your `PATH` environment variable. </ins> 1. Test to ensure the version of `kubectl` is the same as downloaded:"}
{"_id":"q-en-website-6bfdbadda6d6e0cca734f2c2a45f203ba4ef052e1eed7d4b0e53fabaa7d90986","text":"以下の理由によりPodは再起動し、Initコンテナの再実行も引き起こす可能性があります。 <del> * ユーザーが、そのPodのInitコンテナのイメージを変更するようにPodの仕様を更新する場合。アプリケーションコンテナのイメージの変更はそのアプリケーションコンテナの再起動のみ行われます。 </del> * そのPodのインフラストラクチャーコンテナが再起動された場合。これはあまり起きるものでなく、Nodeに対するルート権限を持ったユーザーにより行われることがあります。 <del> * `restartPolicy`が`Always`と設定されているPod内の全てのコンテナが停止され、再起動が行われた場合。およびガーベージコレクションによりInitコンテナの完了記録が失われた場合。 </del> <ins> * `restartPolicy`が`Always`と設定されているPod内の全てのコンテナが停止され、強制的に再起動が行われたことで、ガベージコレクションによりInitコンテナの完了記録が失われた場合。 Kubernetes v1.20以降では、initコンテナのイメージが変更されたり、ガベージコレクションによってinitコンテナの完了記録が失われたりした場合でも、Podは再起動されません。以前のバージョンを使用している場合は、対応バージョンのドキュメントを参照してください。 </ins> <del> ## {{% heading \"whatsnext\" %}} </del> <ins> ## {{% heading \"whatsnext\" %}} {#what-s-next} </ins> * [Initコンテナを含むPodの作成](/docs/tasks/configure-pod-container/configure-pod-initialization/#creating-a-pod-that-has-an-init-container)方法について学ぶ。 * [Initコンテナのデバッグ](/ja/docs/tasks/debug-application-cluster/debug-init-containers/)を行う方法について学ぶ。"}
{"_id":"q-en-website-6ddc317210ea31256d7113de288ed352f10b45ef6b800fb2c7160cd7af6acde8","text":"{{% tab name=\"Ubuntu\" %}} <!-- <del> To install on the following operating systems, set the environment variable `OS` to the appropriate field in the following table: </del> <ins> To install on the following operating systems, set the environment variable `OS` to the appropriate field in the following table: </ins> | Operating system | `$OS`             | | ---------------- | ----------------- |"}
{"_id":"q-en-website-6f6d68feb133088fe817613de90c0b584700f237bcd8a20912ca0cba918e7590","text":"<del> --- title: Bin Packing Sumber Daya untuk Sumber Daya Tambahan content_type: concept weight: 10 --- <!-- overview --> {{< feature-state for_k8s_version=\"1.16\" state=\"alpha\" >}} _Kube-scheduler_ dapat dikonfigurasikan untuk mengaktifkan pembungkusan rapat (_bin packing_) sumber daya bersama dengan sumber daya tambahan melalui fungsi prioritas `RequestedToCapacityRatioResourceAllocation`. Fungsi-fungsi prioritas dapat digunakan untuk menyempurnakan _kube-scheduler_ sesuai dengan kebutuhan. <!-- body --> ## Mengaktifkan _Bin Packing_ menggunakan RequestedToCapacityRatioResourceAllocation Sebelum Kubernetes 1.15, _kube-scheduler_ digunakan untuk memungkinkan mencetak skor berdasarkan rasio permintaan terhadap kapasitas sumber daya utama seperti CPU dan Memori. Kubernetes 1.16 menambahkan parameter baru ke fungsi prioritas yang memungkinkan pengguna untuk menentukan sumber daya beserta dengan bobot untuk setiap sumber daya untuk memberi nilai dari Node berdasarkan rasio permintaan terhadap kapasitas. Hal ini memungkinkan pengguna untuk _bin pack_ sumber daya tambahan dengan menggunakan parameter yang sesuai untuk meningkatkan pemanfaatan sumber daya yang langka dalam klaster yang besar. Perilaku `RequestedToCapacityRatioResourceAllocation` dari fungsi prioritas dapat dikontrol melalui pilihan konfigurasi yang disebut ` RequestToCapacityRatioArguments`. Argumen ini terdiri dari dua parameter yaitu `shape` dan `resources`. Shape memungkinkan pengguna untuk menyempurnakan fungsi menjadi yang paling tidak diminta atau paling banyak diminta berdasarkan nilai `utilization` dan `score`. Sumber daya terdiri dari `name` yang menentukan sumber daya mana yang dipertimbangkan selama penilaian dan `weight` yang menentukan bobot masing-masing sumber daya. Di bawah ini adalah contoh konfigurasi yang menetapkan `requestedToCapacityRatioArguments` pada perilaku _bin packing_ untuk sumber daya tambahan` intel.com/foo` dan `intel.com/bar` ```json { \"kind\" : \"Policy\", \"apiVersion\" : \"v1\", ... \"priorities\" : [ ... { \"name\": \"RequestedToCapacityRatioPriority\", \"weight\": 2, \"argument\": { \"requestedToCapacityRatioArguments\": { \"shape\": [ {\"utilization\": 0, \"score\": 0}, {\"utilization\": 100, \"score\": 10} ], \"resources\": [ {\"name\": \"intel.com/foo\", \"weight\": 3}, {\"name\": \"intel.com/bar\", \"weight\": 5} ] } } } ], } ``` **Fitur ini dinonaktifkan secara _default_** ### Tuning RequestedToCapacityRatioResourceAllocation Priority Function `shape` digunakan untuk menentukan perilaku dari fungsi `RequestedToCapacityRatioPriority`. ```yaml {\"utilization\": 0, \"score\": 0}, {\"utilization\": 100, \"score\": 10} ``` Argumen di atas memberikan Node nilai 0 jika utilisasi 0% dan 10 untuk utilisasi 100%, yang kemudian mengaktfikan perilaku _bin packing_. Untuk mengaktifkan dari paling yang tidak diminta, nilainya harus dibalik sebagai berikut. ```yaml {\"utilization\": 0, \"score\": 100}, {\"utilization\": 100, \"score\": 0} ``` `resources` adalah parameter opsional yang secara _default_ diatur ke: ``` yaml \"resources\": [ {\"name\": \"CPU\", \"weight\": 1}, {\"name\": \"Memory\", \"weight\": 1} ] ``` Ini dapat digunakan untuk menambahkan sumber daya tambahan sebagai berikut: ```yaml \"resources\": [ {\"name\": \"intel.com/foo\", \"weight\": 5}, {\"name\": \"CPU\", \"weight\": 3}, {\"name\": \"Memory\", \"weight\": 1} ] ``` Parameter `weight` adalah opsional dan diatur ke 1 jika tidak ditentukan. Selain itu, `weight` tidak dapat diatur ke nilai negatif. ### Bagaimana Fungsi Prioritas RequestedToCapacityRatioResourceAllocation Menilai Node Bagian ini ditujukan bagi kamu yang ingin memahami secara detail internal dari fitur ini. Di bawah ini adalah contoh bagaimana nilai dari Node dihitung untuk satu kumpulan nilai yang diberikan. ``` Sumber daya yang diminta intel.com/foo : 2 Memory: 256MB CPU: 2 Bobot dari sumber daya intel.com/foo : 5 Memory: 1 CPU: 3 FunctionShapePoint {{0, 0}, {100, 10}} Spesifikasi dari Node 1 Tersedia: intel.com/foo : 4 Memory : 1 GB CPU: 8 Digunakan: intel.com/foo: 1 Memory: 256MB CPU: 1 Nilai Node: intel.com/foo  = resourceScoringFunction((2+1),4) =  (100 - ((4-3)*100/4) =  (100 - 25) =  75 =  rawScoringFunction(75) = 7 Memory         = resourceScoringFunction((256+256),1024) = (100 -((1024-512)*100/1024)) = 50 = rawScoringFunction(50) = 5 CPU            = resourceScoringFunction((2+1),8) = (100 -((8-3)*100/8)) = 37.5 = rawScoringFunction(37.5) = 3 NodeScore   =  (7 * 5) + (5 * 1) + (3 * 3) / (5 + 1 + 3) =  5 Spesifikasi dari Node 2 Tersedia: intel.com/foo: 8 Memory: 1GB CPU: 8 Digunakan: intel.com/foo: 2 Memory: 512MB CPU: 6 Nilai Node: intel.com/foo  = resourceScoringFunction((2+2),8) =  (100 - ((8-4)*100/8) =  (100 - 25) =  50 =  rawScoringFunction(50) = 5 Memory         = resourceScoringFunction((256+512),1024) = (100 -((1024-768)*100/1024)) = 75 = rawScoringFunction(75) = 7 CPU            = resourceScoringFunction((2+6),8) = (100 -((8-8)*100/8)) = 100 = rawScoringFunction(100) = 10 NodeScore   =  (5 * 5) + (7 * 1) + (10 * 3) / (5 + 1 + 3) =  7 ``` </del>"}
{"_id":"q-en-website-6f74d90e3c687e8e948cf213bedacf23ed3452801ff7029be4383bc33d517fba","text":"* [`gcePersistentDisk`](#gcepersistentdisk) * [`vsphereVolume`](#vspherevolume) <del> ### flexVolume (deprecated) </del> <ins> ### flexVolume (deprecated)   {#flexvolume} </ins> {{< feature-state for_k8s_version=\"v1.23\" state=\"deprecated\" >}}"}
{"_id":"q-en-website-6f830cc01263b09c0579c107bf717216de74a0c4a37addd767004900bc0bfed1","text":"You can use _topology spread constraints_ to control how {{< glossary_tooltip text=\"Pods\" term_id=\"Pod\" >}} are spread across your cluster among failure-domains such as regions, zones, nodes, and other user-defined topology domains. This can help to achieve high availability as well as efficient resource utilization. {{< note >}} <del> In versions of Kubernetes before v1.19, you must enable the `EvenPodsSpread` </del> <ins> In versions of Kubernetes before v1.18, you must enable the `EvenPodsSpread` </ins> [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) on the [API server](/docs/concepts/overview/components/#kube-apiserver) and the [scheduler](/docs/reference/generated/kube-scheduler/) in order to use Pod"}
{"_id":"q-en-website-718e7400e19322e3a5f5a20953a2b00589cfadc247f3e2aa910ceca70dd5bfe2","text":"However, using the defined and public Secret type (`kubernetes.io/basic-auth`) helps other people to understand the purpose of your Secret, and sets a convention for what key names to expect. <del> The Kubernetes API verifies that the required keys are set for a Secret of this type. </del> ### SSH authentication Secrets"}
{"_id":"q-en-website-72a21f27702c2c4ece27315851bd379ecc8eab6f93002cdb003391ec0d254954","text":"--- assignees: - bboreham <del> title: Weave Net Addon </del> <ins> title: Using Weave Net for NetworkPolicy </ins> --- The [Weave Net Addon](https://www.weave.works/docs/net/latest/kube-addon/) for Kubernetes comes with a Network Policy Controller."}
{"_id":"q-en-website-72ba62e6810320d4d4e6635449b7587a656a97f5d6a0b1c96bd0035bd4d1b9e6","text":"<ins> --- reviewers: - bowei - zihongz title:  Debugging DNS Resolution content_type: task min-kubernetes-server-version: v1.6 --- <!-- overview --> This page provides hints on diagnosing DNS problems. ## {{% heading \"prerequisites\" %}} {{< include \"task-tutorial-prereqs.md\" >}} Your cluster must be configured to use the CoreDNS {{< glossary_tooltip text=\"addon\" term_id=\"addons\" >}} or its precursor, kube-dns. {{% version-check %}} <!-- steps --> ### Create a simple Pod to use as a test environment {{< codenew file=\"admin/dns/dnsutils.yaml\" >}} Use that manifest to create a Pod: ```shell kubectl apply -f https://k8s.io/examples/admin/dns/dnsutils.yaml ``` ``` pod/dnsutils created ``` …and verify its status: ```shell kubectl get pods dnsutils ``` ``` NAME      READY     STATUS    RESTARTS   AGE dnsutils   1/1       Running   0          <some-time> ``` Once that Pod is running, you can exec `nslookup` in that environment. If you see something like the following, DNS is working correctly. ```shell kubectl exec -i -t dnsutils -- nslookup kubernetes.default ``` ``` Server:    10.0.0.10 Address 1: 10.0.0.10 Name:      kubernetes.default Address 1: 10.0.0.1 ``` If the `nslookup` command fails, check the following: ### Check the local DNS configuration first Take a look inside the resolv.conf file. (See [Inheriting DNS from the node](/docs/tasks/administer-cluster/dns-custom-nameservers/#inheriting-dns-from-the-node) and [Known issues](#known-issues) below for more information) ```shell kubectl exec -ti dnsutils -- cat /etc/resolv.conf ``` Verify that the search path and name server are set up like the following (note that search path may vary for different cloud providers): ``` search default.svc.cluster.local svc.cluster.local cluster.local google.internal c.gce_project_id.internal nameserver 10.0.0.10 options ndots:5 ``` Errors such as the following indicate a problem with the CoreDNS (or kube-dns) add-on or with associated Services: ```shell kubectl exec -i -t dnsutils -- nslookup kubernetes.default ``` ``` Server:    10.0.0.10 Address 1: 10.0.0.10 nslookup: can't resolve 'kubernetes.default' ``` or ```shell kubectl exec -i -t dnsutils -- nslookup kubernetes.default ``` ``` Server:    10.0.0.10 Address 1: 10.0.0.10 kube-dns.kube-system.svc.cluster.local nslookup: can't resolve 'kubernetes.default' ``` ### Check if the DNS pod is running Use the `kubectl get pods` command to verify that the DNS pod is running. ```shell kubectl get pods --namespace=kube-system -l k8s-app=kube-dns ``` ``` NAME                       READY     STATUS    RESTARTS   AGE ... coredns-7b96bf9f76-5hsxb   1/1       Running   0           1h coredns-7b96bf9f76-mvmmt   1/1       Running   0           1h ... ``` {{< note >}} The value for label `k8s-app` is `kube-dns` for both CoreDNS and kube-dns deployments. {{< /note >}} If you see that no CoreDNS Pod is running or that the Pod has failed/completed, the DNS add-on may not be deployed by default in your current environment and you will have to deploy it manually. ### Check for errors in the DNS pod Use the `kubectl logs` command to see logs for the DNS containers. For CoreDNS: ```shell kubectl logs --namespace=kube-system -l k8s-app=kube-dns ``` Here is an example of a healthy CoreDNS log: ``` .:53 2018/08/15 14:37:17 [INFO] CoreDNS-1.2.2 2018/08/15 14:37:17 [INFO] linux/amd64, go1.10.3, 2e322f6 CoreDNS-1.2.2 linux/amd64, go1.10.3, 2e322f6 2018/08/15 14:37:17 [INFO] plugin/reload: Running configuration MD5 = 24e6c59e83ce706f07bcc82c31b1ea1c ``` See if there are any suspicious or unexpected messages in the logs. ### Is DNS service up? Verify that the DNS service is up by using the `kubectl get service` command. ```shell kubectl get svc --namespace=kube-system ``` ``` NAME         TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)             AGE ... kube-dns     ClusterIP   10.0.0.10      <none>        53/UDP,53/TCP        1h ... ``` {{< note >}} The service name is `kube-dns` for both CoreDNS and kube-dns deployments. {{< /note >}} If you have created the Service or in the case it should be created by default but it does not appear, see [debugging Services](/docs/tasks/debug-application-cluster/debug-service/) for more information. ### Are DNS endpoints exposed? You can verify that DNS endpoints are exposed by using the `kubectl get endpoints` command. ```shell kubectl get endpoints kube-dns --namespace=kube-system ``` ``` NAME       ENDPOINTS                       AGE kube-dns   10.180.3.17:53,10.180.3.17:53    1h ``` If you do not see the endpoints, see the endpoints section in the [debugging Services](/docs/tasks/debug-application-cluster/debug-service/) documentation. For additional Kubernetes DNS examples, see the [cluster-dns examples](https://github.com/kubernetes/examples/tree/master/staging/cluster-dns) in the Kubernetes GitHub repository. ### Are DNS queries being received/processed? You can verify if queries are being received by CoreDNS by adding the `log` plugin to the CoreDNS configuration (aka Corefile). The CoreDNS Corefile is held in a {{< glossary_tooltip text=\"ConfigMap\" term_id=\"configmap\" >}} named `coredns`. To edit it, use the command: ``` kubectl -n kube-system edit configmap coredns ``` Then add `log` in the Corefile section per the example below: ```yaml apiVersion: v1 kind: ConfigMap metadata: name: coredns namespace: kube-system data: Corefile: | .:53 { log errors health kubernetes cluster.local in-addr.arpa ip6.arpa { pods insecure upstream fallthrough in-addr.arpa ip6.arpa } prometheus :9153 proxy . /etc/resolv.conf cache 30 loop reload loadbalance } ``` After saving the changes, it may take up to minute or two for Kubernetes to propagate these changes to the CoreDNS pods. Next, make some queries and view the logs per the sections above in this document. If CoreDNS pods are receiving the queries, you should see them in the logs. Here is an example of a query in the log: ``` .:53 2018/08/15 14:37:15 [INFO] CoreDNS-1.2.0 2018/08/15 14:37:15 [INFO] linux/amd64, go1.10.3, 2e322f6 CoreDNS-1.2.0 linux/amd64, go1.10.3, 2e322f6 2018/09/07 15:29:04 [INFO] plugin/reload: Running configuration MD5 = 162475cdf272d8aa601e6fe67a6ad42f 2018/09/07 15:29:04 [INFO] Reloading complete 172.17.0.18:41675 - [07/Sep/2018:15:29:11 +0000] 59925 \"A IN kubernetes.default.svc.cluster.local. udp 54 false 512\" NOERROR qr,aa,rd,ra 106 0.000066649s ``` ## Known issues Some Linux distributions (e.g. Ubuntu) use a local DNS resolver by default (systemd-resolved). Systemd-resolved moves and replaces `/etc/resolv.conf` with a stub file that can cause a fatal forwarding loop when resolving names in upstream servers. This can be fixed manually by using kubelet's `--resolv-conf` flag to point to the correct `resolv.conf` (With `systemd-resolved`, this is `/run/systemd/resolve/resolv.conf`). kubeadm automatically detects `systemd-resolved`, and adjusts the kubelet flags accordingly. Kubernetes installs do not configure the nodes' `resolv.conf` files to use the cluster DNS by default, because that process is inherently distribution-specific. This should probably be implemented eventually. Linux's libc (a.k.a. glibc) has a limit for the DNS `nameserver` records to 3 by default. What's more, for the glibc versions which are older than glibc-2.17-222 ([the new versions update see this issue](https://access.redhat.com/solutions/58028)), the allowed number of DNS `search` records has been limited to 6 ([see this bug from 2005](https://bugzilla.redhat.com/show_bug.cgi?id=168253)). Kubernetes needs to consume 1 `nameserver` record and 3 `search` records. This means that if a local installation already uses 3 `nameserver`s or uses more than 3 `search`es while your glibc version is in the affected list, some of those settings will be lost. To work around the DNS `nameserver` records limit, the node can run `dnsmasq`, which will provide more `nameserver` entries. You can also use kubelet's `--resolv-conf` flag. To fix the DNS `search` records limit, consider upgrading your linux distribution or upgrading to an unaffected version of glibc. If you are using Alpine version 3.3 or earlier as your base image, DNS may not work properly due to a known issue with Alpine. Kubernetes [issue 30215](https://github.com/kubernetes/kubernetes/issues/30215) details more information on this. ## {{% heading \"whatsnext\" %}} - See [Autoscaling the DNS Service in a Cluster](/docs/tasks/administer-cluster/dns-horizontal-autoscaling/). - Read [DNS for Services and Pods](/docs/concepts/services-networking/dns-pod-service/) </ins>"}
{"_id":"q-en-website-72e758f17d23c7f71869629aa02ed1777f46f6dcce5d989927882faa53808efb","text":"Minikube 在用户计算机上的一个虚拟机内运行单节点 Kubernetes 集群。 你可以使用 Minikube <del> [在学习环境中尝试 Kubernetes](/zh-cn/docs/setup/learning-environment/). </del> <ins> [在学习环境中尝试 Kubernetes](/zh-cn/docs/setup/learning-environment/)。 </ins>"}
{"_id":"q-en-website-7313e2f505b9916406682972eca77e18b38408c749b1a7269b470176ba436fc4","text":"or [service account tokens](/docs/reference/access-authn-authz/authentication/#service-account-tokens) are allowed. <del> Nodes should be provisioned with the public root certificate for the cluster such that they can </del> <ins> Nodes should be provisioned with the public root {{< glossary_tooltip text=\"certificate\" term_id=\"certificate\" >}} for the cluster such that they can </ins> connect securely to the API server along with valid client credentials. A good approach is that the client credentials provided to the kubelet are in the form of a client certificate. See [kubelet TLS bootstrapping](/docs/reference/access-authn-authz/kubelet-tls-bootstrapping/) for automated provisioning of kubelet client certificates. <del> Pods that wish to connect to the API server can do so securely by leveraging a service account so </del> <ins> {{< glossary_tooltip text=\"Pods\" term_id=\"pod\" >}} that wish to connect to the API server can do so securely by leveraging a service account so </ins> that Kubernetes will automatically inject the public root certificate and a valid bearer token into the pod when it is instantiated. The `kubernetes` service (in `default` namespace) is configured with a virtual IP address that is <del> redirected (via `kube-proxy`) to the HTTPS endpoint on the API server. </del> <ins> redirected (via `{{< glossary_tooltip text=\"kube-proxy\" term_id=\"kube-proxy\" >}}`) to the HTTPS endpoint on the API server. </ins> The control plane components also communicate with the API server over the secure port. <del> As a result, the default operating mode for connections from the nodes and pods running on the </del> <ins> As a result, the default operating mode for connections from the nodes and pod running on the </ins> nodes to the control plane is secured by default and can run over untrusted and/or public networks. ## Control plane to node There are two primary communication paths from the control plane (the API server) to the nodes. <del> The first is from the API server to the kubelet process which runs on each node in the cluster. </del> <ins> The first is from the API server to the {{< glossary_tooltip text=\"kubelet\" term_id=\"kubelet\" >}} process which runs on each node in the cluster. </ins> The second is from the API server to any node, pod, or service through the API server's _proxy_ functionality."}
{"_id":"q-en-website-732d45e398c31c98d6c9c28ea1682dd0ed80f31adf5c032f5780927ff2a1356e","text":"other versions of Kubernetes, check the documentation for that release. By default, `spec.loadBalancerClass` is `nil` and a `LoadBalancer` type of Service uses the cloud provider's default load balancer implementation if the cluster is configured with <del> a cloud provider using the `--cloud-provider` component flag. </del> <ins> a cloud provider using the `--cloud-provider` component flag. </ins> If `spec.loadBalancerClass` is specified, it is assumed that a load balancer implementation that matches the specified class is watching for Services. Any default load balancer implementation (for example, the one provided by the cloud provider) will ignore Services that have this field set. `spec.loadBalancerClass` can be set on a Service of type `LoadBalancer` only. <del> Once set, it cannot be changed. </del> <ins> Once set, it cannot be changed. </ins> The value of `spec.loadBalancerClass` must be a label-style identifier, with an optional prefix such as \"`internal-vip`\" or \"`example.com/internal-vip`\". Unprefixed names are reserved for end-users."}
{"_id":"q-en-website-73a3a893061db5e8878752685df56a4853ecead59b8bd52a14649528e2626f8f","text":"This annotation is used to set [Pod Deletion Cost](/docs/concepts/workloads/controllers/replicaset/#pod-deletion-cost) which allows users to influence ReplicaSet downscaling order. The annotation parses into an `int32` type. <ins> ### cluster-autoscaler.kubernetes.io/enable-ds-eviction Example: `cluster-autoscaler.kubernetes.io/enable-ds-eviction: \"true\"` Used on: Pod This annotation controls whether a DaemonSet pod should be evicted by a ClusterAutoscaler. This annotation needs to be specified on DaemonSet pods in a DaemonSet manifest. When this annotation is set to `\"true\"`, the ClusterAutoscaler is allowed to evict a DaemonSet Pod, even if other rules would normally prevent that. To disallow the ClusterAutoscaler from evicting DaemonSet pods, you can set this annotation to `\"false\"` for important DaemonSet pods. If this annotation is not set, then the Cluster Autoscaler follows its overall behaviour (i.e evict the DaemonSets based on its configuration). {{< note >}} This annotation only impacts DaemonSet pods. {{< /note >}} </ins> ### kubernetes.io/ingress-bandwidth {{< note >}}"}
{"_id":"q-en-website-7469d3f340153fbbad1ce7485fd7ae9b2b440de8db1781f78d43499fb823a972","text":"in that Pod based on the data in the ConfigMap. The Pod and the ConfigMap must be in the same {{< glossary_tooltip text=\"namespace\" term_id=\"namespace\" >}}. <ins> {{< note >}} The `spec` of a {{< glossary_tooltip text=\"static Pod\" term_id=\"static-pod\" >}} cannot refer to a ConfigMap or any other API objects. {{< /note >}} </ins> Here's an example ConfigMap that has some keys with single values, and other keys where the value looks like a fragment of a configuration format."}
{"_id":"q-en-website-7470a1116ef2f1cf20dc47c4216295d8c484c42a44736f6ffeb9b25c9c72f894","text":"common use cases and suggested solutions. 1. Cluster running only non-proprietary (e.g. open-source) images.  No need to hide images. <del> - Use public images on the Docker hub. </del> <ins> - Use public images from a public registry </ins> - No configuration required. - Some cloud providers automatically cache or mirror public images, which improves availability and reduces the time to pull images. 1. Cluster running some proprietary images which should be hidden to those outside the company, but visible to all cluster users. <del> - Use a hosted private [Docker registry](https://docs.docker.com/registry/). - It may be hosted on the [Docker Hub](https://hub.docker.com/signup), or elsewhere. - Manually configure .docker/config.json on each node as described above. </del> <ins> - Use a hosted private registry - Manual configuration may be required on the nodes that need to access to private registry </ins> - Or, run an internal private registry behind your firewall with open read access. - No Kubernetes configuration is required. - Use a hosted container image registry service that controls image access"}
{"_id":"q-en-website-74de8f6086249796fa9d4647eba8df342d55e43f7c77129583f7662578db32b5","text":"### Stable Storage <del> Kubernetes creates one [PersistentVolume](/docs/concepts/storage/persistent-volumes/) for each VolumeClaimTemplate. In the nginx example above, each Pod will receive a single PersistentVolume with a StorageClass of `my-storage-class` and 1 Gib of provisioned storage. If no StorageClass </del> <ins> For each VolumeClaimTemplate entry defined in a StatefulSet, each Pod receives one PersistentVolumeClaim. In the nginx example above, each Podreceives a single PersistentVolume with a StorageClass of `my-storage-class` and 1 Gib of provisioned storage. If no StorageClass </ins> is specified, then the default StorageClass will be used. When a Pod is (re)scheduled onto a node, its `volumeMounts` mount the PersistentVolumes associated with its PersistentVolume Claims. Note that, the PersistentVolumes associated with the"}
{"_id":"q-en-website-758879f40ce767daedfbdc5a32a36752746922c87edd8f317080743e530da570","text":"cat <<EOF >./kustomization.yaml configMapGenerator: - name: game-config-4 <del> labels: game-config: config-4 </del> <ins> options: labels: game-config: config-4 </ins> files: - configure-pod-container/configmap/game.properties EOF"}
{"_id":"q-en-website-758bd632ceb4cd432bbb7f9aae9af5aa46702ac6094bf0a129d35af4cfd27e67","text":"Now, re-run the test: ```console <del> $ for node in $NODES; do curl --connect-timeout 1 -s $node:$NODEPORT | grep -i client_address; do </del> <ins> $ for node in $NODES; do curl --connect-timeout 1 -s $node:$NODEPORT | grep -i client_address; done </ins> client_address=104.132.1.79 ```"}
{"_id":"q-en-website-75baa8575f24fe024440708fc6ee68c2c3746ad355fc9f527e8e447dd818277c","text":"```shell kubectl describe -f myapp.yaml ``` <ins> 実行結果は下記のようになります。 </ins> ``` Name:          myapp-pod Namespace:     default [...] <del> Labels:        app=myapp </del> <ins> Labels:        app.kubernetes.io/name=MyApp </ins> Status:        Pending [...] Init Containers:"}
{"_id":"q-en-website-76411058ddc4bef16d1758387597ea790288350c571d39318e407db19f8d63cb","text":"{{ range .Params.cards }} <div class=\"launch-card\"> <ins> <div class=\"card-content\"> </ins> <h2 id=\"{{ replace .title \" \" \"-\" | lower }}\">{{ .title }}</h2> <p>{{ .description }}</p> <ul>"}
{"_id":"q-en-website-76fb6e2086bc5d38021bb95bb0cef39e2436eb48f5051e717fa33bd04bd8d206","text":"title: Pod 优先级（Pod Priority） id: pod-priority date: 2019-01-31 <del> full_link: /zh/docs/concepts/configuration/pod-priority-preemption/#pod-priority </del> <ins> full_link: /zh/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority </ins> short_description: > Pod 优先级表示一个 Pod 相对于其他 Pod 的重要性。"}
{"_id":"q-en-website-786736079e03844a7b8c646499a7ca6c36ebde7d8901f4a920844701c42118d9","text":"<ins> <svg width=\"580\" height=\"400\" xmlns=\"http://www.w3.org/2000/svg\"> <g> <title>background</title> <rect x=\"-1\" y=\"-1\" width=\"506.34798\" height=\"349.82619\" id=\"canvas_background\" fill=\"#fff\" opacity=\"0\"/> <g id=\"canvasGrid\" display=\"none\"> <rect opacity=\"0\" id=\"svg_4\" width=\"100%\" height=\"100%\" x=\"0\" y=\"0\" stroke-width=\"0\" fill=\"url(#gridpattern)\"/> </g> </g> <g> <title>Layer 1</title> <rect fill=\"#326ce5\" stroke=\"#000\" stroke-width=\"1.5\" x=\"126.27611\" y=\"84.45079\" width=\"336.49766\" height=\"242.99831\" id=\"svg_1\"/> <rect fill=\"#DDDDDD\" stroke-width=\"0.5\" x=\"127.2761\" y=\"261.05662\" width=\"95.3\" height=\"66\" id=\"svg_2\" stroke=\"#000\"/> <rect fill=\"#BBBBBB\" stroke-opacity=\"null\" x=\"222.4421\" y=\"261.28292\" width=\"108.3\" height=\"66\" id=\"svg_3\" stroke=\"#000\"/> <rect fill=\"#ffffff\" stroke-width=\"0.5\" stroke-opacity=\"null\" x=\"330.77469\" y=\"261.28292\" width=\"131\" height=\"66\" id=\"svg_5\" stroke=\"#000\"/> <text fill=\"#000000\" stroke-width=\"0\" stroke-opacity=\"null\" fill-opacity=\"null\" x=\"126.25112\" y=\"28.72775\" id=\"svg_6\" font-size=\"24\" font-family=\"Helvetica, Arial, sans-serif\" text-anchor=\"start\" xml:space=\"preserve\" transform=\"matrix(3.8729541301727295,0,0,0.698510413795276,-358.40104965794853,12.1371268265946) \" stroke=\"#000\"/> <text fill=\"#000000\" stroke-width=\"0\" stroke-opacity=\"null\" fill-opacity=\"null\" x=\"96.33037\" y=\"92.52907\" id=\"svg_9\" font-size=\"24\" font-family=\"Helvetica, Arial, sans-serif\" text-anchor=\"start\" xml:space=\"preserve\" transform=\"matrix(0.6039765318373469,0,0,0.6213608286284256,43.920523540443796,7.5797796894100635) \" stroke=\"#000\">Node Capacity</text> <text fill=\"#000000\" stroke-width=\"0\" stroke-opacity=\"null\" fill-opacity=\"null\" x=\"146.65172\" y=\"483.69046\" id=\"svg_10\" font-size=\"24\" font-family=\"Helvetica, Arial, sans-serif\" text-anchor=\"start\" xml:space=\"preserve\" transform=\"matrix(0.5187438936507338,0,0,0.5165904901211577,58.14778751529779,47.720737964149194) \" stroke=\"#000\">kube-reserved</text> <text fill=\"#000000\" stroke-width=\"0\" stroke-opacity=\"null\" fill-opacity=\"null\" x=\"333.31931\" y=\"486.27149\" id=\"svg_11\" font-size=\"24\" font-family=\"Helvetica, Arial, sans-serif\" text-anchor=\"start\" xml:space=\"preserve\" transform=\"matrix(0.5187438936507338,0,0,0.5165904901211577,58.14778751529779,47.720737964149194) \" stroke=\"#000\">system-reserved</text> <text fill=\"#000000\" stroke-width=\"0\" stroke-opacity=\"null\" fill-opacity=\"null\" x=\"559.50522\" y=\"487.562\" id=\"svg_12\" font-size=\"24\" font-family=\"Helvetica, Arial, sans-serif\" text-anchor=\"start\" xml:space=\"preserve\" transform=\"matrix(0.5187438936507338,0,0,0.5165904901211577,58.14778751529779,47.720737964149194) \" stroke=\"#000\">eviction-threshold</text> <text fill=\"#ffffff\" stroke-width=\"0\" stroke-opacity=\"null\" fill-opacity=\"null\" x=\"246.31519\" y=\"182.62777\" id=\"svg_14\" font-size=\"24\" font-family=\"Helvetica, Arial, sans-serif\" text-anchor=\"start\" xml:space=\"preserve\" transform=\"matrix(0.8530217831379474,0,0,0.8530217831379474,32.26513711483058,11.272510077186126) \" stroke=\"#000\">allocatable</text> <text fill=\"#ffffff\" stroke-width=\"0\" stroke-opacity=\"null\" fill-opacity=\"null\" x=\"191.56677\" y=\"217.51295\" id=\"svg_15\" font-size=\"24\" font-family=\"Helvetica, Arial, sans-serif\" text-anchor=\"start\" xml:space=\"preserve\" transform=\"matrix(0.6610298739213645,0,0,0.6148439389614191,97.43948566238379,61.05811172356589) \" stroke=\"#000\">(available for pods)</text> <line fill=\"none\" stroke=\"#000\" stroke-width=\"null\" stroke-opacity=\"null\" fill-opacity=\"null\" x1=\"221.6918\" y1=\"348.02537\" x2=\"222.35847\" y2=\"348.02537\" id=\"svg_19\" transform=\"rotate(0.9628710746765137 222.02513122558057,348.0253906249988) \"/> <line stroke=\"#000\" stroke-linecap=\"square\" id=\"svg_8\" y2=\"261.50152\" x2=\"462.85834\" y1=\"261.50152\" x1=\"125.8955\" fill-opacity=\"null\" stroke-opacity=\"null\" fill=\"none\"/> <line stroke=\"#000\" stroke-linecap=\"square\" id=\"svg_13\" y2=\"328.33922\" x2=\"331.2413\" y1=\"261.98921\" x1=\"331.2413\" fill-opacity=\"null\" stroke-opacity=\"null\" fill=\"none\"/> <line stroke=\"#000\" stroke-linecap=\"square\" id=\"svg_17\" y2=\"327.36391\" x2=\"222.00652\" y1=\"261.50155\" x1=\"222.00652\" fill-opacity=\"null\" stroke-opacity=\"null\" fill=\"none\"/> </g> </svg> </ins>"}
{"_id":"q-en-website-78d9fd82fbdc8a8db1d19e4221c78adcffabc2a74ffa74b355b17aee56867ddd","text":"--- <del> title: Intro to Windows support in Kubernetes </del> <ins> title: KubernetesのWindowsサポート概要 </ins> content_type: concept weight: 65 --- <!-- overview --> <del> Windows applications constitute a large portion of the services and applications that run in many organizations. [Windows containers](https://aka.ms/windowscontainers) provide a modern way to encapsulate processes and package dependencies, making it easier to use DevOps practices and follow cloud native patterns for Windows applications. Kubernetes has become the defacto standard container orchestrator, and the release of Kubernetes 1.14 includes production support for scheduling Windows containers on Windows nodes in a Kubernetes cluster, enabling a vast ecosystem of Windows applications to leverage the power of Kubernetes. Organizations with investments in Windows-based applications and Linux-based applications don't have to look for separate orchestrators to manage their workloads, leading to increased operational efficiencies across their deployments, regardless of operating system. </del> <ins> Windowsアプリケーションは、多くの組織で実行されているサービスやアプリケーションの大部分を占めています。[Windowsコンテナ](https://aka.ms/windowscontainers)は、プロセスとパッケージの依存関係を一つにまとめる最新の方法を提供し、DevOpsプラクティスの使用とWindowsアプリケーションのクラウドネイティブパターンの追求を容易にします。Kubernetesは事実上、標準的なコンテナオーケストレータになりました。Kubernetes 1.14のリリースでは、Kubernetesクラスター内のWindowsノードでWindowsコンテナをスケジューリングする本番環境サポートが含まれたので、Windowsアプリケーションの広大なエコシステムにおいて、Kubernetesを有効的に活用できます。WindowsベースのアプリケーションとLinuxベースのアプリケーションに投資している組織は、ワークロードを管理する個別のオーケストレーターが不要となるため、オペレーティングシステムに関係なく導入全体の運用効率が向上します。 </ins> <!-- body --> <del> ## Windows containers in Kubernetes </del> <ins> ## KubernetesのWindowsコンテナ </ins> <del> To enable the orchestration of Windows containers in Kubernetes, simply include Windows nodes in your existing Linux cluster. Scheduling Windows containers in [Pods](/ja/docs/concepts/workloads/pods/pod-overview/) on Kubernetes is as simple and easy as scheduling Linux-based containers. </del> <ins> KubernetesでWindowsコンテナのオーケストレーションを有効にするには、既存のLinuxクラスターにWindowsノードを含めるだけです。Kubernetesの[Pod](/ja/docs/concepts/workloads/pods/pod-overview/)でWindowsコンテナをスケジュールすることは、Linuxベースのコンテナをスケジュールするのと同じくらいシンプルで簡単です。 </ins> <del> In order to run Windows containers, your Kubernetes cluster must include multiple operating systems, with control plane nodes running Linux and workers running either Windows or Linux depending on your workload needs. Windows Server 2019 is the only Windows operating system supported, enabling [Kubernetes Node](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/architecture/architecture.md#the-kubernetes-node) on Windows (including kubelet, [container runtime](https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/containerd), and kube-proxy). For a detailed explanation of Windows distribution channels see the [Microsoft documentation](https://docs.microsoft.com/en-us/windows-server/get-started-19/servicing-channels-19). </del> <ins> Windowsコンテナを実行するには、Kubernetesクラスターに複数のオペレーティングシステムを含める必要があります。コントロールプレーンノードはLinux、ワーカーノードはワークロードのニーズに応じてWindowsまたはLinuxで実行します。Windows Server 2019は、サポートされている唯一のWindowsオペレーティングシステムであり、Windows（kubelet、[コンテナランタイム](https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/containerd)、kube-proxyを含む）で[Kubernetesノード](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/architecture/architecture.md#the-kubernetes-node)を有効にします。Windowsディストリビューションチャンネルの詳細については、[Microsoftのドキュメント](https://docs.microsoft.com/en-us/windows-server/get-started-19/servicing-channels-19)を参照してください。 </ins> {{< note >}} <del> The Kubernetes control plane, including the [master components](/ja/docs/concepts/overview/components/), continues to run on Linux. There are no plans to have a Windows-only Kubernetes cluster. </del> <ins> [マスターコンポーネント](/ja/docs/concepts/overview/components/)を含むKubernetesコントロールプレーンは、Linuxで実行し続けます。WindowsのみのKubernetesクラスターを導入する計画はありません。 </ins> {{< /note >}} {{< note >}} <del> In this document, when we talk about Windows containers we mean Windows containers with process isolation. Windows containers with [Hyper-V isolation](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container) is planned for a future release. </del> <ins> このドキュメントでは、Windowsコンテナについて説明する場合、プロセス分離のWindowsコンテナを意味します。[Hyper-V分離](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container)のWindowsコンテナは、将来リリースが計画されています。 </ins> {{< /note >}} <del> ## Supported Functionality and Limitations </del> <ins> ## サポートされている機能と制限 </ins> <del> ### Supported Functionality </del> <ins> ### サポートされている機能 </ins> <del> #### Compute </del> <ins> #### コンピュート </ins> <del> From an API and kubectl perspective, Windows containers behave in much the same way as Linux-based containers. However, there are some notable differences in key functionality which are outlined in the limitation section. </del> <ins> APIとkubectlの観点から見ると、WindowsコンテナはLinuxベースのコンテナとほとんど同じように動作します。ただし、制限セクションで概説されている主要な機能には、いくつかの顕著な違いがあります。 </ins> <del> Let's start with the operating system version. Refer to the following table for Windows operating system support in Kubernetes. A single heterogeneous Kubernetes cluster can have both Windows and Linux worker nodes. Windows containers have to be scheduled on Windows nodes and Linux containers on Linux nodes. </del> <ins> オペレーティングシステムのバージョンから始めましょう。KubernetesのWindowsオペレーティングシステムのサポートについては、次の表を参照してください。単一の異種Kubernetesクラスターは、WindowsとLinuxの両方のワーカーノードを持つことができます。WindowsコンテナはWindowsノードで、LinuxコンテナはLinuxノードでスケジュールする必要があります。 </ins> <del> | Kubernetes version | Host OS version (Kubernetes Node) | | | </del> <ins> | Kubernetes バージョン | ホストOS バージョン (Kubernetes ノード) | | | </ins> | --- | --- | --- | --- | | | *Windows Server 1709* | *Windows Server 1803* | *Windows Server 1809/Windows Server 2019* | <del> | *Kubernetes v1.14* | Not Supported | Not Supported| Supported for Windows Server containers Builds 17763.* with Docker EE-basic 18.09 | </del> <ins> | *Kubernetes v1.14* | サポートされていません | サポートされていません| Windows Server containers Builds 17763.* と Docker EE-basic 18.09 がサポートされています | </ins> {{< note >}} <del> We don't expect all Windows customers to update the operating system for their apps frequently. Upgrading your applications is what dictates and necessitates upgrading or introducing new nodes to the cluster. For the customers that chose to upgrade their operating system for containers running on Kubernetes, we will offer guidance and step-by-step instructions when we add support for a new operating system version. This guidance will include recommended upgrade procedures for upgrading user applications together with cluster nodes. Windows nodes adhere to Kubernetes [version-skew policy](/ja/docs/setup/release/version-skew-policy/) (node to control plane versioning) the same way as Linux nodes do today. </del> <ins> すべてのWindowsユーザーがアプリのオペレーティングシステムを頻繁に更新することは望んでいません。アプリケーションのアップグレードは、クラスターに新しいノードをアップグレードまたは導入することを要求する必要があります。Kubernetesで実行されているコンテナのオペレーティングシステムをアップグレードすることを選択したお客様には、新しいオペレーティングシステムバージョンのサポート追加時に、ガイダンスと段階的な指示を提供します。このガイダンスには、クラスターノードと共にアプリケーションをアップグレードするための推奨アップグレード手順が含まれます。Windowsノードは、現在のLinuxノードと同じように、Kubernetes[バージョンスキューポリシー](/ja/docs/setup/release/version-skew-policy/)（ノードからコントロールプレーンのバージョン管理）に準拠しています。 </ins> {{< /note >}} {{< note >}} <del> The Windows Server Host Operating System is subject to the [Windows Server ](https://www.microsoft.com/en-us/cloud-platform/windows-server-pricing) licensing. The Windows Container images are subject to the [Supplemental License Terms for Windows containers](https://docs.microsoft.com/en-us/virtualization/windowscontainers/images-eula). </del> <ins> Windows Serverホストオペレーティングシステムには、[Windows Server](https://www.microsoft.com/en-us/cloud-platform/windows-server-pricing)ライセンスが適用されます。Windowsコンテナイメージには、[Windowsコンテナの追加ライセンス条項](https://docs.microsoft.com/en-us/virtualization/windowscontainers/images-eula)ライセンスが提供されます。 </ins> {{< /note >}} {{< note >}} <del> Windows containers with process isolation have strict compatibility rules, [where the host OS version must match the container base image OS version](https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility). Once we support Windows containers with Hyper-V isolation in Kubernetes, the limitation and compatibility rules will change. </del> <ins> プロセス分離のWindowsコンテナには、厳格な互換性ルールがあります[ホストOSのバージョンはコンテナのベースイメージのOSバージョンと一致する必要があります](https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility)。KubernetesでHyper-V分離のWindowsコンテナをサポートすると、制限と互換性ルールが変更されます。 </ins> {{< /note >}} <del> Key Kubernetes elements work the same way in Windows as they do in Linux. In this section, we talk about some of the key workload enablers and how they map to Windows. </del> <ins> Kubernetesの主要な要素は、WindowsでもLinuxと同じように機能します。このセクションでは、主要なワークロードイネーブラーのいくつかと、それらがWindowsにどのようにマップされるかについて説明します。 </ins> * [Pods](/ja/docs/concepts/workloads/pods/pod-overview/) <del> A Pod is the basic building block of Kubernetes–the smallest and simplest unit in the Kubernetes object model that you create or deploy. You may not deploy Windows and Linux containers in the same Pod. All containers in a Pod are scheduled onto a single Node where each Node represents a specific platform and architecture. The following Pod capabilities, properties and events are supported with Windows containers: </del> <ins> Podは、Kubernetesの基本的なビルディングブロックです。作成またはデプロイするKubernetesオブジェクトモデルの最小かつ最も単純なユニットです。WindowsとLinuxのコンテナを同じPodにデプロイすることはできません。Pod内のすべてのコンテナは、各ノードが特定のプラットフォームとアーキテクチャを表す単一のノードにスケジュールされます。次のPod機能、プロパティ、およびイベントがWindowsコンテナでサポートされています。: </ins> <del> * Single or multiple containers per Pod with process isolation and volume sharing * Pod status fields * Readiness and Liveness probes * postStart & preStop container lifecycle events * ConfigMap, Secrets: as environment variables or volumes </del> <ins> * プロセス分離とボリューム共有を備えたPodごとの単一または複数のコンテナ * Podステータスフィールド * ReadinessとLiveness Probe * postStartとpreStopコンテナのライフサイクルイベント * ConfigMap, Secrets: 環境変数またはボリュームとして </ins> * EmptyDir <del> * Named pipe host mounts * Resource limits </del> <ins> * 名前付きパイプホストマウント * リソース制限 </ins> * [Controllers](/ja/docs/concepts/workloads/controllers/) <del> Kubernetes controllers handle the desired state of Pods. The following workload controllers are supported with Windows containers: </del> <ins> Kubernetesコントローラは、Podの望ましい状態を処理します。次のワークロードコントローラーは、Windowsコンテナでサポートされています。: </ins> * ReplicaSet * ReplicationController"}
{"_id":"q-en-website-78f8dfaa0ec989529ced322f74ce9db21e49bd3d03f94b1425d1c69364c003c5","text":"<div class=\"td-page-blog-meta ml-2 pb-1 pt-2 mb-4\"> {{ with site.Home.OutputFormats.Get \"rss\" -}} <link rel=\"{{ .Rel }}\" type=\"{{ .MediaType.Type }}\" href=\"{{ .Permalink | safeURL }}\" title=\"{{ site.Title }}\"> <del> <a class=\"widget-link\" href=\"{{ .Permalink | safeURL }}\"><div> <i class=\"fas fa-rss fab-icon\"> </i> <span class=\"widget-link-text\">RSS Feed</span></div> </a> </del> <ins> <a class=\"widget-link\" href=\"{{ .Permalink | safeURL }}\" target=\"_blank\"><div> <i class=\"fas fa-rss fab-icon\"> </i> <span class=\"widget-link-text\">RSS Feed</span></div> </a> </ins> {{ end -}} <del> <a class=\"widget-link\" href=\"https://kubernetes.io/docs/contribute/new-content/blogs-case-studies/\"><div> <i class=\"fa fa-edit fab-icon\"></i> <span class=\"widget-link-text\">Submit a Post</span></div></a> <a class=\"widget-link\" href=\"https://twitter.com/kubernetesio\"><div> <i class=\"fab fa-twitter-square fab-icon\"> </i> <span class=\"widget-link-text\"> @Kubernetesio</span></div></a> <a class=\"widget-link\" href=\"https://github.com/kubernetes/kubernetes\"><div> <i class=\"fab fa-github-square fab-icon\"></i> <span class=\"widget-link-text\"> on GitHub </span></div></a> <a class=\"widget-link\" href=\"http://slack.k8s.io\"><div><i class=\"fab fa-slack fab-icon\"> </i> <span class=\"widget-link-text\">#kubernetes-users </span></div></a> <a class=\"widget-link\" href=\"https://stackoverflow.com/questions/tagged/kubernetes\"><div><i class=\"fab fa-stack-overflow fab-icon\"></i> <span class=\"widget-link-text\"> Overflow</span></div></a> <a class=\"widget-link\" href=\"https://discuss.kubernetes.io\"><div> <i class=\"fab fa-discourse fab-icon\"></i><span class=\"widget-link-text\"> Forum </span></div></a> </del> <ins> <a class=\"widget-link\" href=\"https://kubernetes.io/docs/contribute/new-content/blogs-case-studies/\" target=\"_blank\"><div> <i class=\"fa fa-edit fab-icon\"></i> <span class=\"widget-link-text\">Submit a Post</span></div></a> <a class=\"widget-link\" href=\"https://twitter.com/kubernetesio\" target=\"_blank\"><div> <i class=\"fab fa-twitter-square fab-icon\"> </i> <span class=\"widget-link-text\"> @Kubernetesio</span></div></a> <a class=\"widget-link\" href=\"https://github.com/kubernetes/kubernetes\" target=\"_blank\"><div> <i class=\"fab fa-github-square fab-icon\"></i> <span class=\"widget-link-text\"> on GitHub </span></div></a> <a class=\"widget-link\" href=\"http://slack.k8s.io\" target=\"_blank\"><div><i class=\"fab fa-slack fab-icon\"> </i> <span class=\"widget-link-text\">#kubernetes-users </span></div></a> <a class=\"widget-link\" href=\"https://stackoverflow.com/questions/tagged/kubernetes\" target=\"_blank\"><div><i class=\"fab fa-stack-overflow fab-icon\"></i> <span class=\"widget-link-text\"> Overflow</span></div></a> <a class=\"widget-link\" href=\"https://discuss.kubernetes.io\" target=\"_blank\"><div> <i class=\"fab fa-discourse fab-icon\"></i><span class=\"widget-link-text\"> Forum </span></div></a> </ins> <a class=\"widget-link\" href=\"https://kubernetes.io/docs/setup\"><div><i class=\"fa fa-download fab-icon\"></i> <span class=\"widget-link-text\"> Kubernetes</span></div></a> </div>"}
{"_id":"q-en-website-79877a747467b18851df502109d62c0d6806057a8a77587f27af2ff5a3bcbac4","text":"The following examples show some `crictl` commands and example output. <del> {{< warning >}} If you use `crictl` to create pod sandboxes or containers on a running Kubernetes cluster, the Kubelet will eventually delete them. `crictl` is not a general purpose workflow tool, but a tool that is useful for debugging. {{< /warning >}} </del> ### List pods List all pods:"}
{"_id":"q-en-website-799fb996d17976b7fb6f8098a4b0f2f5c83b4c67aa444075d2ecd59888e8a951","text":"### SSH tunnels <del> Kubernetes supports SSH tunnels to protect the control plane to nodes communication paths. In this </del> <ins> Kubernetes supports [SSH tunnels](https://www.ssh.com/academy/ssh/tunneling) to protect the control plane to nodes communication paths. In this </ins> configuration, the API server initiates an SSH tunnel to each node in the cluster (connecting to the SSH server listening on port 22) and passes all traffic destined for a kubelet, node, pod, or service through the tunnel."}
{"_id":"q-en-website-79de3cb57487dfd747ac359820077ce9470ca6f98f7bd47fc4483a9b8e557871","text":"### cgroupfs driver {#cgroupfs-cgroup-driver} <del> The `cgroupfs` driver is the default cgroup driver in the kubelet. When the `cgroupfs` driver is used, the kubelet and the container runtime directly interface with the cgroup filesystem to configure cgroups. </del> <ins> The `cgroupfs` driver is the [default cgroup driver in the kubelet](docs/reference/config-api/kubelet-config.v1beta1). When the `cgroupfs` driver is used, the kubelet and the container runtime directly interface with the cgroup filesystem to configure cgroups. </ins> The `cgroupfs` driver is **not** recommended when [systemd](https://www.freedesktop.org/wiki/Software/systemd/) is the init system because systemd expects a single cgroup manager on <del> the system. Additionally, if you use [cgroup v2](/docs/concepts/architecture/cgroups) , use the `systemd` cgroup driver instead of `cgroupfs`. </del> <ins> the system. Additionally, if you use [cgroup v2](/docs/concepts/architecture/cgroups), use the `systemd` cgroup driver instead of `cgroupfs`. </ins> ### systemd cgroup driver {#systemd-cgroup-driver}"}
{"_id":"q-en-website-7aceb53973c6ada89a846b61d8a9ff4d6df03cba44f351ad595da1cc2db737a1","text":"- [`kubectl`を使用してSecretを管理する](/docs/tasks/configmap-secret/managing-secret-using-kubectl/)方法を学ぶ - [config fileを使用してSecretを管理する](/docs/tasks/configmap-secret/managing-secret-using-config-file/)方法を学ぶ - [kustomizeを使用してSecretを管理する](/docs/tasks/configmap-secret/managing-secret-using-kustomize/)方法を学ぶ <ins> - [SecretのAPIリファレンス](/docs/reference/kubernetes-api/config-and-storage-resources/secret-v1/)を読む </ins>"}
{"_id":"q-en-website-7da406bbc86f5d8a0ecd8bc401fe1793d83208d62ddb89e81e699147300c36e3","text":"Example: `node.kubernetes.io/out-of-service:NoExecute` <del> A user can manually add the taint to a Node marking it out-of-service. If the `NodeOutOfServiceVolumeDetach` </del> <ins> A user can manually add the taint to a Node marking it out-of-service. If the `NodeOutOfServiceVolumeDetach` </ins> [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled on <del> `kube-controller-manager`, and a Node is marked out-of-service with this taint, the pods on the node will be forcefully deleted if there are no matching tolerations on it and volume detach operations for the pods terminating on the node will happen immediately. This allows the Pods on the out-of-service node to recover quickly on a different node. </del> <ins> `kube-controller-manager`, and a Node is marked out-of-service with this taint, the pods on the node will be forcefully deleted if there are no matching tolerations on it and volume detach operations for the pods terminating on the node will happen immediately. This allows the Pods on the out-of-service node to recover quickly on a different node. </ins> {{< caution >}} Refer to"}
{"_id":"q-en-website-7da66591d0857b041527c591a68188dae83ab1f7deffb3a54f6935cd43a7c83d","text":"title: Upgrading Windows nodes min-kubernetes-server-version: 1.17 content_type: task <del> weight: 50 </del> <ins> weight: 110 </ins> --- <!-- overview -->"}
{"_id":"q-en-website-7e32d06da4d557621a9b82c3f6c029557974035e1796af995452850ac08d32d2","text":"Internet to download the necessary files, while worker nodes do not. 3. These guide is tested OK on Ubuntu 14.04 LTS 64bit server, but it can not work with Ubuntu 15 which uses systemd instead of upstart. <del> 4. Dependencies of this guide: etcd-2.2.1, flannel-0.5.5, k8s-1.1.4, may work with higher versions. </del> <ins> 4. Dependencies of this guide: etcd-2.2.1, flannel-0.5.5, k8s-1.1.8, may work with higher versions. </ins> 5. All the remote servers can be ssh logged in without a password by using key authentication."}
{"_id":"q-en-website-7e8dc64683427be87fbc4a87e730f035603a92936ef8cd83bba53354e1d1ec10","text":"can find each other via `localhost`. They can also communicate with each other using standard inter-process communications like SystemV semaphores or POSIX shared memory.  Containers in different pods have distinct IP addresses <del> and can not communicate by IPC. </del> <ins> and can not communicate by IPC without [special configuration](/docs/concepts/policy/pod-security-policy/). These containers usually communicate with each other via Pod IP addresses. </ins> Applications within a pod also have access to shared volumes, which are defined as part of a pod and are made available to be mounted into each application's"}
{"_id":"q-en-website-80de7df8245bd7be599d91fecaa08c7774477520aeb72b74cb6130b0f73abfa4","text":"## Node Allocatable <del> ```text Node Capacity --------------------------- |     kube-reserved       | |-------------------------| |     system-reserved     | |-------------------------| |    eviction-threshold   | |-------------------------| |                         | |      allocatable        | |   (available for pods)  | |                         | |                         | --------------------------- ``` </del> <ins> ![node capacity](/images/docs/node-capacity.svg) </ins> `Allocatable` on a Kubernetes node is defined as the amount of compute resources that are available for pods. The scheduler does not over-subscribe"}
{"_id":"q-en-website-82f6ae0689ab0859881e0634e04b67a8a31a04db35ddabf1010f9ec004d5b289","text":"Install crictl (required for kubeadm / Kubelet Container Runtime Interface (CRI)) ```bash <del> CRICTL_VERSION=\"v1.17.0\" </del> <ins> CRICTL_VERSION=\"v1.22.0\" </ins> ARCH=\"amd64\" curl -L \"https://github.com/kubernetes-sigs/cri-tools/releases/download/${CRICTL_VERSION}/crictl-${CRICTL_VERSION}-linux-${ARCH}.tar.gz\" | sudo tar -C $DOWNLOAD_DIR -xz ```"}
{"_id":"q-en-website-847986075ca03777665ba7a4dc56c633b8d5ad258ec9f948cc1c6c1e488a53ff","text":"<ins> --- title: ネットワークポリシー content_type: concept weight: 50 --- <!-- overview --> ネットワークポリシーは、{{< glossary_tooltip text=\"Pod\" term_id=\"pod\">}}のグループが、Pod相互や他のネットワークエンドポイントと通信する場合に許可を与える方法を指定するための仕様です。 NetworkPolicyリソースは、{{< glossary_tooltip text=\"ラベル\" term_id=\"label\">}}を使用してPodを選択し、選択したPodに対してどんなトラフィックを許可するかを指定するルールを定義します。 <!-- body --> ## 前提条件 ネットワークポリシーは、[ネットワークプラグイン](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/)により実装されます。ネットワークポリシーを使用するには、NetworkPolicyをサポートするネットワークソリューションを使用しなければなりません。ネットワークポリシーを実装したコントローラーを使用せずにNetworkPolicyリソースを作成した場合は、何も効果はありません。 ## 分離されたPodと分離されていないPod デフォルトでは、Podは分離されていない状態(non-isolated)となるため、すべてのソースからのトラフィックを受信します。 Podを選択するNetworkPolicyが存在すると、Podは分離されるようになります。名前空間内に特定のPodを選択するNetworkPolicyが1つでも存在すると、そのPodはいずれかのNetworkPolicyで許可されていないすべての接続を拒否するようになります。(同じ名前空間内のPodでも、どのNetworkPolicyにも選択されなかった他のPodは、引き続きすべてのトラフィックを許可します。) ネットワークポリシーは追加式であるため、競合することはありません。複数のポリシーがPodを選択する場合、そのPodに許可されるトラフィックは、それらのポリシーのingress/egressルールの和集合で制限されます。したがって、評価の順序はポリシーの結果には影響がありません。 ## NetworkPolicyリソース {#networkpolicy-resource} リソースの完全な定義については、リファレンスの[NetworkPolicy](/docs/reference/generated/kubernetes-api/{{< param \"version\" >}}/#networkpolicy-v1-networking-k8s-io)のセクションを参照してください。 以下は、NetworkPolicyの一例です。 ```yaml apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: test-network-policy namespace: default spec: podSelector: matchLabels: role: db policyTypes: - Ingress - Egress ingress: - from: - ipBlock: cidr: 172.17.0.0/16 except: - 172.17.1.0/24 - namespaceSelector: matchLabels: project: myproject - podSelector: matchLabels: role: frontend ports: - protocol: TCP port: 6379 egress: - to: - ipBlock: cidr: 10.0.0.0/24 ports: - protocol: TCP port: 5978 ``` {{< note >}} 選択したネットワークソリューションがネットワークポリシーをサポートしていない場合には、これをクラスターのAPIサーバーにPOSTしても効果はありません。 {{< /note >}} __必須フィールド__: 他のKubernetesの設定と同様に、NetworkPolicyにも`apiVersion`、`kind`、`metadata`フィールドが必須です。設定ファイルの扱い方に関する一般的な情報については、[ConfigMapを使用してコンテナを構成する](/ja/docs/tasks/configure-pod-container/configure-pod-configmap/)と[オブジェクト管理](/ja/docs/concepts/overview/working-with-objects/object-management)を参照してください。 __spec__: NetworkPolicyの[spec](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status)を見ると、指定した名前空間内で特定のネットワークポリシーを定義するのに必要なすべての情報が確認できます。 __podSelector__: 各NetworkPolicyには、ポリシーを適用するPodのグループを選択する`podSelector`が含まれます。ポリシーの例では、ラベル\"role=db\"を持つPodを選択しています。`podSelector`を空にすると、名前空間内のすべてのPodが選択されます。 __policyTypes__: 各NetworkPolicyには、`policyTypes`として、`Ingress`、`Egress`、またはその両方からなるリストが含まれます。`policyTypes`フィールドでは、指定したポリシーがどの種類のトラフィックに適用されるかを定めます。トラフィックの種類としては、選択したPodへの内向きのトラフィック(Ingress)、選択したPodからの外向きのトラフィック(Egress)、またはその両方を指定します。`policyTypes`を指定しなかった場合、デフォルトで常に `Ingress`が指定され、NetworkPolicyにegressルールが1つでもあれば`Egress`も設定されます。 __ingress__: 各NetworkPolicyには、許可する`ingress`ルールのリストを指定できます。各ルールは、`from`および`ports`セクションの両方に一致するトラフィックを許可します。ポリシーの例には1つのルールが含まれ、このルールは、3つのソースのいずれかから送信された1つのポート上のトラフィックに一致します。1つ目のソースは`ipBlock`で、2つ目のソースは`namespaceSelector`で、3つ目のソースは`podSelector`でそれぞれ定められます。 __egress__: 各NetworkPolicyには、許可する`egress`ルールのリストを指定できます。各ルールは、`to`および`ports`セクションの両方に一致するトラフィックを許可します。ポリシーの例には1つのルールが含まれ、このルールは、1つのポート上で`10.0.0.0/24`の範囲内の任意の送信先へ送られるトラフィックに一致します。 したがって、上のNetworkPolicyの例では、次のようにネットワークポリシーを適用します。 1. \"default\"名前空間内にある\"role=db\"のPodを、内向きと外向きのトラフィックに対して分離する(まだ分離されていない場合) 2. (Ingressルール) \"default\"名前空間内の\"role=db\"ラベルが付いたすべてのPodのTCPの6379番ポートへの接続のうち、次の送信元からのものを許可する * \"default\"名前空間内のラベル\"role=frontend\"が付いたすべてのPod * ラベル\"project=myproject\"が付いた名前空間内のすべてのPod * 172.17.0.0–172.17.0.255および172.17.2.0–172.17.255.255(言い換えれば、172.17.1.0/24の範囲を除く172.17.0.0/16)の範囲内のすべてのIPアドレス 3. (Egressルール) \"role=db\"というラベルが付いた\"default\"名前空間内のすべてのPodからの、TCPの5978番ポート上でのCIDR 10.0.0.0/24への接続を許可する 追加の例については、[ネットワークポリシーを宣言する](/ja/docs/tasks/administer-cluster/declare-network-policy/)の説明を参照してください。 ## `to`と`from`のセレクターの振る舞い `ingress`の`from`セクションまたは`egress`の`to`セクションに指定できるセレクターは4種類あります。 __podSelector__: NetworkPolicyと同じ名前空間内の特定のPodを選択して、ingressの送信元またはegressの送信先を許可します。 __namespaceSelector__: 特定の名前空間を選択して、その名前空間内のすべてのPodについて、ingressの送信元またはegressの送信先を許可します。 __namespaceSelector__ *および* __podSelector__: 1つの`to`または`from`エントリーで`namespaceSelector`と`podSelector`の両方を指定して、特定の名前空間内の特定のPodを選択します。正しいYAMLの構文を使うように気をつけてください。このポリシーの例を以下に示します。 ```yaml ... ingress: - from: - namespaceSelector: matchLabels: user: alice podSelector: matchLabels: role: client ... ``` このポリシーには、1つの`from`要素があり、ラベル`user=alice`の付いた名前空間内にある、ラベル`role=client`の付いたPodからの接続を許可します。しかし、*以下の*ポリシーには注意が必要です。 ```yaml ... ingress: - from: - namespaceSelector: matchLabels: user: alice - podSelector: matchLabels: role: client ... ``` このポリシーには、`from`配列の中に2つの要素があります。そのため、ラベル`role=client`の付いた名前空間内にあるすべてのPodからの接続、*または*、任意の名前空間内にあるラベル`user=alice`の付いたすべてのPodからの接続を許可します。 正しいルールになっているか自信がないときは、`kubectl describe`を使用すると、Kubernetesがどのようにポリシーを解釈したのかを確認できます。 __ipBlock__: 特定のIPのCIDRの範囲を選択して、ingressの送信元またはegressの送信先を許可します。PodのIPは一時的なもので予測できないため、ここにはクラスター外のIPを指定するべきです。 クラスターのingressとegressの仕組みはパケットの送信元IPや送信先IPの書き換えを必要とすることがよくあります。その場合、NetworkPolicyの処理がIPの書き換えの前後どちらで行われるのかは定義されていません。そのため、ネットワークプラグイン、クラウドプロバイダー、`Service`の実装などの組み合わせによっては、動作が異なる可能性があります。 内向きのトラフィックの場合は、実際のオリジナルの送信元IPに基づいてパケットをフィルタリングできる可能性もあれば、NetworkPolicyが対象とする「送信元IP」が`LoadBalancer`やPodのノードなどのIPになってしまっている可能性もあることになります。 外向きのトラフィックの場合は、クラスター外のIPに書き換えられたPodから`Service`のIPへの接続は、`ipBlock`ベースのポリシーの対象になる場合とならない場合があることになります。 ## デフォルトのポリシー デフォルトでは、名前空間にポリシーが存在しない場合、その名前空間内のPodの内向きと外向きのトラフィックはすべて許可されます。以下の例を利用すると、その名前空間内でのデフォルトの振る舞いを変更できます。 ### デフォルトですべての内向きのトラフィックを拒否する すべてのPodを選択して、そのPodへのすべての内向きのトラフィックを許可しないNetworkPolicyを作成すると、その名前空間に対する「デフォルト」の分離ポリシーを作成できます。 {{< codenew file=\"service/networking/network-policy-default-deny-ingress.yaml\" >}} このポリシーを利用すれば、他のいかなるNetworkPolicyにも選択されなかったPodでも分離されることを保証できます。このポリシーは、デフォルトの外向きの分離の振る舞いを変更しません。 ### デフォルトで内向きのすべてのトラフィックを許可する (たとえPodを「分離されたもの」として扱うポリシーが追加された場合でも)名前空間内のすべてのPodへのすべてのトラフィックを許可したい場合には、その名前空間内のすべてのトラフィックを明示的に許可するポリシーを作成できます。 {{< codenew file=\"service/networking/network-policy-allow-all-ingress.yaml\" >}} ### デフォルトで外向きのすべてのトラフィックを拒否する すべてのPodを選択して、そのPodからのすべての外向きのトラフィックを許可しないNetworkPolicyを作成すると、その名前空間に対する「デフォルト」の外向きの分離ポリシーを作成できます。 {{< codenew file=\"service/networking/network-policy-default-deny-egress.yaml\" >}} このポリシーを利用すれば、他のいかなるNetworkPolicyにも選択されなかったPodでも、外向きのトラフィックが許可されないことを保証できます。このポリシーは、デフォルトの内向きの分離の振る舞いを変更しません。 ### デフォルトで外向きのすべてのトラフィックを許可する (たとえPodを「分離されたもの」として扱うポリシーが追加された場合でも)名前空間内のすべてのPodからのすべてのトラフィックを許可したい場合には、その名前空間内のすべての外向きのトラフィックを明示的に許可するポリシーを作成できます。 {{< codenew file=\"service/networking/network-policy-allow-all-egress.yaml\" >}} ### デフォルトで内向きと外向きのすべてのトラフィックを拒否する 名前空間内に以下のNetworkPolicyを作成すると、その名前空間で内向きと外向きのすべてのトラフィックを拒否する「デフォルト」のポリシーを作成できます。 {{< codenew file=\"service/networking/network-policy-default-deny-all.yaml\" >}} このポリシーを利用すれば、他のいかなるNetworkPolicyにも選択されなかったPodでも、内向きと外向きのトラフィックが許可されないことを保証できます。 ## SCTPのサポート {{< feature-state for_k8s_version=\"v1.12\" state=\"alpha\" >}} この機能を利用するには、クラスター管理者がAPIサーバーで`--feature-gates=SCTPSupport=true,…`と指定して、`SCTPSupport`[フィーチャーゲート](/ja/docs/reference/command-line-tools-reference/feature-gates/)を有効にする必要があります。フィーチャーゲートが有効になれば、NetworkPolicyの`protocol`フィールドに`SCTP`が指定できるようになります。 {{< note >}} SCTPプロトコルのネットワークポリシーをサポートする{{< glossary_tooltip text=\"CNI\" term_id=\"cni\" >}}プラグインを使用している必要があります。 {{< /note >}} ## {{% heading \"whatsnext\" %}} - [ネットワークポリシーを宣言する](/ja/docs/tasks/administer-cluster/declare-network-policy/)で追加の例の説明を読む。 - NetworkPolicyリソースで実現できるよくあるシナリオのためのさまざまな[レシピ](https://github.com/ahmetb/kubernetes-network-policy-recipes)を確認する。 </ins>"}
{"_id":"q-en-website-8606ee1699d8d629fe34223421d3a906b7145d8de30446c03db6036a335752c4","text":"The `spec` of a Pod has a `restartPolicy` field with possible values Always, OnFailure, and Never. The default value is Always. <del> The `restartPolicy` applies to all containers in the Pod. `restartPolicy` only refers to restarts of the containers by the kubelet on the same node. After containers in a Pod exit, the kubelet restarts them with an exponential back-off delay (10s, 20s, 40s, …), that is capped at five minutes. Once a container has executed for 10 minutes without any problems, the kubelet resets the restart backoff timer for that container. </del> <ins> The `restartPolicy` for a Pod applies to {{< glossary_tooltip text=\"app containers\" term_id=\"app-container\" >}} in the Pod and to regular [init containers](/docs/concepts/workloads/pods/init-containers/). [Sidecar containers](/docs/concepts/workloads/pods/sidecar-containers/) ignore the Pod-level `restartPolicy` field: in Kubernetes, a sidecar is defined as an entry inside `initContainers` that has its container-level `restartPolicy` set to `Always`. For init containers that exit with an error, the kubelet restarts the init container if the Pod level `restartPolicy` is either `OnFailure` or `Always`. When the kubelet is handling container restarts according to the configured restart policy, that only applies to restarts that make replacement containers inside the same Pod and running on the same node. After containers in a Pod exit, the kubelet restarts them with an exponential back-off delay (10s, 20s,40s, …), that is capped at five minutes. Once a container has executed for 10 minutes without any problems, the kubelet resets the restart backoff timer for that container. [Sidecar containers and Pod lifecycle](/docs/concepts/workloads/pods/sidecar-containers/#sidecar-containers-and-pod-lifecycle) explains the behaviour of `init containers` when specify `restartpolicy` field on it. </ins> ## Pod conditions"}
{"_id":"q-en-website-885c34103cd2a6a6f785dc80e5623f96ae9b4949b387312a645063aca6d6e6ca","text":"border-radius: 3px; } <ins> .td-documentation .td-content > .highlight { max-width: initial; width: 100%; } </ins> body.td-home #deprecation-warning { max-width: 1000px; margin-top: 2.5rem;"}
{"_id":"q-en-website-88e4ea72dc025c64a30ad50736b637d4a535a2e928c8adc17289488a0cdc7dc9","text":"provide the apiserver with a root certificate bundle to use to verify the kubelet's serving certificate. <del> If that is not possible, use [SSH tunneling](/docs/concepts/architecture/master-node-communication/#ssh-tunnels) </del> <ins> If that is not possible, use [SSH tunneling](/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) </ins> between the apiserver and kubelet if required to avoid connecting over an untrusted or public network."}
{"_id":"q-en-website-8911a702e79742685268c8bf616593baba8d39c322d8df429c489973a509d725","text":"We also allow users to customize garbage collection policy through the following kubelet flags: 1. `minimum-container-ttl-duration`, minimum age for a finished container before it is <del> garbage collected. Default is 0 minute, which means any finished container will be garbaged collected. 2. `maximum-dead-containers-per-container`, maximum number of old instances to retain </del> <ins> garbage collected. Default is 0 minute, which means every finished container will be garbaged collected. 2. `maximum-dead-containers-per-container`, maximum number of old instances to be retained </ins> per container. Default is 1. 3. `maximum-dead-containers`, maximum number of old instances of containers to retain globally. Default is -1, which means there is no global limit."}
{"_id":"q-en-website-89a9a3941d941034b680de791468443ee6ca84430a7362c9bb99dee37bbca298","text":"_Nothing has changed._ ### Changed <del> - k8s.io/utils: 0bdb4ca → d5654de </del> <ins> - github.com/google/cadvisor: [v0.38.4 → v0.38.5](https://github.com/google/cadvisor/compare/v0.38.4...v0.38.5) </ins> ### Removed _Nothing has changed._ <del> # v1.19.0-rc.3 </del> <ins> # v1.20.0-beta.2 </ins> <del> ## Downloads for v1.19.0-rc.3 </del> <ins> ## Downloads for v1.20.0-beta.2 </ins> ### Source Code filename | sha512 hash -------- | ----------- <del> [kubernetes.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes.tar.gz) | 31f98fb8d51c6dfa60e2cf710a35af14bc17a6b3833b3802cebc92586b01996c091943087dc818541fc13ad75f051d20c176d9506fc0c86ab582a9295fb7ed59 [kubernetes-src.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-src.tar.gz) | 4886180edf6287adf9db1cdab1e8439c41296c6b5b40af9c4642bb6cfd1fb894313c6d1210c2b882f1bc40dbfd17ed20c5159ea3a8c79ad2ef7a7630016e99de </del> <ins> [kubernetes.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes.tar.gz) | fe769280aa623802a949b6a35fbddadbba1d6f9933a54132a35625683719595ecf58096a9aa0f7456f8d4931774df21bfa98e148bc3d85913f1da915134f77bd [kubernetes-src.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-src.tar.gz) | ce1c8d97c52e5189af335d673bd7e99c564816f6adebf249838f7e3f0e920f323b4e398a5d163ea767091497012ec38843c59ff14e6fdd07683b682135eed645 </ins> ### Client binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-client-darwin-amd64.tar.gz) | 19b0f9fe95e135329ce2cb9dd3e95551f3552be035ce7235e055c9d775dfa747c773b0806b5c2eef1e69863368be13adcb4c5ef78ae05af65483434686e9a773 [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-client-linux-386.tar.gz) | 219a15b54ba616938960ac38869c87be573e3cd7897e4790c31cdeb819415fcefb4f293fc49d63901b42f70e66555c72a8a774cced7ec15a93592dffef3b1336 [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-client-linux-amd64.tar.gz) | 7c5a2163e0e163d3b1819acc7c4475d35b853318dd5a6084ea0785744a92063edf65254b0f0eae0f69f4598561c182033a9722c1b8a61894959333f1357cb1f9 [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-client-linux-arm.tar.gz) | 5d48f78da6a54b63d8ea68e983d780c672b546b4a5d1fb2c15033377dd3098f0011516b55cc47db316dacabdbbd3660108014d12899ef1f4a6a03158ef503101 [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-client-linux-arm64.tar.gz) | c2db09db465f8ea2bd7b82971a59a2be394b2f9a8c15ff78ab06c3a41d9f1292175de19fdc7450cc28746027d59dc3162cb47b64555e91d324d33d699d89f408 [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-client-linux-ppc64le.tar.gz) | f28c9c672bc2c5e780f6fdcf019a5dad7172537e38e2ab7d52a1ea55babb41d296cef97b482133c7fce0634b1aed1b5322d1e0061d30c3848e4c912a7e1ca248 [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-client-linux-s390x.tar.gz) | 22844af3c97eb9f36a038c552e9818b8670cd02acc98defe5c131c7f88621014cd51c343c1e0921b88ebbfd9850a5c277f50df78350f7565db4e356521d415d4 [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-client-windows-386.tar.gz) | edabe78a1337f73caa81c885d722544fec443f875297291e57608d4f486c897af6c602656048a4325fcc957ce1d7acb1c1cf06cab0bd2e36acee1d6be206d3c6 [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-client-windows-amd64.tar.gz) | f1a370b9ec298838e302909dd826760b50b593ee2d2247416d345ff00331973e7b6b29cef69f07d6c1477ab534d6ec9d1bbf5d3c2d1bb9b5b2933e088c8de3f1 </del> <ins> [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-client-darwin-amd64.tar.gz) | d6c14bd0f6702f4bbdf14a6abdfa4e5936de5b4efee38aa86c2bd7272967ec6d7868b88fc00ad4a7c3a20717a35e6be2b84e56dec04154fd702315f641409f7c [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-client-linux-386.tar.gz) | b923c44cb0acb91a8f6fd442c2168aa6166c848f5d037ce50a7cb11502be3698db65836b373c916f75b648d6ac8d9158807a050eecc4e1c77cffa25b386c8cdb [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-client-linux-amd64.tar.gz) | 8cae14146a9034dcd4e9d69d5d700f195a77aac35f629a148960ae028ed8b4fe12213993fe3e6e464b4b3e111adebe6f3dd7ca0accc70c738ed5cfd8993edd7c [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-client-linux-arm.tar.gz) | 1f54e5262a0432945ead57fcb924e6bfedd9ea76db1dd9ebd946787a2923c247cf16e10505307b47e365905a1b398678dac5af0f433c439c158a33e08362d97b [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-client-linux-arm64.tar.gz) | 31cf79c01e4878a231b4881fe3ed5ef790bd5fb5419388438d3f8c6a2129e655aba9e00b8e1d77e0bc5d05ecc75cf4ae02cf8266788822d0306c49c85ee584ed [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-client-linux-ppc64le.tar.gz) | 2527948c40be2e16724d939316ad5363f15aa22ebf42d59359d8b6f757d30cfef6447434cc93bc5caa5a23a6a00a2da8d8191b6441e06bba469d9d4375989a97 [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-client-linux-s390x.tar.gz) | b777ad764b3a46651ecb0846e5b7f860bb2c1c4bd4d0fcc468c6ccffb7d3b8dcb6dcdd73b13c16ded7219f91bba9f1e92f9258527fd3bb162b54d7901ac303ff [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-client-windows-386.tar.gz) | 8a2f58aaab01be9fe298e4d01456536047cbdd39a37d3e325c1f69ceab3a0504998be41a9f41a894735dfc4ed22bed02591eea5f3c75ce12d9e95ba134e72ec5 [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-client-windows-amd64.tar.gz) | 2f69cda177a178df149f5de66b7dba7f5ce14c1ffeb7c8d7dc4130c701b47d89bb2fbe74e7a262f573e4d21dee2c92414d050d7829e7c6fc3637a9d6b0b9c5c1 </ins> ### Server binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-server-linux-amd64.tar.gz) | 193c023306d7478c2e43c4039642649c77598c05b07dbc466611e166f0233a7ea2a7f2ff61763b2630988c151a591f44428942d8ee06ce6766641e1dcfaac588 [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-server-linux-arm.tar.gz) | c1aa489779fb74855385f24120691771a05b57069064c99471b238e5d541d94d4356e7d2cd5b66c284c46bde1fc3eff2a1cebfcd9e72a78377b76e32a1dbf57a [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-server-linux-arm64.tar.gz) | 73400003571f9f0308051ca448b1f96d83e9d211876a57b572ffb787ad0c3bb5f1e20547d959f0fac51a916cf7f26f8839ddddd55d4a38e59c8270d5eb48a970 [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-server-linux-ppc64le.tar.gz) | bebf75d884d024ffebfda40abaa0bfec99a6d4cd3cc0fac904a1c4c190e6eb8fc9412c7790b2f8a2b3cc8ccdf8556d9a93eec37e5c298f8abd62ee41de641a42 [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-server-linux-s390x.tar.gz) | 8374dfb689abae31480814d6849aaa51e30666b7203cdcf204d49c9a0344391232f40d135671ec8316e26d1685e1cbbea4b829ff3b9f83c08c2d1ba50cd5aeb2 </del> <ins> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-server-linux-amd64.tar.gz) | 3ecaac0213d369eab691ac55376821a80df5013cb12e1263f18d1c236a9e49d42b3cea422175556d8f929cdf3109b22c0b6212ac0f2e80cc7a5f4afa3aba5f24 [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-server-linux-arm.tar.gz) | 580030b57ff207e177208fec0801a43389cae10cc2c9306327d354e7be6a055390184531d54b6742e0983550b7a76693cc4a705c2d2f4ac30495cf63cef26b9b [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-server-linux-arm64.tar.gz) | 3e3286bd54671549fbef0dfdaaf1da99bc5c3efb32cc8d1e1985d9926520cea0c43bcf7cbcbbc8b1c1a95eab961255693008af3bb1ba743362998b5f0017d6d7 [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-server-linux-ppc64le.tar.gz) | 9fa051e7e97648e97e26b09ab6d26be247b41b1a5938d2189204c9e6688e455afe76612bbcdd994ed5692935d0d960bd96dc222bce4b83f61d62557752b9d75b [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-server-linux-s390x.tar.gz) | fa85d432eff586f30975c95664ac130b9f5ae02dc52b97613ed7a41324496631ea11d1a267daba564cf2485a9e49707814d86bbd3175486c7efc8b58a9314af5 </ins> ### Node binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-node-linux-amd64.tar.gz) | 194ee29b012463e6d90c346f76d53f94778f75cc916b0e10a5ee174983fac6e848438e0d9e36a475c5d7ba7b0f3ad5debc039ec8f95fdfb6229843f04dfacb53 [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-node-linux-arm.tar.gz) | f0d075eaa84dae7ce2101dfa421021b0bfea235fe606d693e881775cd37ff0b82ca6a419dfe48becd2eddc5f882e97ba838164e6ac5991445225c31f147b4f97 [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-node-linux-arm64.tar.gz) | 3dc69981f31b01a2d8c439f7047f73e5699a121501c516ed17b3e91ed358ee97e43fa955eb9e1434cbf7864e51097e76c216075d34f4b455930a44af6c64be5c [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-node-linux-ppc64le.tar.gz) | 4a77720373960a0cc20bbcfcdfe17f8d5ddaaf2e38bad607cfe05831029e8e14559e78cd0b5b80ab9c9268a04a8b6bd54ad7232c29301a1f6a6392fcd38ecedf [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-node-linux-s390x.tar.gz) | 319e684340aab739e3da46c6407851ff1c42463ba176bf190e58faa48d143975f02df3443ac287cdfcf652b5d6b6e6721d9e4f35995c4e705297a97dd777fe7e [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.3/kubernetes-node-windows-amd64.tar.gz) | 1ff22497a3f0844ffa8593a2a444a8fcb45d0123da49fd58e17cfc1477d22be7f6809d923898b6aa7a9ce519b0a6e0825f575f6cf71da5c8a0fa5f6b4d0905b6 </del> <ins> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-node-linux-amd64.tar.gz) | 86e631f95fe670b467ead2b88d34e0364eaa275935af433d27cc378d82dcaa22041ccce40f5fa9561b9656dadaa578dc018ad458a59b1690d35f86dca4776b5c [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-node-linux-arm.tar.gz) | a8754ff58a0e902397056b8615ab49af07aca347ba7cc4a812c238e3812234862270f25106b6a94753b157bb153b8eae8b39a01ed67384774d798598c243583b [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-node-linux-arm64.tar.gz) | 28d727d7d08e2c856c9b4a574ef2dbf9e37236a0555f7ec5258b4284fa0582fb94b06783aaf50bf661f7503d101fbd70808aba6de02a2f0af94db7d065d25947 [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-node-linux-ppc64le.tar.gz) | a1283449f1a0b155c11449275e9371add544d0bdd4609d6dc737ed5f7dd228e84e24ff249613a2a153691627368dd894ad64f4e6c0010eecc6efd2c13d4fb133 [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-node-linux-s390x.tar.gz) | 5806028ba15a6a9c54a34f90117bc3181428dbb0e7ced30874c9f4a953ea5a0e9b2c73e6b1e2545e1b4e5253e9c7691588538b44cdfa666ce6865964b92d2fa8 [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.2/kubernetes-node-windows-amd64.tar.gz) | d5327e3b7916c78777b9b69ba0f3758c3a8645c67af80114a0ae52babd7af27bb504febbaf51b1bfe5bd2d74c8c5c573471e1cb449f2429453f4b1be9d5e682a ## Changelog since v1.20.0-beta.1 </ins> <del> ## Changelog since v1.19.0-rc.2 </del> <ins> ## Urgent Upgrade Notes ### (No, really, you MUST read this before you upgrade) - A bug was fixed in kubelet where exec probe timeouts were not respected. Ensure that pods relying on this behavior are updated to correctly handle probe timeouts. This change in behavior may be unexpected for some clusters and can be disabled by turning off the ExecProbeTimeout feature gate. This gate will be locked and removed in future releases so that exec probe timeouts are always respected. ([#94115](https://github.com/kubernetes/kubernetes/pull/94115), [@andrewsykim](https://github.com/andrewsykim)) [SIG Node and Testing] - For CSI drivers, kubelet no longer creates the target_path for NodePublishVolume in accordance with the CSI spec. Kubelet also no longer checks if staging and target paths are mounts or corrupted. CSI drivers need to be idempotent and do any necessary mount verification. ([#88759](https://github.com/kubernetes/kubernetes/pull/88759), [@andyzhangx](https://github.com/andyzhangx)) [SIG Storage] - Kubeadm: - The label applied to control-plane nodes \"node-role.kubernetes.io/master\" is now deprecated and will be removed in a future release after a GA deprecation period. - Introduce a new label \"node-role.kubernetes.io/control-plane\" that will be applied in parallel to \"node-role.kubernetes.io/master\" until the removal of the \"node-role.kubernetes.io/master\" label. - Make \"kubeadm upgrade apply\" add the \"node-role.kubernetes.io/control-plane\" label on existing nodes that only have the \"node-role.kubernetes.io/master\" label during upgrade. - Please adapt your tooling built on top of kubeadm to use the \"node-role.kubernetes.io/control-plane\" label. - The taint applied to control-plane nodes \"node-role.kubernetes.io/master:NoSchedule\" is now deprecated and will be removed in a future release after a GA deprecation period. - Apply toleration for a new, future taint \"node-role.kubernetes.io/control-plane:NoSchedule\" to the kubeadm CoreDNS / kube-dns managed manifests. Note that this taint is not yet applied to kubeadm control-plane nodes. - Please adapt your workloads to tolerate the same future taint preemptively. For more details see: http://git.k8s.io/enhancements/keps/sig-cluster-lifecycle/kubeadm/2067-rename-master-label-taint/README.md ([#95382](https://github.com/kubernetes/kubernetes/pull/95382), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] </ins> ## Changes by Kind <ins> ### Deprecation - Docker support in the kubelet is now deprecated and will be removed in a future release. The kubelet uses a module called \"dockershim\" which implements CRI support for Docker and it has seen maintenance issues in the Kubernetes community. We encourage you to evaluate moving to a container runtime that is a full-fledged implementation of CRI (v1alpha1 or v1 compliant) as they become available. ([#94624](https://github.com/kubernetes/kubernetes/pull/94624), [@dims](https://github.com/dims)) [SIG Node] - Kubectl: deprecate --delete-local-data ([#95076](https://github.com/kubernetes/kubernetes/pull/95076), [@dougsland](https://github.com/dougsland)) [SIG CLI, Cloud Provider and Scalability] </ins> ### API Change <del> - Adds the ability to disable Accelerator/GPU metrics collected by Kubelet ([#91930](https://github.com/kubernetes/kubernetes/pull/91930), [@RenaudWasTaken](https://github.com/RenaudWasTaken)) [SIG Node] - Kubernetes is now built with golang 1.15.0-rc.1. - The deprecated, legacy behavior of treating the CommonName field on X.509 serving certificates as a host name when no Subject Alternative Names are present is now disabled by default. It can be temporarily re-enabled by adding the value x509ignoreCN=0 to the GODEBUG environment variable. ([#93264](https://github.com/kubernetes/kubernetes/pull/93264), [@justaugustus](https://github.com/justaugustus)) [SIG API Machinery, Auth, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Network, Node, Release, Scalability, Storage and Testing] </del> <ins> - API priority and fairness graduated to beta 1.19 servers with APF turned on should not be run in a multi-server cluster with 1.20+ servers. ([#96527](https://github.com/kubernetes/kubernetes/pull/96527), [@adtac](https://github.com/adtac)) [SIG API Machinery and Testing] - Add LoadBalancerIPMode feature gate ([#92312](https://github.com/kubernetes/kubernetes/pull/92312), [@Sh4d1](https://github.com/Sh4d1)) [SIG Apps, CLI, Cloud Provider and Network] - Add WindowsContainerResources and Annotations to CRI-API UpdateContainerResourcesRequest ([#95741](https://github.com/kubernetes/kubernetes/pull/95741), [@katiewasnothere](https://github.com/katiewasnothere)) [SIG Node] - Add a 'serving' and `terminating` condition to the EndpointSlice API. `serving` tracks the readiness of endpoints regardless of their terminating state. This is distinct from `ready` since `ready` is only true when pods are not terminating. `terminating` is true when an endpoint is terminating. For pods this is any endpoint with a deletion timestamp. ([#92968](https://github.com/kubernetes/kubernetes/pull/92968), [@andrewsykim](https://github.com/andrewsykim)) [SIG Apps and Network] - Add support for hugepages to downward API ([#86102](https://github.com/kubernetes/kubernetes/pull/86102), [@derekwaynecarr](https://github.com/derekwaynecarr)) [SIG API Machinery, Apps, CLI, Network, Node, Scheduling and Testing] - Adds kubelet alpha feature, `GracefulNodeShutdown` which makes kubelet aware of node system shutdowns and result in graceful termination of pods during a system shutdown. ([#96129](https://github.com/kubernetes/kubernetes/pull/96129), [@bobbypage](https://github.com/bobbypage)) [SIG Node] - AppProtocol is now GA for Endpoints and Services. The ServiceAppProtocol feature gate will be deprecated in 1.21. ([#96327](https://github.com/kubernetes/kubernetes/pull/96327), [@robscott](https://github.com/robscott)) [SIG Apps and Network] - Automatic allocation of NodePorts for services with type LoadBalancer can now be disabled by setting the (new) parameter Service.spec.allocateLoadBalancerNodePorts=false. The default is to allocate NodePorts for services with type LoadBalancer which is the existing behavior. ([#92744](https://github.com/kubernetes/kubernetes/pull/92744), [@uablrek](https://github.com/uablrek)) [SIG Apps and Network] - Document that ServiceTopology feature is required to use `service.spec.topologyKeys`. ([#96528](https://github.com/kubernetes/kubernetes/pull/96528), [@andrewsykim](https://github.com/andrewsykim)) [SIG Apps] - EndpointSlice has a new NodeName field guarded by the EndpointSliceNodeName feature gate. - EndpointSlice topology field will be deprecated in an upcoming release. - EndpointSlice \"IP\" address type is formally removed after being deprecated in Kubernetes 1.17. - The discovery.k8s.io/v1alpha1 API is deprecated and will be removed in Kubernetes 1.21. ([#96440](https://github.com/kubernetes/kubernetes/pull/96440), [@robscott](https://github.com/robscott)) [SIG API Machinery, Apps and Network] - Fewer candidates are enumerated for preemption to improve performance in large clusters ([#94814](https://github.com/kubernetes/kubernetes/pull/94814), [@adtac](https://github.com/adtac)) [SIG Scheduling] - If BoundServiceAccountTokenVolume is enabled, cluster admins can use metric `serviceaccount_stale_tokens_total` to monitor workloads that are depending on the extended tokens. If there are no such workloads, turn off extended tokens by starting `kube-apiserver` with flag `--service-account-extend-token-expiration=false` ([#96273](https://github.com/kubernetes/kubernetes/pull/96273), [@zshihang](https://github.com/zshihang)) [SIG API Machinery and Auth] - Introduce alpha support for exec-based container registry credential provider plugins in the kubelet. ([#94196](https://github.com/kubernetes/kubernetes/pull/94196), [@andrewsykim](https://github.com/andrewsykim)) [SIG Node and Release] - Kube-apiserver now deletes expired kube-apiserver Lease objects: - The feature is under feature gate `APIServerIdentity`. - A flag is added to kube-apiserver: `identity-lease-garbage-collection-check-period-seconds` ([#95895](https://github.com/kubernetes/kubernetes/pull/95895), [@roycaihw](https://github.com/roycaihw)) [SIG API Machinery, Apps, Auth and Testing] - Move configurable fsgroup change policy for pods to beta ([#96376](https://github.com/kubernetes/kubernetes/pull/96376), [@gnufied](https://github.com/gnufied)) [SIG Apps and Storage] - New flag is introduced, i.e. --topology-manager-scope=container|pod. The default value is the \"container\" scope. ([#92967](https://github.com/kubernetes/kubernetes/pull/92967), [@cezaryzukowski](https://github.com/cezaryzukowski)) [SIG Instrumentation, Node and Testing] - NodeAffinity plugin can be configured with AddedAffinity. ([#96202](https://github.com/kubernetes/kubernetes/pull/96202), [@alculquicondor](https://github.com/alculquicondor)) [SIG Node, Scheduling and Testing] - Promote RuntimeClass feature to GA. Promote node.k8s.io API groups from v1beta1 to v1. ([#95718](https://github.com/kubernetes/kubernetes/pull/95718), [@SergeyKanzhelev](https://github.com/SergeyKanzhelev)) [SIG Apps, Auth, Node, Scheduling and Testing] - Reminder: The labels \"failure-domain.beta.kubernetes.io/zone\" and \"failure-domain.beta.kubernetes.io/region\" are deprecated in favor of \"topology.kubernetes.io/zone\" and \"topology.kubernetes.io/region\" respectively.  All users of the \"failure-domain.beta...\" labels should switch to the \"topology...\" equivalents. ([#96033](https://github.com/kubernetes/kubernetes/pull/96033), [@thockin](https://github.com/thockin)) [SIG API Machinery, Apps, CLI, Cloud Provider, Network, Node, Scheduling, Storage and Testing] - The usage of mixed protocol values in the same LoadBalancer Service is possible if the new feature gate MixedProtocolLBSVC is enabled. \"action required\" The feature gate is disabled by default. The user has to enable it for the API Server. ([#94028](https://github.com/kubernetes/kubernetes/pull/94028), [@janosi](https://github.com/janosi)) [SIG API Machinery and Apps] - This PR will introduce a feature gate CSIServiceAccountToken with two additional fields in `CSIDriverSpec`. ([#93130](https://github.com/kubernetes/kubernetes/pull/93130), [@zshihang](https://github.com/zshihang)) [SIG API Machinery, Apps, Auth, CLI, Network, Node, Storage and Testing] - Users can try the cronjob controller v2 using the feature gate. This will be the default controller in future releases. ([#93370](https://github.com/kubernetes/kubernetes/pull/93370), [@alaypatel07](https://github.com/alaypatel07)) [SIG API Machinery, Apps, Auth and Testing] - VolumeSnapshotDataSource moves to GA in 1.20 release ([#95282](https://github.com/kubernetes/kubernetes/pull/95282), [@xing-yang](https://github.com/xing-yang)) [SIG Apps] ### Feature - **Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.**: ([#95896](https://github.com/kubernetes/kubernetes/pull/95896), [@zshihang](https://github.com/zshihang)) [SIG API Machinery and Cluster Lifecycle] - A new set of alpha metrics are reported by the Kubernetes scheduler under the `/metrics/resources` endpoint that allow administrators to easily see the resource consumption (requests and limits for all resources on the pods) and compare it to actual pod usage or node capacity. ([#94866](https://github.com/kubernetes/kubernetes/pull/94866), [@smarterclayton](https://github.com/smarterclayton)) [SIG API Machinery, Instrumentation, Node and Scheduling] - Add --experimental-logging-sanitization flag enabling runtime protection from leaking sensitive data in logs ([#96370](https://github.com/kubernetes/kubernetes/pull/96370), [@serathius](https://github.com/serathius)) [SIG API Machinery, Cluster Lifecycle and Instrumentation] - Add a StorageVersionAPI feature gate that makes API server update storageversions before serving certain write requests. This feature allows the storage migrator to manage storage migration for built-in resources. Enabling internal.apiserver.k8s.io/v1alpha1 API and APIServerIdentity feature gate are required to use this feature. ([#93873](https://github.com/kubernetes/kubernetes/pull/93873), [@roycaihw](https://github.com/roycaihw)) [SIG API Machinery, Auth and Testing] - Add a new `vSphere` metric: `cloudprovider_vsphere_vcenter_versions`. It's content show `vCenter` hostnames with the associated server version. ([#94526](https://github.com/kubernetes/kubernetes/pull/94526), [@Danil-Grigorev](https://github.com/Danil-Grigorev)) [SIG Cloud Provider and Instrumentation] - Add feature to size memory backed volumes ([#94444](https://github.com/kubernetes/kubernetes/pull/94444), [@derekwaynecarr](https://github.com/derekwaynecarr)) [SIG Storage and Testing] - Add node_authorizer_actions_duration_seconds metric that can be used to estimate load to node authorizer. ([#92466](https://github.com/kubernetes/kubernetes/pull/92466), [@mborsz](https://github.com/mborsz)) [SIG API Machinery, Auth and Instrumentation] - Add pod_ based CPU and memory metrics to Kubelet's  /metrics/resource endpoint ([#95839](https://github.com/kubernetes/kubernetes/pull/95839), [@egernst](https://github.com/egernst)) [SIG Instrumentation, Node and Testing] - Adds a headless service on node-local-cache addon. ([#88412](https://github.com/kubernetes/kubernetes/pull/88412), [@stafot](https://github.com/stafot)) [SIG Cloud Provider and Network] - CRDs: For structural schemas, non-nullable null map fields will now be dropped and defaulted if a default is available. null items in list will continue being preserved, and fail validation if not nullable. ([#95423](https://github.com/kubernetes/kubernetes/pull/95423), [@apelisse](https://github.com/apelisse)) [SIG API Machinery] - E2e test for PodFsGroupChangePolicy ([#96247](https://github.com/kubernetes/kubernetes/pull/96247), [@saikat-royc](https://github.com/saikat-royc)) [SIG Storage and Testing] - Gradudate the Pod Resources API to G.A Introduces the pod_resources_endpoint_requests_total metric which tracks the total number of requests to the pod resources API ([#92165](https://github.com/kubernetes/kubernetes/pull/92165), [@RenaudWasTaken](https://github.com/RenaudWasTaken)) [SIG Instrumentation, Node and Testing] - Introduce api-extensions category which will return: mutating admission configs, validating admission configs, CRDs and APIServices when used in kubectl get, for example. ([#95603](https://github.com/kubernetes/kubernetes/pull/95603), [@soltysh](https://github.com/soltysh)) [SIG API Machinery] - Kube-apiserver now maintains a Lease object to identify itself: - The feature is under feature gate `APIServerIdentity`. - Two flags are added to kube-apiserver: `identity-lease-duration-seconds`, `identity-lease-renew-interval-seconds` ([#95533](https://github.com/kubernetes/kubernetes/pull/95533), [@roycaihw](https://github.com/roycaihw)) [SIG API Machinery] - Kube-apiserver: The timeout used when making health check calls to etcd can now be configured with `--etcd-healthcheck-timeout`. The default timeout is 2 seconds, matching the previous behavior. ([#93244](https://github.com/kubernetes/kubernetes/pull/93244), [@Sh4d1](https://github.com/Sh4d1)) [SIG API Machinery] - Kubectl: Previously users cannot provide arguments to a external diff tool via KUBECTL_EXTERNAL_DIFF env. This release now allow users to specify args to KUBECTL_EXTERNAL_DIFF env. ([#95292](https://github.com/kubernetes/kubernetes/pull/95292), [@dougsland](https://github.com/dougsland)) [SIG CLI] - Scheduler now ignores Pod update events if the resourceVersion of old and new Pods are identical. ([#96071](https://github.com/kubernetes/kubernetes/pull/96071), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling] - Support custom tags for cloud provider managed resources ([#96450](https://github.com/kubernetes/kubernetes/pull/96450), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - Support customize load balancer health probe protocol and request path ([#96338](https://github.com/kubernetes/kubernetes/pull/96338), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - Support multiple standard load balancers in one cluster ([#96111](https://github.com/kubernetes/kubernetes/pull/96111), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - The beta `RootCAConfigMap` feature gate is enabled by default and causes kube-controller-manager to publish a \"kube-root-ca.crt\" ConfigMap to every namespace. This ConfigMap contains a CA bundle used for verifying connections to the kube-apiserver. ([#96197](https://github.com/kubernetes/kubernetes/pull/96197), [@zshihang](https://github.com/zshihang)) [SIG API Machinery, Apps, Auth and Testing] - The kubelet_runtime_operations_duration_seconds metric got additional buckets of 60, 300, 600, 900 and 1200 seconds ([#96054](https://github.com/kubernetes/kubernetes/pull/96054), [@alvaroaleman](https://github.com/alvaroaleman)) [SIG Instrumentation and Node] - There is a new pv_collector_total_pv_count metric that counts persistent volumes by the volume plugin name and volume mode. ([#95719](https://github.com/kubernetes/kubernetes/pull/95719), [@tsmetana](https://github.com/tsmetana)) [SIG Apps, Instrumentation, Storage and Testing] - Volume snapshot e2e test to validate PVC and VolumeSnapshotContent finalizer ([#95863](https://github.com/kubernetes/kubernetes/pull/95863), [@RaunakShah](https://github.com/RaunakShah)) [SIG Cloud Provider, Storage and Testing] - Warns user when executing kubectl apply/diff to resource currently being deleted. ([#95544](https://github.com/kubernetes/kubernetes/pull/95544), [@SaiHarshaK](https://github.com/SaiHarshaK)) [SIG CLI] - `kubectl alpha debug` has graduated to beta and is now `kubectl debug`. ([#96138](https://github.com/kubernetes/kubernetes/pull/96138), [@verb](https://github.com/verb)) [SIG CLI and Testing] - `kubectl debug` gains support for changing container images when copying a pod for debugging, similar to how `kubectl set image` works. See `kubectl help debug` for more information. ([#96058](https://github.com/kubernetes/kubernetes/pull/96058), [@verb](https://github.com/verb)) [SIG CLI] ### Documentation - Updates docs and guidance on cloud provider InstancesV2 and Zones interface for external cloud providers: - removes experimental warning for InstancesV2 - document that implementation of InstancesV2 will disable calls to Zones - deprecate Zones in favor of InstancesV2 ([#96397](https://github.com/kubernetes/kubernetes/pull/96397), [@andrewsykim](https://github.com/andrewsykim)) [SIG Cloud Provider] </ins> ### Bug or Regression <del> - Azure: per VMSS VMSS VMs cache to prevent throttling on clusters having many attached VMSS ([#93107](https://github.com/kubernetes/kubernetes/pull/93107), [@bpineau](https://github.com/bpineau)) [SIG Cloud Provider] - Extended DSR loadbalancer feature in winkernel kube-proxy to HNS versions 9.3-9.max, 10.2+ ([#93080](https://github.com/kubernetes/kubernetes/pull/93080), [@elweb9858](https://github.com/elweb9858)) [SIG Network] - Fix instance not found issues when an Azure Node is recreated in a short time ([#93316](https://github.com/kubernetes/kubernetes/pull/93316), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] </del> <ins> - Change plugin name in fsgroupapplymetrics of csi and flexvolume to distinguish different driver ([#95892](https://github.com/kubernetes/kubernetes/pull/95892), [@JornShen](https://github.com/JornShen)) [SIG Instrumentation, Storage and Testing] - Clear UDP conntrack entry on endpoint changes when using nodeport ([#71573](https://github.com/kubernetes/kubernetes/pull/71573), [@JacobTanenbaum](https://github.com/JacobTanenbaum)) [SIG Network] - Exposes and sets a default timeout for the TokenReview client for DelegatingAuthenticationOptions ([#96217](https://github.com/kubernetes/kubernetes/pull/96217), [@p0lyn0mial](https://github.com/p0lyn0mial)) [SIG API Machinery and Cloud Provider] - Fix CVE-2020-8555 for Quobyte client connections. ([#95206](https://github.com/kubernetes/kubernetes/pull/95206), [@misterikkit](https://github.com/misterikkit)) [SIG Storage] - Fix IP fragmentation of UDP and TCP packets not supported issues on LoadBalancer rules ([#96464](https://github.com/kubernetes/kubernetes/pull/96464), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - Fix a bug that DefaultPreemption plugin is disabled when using (legacy) scheduler policy. ([#96439](https://github.com/kubernetes/kubernetes/pull/96439), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling and Testing] - Fix bug in JSON path parser where an error occurs when a range is empty ([#95933](https://github.com/kubernetes/kubernetes/pull/95933), [@brianpursley](https://github.com/brianpursley)) [SIG API Machinery] - Fix client-go prometheus metrics to correctly present the API path accessed in some environments. ([#74363](https://github.com/kubernetes/kubernetes/pull/74363), [@aanm](https://github.com/aanm)) [SIG API Machinery] - Fix memory leak in kube-apiserver when underlying time goes forth and back. ([#96266](https://github.com/kubernetes/kubernetes/pull/96266), [@chenyw1990](https://github.com/chenyw1990)) [SIG API Machinery] - Fix paging issues when Azure API returns empty values with non-empty nextLink ([#96211](https://github.com/kubernetes/kubernetes/pull/96211), [@feiskyer](https://github.com/feiskyer)) [SIG Cloud Provider] - Fix pull image error from multiple ACRs using azure managed identity ([#96355](https://github.com/kubernetes/kubernetes/pull/96355), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix vSphere volumes that could be erroneously attached to wrong node ([#96224](https://github.com/kubernetes/kubernetes/pull/96224), [@gnufied](https://github.com/gnufied)) [SIG Cloud Provider and Storage] - Fixed a bug that prevents kubectl to validate CRDs with schema using x-kubernetes-preserve-unknown-fields on object fields. ([#96369](https://github.com/kubernetes/kubernetes/pull/96369), [@gautierdelorme](https://github.com/gautierdelorme)) [SIG API Machinery and Testing] - For vSphere Cloud Provider, If VM of worker node is deleted, the node will also be deleted by node controller ([#92608](https://github.com/kubernetes/kubernetes/pull/92608), [@lubronzhan](https://github.com/lubronzhan)) [SIG Cloud Provider] - HTTP/2 connection health check is enabled by default in all Kubernetes clients. The feature should work out-of-the-box. If needed, users can tune the feature via the HTTP2_READ_IDLE_TIMEOUT_SECONDS and HTTP2_PING_TIMEOUT_SECONDS environment variables. The feature is disabled if HTTP2_READ_IDLE_TIMEOUT_SECONDS is set to 0. ([#95981](https://github.com/kubernetes/kubernetes/pull/95981), [@caesarxuchao](https://github.com/caesarxuchao)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation and Node] - If the user specifies an invalid timeout in the request URL, the request will be aborted with an HTTP 400. - If the user specifies a timeout in the request URL that exceeds the maximum request deadline allowed by the apiserver, the request will be aborted with an HTTP 400. ([#96061](https://github.com/kubernetes/kubernetes/pull/96061), [@tkashem](https://github.com/tkashem)) [SIG API Machinery, Network and Testing] - Improve error messages related to nodePort endpoint changes conntrack entries cleanup. ([#96251](https://github.com/kubernetes/kubernetes/pull/96251), [@ravens](https://github.com/ravens)) [SIG Network] - Print go stack traces at -v=4 and not -v=2 ([#94663](https://github.com/kubernetes/kubernetes/pull/94663), [@soltysh](https://github.com/soltysh)) [SIG CLI] - Remove ready file and its directory (which is created during volume SetUp) during emptyDir volume TearDown. ([#95770](https://github.com/kubernetes/kubernetes/pull/95770), [@jingxu97](https://github.com/jingxu97)) [SIG Storage] - Resolves non-deterministic behavior of the garbage collection controller when ownerReferences with incorrect data are encountered. Events with a reason of `OwnerRefInvalidNamespace` are recorded when namespace mismatches between child and owner objects are detected. - A namespaced object with an ownerReference referencing a uid of a namespaced kind which does not exist in the same namespace is now consistently treated as though that owner does not exist, and the child object is deleted. - A cluster-scoped object with an ownerReference referencing a uid of a namespaced kind is now consistently treated as though that owner is not resolvable, and the child object is ignored by the garbage collector. ([#92743](https://github.com/kubernetes/kubernetes/pull/92743), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Apps and Testing] - Skip [k8s.io/kubernetes@v1.19.0/test/e2e/storage/testsuites/base.go:162]: Driver azure-disk doesn't support snapshot type DynamicSnapshot -- skipping skip [k8s.io/kubernetes@v1.19.0/test/e2e/storage/testsuites/base.go:185]: Driver azure-disk doesn't support ntfs -- skipping ([#96144](https://github.com/kubernetes/kubernetes/pull/96144), [@qinpingli](https://github.com/qinpingli)) [SIG Storage and Testing] - The AWS network load balancer attributes can now be specified during service creation ([#95247](https://github.com/kubernetes/kubernetes/pull/95247), [@kishorj](https://github.com/kishorj)) [SIG Cloud Provider] - The kube-apiserver will no longer serve APIs that should have been deleted in GA non-alpha levels.  Alpha levels will continue to serve the removed APIs so that CI doesn't immediately break. ([#96525](https://github.com/kubernetes/kubernetes/pull/96525), [@deads2k](https://github.com/deads2k)) [SIG API Machinery] - Update max azure data disk count map ([#96308](https://github.com/kubernetes/kubernetes/pull/96308), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Update the route table tag in the route reconcile loop ([#96545](https://github.com/kubernetes/kubernetes/pull/96545), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - Volume binding: report UnschedulableAndUnresolvable status instead of an error when bound PVs not found ([#95541](https://github.com/kubernetes/kubernetes/pull/95541), [@cofyc](https://github.com/cofyc)) [SIG Apps, Scheduling and Storage] - [kubectl] Fail when local source file doesn't exist ([#90333](https://github.com/kubernetes/kubernetes/pull/90333), [@bamarni](https://github.com/bamarni)) [SIG CLI] ### Other (Cleanup or Flake) - Handle slow cronjob lister in cronjob controller v2 and improve memory footprint. ([#96443](https://github.com/kubernetes/kubernetes/pull/96443), [@alaypatel07](https://github.com/alaypatel07)) [SIG Apps] - --redirect-container-streaming is no longer functional. The flag will be removed in v1.22 ([#95935](https://github.com/kubernetes/kubernetes/pull/95935), [@tallclair](https://github.com/tallclair)) [SIG Node] - A new metric `requestAbortsTotal` has been introduced that counts aborted requests for each `group`, `version`, `verb`, `resource`, `subresource` and `scope`. ([#95002](https://github.com/kubernetes/kubernetes/pull/95002), [@p0lyn0mial](https://github.com/p0lyn0mial)) [SIG API Machinery, Cloud Provider, Instrumentation and Scheduling] - API priority and fairness metrics use snake_case in label names ([#96236](https://github.com/kubernetes/kubernetes/pull/96236), [@adtac](https://github.com/adtac)) [SIG API Machinery, Cluster Lifecycle, Instrumentation and Testing] - Applies translations on all command descriptions ([#95439](https://github.com/kubernetes/kubernetes/pull/95439), [@HerrNaN](https://github.com/HerrNaN)) [SIG CLI] - Changed: default \"Accept-Encoding\" header removed from HTTP probes. See https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#http-probes ([#96127](https://github.com/kubernetes/kubernetes/pull/96127), [@fonsecas72](https://github.com/fonsecas72)) [SIG Network and Node] - Generators for services are removed from kubectl ([#95256](https://github.com/kubernetes/kubernetes/pull/95256), [@Git-Jiro](https://github.com/Git-Jiro)) [SIG CLI] - Introduce kubectl-convert plugin. ([#96190](https://github.com/kubernetes/kubernetes/pull/96190), [@soltysh](https://github.com/soltysh)) [SIG CLI and Testing] - Kube-scheduler now logs processed component config at startup ([#96426](https://github.com/kubernetes/kubernetes/pull/96426), [@damemi](https://github.com/damemi)) [SIG Scheduling] - NONE ([#96179](https://github.com/kubernetes/kubernetes/pull/96179), [@bbyrne5](https://github.com/bbyrne5)) [SIG Network] - Users will now be able to configure all supported values for AWS NLB health check interval and thresholds for new resources. ([#96312](https://github.com/kubernetes/kubernetes/pull/96312), [@kishorj](https://github.com/kishorj)) [SIG Cloud Provider] </ins> ## Dependencies ### Added <del> - github.com/yuin/goldmark: [v1.1.27](https://github.com/yuin/goldmark/tree/v1.1.27) </del> <ins> - cloud.google.com/go/firestore: v1.1.0 - github.com/armon/go-metrics: [f0300d1](https://github.com/armon/go-metrics/tree/f0300d1) - github.com/armon/go-radix: [7fddfc3](https://github.com/armon/go-radix/tree/7fddfc3) - github.com/bketelsen/crypt: [5cbc8cc](https://github.com/bketelsen/crypt/tree/5cbc8cc) - github.com/hashicorp/consul/api: [v1.1.0](https://github.com/hashicorp/consul/api/tree/v1.1.0) - github.com/hashicorp/consul/sdk: [v0.1.1](https://github.com/hashicorp/consul/sdk/tree/v0.1.1) - github.com/hashicorp/errwrap: [v1.0.0](https://github.com/hashicorp/errwrap/tree/v1.0.0) - github.com/hashicorp/go-cleanhttp: [v0.5.1](https://github.com/hashicorp/go-cleanhttp/tree/v0.5.1) - github.com/hashicorp/go-immutable-radix: [v1.0.0](https://github.com/hashicorp/go-immutable-radix/tree/v1.0.0) - github.com/hashicorp/go-msgpack: [v0.5.3](https://github.com/hashicorp/go-msgpack/tree/v0.5.3) - github.com/hashicorp/go-multierror: [v1.0.0](https://github.com/hashicorp/go-multierror/tree/v1.0.0) - github.com/hashicorp/go-rootcerts: [v1.0.0](https://github.com/hashicorp/go-rootcerts/tree/v1.0.0) - github.com/hashicorp/go-sockaddr: [v1.0.0](https://github.com/hashicorp/go-sockaddr/tree/v1.0.0) - github.com/hashicorp/go-uuid: [v1.0.1](https://github.com/hashicorp/go-uuid/tree/v1.0.1) - github.com/hashicorp/go.net: [v0.0.1](https://github.com/hashicorp/go.net/tree/v0.0.1) - github.com/hashicorp/logutils: [v1.0.0](https://github.com/hashicorp/logutils/tree/v1.0.0) - github.com/hashicorp/mdns: [v1.0.0](https://github.com/hashicorp/mdns/tree/v1.0.0) - github.com/hashicorp/memberlist: [v0.1.3](https://github.com/hashicorp/memberlist/tree/v0.1.3) - github.com/hashicorp/serf: [v0.8.2](https://github.com/hashicorp/serf/tree/v0.8.2) - github.com/mitchellh/cli: [v1.0.0](https://github.com/mitchellh/cli/tree/v1.0.0) - github.com/mitchellh/go-testing-interface: [v1.0.0](https://github.com/mitchellh/go-testing-interface/tree/v1.0.0) - github.com/mitchellh/gox: [v0.4.0](https://github.com/mitchellh/gox/tree/v0.4.0) - github.com/mitchellh/iochan: [v1.0.0](https://github.com/mitchellh/iochan/tree/v1.0.0) - github.com/pascaldekloe/goe: [57f6aae](https://github.com/pascaldekloe/goe/tree/57f6aae) - github.com/posener/complete: [v1.1.1](https://github.com/posener/complete/tree/v1.1.1) - github.com/ryanuber/columnize: [9b3edd6](https://github.com/ryanuber/columnize/tree/9b3edd6) - github.com/sean-/seed: [e2103e2](https://github.com/sean-/seed/tree/e2103e2) - github.com/subosito/gotenv: [v1.2.0](https://github.com/subosito/gotenv/tree/v1.2.0) - github.com/willf/bitset: [d5bec33](https://github.com/willf/bitset/tree/d5bec33) - gopkg.in/ini.v1: v1.51.0 - gopkg.in/yaml.v3: 9f266ea - rsc.io/quote/v3: v3.1.0 - rsc.io/sampler: v1.3.0 </ins> ### Changed <del> - github.com/Microsoft/hcsshim: [v0.8.9 → 5eafd15](https://github.com/Microsoft/hcsshim/compare/v0.8.9...5eafd15) - github.com/containerd/cgroups: [bf292b2 → 0dbf7f0](https://github.com/containerd/cgroups/compare/bf292b2...0dbf7f0) - github.com/urfave/cli: [v1.22.1 → v1.22.2](https://github.com/urfave/cli/compare/v1.22.1...v1.22.2) - golang.org/x/crypto: bac4c82 → 75b2880 - golang.org/x/mod: v0.1.0 → v0.3.0 - golang.org/x/net: d3edc99 → ab34263 - golang.org/x/tools: c00d67e → c1934b7 </del> <ins> - cloud.google.com/go/bigquery: v1.0.1 → v1.4.0 - cloud.google.com/go/datastore: v1.0.0 → v1.1.0 - cloud.google.com/go/pubsub: v1.0.1 → v1.2.0 - cloud.google.com/go/storage: v1.0.0 → v1.6.0 - cloud.google.com/go: v0.51.0 → v0.54.0 - github.com/Microsoft/go-winio: [fc70bd9 → v0.4.15](https://github.com/Microsoft/go-winio/compare/fc70bd9...v0.4.15) - github.com/aws/aws-sdk-go: [v1.35.5 → v1.35.24](https://github.com/aws/aws-sdk-go/compare/v1.35.5...v1.35.24) - github.com/blang/semver: [v3.5.0+incompatible → v3.5.1+incompatible](https://github.com/blang/semver/compare/v3.5.0...v3.5.1) - github.com/checkpoint-restore/go-criu/v4: [v4.0.2 → v4.1.0](https://github.com/checkpoint-restore/go-criu/v4/compare/v4.0.2...v4.1.0) - github.com/containerd/containerd: [v1.3.3 → v1.4.1](https://github.com/containerd/containerd/compare/v1.3.3...v1.4.1) - github.com/containerd/ttrpc: [v1.0.0 → v1.0.2](https://github.com/containerd/ttrpc/compare/v1.0.0...v1.0.2) - github.com/containerd/typeurl: [v1.0.0 → v1.0.1](https://github.com/containerd/typeurl/compare/v1.0.0...v1.0.1) - github.com/coreos/etcd: [v3.3.10+incompatible → v3.3.13+incompatible](https://github.com/coreos/etcd/compare/v3.3.10...v3.3.13) - github.com/docker/docker: [aa6a989 → bd33bbf](https://github.com/docker/docker/compare/aa6a989...bd33bbf) - github.com/go-gl/glfw/v3.3/glfw: [12ad95a → 6f7a984](https://github.com/go-gl/glfw/v3.3/glfw/compare/12ad95a...6f7a984) - github.com/golang/groupcache: [215e871 → 8c9f03a](https://github.com/golang/groupcache/compare/215e871...8c9f03a) - github.com/golang/mock: [v1.3.1 → v1.4.1](https://github.com/golang/mock/compare/v1.3.1...v1.4.1) - github.com/golang/protobuf: [v1.4.2 → v1.4.3](https://github.com/golang/protobuf/compare/v1.4.2...v1.4.3) - github.com/google/cadvisor: [v0.37.0 → v0.38.4](https://github.com/google/cadvisor/compare/v0.37.0...v0.38.4) - github.com/google/go-cmp: [v0.4.0 → v0.5.2](https://github.com/google/go-cmp/compare/v0.4.0...v0.5.2) - github.com/google/pprof: [d4f498a → 1ebb73c](https://github.com/google/pprof/compare/d4f498a...1ebb73c) - github.com/google/uuid: [v1.1.1 → v1.1.2](https://github.com/google/uuid/compare/v1.1.1...v1.1.2) - github.com/gorilla/mux: [v1.7.3 → v1.8.0](https://github.com/gorilla/mux/compare/v1.7.3...v1.8.0) - github.com/gorilla/websocket: [v1.4.0 → v1.4.2](https://github.com/gorilla/websocket/compare/v1.4.0...v1.4.2) - github.com/karrick/godirwalk: [v1.7.5 → v1.16.1](https://github.com/karrick/godirwalk/compare/v1.7.5...v1.16.1) - github.com/opencontainers/runc: [819fcc6 → v1.0.0-rc92](https://github.com/opencontainers/runc/compare/819fcc6...v1.0.0-rc92) - github.com/opencontainers/runtime-spec: [237cc4f → 4d89ac9](https://github.com/opencontainers/runtime-spec/compare/237cc4f...4d89ac9) - github.com/opencontainers/selinux: [v1.5.2 → v1.6.0](https://github.com/opencontainers/selinux/compare/v1.5.2...v1.6.0) - github.com/prometheus/procfs: [v0.1.3 → v0.2.0](https://github.com/prometheus/procfs/compare/v0.1.3...v0.2.0) - github.com/quobyte/api: [v0.1.2 → v0.1.8](https://github.com/quobyte/api/compare/v0.1.2...v0.1.8) - github.com/spf13/cobra: [v1.0.0 → v1.1.1](https://github.com/spf13/cobra/compare/v1.0.0...v1.1.1) - github.com/spf13/viper: [v1.4.0 → v1.7.0](https://github.com/spf13/viper/compare/v1.4.0...v1.7.0) - github.com/stretchr/testify: [v1.4.0 → v1.6.1](https://github.com/stretchr/testify/compare/v1.4.0...v1.6.1) - github.com/vishvananda/netns: [52d707b → db3c7e5](https://github.com/vishvananda/netns/compare/52d707b...db3c7e5) - go.opencensus.io: v0.22.2 → v0.22.3 - golang.org/x/exp: da58074 → 6cc2880 - golang.org/x/lint: fdd1cda → 738671d - golang.org/x/net: ab34263 → 69a7880 - golang.org/x/oauth2: 858c2ad → bf48bf1 - golang.org/x/sys: ed371f2 → 5cba982 - golang.org/x/text: v0.3.3 → v0.3.4 - golang.org/x/time: 555d28b → 3af7569 - golang.org/x/xerrors: 9bdfabe → 5ec99f8 - google.golang.org/api: v0.15.1 → v0.20.0 - google.golang.org/genproto: cb27e3a → 8816d57 - google.golang.org/grpc: v1.27.0 → v1.27.1 - google.golang.org/protobuf: v1.24.0 → v1.25.0 - honnef.co/go/tools: v0.0.1-2019.2.3 → v0.0.1-2020.1.3 - k8s.io/gengo: 8167cfd → 83324d8 - k8s.io/klog/v2: v2.2.0 → v2.4.0 - k8s.io/kube-openapi: 8b50664 → d219536 - k8s.io/utils: d5654de → 67b214c - sigs.k8s.io/apiserver-network-proxy/konnectivity-client: v0.0.12 → v0.0.14 - sigs.k8s.io/structured-merge-diff/v4: b3cf1e8 → v4.0.2 </ins> ### Removed <del> - github.com/godbus/dbus: [ade71ed](https://github.com/godbus/dbus/tree/ade71ed) </del> <ins> - github.com/armon/consul-api: [eb2c6b5](https://github.com/armon/consul-api/tree/eb2c6b5) - github.com/go-ini/ini: [v1.9.0](https://github.com/go-ini/ini/tree/v1.9.0) - github.com/ugorji/go: [v1.1.4](https://github.com/ugorji/go/tree/v1.1.4) - github.com/xordataexchange/crypt: [b2862e3](https://github.com/xordataexchange/crypt/tree/b2862e3) </ins> <del> # v1.19.0-rc.2 </del> <ins> # v1.20.0-beta.1 </ins> <del> ## Downloads for v1.19.0-rc.2 </del> <ins> ## Downloads for v1.20.0-beta.1 </ins> ### Source Code filename | sha512 hash -------- | ----------- <del> [kubernetes.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes.tar.gz) | 7a9fa6af3772be18f8c427d8b96836bd77e271a08fffeba92d01b3fac4bd69d2be1bbc404cdd4fc259dda42b16790a7943eddb7c889b918d7631857e127a724c [kubernetes-src.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-src.tar.gz) | 60184627a181ac99cd914acb0ba61c22f31b315ef13be5504f3cb43dea1fa84abb2142c8a1ba9e98e037e0d9d2765e8d85bd12903b03a86538d7638ceb6ac5c9 </del> <ins> [kubernetes.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes.tar.gz) | 4eddf4850c2d57751696f352d0667309339090aeb30ff93e8db8a22c6cdebf74cb2d5dc78d4ae384c4e25491efc39413e2e420a804b76b421a9ad934e56b0667 [kubernetes-src.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-src.tar.gz) | 59de5221162e9b6d88f5abbdb99765cb2b2e501498ea853fb65f2abe390211e28d9f21e0d87be3ade550a5ea6395d04552cf093d2ce2f99fd45ad46545dd13cb </ins> ### Client binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-client-darwin-386.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-client-darwin-386.tar.gz) | 03332cd70ce6a9c8e533d93d694da32b549bef486cf73c649bcb1c85fc314b0ac0f95e035de7b54c81112c1ac39029abeb8f246d359384bde2119ea5ea3ebe66 [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-client-darwin-amd64.tar.gz) | e82c2908366cc27cbc1d72f89fdc13414b484dfdf26c39c6180bf2e5734169cc97d77a2d1ac051cdb153582a38f4805e5c5b5b8eb88022c914ffb4ef2a8202d3 [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-client-linux-386.tar.gz) | 948be72e8162ee109c670a88c443ba0907acfd0ffb64df62afe41762717bc2fb9308cbc4eb2012a14e0203197e8576e3700ad9f105379841d46acafad2a4c6dc [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-client-linux-amd64.tar.gz) | 54e1980b6967dab1e70be2b4df0cd0171f04c92f12dcdf80908b087facb9d5cc1399a7d9455a4a799daa8e9d48b6ad86cb3666a131e5adfcd36b008d25138fa3 [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-client-linux-arm.tar.gz) | 4edcd2e1a866a16b8b0f6228f93b4a61cdd43dca36dcb53a5dbd865cc5a143ef6fd3b8575925acc8af17cff21dee993df9b88db5724320e7b420ca9d0427677f [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-client-linux-arm64.tar.gz) | 138b215e35cfb5d05bda766763e92352171e018a090d516dbf0c280588c5e6f36228163a75a8147c7bac46e773ad0353daaf550d8fa0e91b1e05c5bc0242531c [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-client-linux-ppc64le.tar.gz) | 3b8e7f5f1f2e34df5dbb06c12f07f660a2a732846c56d0f4b0a939b8121361d381325565bdda3182ef8951f4c2513a2c255940f97011034063ffb506d5aedeab [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-client-linux-s390x.tar.gz) | b695cc0695bd324c51084e64bea113aaad3c0b5ba44b5d122db9da6e359a4108008a80944cbe96c405bd2cf57f5f31b3eaf50f33c23d980bdb9f272937c88d1c [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-client-windows-386.tar.gz) | 8e370a66545cdebe0ae0816afe361c7579c7c6e8ee5652e4e01c6fcc3d6d2a6557101be39be24ceb14302fb30855730894a17f6ae11586759257f12406c653e2 [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-client-windows-amd64.tar.gz) | 89e0fe5aac33c991891b08e5a3891ecbda3e038f0ee6a5cdd771ea294ec84292bd5f65f1a895f23e6892ec28f001f66d0166d204bf135cb1aa467ae56ccc1260 </del> <ins> [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-client-darwin-amd64.tar.gz) | d69ffed19b034a4221fc084e43ac293cf392e98febf5bf580f8d92307a8421d8b3aab18f9ca70608937e836b42c7a34e829f88eba6e040218a4486986e2fca21 [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-client-linux-386.tar.gz) | 1b542e165860c4adcd4550adc19b86c3db8cd75d2a1b8db17becc752da78b730ee48f1b0aaf8068d7bfbb1d8e023741ec293543bc3dd0f4037172a6917db8169 [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-client-linux-amd64.tar.gz) | 90ad52785eecb43a6f9035b92b6ba39fc84e67f8bc91cf098e70f8cfdd405c4b9d5c02dccb21022f21bb5b6ce92fdef304def1da0a7255c308e2c5fb3a9cdaab [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-client-linux-arm.tar.gz) | d0cb3322b056e1821679afa70728ffc0d3375e8f3326dabbe8185be2e60f665ab8985b13a1a432e10281b84a929e0f036960253ac0dd6e0b44677d539e98e61b [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-client-linux-arm64.tar.gz) | 3aecc8197e0aa368408624add28a2dd5e73f0d8a48e5e33c19edf91d5323071d16a27353a6f3e22df4f66ed7bfbae8e56e0a9050f7bbdf927ce6aeb29bba6374 [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-client-linux-ppc64le.tar.gz) | 6ff145058f62d478b98f1e418e272555bfb5c7861834fbbf10a8fb334cc7ff09b32f2666a54b230932ba71d2fc7d3b1c1f5e99e6fe6d6ec83926a9b931cd2474 [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-client-linux-s390x.tar.gz) | ff7b8bb894076e05a3524f6327a4a6353b990466f3292e84c92826cb64b5c82b3855f48b8e297ccadc8bcc15552bc056419ff6ff8725fc4e640828af9cc1331b [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-client-windows-386.tar.gz) | 6c6dcac9c725605763a130b5a975f2b560aa976a5c809d4e0887900701b707baccb9ca1aebc10a03cfa7338a6f42922bbf838ccf6800fc2a3e231686a72568b6 [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-client-windows-amd64.tar.gz) | d12e3a29c960f0ddd1b9aabf5426ac1259863ac6c8f2be1736ebeb57ddca6b1c747ee2c363be19e059e38cf71488c5ea3509ad4d0e67fd5087282a5ad0ae9a48 </ins> ### Server binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-server-linux-amd64.tar.gz) | 2b0a1b107bf31913d9deec57eab9d3db2ea512c995ce3b4fe247f91c36fdebcc4484a2f8ff53d40a5bc6a04c7144827b85b40ac90c46a9b0cec8a680700f1b1c [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-server-linux-arm.tar.gz) | 2f1ab3bcacd82a9b6d92e09b7cdd63f57fc44623cdfb517512b634264fed87999d78b8571c7930839381b1ed4793b68343e85956d7a8c5bae77ba8f8ade06afa [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-server-linux-arm64.tar.gz) | ea67613c8356f650891a096881546afb27f00e86a9c777617817583628d38b4725f0f65da3b0732414cbc8f97316b3029a355177342a4b1d94cf02d79542e4cd [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-server-linux-ppc64le.tar.gz) | d1b151f3f47c28ead2304d2477fa25f24d12e3fd80e9d1b3b593db99b9a1c5821db4d089f4f1dd041796ea3fd814000c225a7e75aac1e5891a4e16517bcaceee [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-server-linux-s390x.tar.gz) | 69bf215fdc3ad53834eaa9a918452feb0803dffe381b6e03b73141364a697a576e5ed0242d448616707cb386190c21564fe89f8cf3409a7c621a86d86b2c7680 </del> <ins> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-server-linux-amd64.tar.gz) | 904e8c049179e071c6caa65f525f465260bb4d4318a6dd9cc05be2172f39f7cfc69d1672736e01d926045764fe8872e806444e3af77ffef823ede769537b7d20 [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-server-linux-arm.tar.gz) | 5934959374868aed8d4294de84411972660bca7b2e952201a9403f37e40c60a5c53eaea8001344d0bf4a00c8cd27de6324d88161388de27f263a5761357cb82b [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-server-linux-arm64.tar.gz) | 4c884585970f80dc5462d9a734d7d5be9558b36c6e326a8a3139423efbd7284fa9f53fb077983647e17e19f03f5cb9bf26201450c78daecf10afa5a1ab5f9efc [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-server-linux-ppc64le.tar.gz) | 235b78b08440350dcb9f13b63f7722bd090c672d8e724ca5d409256e5a5d4f46d431652a1aa908c3affc5b1e162318471de443d38b93286113e79e7f90501a9b [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-server-linux-s390x.tar.gz) | 220fc9351702b3ecdcf79089892ceb26753a8a1deaf46922ffb3d3b62b999c93fef89440e779ca6043372b963081891b3a966d1a5df0cf261bdd44395fd28dce </ins> ### Node binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-node-linux-amd64.tar.gz) | 88ae137316bab3bb1dcb6c78a4d725face618d41714400505b97ce9d3fa37a6caa036b9e8508ade6dd679e3a8c483a32aef9e400ab08d86b6bf39bc13f34e435 [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-node-linux-arm.tar.gz) | 7eaaf2a2a4ee5181cb4c1567e99b8bf82a3da342799f5d2b34dd7f133313c3e3d2ac5a778110e178161788cb226bd64836fba35fbec21c8384e7725cae9b756c [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-node-linux-arm64.tar.gz) | 4f0ef95abc52da0e5d0c40434f8c324ddfb218a577114c4ead00f2ac1c01439922aee6fe347f702927a73b0166cd8b9f4c491d3a18a1a951d24c9ea7259d2655 [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-node-linux-ppc64le.tar.gz) | 0424896e2fedae3a566a5aa2e4af26977a578066d49e3ad66307839c2d2dd1c53d1afcf16b2f6cebf0c74d2d60dbc118e6446d9c02aaab27e95b3a6d26889f51 [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-node-linux-s390x.tar.gz) | 294788687a6e6d1ca2e4d56435b1174e4330abe64cc58b1372c3b9caaab4455586da4e3bfc62616b52ea7d678561fb77ce1f8d0023fd7d1e75e1db348c69939c [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.2/kubernetes-node-windows-amd64.tar.gz) | 61389f8c05c682102e3432a2f05f41b11d531124f61443429627f94ef6e970d44240d44d32aa467b814de0b54a17208b2d2696602ba5dd6d30f64db964900230 </del> <ins> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-node-linux-amd64.tar.gz) | fe59d3a1f21c47bab126f689687657f77fbcb46a2caeef48eecd073b2b22879f997a466911b5c5c829e9cf27e68a36ecdf18686d42714839d4b97d6c7281578d [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-node-linux-arm.tar.gz) | 93e545aa963cfd11e0b2c6d47669b5ef70c5a86ef80c3353c1a074396bff1e8e7371dda25c39d78c7a9e761f2607b8b5ab843fa0c10b8ff9663098fae8d25725 [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-node-linux-arm64.tar.gz) | 5e0f177f9bec406a668d4b37e69b191208551fdf289c82b5ec898959da4f8a00a2b0695cbf1d2de5acb809321c6e5604f5483d33556543d92b96dcf80e814dd3 [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-node-linux-ppc64le.tar.gz) | 574412059e4d257eb904cd4892a075b6a2cde27adfa4976ee64c46d6768facece338475f1b652ad94c8df7cfcbb70ebdf0113be109c7099ab76ffdb6f023eefd [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-node-linux-s390x.tar.gz) | b1ffaa6d7f77d89885c642663cb14a86f3e2ec2afd223e3bb2000962758cf0f15320969ffc4be93b5826ff22d54fdbae0dbea09f9d8228eda6da50b6fdc88758 [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.1/kubernetes-node-windows-amd64.tar.gz) | 388983765213cf3bdc1f8b27103ed79e39028767e5f1571e35ed1f91ed100e49f3027f7b7ff19b53fab7fbb6d723c0439f21fc6ed62be64532c25f5bfa7ee265 </ins> <del> ## Changelog since v1.19.0-rc.1 </del> <ins> ## Changelog since v1.20.0-beta.0 </ins> ## Changes by Kind <ins> ### Deprecation - ACTION REQUIRED: The kube-apiserver ability to serve on an insecure port, deprecated since v1.10, has been removed. The insecure address flags `--address` and `--insecure-bind-address` have no effect in kube-apiserver and will be removed in v1.24. The insecure port flags `--port` and `--insecure-port` may only be set to 0 and will be removed in v1.24. ([#95856](https://github.com/kubernetes/kubernetes/pull/95856), [@knight42](https://github.com/knight42)) [SIG API Machinery, Node and Testing] </ins> ### API Change <del> - A new alpha-level field, `SupportsFsGroup`, has been introduced for CSIDrivers to allow them to specify whether they support volume ownership and permission modifications. The `CSIVolumeSupportFSGroup` feature gate must be enabled to allow this field to be used. ([#92001](https://github.com/kubernetes/kubernetes/pull/92001), [@huffmanca](https://github.com/huffmanca)) [SIG API Machinery, CLI and Storage] - The kube-controller-manager managed signers can now have distinct signing certificates and keys.  See the help about `--cluster-signing-[signer-name]-{cert,key}-file`.  `--cluster-signing-{cert,key}-file` is still the default. ([#90822](https://github.com/kubernetes/kubernetes/pull/90822), [@deads2k](https://github.com/deads2k)) [SIG API Machinery, Apps and Auth] </del> <ins> - + `TokenRequest` and `TokenRequestProjection` features have been promoted to GA. This feature allows generating service account tokens that are not visible in Secret objects and are tied to the lifetime of a Pod object. See https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#service-account-token-volume-projection for details on configuring and using this feature. The `TokenRequest` and `TokenRequestProjection` feature gates will be removed in v1.21. + kubeadm's kube-apiserver Pod manifest now includes the following flags by default \"--service-account-key-file\", \"--service-account-signing-key-file\", \"--service-account-issuer\". ([#93258](https://github.com/kubernetes/kubernetes/pull/93258), [@zshihang](https://github.com/zshihang)) [SIG API Machinery, Auth, Cluster Lifecycle, Storage and Testing] - Certain fields on  Service objects will be automatically cleared when changing the service's `type` to a mode that does not need those fields.  For example, changing from type=LoadBalancer to type=ClusterIP will clear the NodePort assignments, rather than forcing the user to clear them. ([#95196](https://github.com/kubernetes/kubernetes/pull/95196), [@thockin](https://github.com/thockin)) [SIG API Machinery, Apps, Network and Testing] - Services will now have a `clusterIPs` field to go with `clusterIP`.  `clusterIPs[0]` is a synonym for `clusterIP` and will be syncronized on create and update operations. ([#95894](https://github.com/kubernetes/kubernetes/pull/95894), [@thockin](https://github.com/thockin)) [SIG Network] </ins> ### Feature <del> - Added kube-apiserver metrics: apiserver_current_inflight_request_measures and, when API Priority and Fairness is enable, windowed_request_stats. ([#91177](https://github.com/kubernetes/kubernetes/pull/91177), [@MikeSpreitzer](https://github.com/MikeSpreitzer)) [SIG API Machinery, Instrumentation and Testing] - Rename pod_preemption_metrics to preemption_metrics. ([#93256](https://github.com/kubernetes/kubernetes/pull/93256), [@ahg-g](https://github.com/ahg-g)) [SIG Instrumentation and Scheduling] </del> <ins> - A new metric `apiserver_request_filter_duration_seconds` has been introduced that measures request filter latency in seconds. ([#95207](https://github.com/kubernetes/kubernetes/pull/95207), [@tkashem](https://github.com/tkashem)) [SIG API Machinery and Instrumentation] - Add a new flag to set priority for the kubelet on Windows nodes so that workloads cannot overwhelm the node there by disrupting kubelet process. ([#96051](https://github.com/kubernetes/kubernetes/pull/96051), [@ravisantoshgudimetla](https://github.com/ravisantoshgudimetla)) [SIG Node and Windows] - Changed: default \"Accept: */*\" header added to HTTP probes. See https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#http-probes (https://github.com/kubernetes/website/pull/24756) ([#95641](https://github.com/kubernetes/kubernetes/pull/95641), [@fonsecas72](https://github.com/fonsecas72)) [SIG Network and Node] - Client-go credential plugins can now be passed in the current cluster information via the KUBERNETES_EXEC_INFO environment variable. ([#95489](https://github.com/kubernetes/kubernetes/pull/95489), [@ankeesler](https://github.com/ankeesler)) [SIG API Machinery and Auth] - Kube-apiserver: added support for compressing rotated audit log files with `--audit-log-compress` ([#94066](https://github.com/kubernetes/kubernetes/pull/94066), [@lojies](https://github.com/lojies)) [SIG API Machinery and Auth] ### Documentation - Fake dynamic client: document that List does not preserve TypeMeta in UnstructuredList ([#95117](https://github.com/kubernetes/kubernetes/pull/95117), [@andrewsykim](https://github.com/andrewsykim)) [SIG API Machinery] </ins> ### Bug or Regression <del> - Do not add nodes labeled with kubernetes.azure.com/managed=false to backend pool of load balancer. ([#93034](https://github.com/kubernetes/kubernetes/pull/93034), [@matthias50](https://github.com/matthias50)) [SIG Cloud Provider] - Do not retry volume expansion if CSI driver returns FailedPrecondition error ([#92986](https://github.com/kubernetes/kubernetes/pull/92986), [@gnufied](https://github.com/gnufied)) [SIG Node and Storage] - Fix: determine the correct ip config based on ip family ([#93043](https://github.com/kubernetes/kubernetes/pull/93043), [@aramase](https://github.com/aramase)) [SIG Cloud Provider] - Fix: initial delay in mounting azure disk & file ([#93052](https://github.com/kubernetes/kubernetes/pull/93052), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Fixed the EndpointSliceController to correctly create endpoints for IPv6-only pods. Fixed the EndpointController to allow IPv6 headless services, if the IPv6DualStack feature gate is enabled, by specifying `ipFamily: IPv6` on the service. (This already worked with the EndpointSliceController.) ([#91399](https://github.com/kubernetes/kubernetes/pull/91399), [@danwinship](https://github.com/danwinship)) [SIG Apps and Network] </del> <ins> - Added support to kube-proxy for externalTrafficPolicy=Local setting via Direct Server Return (DSR) load balancers on Windows. ([#93166](https://github.com/kubernetes/kubernetes/pull/93166), [@elweb9858](https://github.com/elweb9858)) [SIG Network] - Disable watchcache for events ([#96052](https://github.com/kubernetes/kubernetes/pull/96052), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery] - Disabled `LocalStorageCapacityIsolation` feature gate is honored during scheduling. ([#96092](https://github.com/kubernetes/kubernetes/pull/96092), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling] - Fix bug in JSON path parser where an error occurs when a range is empty ([#95933](https://github.com/kubernetes/kubernetes/pull/95933), [@brianpursley](https://github.com/brianpursley)) [SIG API Machinery] - Fix k8s.io/apimachinery/pkg/api/meta.SetStatusCondition to update ObservedGeneration ([#95961](https://github.com/kubernetes/kubernetes/pull/95961), [@KnicKnic](https://github.com/KnicKnic)) [SIG API Machinery] - Fixed a regression which prevented pods with `docker/default` seccomp annotations from being created in 1.19 if a PodSecurityPolicy was in place which did not allow `runtime/default` seccomp profiles. ([#95985](https://github.com/kubernetes/kubernetes/pull/95985), [@saschagrunert](https://github.com/saschagrunert)) [SIG Auth] - Kubectl: print error if users place flags before plugin name ([#92343](https://github.com/kubernetes/kubernetes/pull/92343), [@knight42](https://github.com/knight42)) [SIG CLI] - When creating a PVC with the volume.beta.kubernetes.io/storage-provisioner annotation already set, the PV controller might have incorrectly deleted the newly provisioned PV instead of binding it to the PVC, depending on timing and system load. ([#95909](https://github.com/kubernetes/kubernetes/pull/95909), [@pohly](https://github.com/pohly)) [SIG Apps and Storage] </ins> ### Other (Cleanup or Flake) <del> - Kube-up: defaults to limiting critical pods to the kube-system namespace to match behavior prior to 1.17 ([#93121](https://github.com/kubernetes/kubernetes/pull/93121), [@liggitt](https://github.com/liggitt)) [SIG Cloud Provider and Scheduling] - Update Golang to v1.14.5 - Update repo-infra to 0.0.7 (to support go1.14.5 and go1.13.13) - Includes: - bazelbuild/bazel-toolchains@3.3.2 - bazelbuild/rules_go@v0.22.7 ([#93088](https://github.com/kubernetes/kubernetes/pull/93088), [@justaugustus](https://github.com/justaugustus)) [SIG Release and Testing] - Update Golang to v1.14.6 - Update repo-infra to 0.0.8 (to support go1.14.6 and go1.13.14) - Includes: - bazelbuild/bazel-toolchains@3.4.0 - bazelbuild/rules_go@v0.22.8 ([#93198](https://github.com/kubernetes/kubernetes/pull/93198), [@justaugustus](https://github.com/justaugustus)) [SIG Release and Testing] - Update default etcd server version to 3.4.9 ([#92349](https://github.com/kubernetes/kubernetes/pull/92349), [@jingyih](https://github.com/jingyih)) [SIG API Machinery, Cloud Provider, Cluster Lifecycle and Testing] </del> <ins> - Kubectl: the `generator` flag of `kubectl autoscale` has been deprecated and has no effect, it will be removed in a feature release ([#92998](https://github.com/kubernetes/kubernetes/pull/92998), [@SataQiu](https://github.com/SataQiu)) [SIG CLI] - V1helpers.MatchNodeSelectorTerms now accepts just a Node and a list of Terms ([#95871](https://github.com/kubernetes/kubernetes/pull/95871), [@damemi](https://github.com/damemi)) [SIG Apps, Scheduling and Storage] - `MatchNodeSelectorTerms` function moved to `k8s.io/component-helpers` ([#95531](https://github.com/kubernetes/kubernetes/pull/95531), [@damemi](https://github.com/damemi)) [SIG Apps, Scheduling and Storage] </ins> ## Dependencies"}
{"_id":"q-en-website-8ac324770b4b9ffa82dcda8517b8c5bcd61b7a6b5af74c5ff82b2d6a6be82f41","text":"The upgrade procedure on worker nodes should be executed one node at a time or few nodes at a time, without compromising the minimum required capacity for running your workloads. <del> ### Upgrade kubeadm </del> <ins> The following pages show how to  Upgrade Linux and Windows worker nodes: </ins> <del> - Upgrade kubeadm: {{< tabs name=\"k8s_install_kubeadm_worker_nodes\" >}} {{% tab name=\"Ubuntu, Debian or HypriotOS\" %}} ```shell # replace x in {{< skew currentVersion >}}.x-00 with the latest patch version apt-mark unhold kubeadm &&  apt-get update && apt-get install -y kubeadm={{< skew currentVersion >}}.x-00 &&  apt-mark hold kubeadm ``` {{% /tab %}} {{% tab name=\"CentOS, RHEL or Fedora\" %}} ```shell # replace x in {{< skew currentVersion >}}.x-0 with the latest patch version yum install -y kubeadm-{{< skew currentVersion >}}.x-0 --disableexcludes=kubernetes ``` {{% /tab %}} {{< /tabs >}} ### Call \"kubeadm upgrade\" - For worker nodes this upgrades the local kubelet configuration: ```shell sudo kubeadm upgrade node ``` ### Drain the node - Prepare the node for maintenance by marking it unschedulable and evicting the workloads: ```shell # replace <node-to-drain> with the name of your node you are draining kubectl drain <node-to-drain> --ignore-daemonsets ``` ### Upgrade kubelet and kubectl - Upgrade the kubelet and kubectl: {{< tabs name=\"k8s_kubelet_and_kubectl\" >}} {{% tab name=\"Ubuntu, Debian or HypriotOS\" %}} ```shell # replace x in {{< skew currentVersion >}}.x-00 with the latest patch version apt-mark unhold kubelet kubectl &&  apt-get update && apt-get install -y kubelet={{< skew currentVersion >}}.x-00 kubectl={{< skew currentVersion >}}.x-00 &&  apt-mark hold kubelet kubectl ``` {{% /tab %}} {{% tab name=\"CentOS, RHEL or Fedora\" %}} ```shell # replace x in {{< skew currentVersion >}}.x-0 with the latest patch version yum install -y kubelet-{{< skew currentVersion >}}.x-0 kubectl-{{< skew currentVersion >}}.x-0 --disableexcludes=kubernetes ``` {{% /tab %}} {{< /tabs >}} <br /> - Restart the kubelet: ```shell sudo systemctl daemon-reload sudo systemctl restart kubelet ``` ### Uncordon the node - Bring the node back online by marking it schedulable: ```shell # replace <node-to-uncordon> with the name of your node kubectl uncordon <node-to-uncordon> ``` </del> <ins> * [Upgrade Linux nodes](/docs/tasks/administer-cluster/kubeadm/upgrading-linux-nodes/) * [Upgrade Windows nodes](/docs/tasks/administer-cluster/kubeadm/upgrading-windows-nodes/) </ins> ## Verify the status of the cluster"}
{"_id":"q-en-website-8af87a76d8e227bc1ccfe51200da387b8bef49410b8f32d006fb2477e7cced22","text":"- [Pods](/docs/concepts/workloads/pods/) - [Cluster DNS](/docs/concepts/services-networking/dns-pod-service/) - [Headless Services](/docs/concepts/services-networking/service/#headless-services) <del> - [PersistentVolumes](/docs/concepts/storage/volumes/) </del> <ins> - [PersistentVolumes](/docs/concepts/storage/persistent-volumes/) </ins> - [PersistentVolume Provisioning](https://github.com/kubernetes/examples/tree/master/staging/persistent-volume-provisioning/) - [StatefulSets](/docs/concepts/workloads/controllers/statefulset/) - [PodDisruptionBudgets](/docs/concepts/workloads/pods/disruptions/#pod-disruption-budget)"}
{"_id":"q-en-website-8b6bafe65a9d9065e3609d92a0b43350a8f53d769a5b05cdb0cb5e91ebec7379","text":"{{< note >}} <!-- <del> `overlay2` is the preferred storage driver for systems running Linux kernel version 4.0 or higher, or RHEL or CentOS using version 3.10.0-514 and above. </del> <ins> `overlay2` is the preferred storage driver for systems running Linux kernel version 4.0 or higher, or RHEL or CentOS using version 3.10.0-514 and above. </ins> --> 对于运行 Linux 内核版本 4.0 或更高版本，或使用 3.10.0-51 及更高版本的 RHEL 或 CentOS 的系统，`overlay2`是首选的存储驱动程序。"}
{"_id":"q-en-website-8c90f28a6760a8de3951cddf8525a5fe6f248297ebbe15286a73db90465d6d63","text":"This section outlines the necessary steps to use containerd as CRI runtime. <del> To install containerd on your system, follow the instructions on [getting started with containerd](https://github.com/containerd/containerd/blob/main/docs/getting-started.md).Return to this step once you've created a valid `config.toml` configuration file. </del> <ins> To install containerd on your system, follow the instructions on [getting started with containerd](https://github.com/containerd/containerd/blob/main/docs/getting-started.md). Return to this step once you've created a valid `config.toml` configuration file. </ins> {{< tabs name=\"Finding your config.toml file\" >}} {{% tab name=\"Linux\" %}}"}
{"_id":"q-en-website-8c93e6ad20702183efb17939f94dbd1aa7c754524b8f4d826b968eb0fdf0ae17","text":"## Using the built-in Pod Security Admission Controller <del> {{< feature-state for_k8s_version=\"v1.22\" state=\"alpha\" >}} </del> <ins> {{< feature-state for_k8s_version=\"v1.23\" state=\"beta\" >}} </ins> The [Pod Security Admission Controller](/docs/reference/access-authn-authz/admission-controllers/#podsecurity) intends to replace the deprecated PodSecurityPolicies."}
{"_id":"q-en-website-8dc2afd63988141a5d13a514eb7d2afe6ce7faebcb6266f861c02adb73d42df1","text":"<ins> --- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: allow-all-ingress spec: podSelector: {} ingress: - {} policyTypes: - Ingress </ins>"}
{"_id":"q-en-website-8e29a2c3638c1fee28a7042bd8648d96a55e84199a5cf69d59d29a3bc752ed2d","text":"</form> <h5 style=\"text-align: center\"><a href=\"https://us10.campaign-archive.com/home/?u=3885586f8f1175194017967d6&id=11c1b8bcb2\" aria-label=\"Kube Weekly\" style=\"color: #3371E3; font-weight: 400; font-size: 20px\">{{ T \"main_kubeweekly_past_link\" }}</a></h5> </div> <del> <br> <br> </del> <!--End mc_embed_signup--> </div> </section>"}
{"_id":"q-en-website-8e369f1e1c70eed088a4ec5e57af3eda808e43872acb70d7150fe84e70029e4b","text":"``` <del> For initial troubleshooting, you can use the following flags in [nssm.exe](https://nssm.cc/) to redirect stdout and stderr to a output file: </del> <ins> 最初のトラブルシューティングでは、[nssm.exe](https://nssm.cc/)で次のフラグを使用して、stdoutおよびstderrを出力ファイルにリダイレクトできます。: </ins> ```powershell nssm set <Service Name> AppStdout C:kmysvc.log nssm set <Service Name> AppStderr C:kmysvc.log ``` <del> For additional details, see official [nssm usage](https://nssm.cc/usage) docs. </del> <ins> 詳細については、公式の[nssmの使用法](https://nssm.cc/usage)のドキュメントを参照してください。 </ins> <del> 1. My Windows Pods do not have network connectivity </del> <ins> 1. Windows Podにネットワーク接続がありません </ins> <del> If you are using virtual machines, ensure that MAC spoofing is enabled on all the VM network adapter(s). </del> <ins> 仮想マシンを使用している場合は、すべてのVMネットワークアダプターでMACスプーフィングが有効になっていることを確認してください。 </ins> <del> 1. My Windows Pods cannot ping external resources </del> <ins> 1. Windows Podが外部リソースにpingできません </ins> <del> Windows Pods do not have outbound rules programmed for the ICMP protocol today. However, TCP/UDP is supported. When trying to demonstrate connectivity to resources outside of the cluster, please substitute `ping <IP>` with corresponding `curl <IP>` commands. </del> <ins> 現在、Windows Podには、ICMPプロトコル用にプログラムされた送信ルールはありません。ただし、TCP/UDPはサポートされています。クラスター外のリソースへの接続を実証する場合は、`ping <IP>`に対応する`curl <IP>`コマンドに置き換えてください。 </ins> <del> If you are still facing problems, most likely your network configuration in [cni.conf](https://github.com/Microsoft/SDN/blob/master/Kubernetes/flannel/l2bridge/cni/config/cni.conf) deserves some extra attention. You can always edit this static file. The configuration update will apply to any newly created Kubernetes resources. </del> <ins> それでも問題が解決しない場合は、[cni.conf](https://github.com/Microsoft/SDN/blob/master/Kubernetes/flannel/l2bridge/cni/config/cni.conf)のネットワーク構成に値する可能性があるので、いくつかの特別な注意が必要です。この静的ファイルはいつでも編集できます。構成の更新は、新しく作成されたすべてのKubernetesリソースに適用されます。 </ins> <del> One of the Kubernetes networking requirements (see [Kubernetes model](/ja/docs/concepts/cluster-administration/networking/)) is for cluster communication to occur without NAT internally. To honor this requirement, there is an [ExceptionList](https://github.com/Microsoft/SDN/blob/master/Kubernetes/flannel/l2bridge/cni/config/cni.conf#L20) for all the communication where we do not want outbound NAT to occur. However, this also means that you need to exclude the external IP you are trying to query from the ExceptionList. Only then will the traffic originating from your Windows pods be SNAT'ed correctly to receive a response from the outside world. In this regard, your ExceptionList in `cni.conf` should look as follows: </del> <ins> Kubernetesのネットワーキング要件の1つ(参照[Kubernetesモデル](/ja/docs/concepts/cluster-administration/networking/))は、内部でNATを使用せずにクラスター通信を行うためのものです。この要件を遵守するために、すべての通信に[ExceptionList](https://github.com/Microsoft/SDN/blob/master/Kubernetes/flannel/l2bridge/cni/config/cni.conf#L20)があり、アウトバウンドNATが発生しないようにします。ただし、これは、クエリしようとしている外部IPをExceptionListから除外する必要があることも意味します。そうして初めて、Windows PodからのトラフィックがSNAT処理され、外部からの応答を受信できるようになります。この点で、`cni.conf`のExceptionListは次のようになります。: </ins> ```conf \"ExceptionList\": [ <del> \"10.244.0.0/16\",  # Cluster subnet \"10.96.0.0/12\",   # Service subnet \"10.127.130.0/24\" # Management (host) subnet </del> <ins> \"10.244.0.0/16\",  # クラスターのサブネット \"10.96.0.0/12\",   # Serviceのサブネット \"10.127.130.0/24\" # 管理 (ホスト) のサブネット </ins> ] ``` <del> 1. My Windows node cannot access NodePort service </del> <ins> 1. WindowsノードがNodePort Serviceにアクセスできません </ins> <del> Local NodePort access from the node itself fails. This is a known limitation. NodePort access works from other nodes or external clients. </del> <ins> ノード自体からのローカルNodePortアクセスは失敗します。これは既知の制限です。NodePortアクセスは、他のノードまたは外部クライアントから行えます。 </ins> <del> 1. vNICs and HNS endpoints of containers are being deleted </del> <ins> 1. コンテナのvNICとHNSエンドポイントが削除されています </ins> <del> This issue can be caused when the `hostname-override` parameter is not passed to [kube-proxy](/docs/reference/command-line-tools-reference/kube-proxy/). To resolve it, users need to pass the hostname to kube-proxy as follows: </del> <ins> この問題は、`hostname-override`パラメータが[kube-proxy](/docs/reference/command-line-tools-reference/kube-proxy/)に渡されない場合に発生する可能性があります。これを解決するには、ユーザーは次のようにホスト名をkube-proxyに渡す必要があります。: </ins> ```powershell C:kkube-proxy.exe --hostname-override=$(hostname) ``` <del> 1. With flannel my nodes are having issues after rejoining a cluster </del> <ins> 1. flannelを使用すると、クラスターに再参加した後、ノードに問題が発生します </ins> <del> Whenever a previously deleted node is being re-joined to the cluster, flannelD tries to assign a new pod subnet to the node. Users should remove the old pod subnet configuration files in the following paths: </del> <ins> 以前に削除されたノードがクラスターに再参加するときはいつも、flannelDは新しいPodサブネットをノードに割り当てようとします。ユーザーは、次のパスにある古いPodサブネット構成ファイルを削除する必要があります。: </ins> ```powershell Remove-Item C:kSourceVip.json Remove-Item C:kSourceVipRequest.json ``` <del> 1. After launching `start.ps1`, flanneld is stuck in \"Waiting for the Network to be created\" </del> <ins> 1. `start.ps1`を起動した後、flanneldが「ネットワークが作成されるのを待っています」と表示されたままになります </ins> <del> There are numerous reports of this [issue which are being investigated](https://github.com/coreos/flannel/issues/1066); most likely it is a timing issue for when the management IP of the flannel network is set. A workaround is to simply relaunch start.ps1 or relaunch it manually as follows: </del> <ins> この[調査中の問題](https://github.com/coreos/flannel/issues/1066)に関する多数の報告があります。最も可能性が高いのは、flannelネットワークの管理IPが設定されるタイミングの問題です。回避策は、単純にstart.ps1を再起動するか、次のように手動で再起動することです。: </ins> ```powershell PS C:> [Environment]::SetEnvironmentVariable(\"NODE_NAME\", \"<Windows_Worker_Hostname>\") PS C:> C:flannelflanneld.exe --kubeconfig-file=c:kconfig --iface=<Windows_Worker_Node_IP> --ip-masq=1 --kube-subnet-mgr=1 ``` <del> 1. My Windows Pods cannot launch because of missing `/run/flannel/subnet.env` </del> <ins> 1. `/run/flannel/subnet.env`がないため、Windows Podを起動できません </ins> <del> This indicates that Flannel didn't launch correctly. You can either try to restart flanneld.exe or you can copy the files over manually from `/run/flannel/subnet.env` on the Kubernetes master to` C:runflannelsubnet.env` on the Windows worker node and modify the `FLANNEL_SUBNET` row to a different number. For example, if node subnet 10.244.4.1/24 is desired: </del> <ins> これは、Flannelが正しく起動しなかったことを示しています。 flanneld.exeの再起動を試みるか、Kubernetesマスターの`/run/flannel/subnet.env`からWindowsワーカーノードの`C:runflannelsubnet.env`に手動でファイルをコピーすることができます。「FLANNEL_SUBNET」行を別の番号に変更します。たとえば、ノードサブネット10.244.4.1/24が必要な場合は以下となります。: </ins> ```env FLANNEL_NETWORK=10.244.0.0/16"}
{"_id":"q-en-website-8eec86cd77c269fd4504fab84737829142c4bc798d1bb363b6f0caf5e111cc41","text":"See [Traffic Policies](/docs/reference/networking/virtual-ips/#traffic-policies) for more details. <del> ### Trafic distribution </del> <ins> ### Traffic distribution </ins> {{< feature-state feature_gate_name=\"ServiceTrafficDistribution\" >}}"}
{"_id":"q-en-website-8f5432037530f34dc0998774ee8dea41397c7e45f2ee57f982d6545c2f733852","text":"これで、Hugoのサーバーが1313番ポートを使って開始します。お使いのブラウザにて http://localhost:1313 にアクセスしてください。リポジトリ内のソースファイルに変更を加えると、HugoがWebサイトの内容を更新してブラウザに反映します。 <ins> ## API reference pagesをビルドする `content/en/docs/reference/kubernetes-api`に配置されているAPIリファレンスページは<https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs>を使ってSwagger仕様書からビルドされています。 新しいKubernetesリリースのためにリファレンスページをアップデートするには、次の手順を実行します: 1. `api-ref-generator`サブモジュールをプルする: ```bash git submodule update --init --recursive --depth 1 ``` 2. Swagger仕様書を更新する: ```bash curl 'https://raw.githubusercontent.com/kubernetes/kubernetes/master/api/openapi-spec/swagger.json' > api-ref-assets/api/swagger.json ``` 3. 新しいリリースの変更を反映するため、`api-ref-assets/config/`で`toc.yaml`と`fields.yaml`を適用する。 4. 次に、ページをビルドする: ```bash make api-reference ``` コンテナイメージからサイトを作成・サーブする事でローカルで結果をテストすることができます: ```bash make container-image make container-serve ``` APIリファレンスを見るために、ブラウザで<http://localhost:1313/docs/reference/kubernetes-api/>を開いてください。 5. 新しいコントラクトのすべての変更が設定ファイル`toc.yaml`と`fields.yaml`に反映されたら、新しく生成されたAPIリファレンスページとともにPull Requestを作成します。 </ins> ## トラブルシューティング ### error: failed to transform resource: TOCSS: failed to transform \"scss/main.scss\" (text/x-scss): this feature is not available in your current Hugo version"}
{"_id":"q-en-website-900ff711a802f3e25639c6320c880546f7d430bc19bf7a007d9bc5f3ca154ae4","text":"* `apiserver_flowcontrol_request_concurrency_limit` is a gauge vector hoding the computed concurrency limit (based on the API server's total concurrency limit and PriorityLevelConfigurations' concurrency <del> shares), broken down by the label `priorityLevel`. </del> <ins> shares), broken down by the label `priority_level`. </ins> * `apiserver_flowcontrol_request_wait_duration_seconds` is a histogram vector of how long requests spent queued, broken down by the labels <del> `flowSchema` (indicating which one matched the request), `priorityLevel` (indicating the one to which the request was </del> <ins> `flow_schema` (indicating which one matched the request), `priority_level` (indicating the one to which the request was </ins> assigned), and `execute` (indicating whether the request started executing). {{< note >}}"}
{"_id":"q-en-website-9050accb6e0ec489d71bf94164fa95620005fed30799677d9029ca1620e9816f","text":"## Securing etcd clusters <del> Access to etcd is equivalent to root permission in the cluster so ideally only the API server should have access to it. Considering the sensitivity of the data, it is recommended to grant permission to only those nodes that require access to etcd clusters. To secure etcd, either set up firewall rules or use the security features provided by etcd. etcd security features depend on x509 Public Key Infrastructure (PKI). To begin, establish secure communication channels by generating a key and certificate pair. For example, use key pairs `peer.key` and `peer.cert` for securing communication between etcd members, and `client.key` and `client.cert` for securing communication between etcd and its clients. See the [example scripts](https://github.com/coreos/etcd/tree/master/hack/tls-setup) provided by the etcd project to generate key pairs and CA files for client authentication. </del> <ins> Access to etcd is equivalent to root permission in the cluster so ideally only the API server should have access to it. Considering the sensitivity of the data, it is recommended to grant permission to only those nodes that require access to etcd clusters. To secure etcd, either set up firewall rules or use the security features provided by etcd. etcd security features depend on x509 Public Key Infrastructure (PKI). To begin, establish secure communication channels by generating a key and certificate pair. For example, use key pairs `peer.key` and `peer.cert` for securing communication between etcd members, and `client.key` and `client.cert` for securing communication between etcd and its clients. See the [example scripts](https://github.com/coreos/etcd/tree/master/hack/tls-setup) provided by the etcd project to generate key pairs and CA files for client authentication. </ins> ### Securing communication <del> To configure etcd with secure peer communication, specify flags `--peer-key-file=peer.key` and `--peer-cert-file=peer.cert`, and use https as URL schema. </del> <ins> To configure etcd with secure peer communication, specify flags `--peer-key-file=peer.key` and `--peer-cert-file=peer.cert`, and use HTTPS as the URL schema. </ins> <del> Similarly, to configure etcd with secure client communication, specify flags `--key-file=k8sclient.key` and `--cert-file=k8sclient.cert`, and use https as URL schema. </del> <ins> Similarly, to configure etcd with secure client communication, specify flags `--key-file=k8sclient.key` and `--cert-file=k8sclient.cert`, and use HTTPS as the URL schema. </ins> ### Limiting access of etcd clusters <del> After configuring secure communication, restrict the access of etcd cluster to only the Kubernetes API server. Use TLS authentication to do so. </del> <ins> After configuring secure communication, restrict the access of etcd cluster to only the Kubernetes API servers. Use TLS authentication to do so. </ins> <del> For example, consider key pairs `k8sclient.key` and `k8sclient.cert` that are trusted by the CA `etcd.ca`. When etcd is configured with `--client-cert-auth` along with TLS, it verifies the certificates from clients by using system CAs or the CA passed in by `--trusted-ca-file` flag. Specifying flags `--client-cert-auth=true` and `--trusted-ca-file=etcd.ca` will restrict the access to clients with the certificate `k8sclient.cert`. </del> <ins> For example, consider key pairs `k8sclient.key` and `k8sclient.cert` that are trusted by the CA `etcd.ca`. When etcd is configured with `--client-cert-auth` along with TLS, it verifies the certificates from clients by using system CAs or the CA passed in by `--trusted-ca-file` flag. Specifying flags `--client-cert-auth=true` and `--trusted-ca-file=etcd.ca` will restrict the access to clients with the certificate `k8sclient.cert`. </ins> <del> Once etcd is configured correctly, only clients with valid certificates can access it. To give Kubernetes API server the access, configure it with the flags `--etcd-certfile=k8sclient.cert`,`--etcd-keyfile=k8sclient.key` and `--etcd-cafile=ca.cert`. </del> <ins> Once etcd is configured correctly, only clients with valid certificates can access it. To give Kubernetes API servers the access, configure them with the flags `--etcd-certfile=k8sclient.cert`,`--etcd-keyfile=k8sclient.key` and `--etcd-cafile=ca.cert`. </ins> {{< note >}} <del> etcd authentication is not currently supported by Kubernetes. For more information, see the related issue [Support Basic Auth for Etcd v2](https://github.com/kubernetes/kubernetes/issues/23398). </del> <ins> etcd authentication is not currently supported by Kubernetes. For more information, see the related issue [Support Basic Auth for Etcd v2](https://github.com/kubernetes/kubernetes/issues/23398). </ins> {{< /note >}} ## Replacing a failed etcd member <del> etcd cluster achieves high availability by tolerating minor member failures. However, to improve the overall health of the cluster, replace failed members immediately. When multiple members fail, replace them one by one. Replacing a failed member involves two steps: removing the failed member and adding a new member. </del> <ins> etcd cluster achieves high availability by tolerating minor member failures. However, to improve the overall health of the cluster, replace failed members immediately. When multiple members fail, replace them one by one. Replacing a failed member involves two steps: removing the failed member and adding a new member. </ins> <del> Though etcd keeps unique member IDs internally, it is recommended to use a unique name for each member to avoid human errors. For example, consider a three-member etcd cluster. Let the URLs be, member1=http://10.0.0.1, member2=http://10.0.0.2, and member3=http://10.0.0.3. When member1 fails, replace it with member4=http://10.0.0.4. </del> <ins> Though etcd keeps unique member IDs internally, it is recommended to use a unique name for each member to avoid human errors. For example, consider a three-member etcd cluster. Let the URLs be, `member1=http://10.0.0.1`, `member2=http://10.0.0.2`, and `member3=http://10.0.0.3`. When `member1` fails, replace it with `member4=http://10.0.0.4`. </ins> <del> 1. Get the member ID of the failed member1: </del> <ins> 1. Get the member ID of the failed `member1`: </ins> <del> `etcdctl --endpoints=http://10.0.0.2,http://10.0.0.3 member list` </del> <ins> ```shell etcdctl --endpoints=http://10.0.0.2,http://10.0.0.3 member list ``` </ins> <del> The following message is displayed: </del> <ins> The following message is displayed: </ins> <del> 8211f1d0f64f3269, started, member1, http://10.0.0.1:2380, http://10.0.0.1:2379 91bc3c398fb3c146, started, member2, http://10.0.0.2:2380, http://10.0.0.2:2379 fd422379fda50e48, started, member3, http://10.0.0.3:2380, http://10.0.0.3:2379 </del> <ins> ```console 8211f1d0f64f3269, started, member1, http://10.0.0.1:2380, http://10.0.0.1:2379 91bc3c398fb3c146, started, member2, http://10.0.0.2:2380, http://10.0.0.2:2379 fd422379fda50e48, started, member3, http://10.0.0.3:2380, http://10.0.0.3:2379 ``` </ins> 2. Remove the failed member: <del> `etcdctl member remove 8211f1d0f64f3269` </del> <ins> ```shell etcdctl member remove 8211f1d0f64f3269 ``` </ins> <del> The following message is displayed: </del> <ins> The following message is displayed: </ins> <del> Removed member 8211f1d0f64f3269 from cluster </del> <ins> ```console Removed member 8211f1d0f64f3269 from cluster ``` </ins> 3. Add the new member: <del> `./etcdctl member add member4 --peer-urls=http://10.0.0.4:2380` </del> <ins> ```shell etcdctl member add member4 --peer-urls=http://10.0.0.4:2380 ``` </ins> <del> The following message is displayed: </del> <ins> The following message is displayed: </ins> <del> Member 2be1eb8f84b7f63e added to cluster ef37ad9dc622a7c4 </del> <ins> ```console Member 2be1eb8f84b7f63e added to cluster ef37ad9dc622a7c4 ``` </ins> 4. Start the newly added member on a machine with the IP `10.0.0.4`: <del> export ETCD_NAME=\"member4\" export ETCD_INITIAL_CLUSTER=\"member2=http://10.0.0.2:2380,member3=http://10.0.0.3:2380,member4=http://10.0.0.4:2380\" export ETCD_INITIAL_CLUSTER_STATE=existing etcd [flags] </del> <ins> ```shell export ETCD_NAME=\"member4\" export ETCD_INITIAL_CLUSTER=\"member2=http://10.0.0.2:2380,member3=http://10.0.0.3:2380,member4=http://10.0.0.4:2380\" export ETCD_INITIAL_CLUSTER_STATE=existing etcd [flags] ``` </ins> 5. Do either of the following: <del> 1. Update its `--etcd-servers` flag to make Kubernetes aware of the configuration changes, then restart the Kubernetes API server. 2. Update the load balancer configuration if a load balancer is used in the deployment. </del> <ins> 1. Update the `--etcd-servers` flag for the Kubernetes API servers to make Kubernetes aware of the configuration changes, then restart the Kubernetes API servers. 2. Update the load balancer configuration if a load balancer is used in the deployment. </ins> <del> For more information on cluster reconfiguration, see [etcd Reconfiguration Documentation](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/runtime-configuration.md#remove-a-member). </del> <ins> For more information on cluster reconfiguration, see [etcd reconfiguration documentation](https://etcd.io/docs/current/op-guide/runtime-configuration/#remove-a-member). </ins> ## Backing up an etcd cluster <del> All Kubernetes objects are stored on etcd. Periodically backing up the etcd cluster data is important to recover Kubernetes clusters under disaster scenarios, such as losing all master nodes. The snapshot file contains all the Kubernetes states and critical information. In order to keep the sensitive Kubernetes data safe, encrypt the snapshot files. </del> <ins> All Kubernetes objects are stored on etcd. Periodically backing up the etcd cluster data is important to recover Kubernetes clusters under disaster scenarios, such as losing all control plane nodes. The snapshot file contains all the Kubernetes states and critical information. In order to keep the sensitive Kubernetes data safe, encrypt the snapshot files. </ins> <del> Backing up an etcd cluster can be accomplished in two ways: etcd built-in snapshot and volume snapshot. </del> <ins> Backing up an etcd cluster can be accomplished in two ways: etcd built-in snapshot and volume snapshot. </ins> ### Built-in snapshot <del> etcd supports built-in snapshot. A snapshot may either be taken from a live member with the `etcdctl snapshot save` command or by copying the `member/snap/db` file from an etcd [data directory](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/configuration.md#--data-dir) that is not currently used by an etcd process. Taking the snapshot will normally not affect the performance of the member. </del> <ins> etcd supports built-in snapshot. A snapshot may either be taken from a live member with the `etcdctl snapshot save` command or by copying the `member/snap/db` file from an etcd [data directory](https://etcd.io/docs/current/op-guide/configuration/#--data-dir) that is not currently used by an etcd process. Taking the snapshot will not affect the performance of the member. </ins> <del> Below is an example for taking a snapshot of the keyspace served by `$ENDPOINT` to the file `snapshotdb`: </del> <ins> Below is an example for taking a snapshot of the keyspace served by `$ENDPOINT` to the file `snapshotdb`: </ins> <del> ```sh </del> <ins> ```shell </ins> ETCDCTL_API=3 etcdctl --endpoints $ENDPOINT snapshot save snapshotdb <del> # exit 0 </del> <ins> ``` Verify the snapshot: </ins> <del> # verify the snapshot </del> <ins> ```shell </ins> ETCDCTL_API=3 etcdctl --write-out=table snapshot status snapshotdb <ins> ``` ```console </ins> +----------+----------+------------+------------+ |   HASH   | REVISION | TOTAL KEYS | TOTAL SIZE | +----------+----------+------------+------------+"}
{"_id":"q-en-website-90565ac187b34a40a0e4675a17f023fef981befb809f9094501f716f5b783ac0","text":"API resource allows you to define custom resources. Defining a CRD object creates a new custom resource with a name and schema that you specify. The Kubernetes API serves and handles the storage of your custom resource. <del> The name of a CRD object must be a valid [DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names). </del> <ins> The name of the CRD object itself must be a valid [DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names) derived from the defined resource name and its API group; see [how to create a CRD](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions#create-a-customresourcedefinition) for more details. Further, the name of an object whose kind/resource is defined by a CRD must also be a valid DNS subdomain name. </ins> This frees you from writing your own API server to handle the custom resource, but the generic nature of the implementation means you have less flexibility than with"}
{"_id":"q-en-website-91ae72a5ba012f141fee99b662f22b88fc81ddb80f0f80fcb4f71f4e5afe543f","text":"The latter selects all resources with key equal to `tier` and value distinct from `frontend`, and all resources with no labels with the `tier` key. One could filter for resources in `production` excluding `frontend` using the comma operator: `environment=production,tier!=frontend` <ins> One usage scenario for equality-based label requirement is for Pods to specify node selection criteria. For example, the sample Pod below selects nodes with the label \"`accelerator=nvidia-tesla-p100`\". ```yaml apiVersion: v1 kind: Pod metadata: name: cuda-test spec: containers: - name: cuda-test image: \"k8s.gcr.io/cuda-vector-add:v0.1\" resources: limits: nvidia.com/gpu: 1 nodeSelector: accelerator: nvidia-tesla-p100 ``` </ins> ### _Set-based_ requirement"}
{"_id":"q-en-website-91b0df982fe3b79f1a5b6af89ef7faf7b5dcb7bc243b66121e6d7d110a710524","text":"You can specify init containers in the Pod specification alongside the `containers` array (which describes app containers). <ins> In Kubernetes, a [sidecar container](/docs/concepts/workloads/pods/sidecar-containers/) is a container that starts before the main application container and _continues to run_. This document is about init containers: containers that run to completion during Pod initialization. </ins> <!-- body -->"}
{"_id":"q-en-website-92d25970d29f01c507c021f6e6cbcbf56e9b6aec4fe987ab7b7b3d2228ce6454","text":"{{< /note >}} Both approaches are equivalent. After reloading your shell, kubectl autocompletion should be working. <del> To enable bash autocompletion in current session of shell, source the ~/.bashrc file: </del> <ins> To enable bash autocompletion in current session of shell, run `exec bash`: </ins> ```bash <del> source ~/.bashrc </del> <ins> exec bash </ins> ```"}
{"_id":"q-en-website-932d467c289eaf5dfbd0cb55d6e0b94a00c481da6a147288185a47ca6b5a9c18","text":"{ type: 0, name: 'ASM Technologies Limited', <del> logo: 'asmtech', </del> <ins> logo: 'asm', </ins> link: 'http://www.asmtech.com/', <del> blurb: 'http://www.asmtech.com/audience-channels/software_publisher/' </del> <ins> blurb: 'Our technology supply chain portfolio enables your software products to be accessible, viable and available more effectively.' </ins> }, { type: 1,"}
{"_id":"q-en-website-935e1e293d118663ada4377c1884d7b9b3a12ce4eb1a346354e52e307b59b93c","text":"例如：要禁用batch/v1，请设置 `--runtime-config=batch/v1=false`，以启用batch/v2alpha1，请设置`--runtime-config=batch/v2alpha1`。 该标志接受描述apiserver的运行时配置的逗号分隔的一组键值对。 <del> 重要：启用或禁用组或资源需要重新启动apiserver和控制器管理器来使得 `--runtime-config` 更改生效。 </del> <ins> {{< note >}} 启用或禁用组或资源需要重新启动apiserver和控制器管理器来使得 `--runtime-config` 更改生效。 {{< /note >}} </ins> <!-- <del> ## Enabling resources in the groups </del> <ins> ## Enabling specific resources in the extensions/v1beta1 group DaemonSets, Deployments, StatefulSet, NetworkPolicies, PodSecurityPolicies and ReplicaSets in the `extensions/v1beta1` API group are disabled by default. For example: to enable deployments and daemonsets, set `--runtime-config=extensions/v1beta1/deployments=true,extensions/v1beta1/daemonsets=true`. </ins> <del> DaemonSets, Deployments, HorizontalPodAutoscalers, Ingresses, Jobs and ReplicaSets are enabled by default. Other extensions resources can be enabled by setting `--runtime-config` on apiserver. `--runtime-config` accepts comma separated values. For example: to disable deployments and ingress, set `--runtime-config=extensions/v1beta1/deployments=false,extensions/v1beta1/ingresses=false` </del> <ins> Individual resource enablement/disablement is only supported in the `extensions/v1beta1` API group for legacy reasons. </ins> --> <del> ## 启用组中资源 </del> <ins> ## 启用 extensions/v1beta1 组中资源 在 `extensions/v1beta1` API 组中，DaemonSets，Deployments，StatefulSet, NetworkPolicies, PodSecurityPolicies 和 ReplicaSets 是默认禁用的。 例如：要启用 deployments 和 daemonsets，请设置 `--runtime-config=extensions/v1beta1/deployments=true,extensions/v1beta1/daemonsets=true`。 {{< note >}} 出于遗留原因，仅在 `extensions / v1beta1` API 组中支持各个资源的启用/禁用。 </ins> <del> DaemonSets，Deployments，HorizontalPodAutoscalers，Ingress，Jobs 和 ReplicaSets是默认启用的。 其他扩展资源可以通过在apiserver上设置 `--runtime-config` 来启用。 `--runtime-config` 接受逗号分隔的值。 例如：要禁用 Deployment 和 Ingress， 请设置 `--runtime-config=extensions/v1beta1/deployments=false,extensions/v1beta1/ingress=false` </del> <ins> {{< /note >}} </ins> {{% /capture %}}"}
{"_id":"q-en-website-93d92787f082d3f43b4fed6cc31fe971df9cce685a223e09e8a327ed2e8578f0","text":"### Calico <del> [Calico](https://docs.projectcalico.org/) is an open source networking and network security solution for containers, virtual machines, and native host-based workloads. Calico supports multiple data planes including: a pure Linux eBPF dataplane, a standard Linux networking dataplane, and a Windows HNS dataplane. Calico provides a full networking stack but can also be used in conjunction with [cloud provider CNIs](https://docs.projectcalico.org/networking/determine-best-networking#calico-compatible-cni-plugins-and-cloud-provider-integrations) to provide network policy enforcement. </del> <ins> [Calico](https://projectcalico.docs.tigera.io/about/about-calico/) is an open source networking and network security solution for containers, virtual machines, and native host-based workloads. Calico supports multiple data planes including: a pure Linux eBPF dataplane, a standard Linux networking dataplane, and a Windows HNS dataplane. Calico provides a full networking stack but can also be used in conjunction with [cloud provider CNIs](https://projectcalico.docs.tigera.io/networking/determine-best-networking#calico-compatible-cni-plugins-and-cloud-provider-integrations) to provide network policy enforcement. </ins> ### Cilium"}
{"_id":"q-en-website-958ce5729bb6cfe78297c45a527f01cc383f9d305b28b7239a94c86c7ae90359","text":"--- <del> title: Control Plane </del> <ins> title: Ambiente de gerenciamento </ins> id: control-plane date: 2020-04-19 full_link:"}
{"_id":"q-en-website-965cbd5102d418ae4d52122b0e94c09bb58daaf9ba3ab73a6b65021419f6fea7","text":"The name of each app and init container in a Pod must be unique; a validation error is thrown for any container sharing a name with another. <del> #### API for sidecar containers {{< feature-state for_k8s_version=\"v1.28\" state=\"alpha\" >}} Starting with Kubernetes 1.28 in alpha, a feature gate named `SidecarContainers` allows you to specify a `restartPolicy` for init containers which is independent of the Pod and other init containers. Container [probes](/docs/concepts/workloads/pods/pod-lifecycle/#types-of-probe) can also be added to control their lifecycle. If an init container is created with its `restartPolicy` set to `Always`, it will start and remain running during the entire life of the Pod, which is useful for running supporting services separated from the main application containers. If a `readinessProbe` is specified for this init container, its result will be used to determine the `ready` state of the Pod. Since these containers are defined as init containers, they benefit from the same ordering and sequential guarantees as other init containers, allowing them to be mixed with other init containers into complex Pod initialization flows. Compared to regular init containers, sidecar-style init containers continue to run and the next init container can begin starting once the kubelet has set the `started` container status for the sidecar-style init container to true. That status either becomes true because there is a process running in the container and no startup probe defined, or as a result of its `startupProbe` succeeding. This feature can be used to implement the sidecar container pattern in a more robust way, as the kubelet always restarts a sidecar container if it fails. Here's an example of a Deployment with two containers, one of which is a sidecar: {{% code_sample language=\"yaml\" file=\"application/deployment-sidecar.yaml\" %}} This feature is also useful for running Jobs with sidecars, as the sidecar container will not prevent the Job from completing after the main container has finished. Here's an example of a Job with two containers, one of which is a sidecar: {{% code_sample language=\"yaml\" file=\"application/job/job-sidecar.yaml\" %}} #### Resource sharing within containers </del> <ins> ### Resource sharing within containers </ins> <del> Given the ordering and execution for init containers, the following rules </del> <ins> Given the order of execution for init, sidecar and app containers, the following rules </ins> for resource usage apply: * The highest of any particular resource request or limit defined on all init"}
{"_id":"q-en-website-96f3ffc17c8977fbb65713983e3951d51e4d7b75a17747ae12a192d7913a66ef","text":"is an [Istio](https://istio.io/) based ingress controller. * The [Kong Ingress Controller for Kubernetes](https://github.com/Kong/kubernetes-ingress-controller#readme) is an ingress controller driving [Kong Gateway](https://konghq.com/kong/). <del> * The [NGINX Ingress Controller for Kubernetes](https://www.nginx.com/products/nginx/kubernetes-ingress-controller) </del> <ins> * The [NGINX Ingress Controller for Kubernetes](https://www.nginx.com/products/nginx-ingress-controller/) </ins> works with the [NGINX](https://www.nginx.com/resources/glossary/nginx/) webserver (as a proxy). * [Skipper](https://opensource.zalando.com/skipper/kubernetes/ingress-controller/) HTTP router and reverse proxy for service composition, including use cases like Kubernetes Ingress, designed as a library to build your custom proxy. * The [Traefik Kubernetes Ingress provider](https://doc.traefik.io/traefik/providers/kubernetes-ingress/) is an"}
{"_id":"q-en-website-9761d4d04d089367135be7ef0008c88e2c4b54a888e0e3721b4ec7cc961f7da3","text":"The Kubernetes project recommends that you use the TokenReview API, because this method invalidates tokens that are bound to API objects such as Secrets, ServiceAccounts, and Pods when those objects are deleted. For example, if you <del> delete the Pod that contains a projected ServiceAccount token, the TokenReview API invalidates that token immediately. If you use OIDC validation instead, your clients continue to treat the token as valid until the token reaches its expiration timestamp. </del> <ins> delete the Pod that contains a projected ServiceAccount token, the cluster invalidates that token immediately and a TokenReview immediately fails. If you use OIDC validation instead, your clients continue to treat the token as valid until the token reaches its expiration timestamp. </ins> Your application should always define the audience that it accepts, and should check that the token's audiences match the audiences that the application expects. This helps to minimize the scope of the token so that it can only be <del> used in your appplication and nowhere else. </del> <ins> used in your application and nowhere else. </ins> ## Alternatives"}
{"_id":"q-en-website-97e7d615534275c9644161994a1078dd8d4c0ec4236a479042696631765e8d93","text":"```shell sudo systemctl daemon-reload <del> sudo systemctl enable crio --no </del> <ins> sudo systemctl enable crio --now </ins> ``` <!--"}
{"_id":"q-en-website-984095716653be3acaf1d275f8f030b7ecb890ca6374c47d9a179b52dda68608","text":"### Preparing the hosts <ins> #### Component installation </ins> Install a {{< glossary_tooltip term_id=\"container-runtime\" text=\"container runtime\" >}} and kubeadm on all the hosts. For detailed instructions and other prerequisites, see [Installing kubeadm](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/)."}
{"_id":"q-en-website-9876da29c910ed5b246ea704e13fe5b185f814bba3205161619ac0861d74351a","text":"{{% /tab %}} {{< /tabs >}} <del> #### systemd {#containerd-systemd} </del> <ins> #### Using the `systemd` cgroup driver {#containerd-systemd} </ins> To use the `systemd` cgroup driver in `/etc/containerd/config.toml` with `runc`, set"}
{"_id":"q-en-website-98b0532aa7055580ba68bc03fef6693dba7d98fac5412bfd10f16941618922ad","text":"```shell kubectl apply -f myapp.yaml ``` <ins> 実行結果は下記のようになります。 </ins> ``` pod/myapp-pod created ```"}
{"_id":"q-en-website-98bf8763a43023f0f948766b28a643ea632881cd09154b7f60a1c423567c6951","text":"A `csi` volume can be used in a Pod in three different ways: * through a reference to a [PersistentVolumeClaim](#persistentvolumeclaim) <del> * with a [generic ephemeral volume](/docs/concepts/storage/ephemeral-volumes/#generic-ephemeral-volume) * with a [CSI ephemeral volume](/docs/concepts/storage/ephemeral-volumes/#csi-ephemeral-volume) </del> <ins> * with a [generic ephemeral volume](/docs/concepts/storage/ephemeral-volumes/#generic-ephemeral-volumes) * with a [CSI ephemeral volume](/docs/concepts/storage/ephemeral-volumes/#csi-ephemeral-volumes) </ins> if the driver supports that (beta feature) The following fields are available to storage administrators to configure a CSI"}
{"_id":"q-en-website-994cac7b9c3ff04964d90a97468c09bbc805e31c33582d1be5fa78764d60aa68","text":"<del> --- title: Podの優先度とプリエンプション content_type: concept weight: 70 --- <!-- overview --> {{< feature-state for_k8s_version=\"v1.14\" state=\"stable\" >}} [Pod](/ja/docs/concepts/workloads/pods/)は _priority_（優先度）を持つことができます。 優先度は他のPodに対する相対的なPodの重要度を示します。 もしPodをスケジューリングできないときには、スケジューラーはそのPodをスケジューリングできるようにするため、優先度の低いPodをプリエンプトする（追い出す）ことを試みます。 <!-- body --> {{< warning >}} クラスターの全てのユーザーが信用されていない場合、悪意のあるユーザーが可能な範囲で最も高い優先度のPodを作成することが可能です。これは他のPodが追い出されたりスケジューリングできない状態を招きます。 管理者はResourceQuotaを使用して、ユーザーがPodを高い優先度で作成することを防ぐことができます。 詳細は[デフォルトで優先度クラスの消費を制限する](/ja/docs/concepts/policy/resource-quotas/#limit-priority-class-consumption-by-default) を参照してください。 {{< /warning >}} ## 優先度とプリエンプションを使う方法 優先度とプリエンプションを使うには、 1.  1つまたは複数の[PriorityClass](#priorityclass)を追加します 1.  追加したPriorityClassを[`priorityClassName`](#pod-priority)に設定したPodを作成します。 もちろんPodを直接作る必要はありません。 一般的には`priorityClassName`をDeploymentのようなコレクションオブジェクトのPodテンプレートに追加します。 これらの手順のより詳しい情報については、この先を読み進めてください。 {{< note >}} Kubernetesには最初から既に2つのPriorityClassが設定された状態になっています。 `system-cluster-critical`と`system-node-critical`です。 これらは汎用のクラスであり、[重要なコンポーネントが常に最初にスケジュールされることを保証する](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/)ために使われます。 {{< /note >}} ## PriorityClass PriorityClassはnamespaceによらないオブジェクトで、優先度クラスの名称から優先度を表す整数値への対応を定義します。 PriorityClassオブジェクトのメタデータの`name`フィールドにて名称を指定します。 値は`value`フィールドで指定し、必須です。 値が大きいほど、高い優先度を示します。 PriorityClassオブジェクトの名称は[DNSサブドメイン名](/ja/docs/concepts/overview/working-with-objects/names#dns-subdomain-names)として適切であり、かつ`system-`から始まってはいけません。 PriorityClassオブジェクトは10億以下の任意の32ビットの整数値を持つことができます。 それよりも大きな値は通常はプリエンプトや追い出すべきではない重要なシステム用のPodのために予約されています。 クラスターの管理者は割り当てたい優先度に対して、PriorityClassオブジェクトを1つずつ作成すべきです。 PriorityClassは任意でフィールド`globalDefault`と`description`を設定可能です。 `globalDefault`フィールドは`priorityClassName`が指定されないPodはこのPriorityClassを使うべきであることを示します。`globalDefault`がtrueに設定されたPriorityClassはシステムで一つのみ存在可能です。`globalDefault`が設定されたPriorityClassが存在しない場合は、`priorityClassName`が設定されていないPodの優先度は0に設定されます。 `description`フィールドは任意の文字列です。クラスターの利用者に対して、PriorityClassをどのような時に使うべきか示すことを意図しています。 ### PodPriorityと既存のクラスターに関する注意 -   もし既存のクラスターをこの機能がない状態でアップグレードすると、既存のPodの優先度は実質的に0になります。 -   `globalDefault`が`true`に設定されたPriorityClassを追加しても、既存のPodの優先度は変わりません。PriorityClassのそのような値は、PriorityClassが追加された以後に作成されたPodのみに適用されます。 -   PriorityClassを削除した場合、削除されたPriorityClassの名前を使用する既存のPodは変更されませんが、削除されたPriorityClassの名前を使うPodをそれ以上作成することはできなくなります。 ### PriorityClassの例 ```yaml apiVersion: scheduling.k8s.io/v1 kind: PriorityClass metadata: name: high-priority value: 1000000 globalDefault: false description: \"この優先度クラスはXYZサービスのPodに対してのみ使用すべきです。\" ``` ## 非プリエンプトのPriorityClass {#non-preempting-priority-class} {{< feature-state for_k8s_version=\"v1.19\" state=\"beta\" >}} `PreemptionPolicy: Never`と設定されたPodは、スケジューリングのキューにおいて他の優先度の低いPodよりも優先されますが、他のPodをプリエンプトすることはありません。 スケジューリングされるのを待つ非プリエンプトのPodは、リソースが十分に利用可能になるまでスケジューリングキューに残ります。 非プリエンプトのPodは、他のPodと同様に、スケジューラーのバックオフの対象になります。これは、スケジューラーがPodをスケジューリングしようと試みたものの失敗した場合、低い頻度で再試行するようにして、より優先度の低いPodが先にスケジューリングされることを許します。 非プリエンプトのPodは、他の優先度の高いPodにプリエンプトされる可能性はあります。 `PreemptionPolicy`はデフォルトでは`PreemptLowerPriority`に設定されており、これが設定されているPodは優先度の低いPodをプリエンプトすることを許容します。これは既存のデフォルトの挙動です。 `PreemptionPolicy`を`Never`に設定すると、これが設定されたPodはプリエンプトを行わないようになります。 ユースケースの例として、データサイエンスの処理を挙げます。 ユーザーは他の処理よりも優先度を高くしたいジョブを追加できますが、そのとき既存の実行中のPodの処理結果をプリエンプトによって破棄させたくはありません。 `PreemptionPolicy: Never`が設定された優先度の高いジョブは、他の既にキューイングされたPodよりも先に、クラスターのリソースが「自然に」開放されたときにスケジューリングされます。 ### 非プリエンプトのPriorityClassの例 ```yaml apiVersion: scheduling.k8s.io/v1 kind: PriorityClass metadata: name: high-priority-nonpreempting value: 1000000 preemptionPolicy: Never globalDefault: false description: \"この優先度クラスは他のPodをプリエンプトさせません。\" ``` ## Podの優先度 {#pod-priority} 一つ以上のPriorityClassがあれば、仕様にPriorityClassを指定したPodを作成することができるようになります。優先度のアドミッションコントローラーは`priorityClassName`フィールドを使用し、優先度の整数値を設定します。PriorityClassが見つからない場合、そのPodの作成は拒否されます。 下記のYAMLは上記の例で作成したPriorityClassを使用するPodの設定の例を示します。優先度のアドミッションコントローラーは仕様を確認し、このPodの優先度は1000000であると設定します。 ```yaml apiVersion: v1 kind: Pod metadata: name: nginx labels: env: test spec: containers: - name: nginx image: nginx imagePullPolicy: IfNotPresent priorityClassName: high-priority ``` ### スケジューリング順序におけるPodの優先度の効果 Podの優先度が有効な場合、スケジューラーは待機状態のPodをそれらの優先度順に並べ、スケジューリングキューにおいてより優先度の低いPodよりも前に来るようにします。その結果、その条件を満たしたときには優先度の高いPodは優先度の低いPodより早くスケジューリングされます。優先度の高いPodがスケジューリングできない場合は、スケジューラーは他の優先度の低いPodのスケジューリングも試みます。 ## プリエンプション Podが作成されると、スケジューリング待ちのキューに入り待機状態になります。スケジューラーはキューからPodを取り出し、ノードへのスケジューリングを試みます。Podに指定された条件を全て満たすノードが見つからない場合は、待機状態のPodのためにプリエンプションロジックが発動します。待機状態のPodをPと呼ぶことにしましょう。プリエンプションロジックはPよりも優先度の低いPodを一つ以上追い出せばPをスケジューリングできるようになるノードを探します。そのようなノードがあれば、優先度の低いPodはノードから追い出されます。Podが追い出された後に、Pはノードへスケジューリング可能になります。 ### ユーザーへ開示される情報 Pod PがノードNのPodをプリエンプトした場合、ノードNの名称がPのステータスの`nominatedNodeName`フィールドに設定されます。このフィールドはスケジューラーがPod Pのために予約しているリソースの追跡を助け、ユーザーにクラスターにおけるプリエンプトに関する情報を与えます。 Pod Pは必ずしも「指名したノード」へスケジューリングされないことに注意してください。Podがプリエンプトされると、そのPodは終了までの猶予期間を得ます。スケジューラーがPodの終了を待つ間に他のノードが利用可能になると、スケジューラーは他のノードをPod Pのスケジューリング先にします。この結果、Podの`nominatedNodeName`と`nodeName`は必ずしも一致しません。また、スケジューラーがノードNのPodをプリエンプトさせた後に、Pod Pよりも優先度の高いPodが来た場合、スケジューラーはノードNをその新しい優先度の高いPodへ与えます。このような場合は、スケジューラーはPod Pの`nominatedNodeName`を消去します。これによって、スケジューラーはPod Pが他のノードのPodをプリエンプトさせられるようにします。 ### プリエンプトの制限 #### プリエンプトされるPodの正常終了 Podがプリエンプトされると、[猶予期間](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination)が与えられます。 Podは作業を完了し、終了するために十分な時間が与えられます。仮にそうでない場合、強制終了されます。この猶予期間によって、スケジューラーがPodをプリエンプトした時刻と、待機状態のPod Pがノード Nにスケジュール可能になるまでの時刻の間に間が開きます。この間、スケジューラーは他の待機状態のPodをスケジュールしようと試みます。プリエンプトされたPodが終了したら、スケジューラーは待ち行列にあるPodをスケジューリングしようと試みます。そのため、Podがプリエンプトされる時刻と、Pがスケジュールされた時刻には間が開くことが一般的です。この間を最小にするには、優先度の低いPodの猶予期間を0または小さい値にする方法があります。 #### PodDisruptionBudgetは対応するが、保証されない [PodDisruptionBudget](/docs/concepts/workloads/pods/disruptions/) (PDB)は、アプリケーションのオーナーが冗長化されたアプリケーションのPodが意図的に中断される数の上限を設定できるようにするものです。KubernetesはPodをプリエンプトする際にPDBに対応しますが、PDBはベストエフォートで考慮します。スケジューラーはプリエンプトさせたとしてもPDBに違反しないPodを探します。そのようなPodが見つからない場合でもプリエンプションは実行され、PDBに反しますが優先度の低いPodが追い出されます。 #### 優先度の低いPodにおけるPod間のアフィニティ 次の条件が真の場合のみ、ノードはプリエンプションの候補に入ります。 「待機状態のPodよりも優先度の低いPodをノードから全て追い出したら、待機状態のPodをノードへスケジュールできるか」 {{< note >}} プリエンプションは必ずしも優先度の低いPodを全て追い出しません。 優先度の低いPodを全て追い出さなくても待機状態のPodがスケジューリングできる場合、一部のPodのみ追い出されます。 このような場合であったとしても、上記の条件は真である必要があります。偽であれば、そのノードはプリエンプションの対象とはされません。 {{< /note >}} 待機状態のPodが、優先度の低いPodとの間でPod間のアフィニティを持つ場合、Pod間のアフィニティはそれらの優先度の低いPodがなければ満たされません。この場合、スケジューラーはノードのどのPodもプリエンプトしようとはせず、代わりに他のノードを探します。スケジューラーは適切なノードを探せる場合と探せない場合があります。この場合、待機状態のPodがスケジューリングされる保証はありません。 この問題に対して推奨される解決策は、優先度が同一または高いPodに対してのみPod間のアフィニティを作成することです。 #### 複数ノードに対するプリエンプション Pod PがノードNにスケジューリングできるよう、ノードNがプリエンプションの対象となったとします。 他のノードのPodがプリエンプトされた場合のみPが実行可能になることもあります。下記に例を示します。 *   Pod PをノードNに配置することを検討します。 *   Pod QはノードNと同じゾーンにある別のノードで実行中です。 *   Pod Pはゾーンに対するQへのアンチアフィニティを持ちます (`topologyKey: topology.kubernetes.io/zone`)。 *   Pod Pと、ゾーン内の他のPodに対しては他のアンチアフィニティはない状態です。 *   Pod PをノードNへスケジューリングするには、Pod Qをプリエンプトすることが考えられますが、スケジューラーは複数ノードにわたるプリエンプションは行いません。そのため、Pod PはノードNへはスケジューリングできないとみなされます。 Pod Qがそのノードから追い出されると、Podアンチアフィニティに違反しなくなるので、Pod PはノードNへスケジューリング可能になります。 複数ノードに対するプリエンプションに関しては、十分な需要があり、合理的な性能を持つアルゴリズムを見つけられた場合に、追加することを検討する可能性があります。 ## トラブルシューティング Podの優先度とプリエンプションは望まない副作用をもたらす可能性があります。 いくつかの起こりうる問題と、その対策について示します。 ### Podが不必要にプリエンプトされる プリエンプションは、リソースが不足している場合に優先度の高い待機状態のPodのためにクラスターの既存のPodを追い出します。 誤って高い優先度をPodに割り当てると、意図しない高い優先度のPodはクラスター内でプリエンプションを引き起こす可能性があります。Podの優先度はPodの仕様の`priorityClassName`フィールドにて指定されます。優先度を示す整数値へと変換された後、`podSpec`の`priority`へ設定されます。 この問題に対処するには、Podの`priorityClassName`をより低い優先度に変更するか、このフィールドを未設定にすることができます。`priorityClassName`が未設定の場合、デフォルトでは優先度は0とされます。 Podがプリエンプトされたとき、プリエンプトされたPodのイベントが記録されます。 プリエンプションはPodに必要なリソースがクラスターにない場合のみ起こるべきです。 このような場合、プリエンプションはプリエンプトされるPodよりも待機状態のPodの優先度が高い場合のみ発生します。 プリエンプションは待機状態のPodがない場合や待機状態のPodがプリエンプト対象のPod以下の優先度を持つ場合には決して発生しません。そのような状況でプリエンプションが発生した場合、問題を報告してください。 ### Podはプリエンプトされたが、プリエンプトさせたPodがスケジューリングされない Podがプリエンプトされると、それらのPodが要求した猶予期間が与えられます。そのデフォルトは30秒です。 Podがその期間内に終了しない場合、強制終了されます。プリエンプトされたPodがなくなれば、プリエンプトさせたPodはスケジューリング可能です。 プリエンプトさせたPodがプリエンプトされたPodの終了を待っている間に、より優先度の高いPodが同じノードに対して作成されることもあります。この場合、スケジューラーはプリエンプトさせたPodの代わりに優先度の高いPodをスケジューリングします。 これは予期された挙動です。優先度の高いPodは優先度の低いPodに取って代わります。 ### 優先度の高いPodが優先度の低いPodより先にプリエンプトされる スケジューラーは待機状態のPodが実行可能なノードを探します。ノードが見つからない場合、スケジューラーは任意のノードから優先度の低いPodを追い出し、待機状態のPodのためのリソースを確保しようとします。 仮に優先度の低いPodが動いているノードが待機状態のPodを動かすために適切ではない場合、スケジューラーは他のノードで動いているPodと比べると、優先度の高いPodが動いているノードをプリエンプションの対象に選ぶことがあります。この場合もプリエンプトされるPodはプリエンプトを起こしたPodよりも優先度が低い必要があります。 複数のノードがプリエンプションの対象にできる場合、スケジューラーは優先度が最も低いPodのあるノードを選ぼうとします。しかし、そのようなPodがPodDisruptionBudgetを持っており、プリエンプトするとPDBに反する場合はスケジューラーは優先度の高いPodのあるノードを選ぶこともあります。 複数のノードがプリエンプションの対象として利用可能で、上記の状況に当てはまらない場合、スケジューラーは優先度の最も低いノードを選択します。 ## Podの優先度とQoSの相互作用 {#interactions-of-pod-priority-and-qos} Podの優先度と{{< glossary_tooltip text=\"QoSクラス\" term_id=\"qos-class\" >}}は直交する機能で、わずかに相互作用がありますが、デフォルトではQoSクラスによる優先度の設定の制約はありません。スケジューラーのプリエンプションのロジックはプリエンプションの対象を決めるときにQoSクラスは考慮しません。 プリエンプションはPodの優先度を考慮し、優先度が最も低いものを候補とします。より優先度の高いPodは優先度の低いPodを追い出すだけではプリエンプトを起こしたPodのスケジューリングに不十分な場合と、`PodDisruptionBudget`により優先度の低いPodが保護されている場合のみ対象になります。 QoSとPodの優先度の両方を考慮するコンポーネントは[リソース不足によりkubeletがPodを追い出す](/docs/tasks/administer-cluster/out-of-resource/)のみです。 kubeletは追い出すPodの順位付けを次の順で行います。枯渇したリソースを要求以上に使用しているか、優先度、枯渇したリソースの消費量の複数のPodの要求に対する相対値。 詳細は[エンドユーザーのPodの追い出し](/docs/tasks/administer-cluster/out-of-resource/#evicting-end-user-pods)を参照してください。 kubeletによるリソース不足時のPodの追い出しでは、リソースの消費が要求を超えないPodは追い出されません。優先度の低いPodのリソースの利用量がその要求を超えていなければ、追い出されることはありません。より優先度が高く、要求を超えてリソースを使用しているPodが追い出されます。 ## {{% heading \"whatsnext\" %}} * PriorityClassと関連付けてResourceQuotaを使用することに関して [デフォルトで優先度クラスの消費を制限する](/ja/docs/concepts/policy/resource-quotas/#limit-priority-class-consumption-by-default) </del>"}
{"_id":"q-en-website-995788068759841773a26435655d2eb80690d82fa97874e77c62b7ee88d95bad","text":"Talking to the control-plane node with the appropriate credentials, run: ```bash <del> kubectl drain <node name> --delete-local-data --force --ignore-daemonsets </del> <ins> kubectl drain <node name> --delete-emptydir-data --force --ignore-daemonsets </ins> ``` Before removing the node, reset the state installed by `kubeadm`:"}
{"_id":"q-en-website-99bcac23e51e25dfd813d5cebfe29876396baf62e9d66bb12f888fba9ba86030","text":"<ins> --- title: Node Shutdowns content_type: concept weight: 10 --- <!-- overview --> In a Kubernetes cluster, a {{< glossary_tooltip text=\"node\" term_id=\"node\" >}} can be shutdown in a planned graceful way or unexpectedly because of reasons such as a power outage or something else external. A node shutdown could lead to workload failure if the node is not drained before the shutdown. A node shutdown can be either **graceful** or **non-graceful**. <!-- body --> ## Graceful node shutdown {#graceful-node-shutdown} {{< feature-state feature_gate_name=\"GracefulNodeShutdown\" >}} The kubelet attempts to detect node system shutdown and terminates pods running on the node. Kubelet ensures that pods follow the normal [pod termination process](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination) during the node shutdown. During node shutdown, the kubelet does not accept new Pods (even if those Pods are already bound to the node). The Graceful node shutdown feature depends on systemd since it takes advantage of [systemd inhibitor locks](https://www.freedesktop.org/wiki/Software/systemd/inhibit/) to delay the node shutdown with a given duration. Graceful node shutdown is controlled with the `GracefulNodeShutdown` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) which is enabled by default in 1.21. Note that by default, both configuration options described below, `shutdownGracePeriod` and `shutdownGracePeriodCriticalPods` are set to zero, thus not activating the graceful node shutdown functionality. To activate the feature, the two kubelet config settings should be configured appropriately and set to non-zero values. Once systemd detects or notifies node shutdown, the kubelet sets a `NotReady` condition on the Node, with the `reason` set to `\"node is shutting down\"`. The kube-scheduler honors this condition and does not schedule any Pods onto the affected node; other third-party schedulers are expected to follow the same logic. This means that new Pods won't be scheduled onto that node and therefore none will start. The kubelet **also** rejects Pods during the `PodAdmission` phase if an ongoing node shutdown has been detected, so that even Pods with a {{< glossary_tooltip text=\"toleration\" term_id=\"toleration\" >}} for `node.kubernetes.io/not-ready:NoSchedule` do not start there. At the same time when kubelet is setting that condition on its Node via the API, the kubelet also begins terminating any Pods that are running locally. During a graceful shutdown, kubelet terminates pods in two phases: 1. Terminate regular pods running on the node. 2. Terminate [critical pods](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/#marking-pod-as-critical) running on the node. Graceful node shutdown feature is configured with two [`KubeletConfiguration`](/docs/tasks/administer-cluster/kubelet-config-file/) options: * `shutdownGracePeriod`: * Specifies the total duration that the node should delay the shutdown by. This is the total grace period for pod termination for both regular and [critical pods](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/#marking-pod-as-critical). * `shutdownGracePeriodCriticalPods`: * Specifies the duration used to terminate [critical pods](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/#marking-pod-as-critical) during a node shutdown. This value should be less than `shutdownGracePeriod`. {{< note >}} There are cases when Node termination was cancelled by the system (or perhaps manually by an administrator). In either of those situations the Node will return to the `Ready` state. However, Pods which already started the process of termination will not be restored by kubelet and will need to be re-scheduled. {{< /note >}} For example, if `shutdownGracePeriod=30s`, and `shutdownGracePeriodCriticalPods=10s`, kubelet will delay the node shutdown by 30 seconds. During the shutdown, the first 20 (30-10) seconds would be reserved for gracefully terminating normal pods, and the last 10 seconds would be reserved for terminating [critical pods](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/#marking-pod-as-critical). {{< note >}} When pods were evicted during the graceful node shutdown, they are marked as shutdown. Running `kubectl get pods` shows the status of the evicted pods as `Terminated`. And `kubectl describe pod` indicates that the pod was evicted because of node shutdown: ``` Reason:         Terminated Message:        Pod was terminated in response to imminent node shutdown. ``` {{< /note >}} ### Pod Priority based graceful node shutdown {#pod-priority-graceful-node-shutdown} {{< feature-state feature_gate_name=\"GracefulNodeShutdownBasedOnPodPriority\" >}} To provide more flexibility during graceful node shutdown around the ordering of pods during shutdown, graceful node shutdown honors the PriorityClass for Pods, provided that you enabled this feature in your cluster. The feature allows cluster administers to explicitly define the ordering of pods during graceful node shutdown based on [priority classes](/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass). The [Graceful Node Shutdown](#graceful-node-shutdown) feature, as described above, shuts down pods in two phases, non-critical pods, followed by critical pods. If additional flexibility is needed to explicitly define the ordering of pods during shutdown in a more granular way, pod priority based graceful shutdown can be used. When graceful node shutdown honors pod priorities, this makes it possible to do graceful node shutdown in multiple phases, each phase shutting down a particular priority class of pods. The kubelet can be configured with the exact phases and shutdown time per phase. Assuming the following custom pod [priority classes](/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass) in a cluster, |Pod priority class name|Pod priority class value| |-------------------------|------------------------| |`custom-class-a`         | 100000                 | |`custom-class-b`         | 10000                  | |`custom-class-c`         | 1000                   | |`regular/unset`          | 0                      | Within the [kubelet configuration](/docs/reference/config-api/kubelet-config.v1beta1/) the settings for `shutdownGracePeriodByPodPriority` could look like: |Pod priority class value|Shutdown period| |------------------------|---------------| | 100000                 |10 seconds     | | 10000                  |180 seconds    | | 1000                   |120 seconds    | | 0                      |60 seconds     | The corresponding kubelet config YAML configuration would be: ```yaml shutdownGracePeriodByPodPriority: - priority: 100000 shutdownGracePeriodSeconds: 10 - priority: 10000 shutdownGracePeriodSeconds: 180 - priority: 1000 shutdownGracePeriodSeconds: 120 - priority: 0 shutdownGracePeriodSeconds: 60 ``` The above table implies that any pod with `priority` value >= 100000 will get just 10 seconds to stop, any pod with value >= 10000 and < 100000 will get 180 seconds to stop, any pod with value >= 1000 and < 10000 will get 120 seconds to stop. Finally, all other pods will get 60 seconds to stop. One doesn't have to specify values corresponding to all of the classes. For example, you could instead use these settings: |Pod priority class value|Shutdown period| |------------------------|---------------| | 100000                 |300 seconds    | | 1000                   |120 seconds    | | 0                      |60 seconds     | In the above case, the pods with `custom-class-b` will go into the same bucket as `custom-class-c` for shutdown. If there are no pods in a particular range, then the kubelet does not wait for pods in that priority range. Instead, the kubelet immediately skips to the next priority class value range. If this feature is enabled and no configuration is provided, then no ordering action will be taken. Using this feature requires enabling the `GracefulNodeShutdownBasedOnPodPriority` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/), and setting `ShutdownGracePeriodByPodPriority` in the [kubelet config](/docs/reference/config-api/kubelet-config.v1beta1/) to the desired configuration containing the pod priority class values and their respective shutdown periods. {{< note >}} The ability to take Pod priority into account during graceful node shutdown was introduced as an Alpha feature in Kubernetes v1.23. In Kubernetes {{< skew currentVersion >}} the feature is Beta and is enabled by default. {{< /note >}} Metrics `graceful_shutdown_start_time_seconds` and `graceful_shutdown_end_time_seconds` are emitted under the kubelet subsystem to monitor node shutdowns. ## Non-graceful node shutdown handling {#non-graceful-node-shutdown} {{< feature-state feature_gate_name=\"NodeOutOfServiceVolumeDetach\" >}} A node shutdown action may not be detected by kubelet's Node Shutdown Manager, either because the command does not trigger the inhibitor locks mechanism used by kubelet or because of a user error, i.e., the ShutdownGracePeriod and ShutdownGracePeriodCriticalPods are not configured properly. Please refer to above section [Graceful Node Shutdown](#graceful-node-shutdown) for more details. When a node is shutdown but not detected by kubelet's Node Shutdown Manager, the pods that are part of a {{< glossary_tooltip text=\"StatefulSet\" term_id=\"statefulset\" >}} will be stuck in terminating status on the shutdown node and cannot move to a new running node. This is because kubelet on the shutdown node is not available to delete the pods so the StatefulSet cannot create a new pod with the same name. If there are volumes used by the pods, the VolumeAttachments will not be deleted from the original shutdown node so the volumes used by these pods cannot be attached to a new running node. As a result, the application running on the StatefulSet cannot function properly. If the original shutdown node comes up, the pods will be deleted by kubelet and new pods will be created on a different running node. If the original shutdown node does not come up, these pods will be stuck in terminating status on the shutdown node forever. To mitigate the above situation, a user can manually add the taint `node.kubernetes.io/out-of-service` with either `NoExecute` or `NoSchedule` effect to a Node marking it out-of-service. If the `NodeOutOfServiceVolumeDetach`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled on {{< glossary_tooltip text=\"kube-controller-manager\" term_id=\"kube-controller-manager\" >}}, and a Node is marked out-of-service with this taint, the pods on the node will be forcefully deleted if there are no matching tolerations on it and volume detach operations for the pods terminating on the node will happen immediately. This allows the Pods on the out-of-service node to recover quickly on a different node. During a non-graceful shutdown, Pods are terminated in the two phases: 1. Force delete the Pods that do not have matching `out-of-service` tolerations. 2. Immediately perform detach volume operation for such pods. {{< note >}} - Before adding the taint `node.kubernetes.io/out-of-service`, it should be verified that the node is already in shutdown or power off state (not in the middle of restarting). - The user is required to manually remove the out-of-service taint after the pods are moved to a new node and the user has checked that the shutdown node has been recovered since the user was the one who originally added the taint. {{< /note >}} ### Forced storage detach on timeout {#storage-force-detach-on-timeout} In any situation where a pod deletion has not succeeded for 6 minutes, kubernetes will force detach volumes being unmounted if the node is unhealthy at that instant. Any workload still running on the node that uses a force-detached volume will cause a violation of the [CSI specification](https://github.com/container-storage-interface/spec/blob/master/spec.md#controllerunpublishvolume), which states that `ControllerUnpublishVolume` \"**must** be called after all `NodeUnstageVolume` and `NodeUnpublishVolume` on the volume are called and succeed\". In such circumstances, volumes on the node in question might encounter data corruption. The forced storage detach behaviour is optional; users might opt to use the \"Non-graceful node shutdown\" feature instead. Force storage detach on timeout can be disabled by setting the `disable-force-detach-on-timeout` config field in `kube-controller-manager`. Disabling the force detach on timeout feature means that a volume that is hosted on a node that is unhealthy for more than 6 minutes will not have its associated [VolumeAttachment](/docs/reference/kubernetes-api/config-and-storage-resources/volume-attachment-v1/) deleted. After this setting has been applied, unhealthy pods still attached to a volumes must be recovered via the [Non-Graceful Node Shutdown](#non-graceful-node-shutdown) procedure mentioned above. {{< note >}} - Caution must be taken while using the [Non-Graceful Node Shutdown](#non-graceful-node-shutdown) procedure. - Deviation from the steps documented above can result in data corruption. {{< /note >}} ## {{% heading \"whatsnext\" %}} Learn more about the following: * Blog: [Non-Graceful Node Shutdown](/blog/2023/08/16/kubernetes-1-28-non-graceful-node-shutdown-ga/). * Cluster Architecture: [Nodes](/docs/concepts/architecture/nodes/). </ins>"}
{"_id":"q-en-website-9bf05b1d331ed22201a5709f858e411b1d96f0f09600fa0e2bf4f6083b389b08","text":"<ins> --- title: Podの優先度とプリエンプション content_type: concept weight: 90 --- <!-- overview --> {{< feature-state for_k8s_version=\"v1.14\" state=\"stable\" >}} [Pod](/ja/docs/concepts/workloads/pods/)は _priority_（優先度）を持つことができます。 優先度は他のPodに対する相対的なPodの重要度を示します。 もしPodをスケジューリングできないときには、スケジューラーはそのPodをスケジューリングできるようにするため、優先度の低いPodをプリエンプトする（追い出す）ことを試みます。 <!-- body --> {{< warning >}} クラスターの全てのユーザーが信用されていない場合、悪意のあるユーザーが可能な範囲で最も高い優先度のPodを作成することが可能です。これは他のPodが追い出されたりスケジューリングできない状態を招きます。 管理者はResourceQuotaを使用して、ユーザーがPodを高い優先度で作成することを防ぐことができます。 詳細は[デフォルトで優先度クラスの消費を制限する](/ja/docs/concepts/policy/resource-quotas/#limit-priority-class-consumption-by-default) を参照してください。 {{< /warning >}} ## 優先度とプリエンプションを使う方法 優先度とプリエンプションを使うには、 1.  1つまたは複数の[PriorityClass](#priorityclass)を追加します 1.  追加したPriorityClassを[`priorityClassName`](#pod-priority)に設定したPodを作成します。 もちろんPodを直接作る必要はありません。 一般的には`priorityClassName`をDeploymentのようなコレクションオブジェクトのPodテンプレートに追加します。 これらの手順のより詳しい情報については、この先を読み進めてください。 {{< note >}} Kubernetesには最初から既に2つのPriorityClassが設定された状態になっています。 `system-cluster-critical`と`system-node-critical`です。 これらは汎用のクラスであり、[重要なコンポーネントが常に最初にスケジュールされることを保証する](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/)ために使われます。 {{< /note >}} ## PriorityClass PriorityClassはnamespaceによらないオブジェクトで、優先度クラスの名称から優先度を表す整数値への対応を定義します。 PriorityClassオブジェクトのメタデータの`name`フィールドにて名称を指定します。 値は`value`フィールドで指定し、必須です。 値が大きいほど、高い優先度を示します。 PriorityClassオブジェクトの名称は[DNSサブドメイン名](/ja/docs/concepts/overview/working-with-objects/names#dns-subdomain-names)として適切であり、かつ`system-`から始まってはいけません。 PriorityClassオブジェクトは10億以下の任意の32ビットの整数値を持つことができます。 それよりも大きな値は通常はプリエンプトや追い出すべきではない重要なシステム用のPodのために予約されています。 クラスターの管理者は割り当てたい優先度に対して、PriorityClassオブジェクトを1つずつ作成すべきです。 PriorityClassは任意でフィールド`globalDefault`と`description`を設定可能です。 `globalDefault`フィールドは`priorityClassName`が指定されないPodはこのPriorityClassを使うべきであることを示します。`globalDefault`がtrueに設定されたPriorityClassはシステムで一つのみ存在可能です。`globalDefault`が設定されたPriorityClassが存在しない場合は、`priorityClassName`が設定されていないPodの優先度は0に設定されます。 `description`フィールドは任意の文字列です。クラスターの利用者に対して、PriorityClassをどのような時に使うべきか示すことを意図しています。 ### PodPriorityと既存のクラスターに関する注意 -   もし既存のクラスターをこの機能がない状態でアップグレードすると、既存のPodの優先度は実質的に0になります。 -   `globalDefault`が`true`に設定されたPriorityClassを追加しても、既存のPodの優先度は変わりません。PriorityClassのそのような値は、PriorityClassが追加された以後に作成されたPodのみに適用されます。 -   PriorityClassを削除した場合、削除されたPriorityClassの名前を使用する既存のPodは変更されませんが、削除されたPriorityClassの名前を使うPodをそれ以上作成することはできなくなります。 ### PriorityClassの例 ```yaml apiVersion: scheduling.k8s.io/v1 kind: PriorityClass metadata: name: high-priority value: 1000000 globalDefault: false description: \"この優先度クラスはXYZサービスのPodに対してのみ使用すべきです。\" ``` ## 非プリエンプトのPriorityClass {#non-preempting-priority-class} {{< feature-state for_k8s_version=\"v1.24\" state=\"stable\" >}} `preemptionPolicy: Never`と設定されたPodは、スケジューリングのキューにおいて他の優先度の低いPodよりも優先されますが、他のPodをプリエンプトすることはありません。 スケジューリングされるのを待つ非プリエンプトのPodは、リソースが十分に利用可能になるまでスケジューリングキューに残ります。 非プリエンプトのPodは、他のPodと同様に、スケジューラーのバックオフの対象になります。これは、スケジューラーがPodをスケジューリングしようと試みたものの失敗した場合、低い頻度で再試行するようにして、より優先度の低いPodが先にスケジューリングされることを許します。 非プリエンプトのPodは、他の優先度の高いPodにプリエンプトされる可能性はあります。 `preemptionPolicy`はデフォルトでは`PreemptLowerPriority`に設定されており、これが設定されているPodは優先度の低いPodをプリエンプトすることを許容します。これは既存のデフォルトの挙動です。 `preemptionPolicy`を`Never`に設定すると、これが設定されたPodはプリエンプトを行わないようになります。 ユースケースの例として、データサイエンスの処理を挙げます。 ユーザーは他の処理よりも優先度を高くしたいジョブを追加できますが、そのとき既存の実行中のPodの処理結果をプリエンプトによって破棄させたくはありません。 `preemptionPolicy: Never`が設定された優先度の高いジョブは、他の既にキューイングされたPodよりも先に、クラスターのリソースが「自然に」開放されたときにスケジューリングされます。 ### 非プリエンプトのPriorityClassの例 ```yaml apiVersion: scheduling.k8s.io/v1 kind: PriorityClass metadata: name: high-priority-nonpreempting value: 1000000 preemptionPolicy: Never globalDefault: false description: \"この優先度クラスは他のPodをプリエンプトさせません。\" ``` ## Podの優先度 {#pod-priority} 一つ以上のPriorityClassがあれば、仕様にPriorityClassを指定したPodを作成することができるようになります。優先度のアドミッションコントローラーは`priorityClassName`フィールドを使用し、優先度の整数値を設定します。PriorityClassが見つからない場合、そのPodの作成は拒否されます。 下記のYAMLは上記の例で作成したPriorityClassを使用するPodの設定の例を示します。優先度のアドミッションコントローラーは仕様を確認し、このPodの優先度は1000000であると設定します。 ```yaml apiVersion: v1 kind: Pod metadata: name: nginx labels: env: test spec: containers: - name: nginx image: nginx imagePullPolicy: IfNotPresent priorityClassName: high-priority ``` ### スケジューリング順序におけるPodの優先度の効果 Podの優先度が有効な場合、スケジューラーは待機状態のPodをそれらの優先度順に並べ、スケジューリングキューにおいてより優先度の低いPodよりも前に来るようにします。その結果、その条件を満たしたときには優先度の高いPodは優先度の低いPodより早くスケジューリングされます。優先度の高いPodがスケジューリングできない場合は、スケジューラーは他の優先度の低いPodのスケジューリングも試みます。 ## プリエンプション Podが作成されると、スケジューリング待ちのキューに入り待機状態になります。スケジューラーはキューからPodを取り出し、ノードへのスケジューリングを試みます。Podに指定された条件を全て満たすノードが見つからない場合は、待機状態のPodのためにプリエンプションロジックが発動します。待機状態のPodをPと呼ぶことにしましょう。プリエンプションロジックはPよりも優先度の低いPodを一つ以上追い出せばPをスケジューリングできるようになるノードを探します。そのようなノードがあれば、優先度の低いPodはノードから追い出されます。Podが追い出された後に、Pはノードへスケジューリング可能になります。 ### ユーザーへ開示される情報 Pod PがノードNのPodをプリエンプトした場合、ノードNの名称がPのステータスの`nominatedNodeName`フィールドに設定されます。このフィールドはスケジューラーがPod Pのために予約しているリソースの追跡を助け、ユーザーにクラスターにおけるプリエンプトに関する情報を与えます。 Pod Pは必ずしも「指名したノード」へスケジューリングされないことに注意してください。スケジューラーは、他のノードに対して処理を繰り返す前に、常に「指定したノード」に対して試行します。Podがプリエンプトされると、そのPodは終了までの猶予期間を得ます。スケジューラーがPodの終了を待つ間に他のノードが利用可能になると、スケジューラーは他のノードをPod Pのスケジューリング先にすることがあります。この結果、Podの`nominatedNodeName`と`nodeName`は必ずしも一致しません。また、スケジューラーがノードNのPodをプリエンプトさせた後に、Pod Pよりも優先度の高いPodが来た場合、スケジューラーはノードNをその新しい優先度の高いPodへ与えることもあります。このような場合は、スケジューラーはPod Pの`nominatedNodeName`を消去します。これによって、スケジューラーはPod Pが他のノードのPodをプリエンプトさせられるようにします。 ### プリエンプトの制限 #### プリエンプトされるPodの正常終了 Podがプリエンプトされると、[猶予期間](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination)が与えられます。 Podは作業を完了し、終了するために十分な時間が与えられます。仮にそうでない場合、強制終了されます。この猶予期間によって、スケジューラーがPodをプリエンプトした時刻と、待機状態のPod Pがノード Nにスケジュール可能になるまでの時刻の間に間が開きます。この間、スケジューラーは他の待機状態のPodをスケジュールしようと試みます。プリエンプトされたPodが終了したら、スケジューラーは待ち行列にあるPodをスケジューリングしようと試みます。そのため、Podがプリエンプトされる時刻と、Pがスケジュールされた時刻には間が開くことが一般的です。この間を最小にするには、優先度の低いPodの猶予期間を0または小さい値にする方法があります。 #### PodDisruptionBudgetは対応するが、保証されない [PodDisruptionBudget](/docs/concepts/workloads/pods/disruptions/) (PDB)は、アプリケーションのオーナーが冗長化されたアプリケーションのPodが意図的に中断される数の上限を設定できるようにするものです。KubernetesはPodをプリエンプトする際にPDBに対応しますが、PDBはベストエフォートで考慮します。スケジューラーはプリエンプトさせたとしてもPDBに違反しないPodを探します。そのようなPodが見つからない場合でもプリエンプションは実行され、PDBに反しますが優先度の低いPodが追い出されます。 #### 優先度の低いPodにおけるPod間のアフィニティ 次の条件が真の場合のみ、ノードはプリエンプションの候補に入ります。 「待機状態のPodよりも優先度の低いPodをノードから全て追い出したら、待機状態のPodをノードへスケジュールできるか」 {{< note >}} プリエンプションは必ずしも優先度の低いPodを全て追い出しません。 優先度の低いPodを全て追い出さなくても待機状態のPodがスケジューリングできる場合、一部のPodのみ追い出されます。 このような場合であったとしても、上記の条件は真である必要があります。偽であれば、そのノードはプリエンプションの対象とはされません。 {{< /note >}} 待機状態のPodが、優先度の低いPodとの間でPod間の{{< glossary_tooltip text=\"アフィニティ\" term_id=\"affinity\" >}}を持つ場合、Pod間のアフィニティはそれらの優先度の低いPodがなければ満たされません。この場合、スケジューラーはノードのどのPodもプリエンプトしようとはせず、代わりに他のノードを探します。スケジューラーは適切なノードを探せる場合と探せない場合があります。この場合、待機状態のPodがスケジューリングされる保証はありません。 この問題に対して推奨される解決策は、優先度が同一または高いPodに対してのみPod間のアフィニティを作成することです。 #### 複数ノードに対するプリエンプション Pod PがノードNにスケジューリングできるよう、ノードNがプリエンプションの対象となったとします。 他のノードのPodがプリエンプトされた場合のみPが実行可能になることもあります。下記に例を示します。 *   Pod PをノードNに配置することを検討します。 *   Pod QはノードNと同じゾーンにある別のノードで実行中です。 *   Pod Pはゾーンに対するQへのアンチアフィニティを持ちます (`topologyKey: topology.kubernetes.io/zone`)。 *   Pod Pと、ゾーン内の他のPodに対しては他のアンチアフィニティはない状態です。 *   Pod PをノードNへスケジューリングするには、Pod Qをプリエンプトすることが考えられますが、スケジューラーは複数ノードにわたるプリエンプションは行いません。そのため、Pod PはノードNへはスケジューリングできないとみなされます。 Pod Qがそのノードから追い出されると、Podアンチアフィニティに違反しなくなるので、Pod PはノードNへスケジューリング可能になります。 複数ノードに対するプリエンプションに関しては、十分な需要があり、合理的な性能を持つアルゴリズムを見つけられた場合に、将来的に機能追加を検討する可能性があります。 ## トラブルシューティング Podの優先度とプリエンプションは望まない副作用をもたらす可能性があります。 いくつかの起こりうる問題と、その対策について示します。 ### Podが不必要にプリエンプトされる プリエンプションは、リソースが不足している場合に優先度の高い待機状態のPodのためにクラスターの既存のPodを追い出します。 誤って高い優先度をPodに割り当てると、意図しない高い優先度のPodはクラスター内でプリエンプションを引き起こす可能性があります。Podの優先度はPodの仕様の`priorityClassName`フィールドにて指定されます。優先度を示す整数値へと変換された後、`podSpec`の`priority`へ設定されます。 この問題に対処するには、Podの`priorityClassName`をより低い優先度に変更するか、このフィールドを未設定にすることができます。`priorityClassName`が未設定の場合、デフォルトでは優先度は0とされます。 Podがプリエンプトされたとき、プリエンプトされたPodのイベントが記録されます。 プリエンプションはPodに必要なリソースがクラスターにない場合のみ起こるべきです。 このような場合、プリエンプションはプリエンプトされるPodよりも待機状態のPodの優先度が高い場合のみ発生します。 プリエンプションは待機状態のPodがない場合や待機状態のPodがプリエンプト対象のPod以下の優先度を持つ場合には決して発生しません。そのような状況でプリエンプションが発生した場合、問題を報告してください。 ### Podはプリエンプトされたが、プリエンプトさせたPodがスケジューリングされない Podがプリエンプトされると、それらのPodが要求した猶予期間が与えられます。そのデフォルトは30秒です。 Podがその期間内に終了しない場合、強制終了されます。プリエンプトされたPodがなくなれば、プリエンプトさせたPodはスケジューリング可能です。 プリエンプトさせたPodがプリエンプトされたPodの終了を待っている間に、より優先度の高いPodが同じノードに対して作成されることもあります。この場合、スケジューラーはプリエンプトさせたPodの代わりに優先度の高いPodをスケジューリングします。 これは予期された挙動です。優先度の高いPodは優先度の低いPodに取って代わります。 ### 優先度の高いPodが優先度の低いPodより先にプリエンプトされる スケジューラーは待機状態のPodが実行可能なノードを探します。ノードが見つからない場合、スケジューラーは任意のノードから優先度の低いPodを追い出し、待機状態のPodのためのリソースを確保しようとします。 仮に優先度の低いPodが動いているノードが待機状態のPodを動かすために適切ではない場合、スケジューラーは他のノードで動いているPodと比べると、優先度の高いPodが動いているノードをプリエンプションの対象に選ぶことがあります。この場合もプリエンプトされるPodはプリエンプトを起こしたPodよりも優先度が低い必要があります。 複数のノードがプリエンプションの対象にできる場合、スケジューラーは優先度が最も低いPodのあるノードを選ぼうとします。しかし、そのようなPodがPodDisruptionBudgetを持っており、プリエンプトするとPDBに反する場合はスケジューラーは優先度の高いPodのあるノードを選ぶこともあります。 複数のノードがプリエンプションの対象として利用可能で、上記の状況に当てはまらない場合、スケジューラーは優先度の最も低いノードを選択します。 ## Podの優先度とQoSの相互作用 {#interactions-of-pod-priority-and-qos} Podの優先度と{{< glossary_tooltip text=\"QoSクラス\" term_id=\"qos-class\" >}}は直交する機能で、わずかに相互作用がありますが、デフォルトではQoSクラスによる優先度の設定の制約はありません。スケジューラーのプリエンプションのロジックはプリエンプションの対象を決めるときにQoSクラスは考慮しません。 プリエンプションはPodの優先度を考慮し、優先度が最も低いものを候補とします。より優先度の高いPodは優先度の低いPodを追い出すだけではプリエンプトを起こしたPodのスケジューリングに不十分な場合と、`PodDisruptionBudget`により優先度の低いPodが保護されている場合のみ対象になります。 kubeletは[node-pressureによる退避](/docs/concepts/scheduling-eviction/node-pressure-eviction/)を行うPodの順番を決めるために、優先度を利用します。QoSクラスを使用して、最も退避される可能性の高いPodの順番を推定することができます。 kubeletは追い出すPodの順位付けを次の順で行います。 1. 枯渇したリソースを要求以上に使用しているか 1. Podの優先度 1. 要求に対するリソースの使用量 詳細は[kubeletによるPodの退避](/docs/concepts/scheduling-eviction/node-pressure-eviction/#pod-selection-for-kubelet-eviction)を参照してください。 kubeletによるリソース不足時のPodの追い出しでは、リソースの消費が要求を超えないPodは追い出されません。優先度の低いPodのリソースの利用量がその要求を超えていなければ、追い出されることはありません。より優先度が高く、要求を超えてリソースを使用しているPodが追い出されます。 ## {{% heading \"whatsnext\" %}} * PriorityClassと関連付けてResourceQuotaを使用することに関して [デフォルトで優先度クラスの消費を制限する](/ja/docs/concepts/policy/resource-quotas/#limit-priority-class-consumption-by-default) * [Podの破壊](/docs/concepts/workloads/pods/disruptions/)を読む * [APIを起点とした退避](/ja/docs/concepts/scheduling-eviction/api-eviction/)を読む * [Node-pressureによる退避](/docs/concepts/scheduling-eviction/node-pressure-eviction/)を読む </ins>"}
{"_id":"q-en-website-9c2ade6cdf26159078192e880bfa9f709ca8240448f7006570689573dd5f089c","text":"* `apiserver_flowcontrol_request_queue_length_after_enqueue` is a histogram vector of queue lengths for the queues, broken down by <del> the labels `priorityLevel` and `flowSchema`, as sampled by the </del> <ins> the labels `priority_level` and `flow_schema`, as sampled by the </ins> enqueued requests.  Each request that gets queued contributes one sample to its histogram, reporting the length of the queue just after the request was added.  Note that this produces different"}
{"_id":"q-en-website-9d051e9a6abda298694935e080d52f1ab68332f38e1051007ed3cccf581febe1","text":"<ins> --- layout: blog title: \"Don't Panic: Kubernetes and Docker\" date: 2020-12-02 slug: dont-panic-kubernetes-and-docker --- **著者:** Jorge Castro, Duffie Cooley, Kat Cosgrove, Justin Garrison, Noah Kantrowitz, Bob Killen, Rey Lejano, Dan “POP” Papandrea, Jeffrey Sica, Davanum “Dims” Srinivas Kubernetesはv1.20より新しいバージョンで、コンテナランタイムとして[Dockerをサポートしません](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.20.md#deprecation)。 **パニックを起こす必要はありません。これはそれほど抜本的なものではないのです。** 概要: ランタイムとしてのDockerは、Kubernetesのために開発された[Container Runtime Interface(CRI)](https://kubernetes.io/blog/2016/12/container-runtime-interface-cri-in-kubernetes/)を利用しているランタイムを選んだ結果としてサポートされなくなります。しかし、Dockerによって生成されたイメージはこれからも、今までもそうだったように、みなさんのクラスターで使用可能です。 もし、あなたがKubernetesのエンドユーザーであるならば、多くの変化はないでしょう。これはDockerの死を意味するものではありませんし、開発ツールとして今後Dockerを使用するべきでない、使用することは出来ないと言っているのでもありません。Dockerはコンテナを作成するのに便利なツールですし、docker buildコマンドで作成されたImageはKubernetesクラスタ上でこれからも動作可能なのです。 もし、GKE、EKS、AKSといったマネージドKubernetesサービス(それらはデフォルトで[containerdを使用しています](https://github.com/Azure/AKS/releases/tag/2020-11-16))を使っているのなら、Workerノードがサポート対象のRuntimeを使用しているか、Dockerのサポートが将来のK8sバージョンで切れる前に確認しておく必要があるでしょう。 もし、ノードをカスタマイズしているのなら、環境やRuntimeの仕様に合わせて更新する必要があるでしょう。サービスプロバイダーと確認し、アップグレードのための適切なテストと計画を立ててください。 もし、ご自身でClusterを管理しているのなら、やはり問題が発生する前に必要な対応を行う必要があります。v1.20の時点で、Dockerの使用についての警告メッセージが表示されるようになります。将来のKubernetesリリース(現在の計画では2021年下旬のv1.22)でDockerのRuntimeとしての使用がサポートされなくなれば、containerdやCRI-Oといった他のサポート対象のRuntimeに切り替える必要があります。切り替える際、そのRuntimeが現在使用しているDocker Daemonの設定をサポートすることを確認してください。(Loggingなど) ## では、なぜ混乱が生じ、誰もが恐怖に駆られているのか。 ここで議論になっているのは2つの異なる場面についてであり、それが混乱の原因になっています。Kubernetesクラスターの内部では、Container runtimeと呼ばれるものがあり、それはImageをPullし起動する役目を持っています。Dockerはその選択肢として人気があります(他にはcontainerdやCRI-Oが挙げられます)が、しかしDockerはそれ自体がKubernetesの一部として設計されているわけではありません。これが問題の原因となっています。 お分かりかと思いますが、ここで”Docker”と呼んでいるものは、ある1つのものではなく、その技術的な体系の全体であり、その一部には\"containerd\"と呼ばれるものもあり、これはそれ自体がハイレベルなContainer runtimeとなっています。Dockerは素晴らしいもので、便利です。なぜなら、多くのUXの改善がされており、それは人間が開発を行うための操作を簡単にしているのです。しかし、それらはKubernetesに必要なものではありません。Kubernetesは人間ではないからです。 このhuman-friendlyな抽象化レイヤが作られてために、結果としてはKubernetesクラスタはDockershimと呼ばれるほかのツールを使い、本当に必要な機能つまりcontainerdを利用してきました。これは素晴らしいとは言えません。なぜなら、我々がメンテする必要のあるものが増えますし、それは問題が発生する要因ともなります。今回の変更で実際に行われることというのは、Dockershimを最も早い場合でv1.23のリリースでkubeletから除外することです。その結果として、Dockerのサポートがなくなるということなのです。 ここで、containerdがDockerに含まれているなら、なぜDockershimが必要なのかと疑問に思われる方もいるでしょう。 DockerはCRI([Container Runtime Interface](https://kubernetes.io/blog/2016/12/container-runtime-interface-cri-in-kubernetes/))に準拠していません。もしそうであればshimは必要ないのですが、現実はそうでありません。 しかし、これは世界の終わりでありません、心配しないでください。みなさんはContainer runtimeをDockerから他のサポート対象であるContainer runtimeに切り替えるだけでよいのです。 1つ注意すべきことは、クラスターで行われる処理のなかでDocker socket(`/var/run/docker.sock`)に依存する部分がある場合、他のRuntimeへ切り替えるとこの部分が働かなくなるでしょう。このパターンはしばしばDocker in Dockerと呼ばれます。このような場合の対応方法はたくさんあります。[kaniko](https://github.com/GoogleContainerTools/kaniko)、[img](https://github.com/genuinetools/img)、[buildah](https://github.com/containers/buildah)などです。 ## では開発者にとって、この変更は何を意味するのか。これからもDockerfileを使ってよいのか。これからもDockerでビルドを行ってよいのか。 この変更は、Dockerを直接操作している多くのみなさんとは別の場面に影響を与えるでしょう。 みなさんが開発を行う際に使用しているDockerと、Kubernetesクラスタの内部で使われているDocker runtimeは関係ありません。これがわかりにくいことは理解しています。開発者にとって、Dockerはこれからも便利なものであり、このアナウンスがあった前と変わらないでしょう。DockerでビルドされたImageは、決してDockerでだけ動作するというわけではありません。それはOCI([Open Container Initiative](https://opencontainers.org/)) Imageと呼ばれるものです。あらゆるOCI準拠のImageは、それを何のツールでビルドしたかによらず、Kubernetesから見れば同じものなのです。[containerd](https://containerd.io/)も[CRI-O](https://cri-o.io/)も、そのようなImageをPullし、起動することが出来ます。 これがコンテナの仕様について、共通の仕様を策定している理由なのです。 さて、この変更は決定しています。いくつかの問題は発生するかもしてませんが、決して壊滅的なものではなく、ほとんどの場合は良い変化となるでしょう。Kubernetesをどのように使用しているかによりますが、この変更が特に何の影響も及ぼさない人もいるでしょうし、影響がとても少ない場合もあります。長期的に見れば、物事を簡単にするのに役立つものです。 もし、この問題がまだわかりにくいとしても、心配しないでください。Kubernetesでは多くのものが変化しており、その全てに完璧に精通している人など存在しません。 経験の多寡や難易度にかかわらず、どんなことでも質問してください。我々の目標は、全ての人が将来の変化について、可能な限りの知識と理解を得られることです。 このブログが多くの質問の答えとなり、不安を和らげることができればと願っています。 別の情報をお探してあれば、[Dockershim Deprecation FAQ](/blog/2020/12/02/dockershim-faq/)を参照してください。 </ins>"}
{"_id":"q-en-website-9d1e7ecde69228214d657015524b2deafff2960cf88d1826761de950496f562c","text":"## Constraints <del> * Topology Aware Hints are not used when either `externalTrafficPolicy` or `internalTrafficPolicy` is set to `Local` on a Service. It is possible to use both features in the same cluster on different Services, just not on the same Service. </del> <ins> * Topology Aware Hints are not used when `internalTrafficPolicy` is set to `Local` on a Service. It is possible to use both features in the same cluster on different Services, just not on the same Service. </ins> * This approach will not work well for Services that have a large proportion of traffic originating from a subset of zones. Instead this assumes that incoming"}
{"_id":"q-en-website-9dd55c68cad801ed3f81f577b3230c0c7c5c3e61eeed134c9217aa066a918f4a","text":"_Nothing has changed._ ### Changed <del> - go.etcd.io/etcd: 54ba958 → 18dfb9c - k8s.io/utils: 6e3d28b → 0bdb4ca </del> <ins> _Nothing has changed._ </ins> ### Removed _Nothing has changed._ <del> # v1.19.0-rc.1 </del> <ins> # v1.20.0-beta.0 </ins> <del> ## Downloads for v1.19.0-rc.1 </del> <ins> ## Downloads for v1.20.0-beta.0 </ins> ### Source Code filename | sha512 hash -------- | ----------- <del> [kubernetes.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes.tar.gz) | d4bc1d86ff77a1a8695091207b8181a246c8964ae1dd8967392aae95197c0339c7915a016c017ecab0b9d203b3205221ca766ce568d7ee52947e7f50f057af4f [kubernetes-src.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-src.tar.gz) | 79af4e01b0d5432f92b026730a0c60523069d312858c30fdcaeaf6ee159c71f3413a5075d82c0acd9b135b7a06d5ecb0c0d38b8a8d0f301a9d9bffb35d22f029 </del> <ins> [kubernetes.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes.tar.gz) | 385e49e32bbd6996f07bcadbf42285755b8a8ef9826ee1ba42bd82c65827cf13f63e5634b834451b263a93b708299cbb4b4b0b8ddbc688433deaf6bec240aa67 [kubernetes-src.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-src.tar.gz) | 842e80f6dcad461426fb699de8a55fde8621d76a94e54288fe9939cc1a3bbd0f4799abadac2c59bcf3f91d743726dbd17e1755312ae7fec482ef560f336dbcbb </ins> ### Client binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-client-darwin-386.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-client-darwin-386.tar.gz) | 7d21bf9733810659576e67986d129208894adea3c571de662dbf80fb822e18abfc1644ea60a4e5fbe244a23b56aa973b76dafe789ead1bf7539f41bdd9bca886 [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-client-darwin-amd64.tar.gz) | b4622e06c09bb08a0dc0115bfcd991c50459c7b772889820648ed1c05a425605d10b71b92c58c119b77baa3bca209f9c75827d2cde69d128a5cfcada5f37be39 [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-client-linux-386.tar.gz) | f51032ad605543f68a2a4da3bede1f3e7be0dd63b03b751fef5f133e8d64bec02bfe7433b75e3d0c4ae122d4e0cf009095800c638d2cc81f6fb81b488f5a6dab [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-client-linux-amd64.tar.gz) | 48489d22969f69a5015988e596d597c64ea18675649afe55ad119dbbe98ba9a4104d5e323704cf1f3cbdfca3feac629d3813e260a330a72da12f1a794d054f76 [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-client-linux-arm.tar.gz) | d9f8a6f6f3d09be9c08588c2b5153a4d8cc9db496bde3da2f3af472c260566d1391cd8811f2c05d4f302db849a38432f25228d9bbb59aaaf0dfba64b33f8ee8e [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-client-linux-arm64.tar.gz) | 1c3590750a3f02e0e5845e1135cc3ab990309bdecfe64c089842a134eae57b573488531696796185ed12dde2d6f95d2e3656dd9893d04cd0adbe025513ffff30 [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-client-linux-ppc64le.tar.gz) | 158a562d5dbbe90cd56b5d757823adda1919e9b5db8005fb6e2523358e5a20628d55ec1903c0e317a0d8ac9b9a649eea23d9ea746db22b73d6d580ae8c067077 [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-client-linux-s390x.tar.gz) | 47c140567dc593caf065f295ed6006efcde010a526a96c8d3ef5f3d9a9dc6b413bc197dc822648067fe16299908ada7046c2a8a3213d4296b04b51a264ad40e9 [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-client-windows-386.tar.gz) | e25d7d4ad3e6f6e6cfba181c5871e56de2751f88b640502745f6693ddd86ccd7eef8aebaa30955afdbbd0320a5b51d4e9e17f71baab37a470aac284178a0e21c [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-client-windows-amd64.tar.gz) | fd8463b04b5d7f115104245fa1dd53de6656b349dad4cfd55f239012d4f2c1a8e35aa3f3554138df9ddfea9d7702b51a249f6db698c0cea7c36e5bc98a017fe7 </del> <ins> [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-client-darwin-amd64.tar.gz) | bde5e7d9ee3e79d1e69465a3ddb4bb36819a4f281b5c01a7976816d7c784410812dde133cdf941c47e5434e9520701b9c5e8b94d61dca77c172f87488dfaeb26 [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-client-linux-386.tar.gz) | 721bb8444c9e0d7a9f8461e3f5428882d76fcb3def6eb11b8e8e08fae7f7383630699248660d69d4f6a774124d6437888666e1fa81298d5b5518bc4a6a6b2c92 [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-client-linux-amd64.tar.gz) | 71e4edc41afbd65f813e7ecbc22b27c95f248446f005e288d758138dc4cc708735be7218af51bcf15e8b9893a3598c45d6a685f605b46f50af3762b02c32ed76 [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-client-linux-arm.tar.gz) | bbefc749156f63898973f2f7c7a6f1467481329fb430d641fe659b497e64d679886482d557ebdddb95932b93de8d1e3e365c91d4bf9f110b68bd94b0ba702ded [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-client-linux-arm64.tar.gz) | 9803190685058b4b64d002c2fbfb313308bcea4734ed53a8c340cfdae4894d8cb13b3e819ae64051bafe0fbf8b6ecab53a6c1dcf661c57640c75b0eb60041113 [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-client-linux-ppc64le.tar.gz) | bcdceea64cba1ae38ea2bab50d8fd77c53f6d673de12566050b0e3c204334610e6c19e4ace763e68b5e48ab9e811521208b852b1741627be30a2b17324fc1daf [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-client-linux-s390x.tar.gz) | 41e36d00867e90012d5d5adfabfaae8d9f5a9fd32f290811e3c368e11822916b973afaaf43961081197f2cbab234090d97d89774e674aeadc1da61f7a64708a9 [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-client-windows-386.tar.gz) | c50fec5aec2d0e742f851f25c236cb73e76f8fc73b0908049a10ae736c0205b8fff83eb3d29b1748412edd942da00dd738195d9003f25b577d6af8359d84fb2f [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-client-windows-amd64.tar.gz) | 0fd6777c349908b6d627e849ea2d34c048b8de41f7df8a19898623f597e6debd35b7bcbf8e1d43a1be3a9abb45e4810bc498a0963cf780b109e93211659e9c7e </ins> ### Server binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-server-linux-amd64.tar.gz) | 96acce78bba3779bef616de28da5d75bc4dc0b52fe0bf03b169c469ade9a8cd38b19c4620d222d67bff9ceeb0c5ebf893f55c1de02356bcebe5689890d0478f7 [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-server-linux-arm.tar.gz) | 1e561f3edbc66d2ab7f6f1ffe8dc1c01cec13ee3ba700458bd5d87202723cc832f3305a864a3b569463c96d60c9f60c03b77f210663cc40589e40515b3a32e75 [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-server-linux-arm64.tar.gz) | ba8fc011ac0e54cb1a0e0e3ee5f1cff4d877f4fdd75e15bf25b1cf817b3cf2bc85f9809d3cc76e9145f07a837960843ca68bdf02fe970c0043fc9ff7b53da021 [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-server-linux-ppc64le.tar.gz) | 1f506676284ab2f6bd3fc8a29a062f4fddf5346ef30be9363f640467c64011144381180c5bf74ec885d2f54524e82e21c745c5d2f1b191948bc40db2a09a2900 [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-server-linux-s390x.tar.gz) | 5a7101288d51297c3346d028176b4b997afd8652d6481cec82f8863a91209fec6e8a9286a9bd7543b428e6ef82c1c68a7ce0782191c4682634015a032f749554 </del> <ins> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-server-linux-amd64.tar.gz) | 30d982424ca64bf0923503ae8195b2e2a59497096b2d9e58dfd491cd6639633027acfa9750bc7bccf34e1dc116d29d2f87cbd7ae713db4210ce9ac16182f0576 [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-server-linux-arm.tar.gz) | f08b62be9bc6f0745f820b0083c7a31eedb2ce370a037c768459a59192107b944c8f4345d0bb88fc975f2e7a803ac692c9ac3e16d4a659249d4600e84ff75d9e [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-server-linux-arm64.tar.gz) | e3472b5b3dfae0a56e5363d52062b1e4a9fc227a05e0cf5ece38233b2c442f427970aab94a52377fb87e583663c120760d154bc1c4ac22dca1f4d0d1ebb96088 [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-server-linux-ppc64le.tar.gz) | 06c254e0a62f755d31bc40093d86c44974f0a60308716cc3214a6b3c249a4d74534d909b82f8a3dd3a3c9720e61465b45d2bb3a327ef85d3caba865750020dfb [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-server-linux-s390x.tar.gz) | 2edeb4411c26a0de057a66787091ab1044f71774a464aed898ffee26634a40127181c2edddb38e786b6757cca878fd0c3a885880eec6c3448b93c645770abb12 </ins> ### Node binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-node-linux-amd64.tar.gz) | 6852edc9818cb51a7e738e44a8bca2290777320e62518c024962fddd05f7ef390fb5696537068fd75e340bae909602f0bbc2aa5ebf6c487c7b1e990250f16810 [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-node-linux-arm.tar.gz) | f13edad4684d0de61e4cd7e524f891c75e0efe1050911d9bf0ee3a77cac28f57dca68fb990df6b5d9646e9b389527cbb861de10e12a84e57788f339db05936cb [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-node-linux-arm64.tar.gz) | 69480150325525459aed212b8c96cb1865598cb5ecbeb57741134142d65e8a96258ec298b86d533ce88d2c499c4ad17e66dd3f0f7b5e9c34882889e9cb384805 [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-node-linux-ppc64le.tar.gz) | 774cfa9a4319ede166674d3e8c46900c9319d98ffba5b46684244e4bb15d94d31df8a6681e4711bc744d7e92fd23f207505eda98f43c8e2383107badbd43f289 [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-node-linux-s390x.tar.gz) | 7e696988febb1e913129353134191b23c6aa5b0bea7c9c9168116596b827c091a88049ca8b8847dda25ecd4467cca4cc48cae8699635b5e78b83aab482c109f5 [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-rc.1/kubernetes-node-windows-amd64.tar.gz) | 067182292d9e17f0d4974051681bedcf5ed6017dc80485541f89ea1f211085714165941a5262a4997b7bfc2bd190f2255df4c1b39f86a3278487248111d83cd4 </del> <ins> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-node-linux-amd64.tar.gz) | cc1d5b94b86070b5e7746d7aaeaeac3b3a5e5ebbff1ec33885f7eeab270a6177d593cb1975b2e56f4430b7859ad42da76f266629f9313e0f688571691ac448ed [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-node-linux-arm.tar.gz) | 75e82c7c9122add3b24695b94dcb0723c52420c3956abf47511e37785aa48a1fa8257db090c6601010c4475a325ccfff13eb3352b65e3aa1774f104b09b766b0 [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-node-linux-arm64.tar.gz) | 16ef27c40bf4d678a55fcd3d3f7d09f1597eec2cc58f9950946f0901e52b82287be397ad7f65e8d162d8a9cdb4a34a610b6db8b5d0462be8e27c4b6eb5d6e5e7 [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-node-linux-ppc64le.tar.gz) | 939865f2c4cb6a8934f22a06223e416dec5f768ffc1010314586149470420a1d62aef97527c34d8a636621c9669d6489908ce1caf96f109e8d073cee1c030b50 [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-node-linux-s390x.tar.gz) | bbfdd844075fb816079af7b73d99bc1a78f41717cdbadb043f6f5872b4dc47bc619f7f95e2680d4b516146db492c630c17424e36879edb45e40c91bc2ae4493c [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0-beta.0/kubernetes-node-windows-amd64.tar.gz) | a2b3ea40086fd71aed71a4858fd3fc79fd1907bc9ea8048ff3c82ec56477b0a791b724e5a52d79b3b36338c7fbd93dfd3d03b00ccea9042bda0d270fc891e4ec </ins> <del> ## Changelog since v1.19.0-rc.0 </del> <ins> ## Changelog since v1.20.0-alpha.3 </ins> ## Urgent Upgrade Notes ### (No, really, you MUST read this before you upgrade) <del> - Azure blob disk feature(`kind`: `Shared`, `Dedicated`) has been deprecated, you should use `kind`: `Managed` in `kubernetes.io/azure-disk` storage class. ([#92905](https://github.com/kubernetes/kubernetes/pull/92905), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] </del> <ins> - Kubeadm: improve the validation of serviceSubnet and podSubnet. ServiceSubnet has to be limited in size, due to implementation details, and the mask can not allocate more than 20 bits. PodSubnet validates against the corresponding cluster \"--node-cidr-mask-size\" of the kube-controller-manager, it fail if the values are not compatible. kubeadm no longer sets the node-mask automatically on IPv6 deployments, you must check that your IPv6 service subnet mask is compatible with the default node mask /64 or set it accordenly. Previously, for IPv6, if the podSubnet had a mask lower than /112, kubeadm calculated a node-mask to be multiple of eight and splitting the available bits to maximise the number used for nodes. ([#95723](https://github.com/kubernetes/kubernetes/pull/95723), [@aojea](https://github.com/aojea)) [SIG Cluster Lifecycle] - Windows hyper-v container featuregate is deprecated in 1.20 and will be removed in 1.21 ([#95505](https://github.com/kubernetes/kubernetes/pull/95505), [@wawa0210](https://github.com/wawa0210)) [SIG Node and Windows] </ins> ## Changes by Kind ### Deprecation <del> - Kubeadm: deprecate the \"kubeadm alpha kubelet config enable-dynamic\" command. To continue using the feature please defer to the guide for \"Dynamic Kubelet Configuration\" at k8s.io. ([#92881](https://github.com/kubernetes/kubernetes/pull/92881), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] </del> <ins> - Support 'controlplane' as a valid EgressSelection type in the EgressSelectorConfiguration API. 'Master' is deprecated and will be removed in v1.22. ([#95235](https://github.com/kubernetes/kubernetes/pull/95235), [@andrewsykim](https://github.com/andrewsykim)) [SIG API Machinery] </ins> ### API Change <del> - Added pod version skew strategy for seccomp profile to synchronize the deprecated annotations with the new API Server fields. Please see the corresponding section [in the KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/20190717-seccomp-ga.mdversion-skew-strategy) for more detailed explanations. ([#91408](https://github.com/kubernetes/kubernetes/pull/91408), [@saschagrunert](https://github.com/saschagrunert)) [SIG Apps, Auth, CLI and Node] - Custom Endpoints are now mirrored to EndpointSlices by a new EndpointSliceMirroring controller. ([#91637](https://github.com/kubernetes/kubernetes/pull/91637), [@robscott](https://github.com/robscott)) [SIG API Machinery, Apps, Auth, Cloud Provider, Instrumentation, Network and Testing] - Generic ephemeral volumes, a new alpha feature under the `GenericEphemeralVolume` feature gate, provide a more flexible alternative to `EmptyDir` volumes: as with `EmptyDir`, volumes are created and deleted for each pod automatically by Kubernetes. But because the normal provisioning process is used (`PersistentVolumeClaim`), storage can be provided by third-party storage vendors and all of the usual volume features work. Volumes don't need to be empt; for example, restoring from snapshot is supported. ([#92784](https://github.com/kubernetes/kubernetes/pull/92784), [@pohly](https://github.com/pohly)) [SIG API Machinery, Apps, Auth, CLI, Instrumentation, Node, Scheduling, Storage and Testing] </del> <ins> - Add dual-stack Services (alpha).  This is a BREAKING CHANGE to an alpha API. It changes the dual-stack API wrt Service from a single ipFamily field to 3 fields: ipFamilyPolicy (SingleStack, PreferDualStack, RequireDualStack), ipFamilies (a list of families assigned), and clusterIPs (inclusive of clusterIP).  Most users do not need to set anything at all, defaulting will handle it for them.  Services are single-stack unless the user asks for dual-stack.  This is all gated by the \"IPv6DualStack\" feature gate. ([#91824](https://github.com/kubernetes/kubernetes/pull/91824), [@khenidak](https://github.com/khenidak)) [SIG API Machinery, Apps, CLI, Network, Node, Scheduling and Testing] - Introduces a metric source for HPAs which allows scaling based on container resource usage. ([#90691](https://github.com/kubernetes/kubernetes/pull/90691), [@arjunrn](https://github.com/arjunrn)) [SIG API Machinery, Apps, Autoscaling and CLI] </ins> ### Feature <del> - ACTION REQUIRED : In CoreDNS v1.7.0, [metrics names have been changed](https://github.com/coredns/coredns/blob/master/notes/coredns-1.7.0.md&#35;metric-changes) which will be backward incompatible with existing reporting formulas that use the old metrics' names. Adjust your formulas to the new names before upgrading. Kubeadm now includes CoreDNS version v1.7.0. Some of the major changes include: -  Fixed a bug that could cause CoreDNS to stop updating service records. -  Fixed a bug in the forward plugin where only the first upstream server is always selected no matter which policy is set. -  Remove already deprecated options `resyncperiod` and `upstream` in the Kubernetes plugin. -  Includes Prometheus metrics name changes (to bring them in line with standard Prometheus metrics naming convention). They will be backward incompatible with existing reporting formulas that use the old metrics' names. -  The federation plugin (allows for v1 Kubernetes federation) has been removed. More details are available in https://coredns.io/2020/06/15/coredns-1.7.0-release/ ([#92651](https://github.com/kubernetes/kubernetes/pull/92651), [@rajansandeep](https://github.com/rajansandeep)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle and Instrumentation] - Add tags support for Azure File Driver ([#92825](https://github.com/kubernetes/kubernetes/pull/92825), [@ZeroMagic](https://github.com/ZeroMagic)) [SIG Cloud Provider and Storage] - Audit events for API requests to deprecated API versions now include a `\"k8s.io/deprecated\": \"true\"` audit annotation. If a target removal release is identified, the audit event includes a `\"k8s.io/removal-release\": \"<majorVersion>.<minorVersion>\"` audit annotation as well. ([#92842](https://github.com/kubernetes/kubernetes/pull/92842), [@liggitt](https://github.com/liggitt)) [SIG API Machinery and Instrumentation] - Cloud node-controller use InstancesV2 ([#91319](https://github.com/kubernetes/kubernetes/pull/91319), [@gongguan](https://github.com/gongguan)) [SIG Apps, Cloud Provider, Scalability and Storage] - Kubeadm: deprecate the \"--csr-only\" and \"--csr-dir\" flags of the \"kubeadm init phase certs\" subcommands. Please use \"kubeadm alpha certs generate-csr\" instead. This new command allows you to generate new private keys and certificate signing requests for all the control-plane components, so that the certificates can be signed by an external CA. ([#92183](https://github.com/kubernetes/kubernetes/pull/92183), [@wallrj](https://github.com/wallrj)) [SIG Cluster Lifecycle] - Server-side apply behavior has been regularized in the case where a field is removed from the applied configuration. Removed fields which have no other owners are deleted from the live object, or reset to their default value if they have one. Safe ownership transfers, such as the transfer of a `replicas` field from a user to an HPA without resetting to the default value are documented in [Transferring Ownership](https://kubernetes.io/docs/reference/using-api/api-concepts/&#35;transferring-ownership) ([#92661](https://github.com/kubernetes/kubernetes/pull/92661), [@jpbetz](https://github.com/jpbetz)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation and Testing] - Set CSIMigrationvSphere feature gates to beta. Users should enable CSIMigration + CSIMigrationvSphere features and install the vSphere CSI Driver (https://github.com/kubernetes-sigs/vsphere-csi-driver) to move workload from the in-tree vSphere plugin \"kubernetes.io/vsphere-volume\" to vSphere CSI Driver. Requires: vSphere vCenter/ESXi Version: 7.0u1, HW Version: VM version 15 ([#92816](https://github.com/kubernetes/kubernetes/pull/92816), [@divyenpatel](https://github.com/divyenpatel)) [SIG Cloud Provider and Storage] - Support a smooth upgrade from client-side apply to server-side apply without conflicts, as well as support the corresponding downgrade. ([#90187](https://github.com/kubernetes/kubernetes/pull/90187), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG API Machinery and Testing] - Trace output in apiserver logs is more organized and comprehensive. Traces are nested, and for all non-long running request endpoints, the entire filter chain is instrumented (e.g. authentication check is included). ([#88936](https://github.com/kubernetes/kubernetes/pull/88936), [@jpbetz](https://github.com/jpbetz)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation and Scheduling] - `kubectl alpha debug` now supports debugging nodes by creating a debugging container running in the node's host namespaces. ([#92310](https://github.com/kubernetes/kubernetes/pull/92310), [@verb](https://github.com/verb)) [SIG CLI] </del> <ins> - Add a metric for time taken to perform recursive permission change ([#95866](https://github.com/kubernetes/kubernetes/pull/95866), [@JornShen](https://github.com/JornShen)) [SIG Instrumentation and Storage] - Allow cross compilation of kubernetes on different platforms. ([#94403](https://github.com/kubernetes/kubernetes/pull/94403), [@bnrjee](https://github.com/bnrjee)) [SIG Release] - Command to start network proxy changes from 'KUBE_ENABLE_EGRESS_VIA_KONNECTIVITY_SERVICE ./cluster/kube-up.sh' to 'KUBE_ENABLE_KONNECTIVITY_SERVICE=true ./hack/kube-up.sh' ([#92669](https://github.com/kubernetes/kubernetes/pull/92669), [@Jefftree](https://github.com/Jefftree)) [SIG Cloud Provider] - DefaultPodTopologySpread graduated to Beta. The feature gate is enabled by default. ([#95631](https://github.com/kubernetes/kubernetes/pull/95631), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling and Testing] - Kubernetes E2E test image manifest lists now contain Windows images. ([#77398](https://github.com/kubernetes/kubernetes/pull/77398), [@claudiubelu](https://github.com/claudiubelu)) [SIG Testing and Windows] - Support for Windows container images (OS Versions: 1809, 1903, 1909, 2004) was added the pause:3.4 image. ([#91452](https://github.com/kubernetes/kubernetes/pull/91452), [@claudiubelu](https://github.com/claudiubelu)) [SIG Node, Release and Windows] </ins> <del> ### Failing Test </del> <ins> ### Documentation </ins> <del> - Kube-proxy iptables min-sync-period defaults to 1 sec. Previously, it was 0. ([#92836](https://github.com/kubernetes/kubernetes/pull/92836), [@aojea](https://github.com/aojea)) [SIG Network] </del> <ins> - Fake dynamic client: document that List does not preserve TypeMeta in UnstructuredList ([#95117](https://github.com/kubernetes/kubernetes/pull/95117), [@andrewsykim](https://github.com/andrewsykim)) [SIG API Machinery] </ins> ### Bug or Regression <del> - Dockershim security: pod sandbox now always run with `no-new-privileges` and `runtime/default` seccomp profile dockershim seccomp: custom profiles can now have smaller seccomp profiles when set at pod level ([#90948](https://github.com/kubernetes/kubernetes/pull/90948), [@pjbgf](https://github.com/pjbgf)) [SIG Node] - Eviction requests for pods that have a non-zero DeletionTimestamp will always succeed ([#91342](https://github.com/kubernetes/kubernetes/pull/91342), [@michaelgugino](https://github.com/michaelgugino)) [SIG Apps] - Fix detection of image filesystem, disk metrics for devicemapper, detection of OOM Kills on 5.0+ linux kernels. ([#92919](https://github.com/kubernetes/kubernetes/pull/92919), [@dashpole](https://github.com/dashpole)) [SIG API Machinery, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation and Node] - Fixed memory leak in endpointSliceTracker ([#92838](https://github.com/kubernetes/kubernetes/pull/92838), [@tnqn](https://github.com/tnqn)) [SIG Apps and Network] - Kube-aggregator certificates are dynamically loaded on change from disk ([#92791](https://github.com/kubernetes/kubernetes/pull/92791), [@p0lyn0mial](https://github.com/p0lyn0mial)) [SIG API Machinery] - Kube-up now includes CoreDNS version v1.7.0. Some of the major changes include: -  Fixed a bug that could cause CoreDNS to stop updating service records. -  Fixed a bug in the forward plugin where only the first upstream server is always selected no matter which policy is set. -  Remove already deprecated options `resyncperiod` and `upstream` in the Kubernetes plugin. -  Includes Prometheus metrics name changes (to bring them in line with standard Prometheus metrics naming convention). They will be backward incompatible with existing reporting formulas that use the old metrics' names. -  The federation plugin (allows for v1 Kubernetes federation) has been removed. More details are available in https://coredns.io/2020/06/15/coredns-1.7.0-release/ ([#92718](https://github.com/kubernetes/kubernetes/pull/92718), [@rajansandeep](https://github.com/rajansandeep)) [SIG Cloud Provider] - The apiserver will no longer proxy non-101 responses for upgrade requests. This could break proxied backends (such as an extension API server) that respond to upgrade requests with a non-101 response code. ([#92941](https://github.com/kubernetes/kubernetes/pull/92941), [@tallclair](https://github.com/tallclair)) [SIG API Machinery] - The terminationGracePeriodSeconds from pod spec is respected for the mirror pod. ([#92442](https://github.com/kubernetes/kubernetes/pull/92442), [@tedyu](https://github.com/tedyu)) [SIG Node and Testing] </del> <ins> - Exposes and sets a default timeout for the SubjectAccessReview client for DelegatingAuthorizationOptions. ([#95725](https://github.com/kubernetes/kubernetes/pull/95725), [@p0lyn0mial](https://github.com/p0lyn0mial)) [SIG API Machinery and Cloud Provider] - Alter wording to describe pods using a pvc ([#95635](https://github.com/kubernetes/kubernetes/pull/95635), [@RaunakShah](https://github.com/RaunakShah)) [SIG CLI] - If we set SelectPolicy MinPolicySelect on scaleUp behavior or scaleDown behavior,Horizontal Pod Autoscaler doesn`t automatically scale the number of pods correctly ([#95647](https://github.com/kubernetes/kubernetes/pull/95647), [@JoshuaAndrew](https://github.com/JoshuaAndrew)) [SIG Apps and Autoscaling] - Ignore apparmor for non-linux operating systems ([#93220](https://github.com/kubernetes/kubernetes/pull/93220), [@wawa0210](https://github.com/wawa0210)) [SIG Node and Windows] - Ipvs: ensure selected scheduler kernel modules are loaded ([#93040](https://github.com/kubernetes/kubernetes/pull/93040), [@cmluciano](https://github.com/cmluciano)) [SIG Network] - Kubeadm: add missing \"--experimental-patches\" flag to \"kubeadm init phase control-plane\" ([#95786](https://github.com/kubernetes/kubernetes/pull/95786), [@Sh4d1](https://github.com/Sh4d1)) [SIG Cluster Lifecycle] - Reorganized iptables rules to fix a performance issue ([#95252](https://github.com/kubernetes/kubernetes/pull/95252), [@tssurya](https://github.com/tssurya)) [SIG Network] - Unhealthy pods covered by PDBs can be successfully evicted if enough healthy pods are available. ([#94381](https://github.com/kubernetes/kubernetes/pull/94381), [@michaelgugino](https://github.com/michaelgugino)) [SIG Apps] - Update the PIP when it is not in the Succeeded provisioning state during the LB update. ([#95748](https://github.com/kubernetes/kubernetes/pull/95748), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] - Update the frontend IP config when the service's `pipName` annotation is changed ([#95813](https://github.com/kubernetes/kubernetes/pull/95813), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] </ins> ### Other (Cleanup or Flake) <del> - --cache-dir sets cache directory for both http and discovery, defaults to $HOME/.kube/cache ([#92910](https://github.com/kubernetes/kubernetes/pull/92910), [@soltysh](https://github.com/soltysh)) [SIG API Machinery and CLI] - Fix: license issue in blob disk feature ([#92824](https://github.com/kubernetes/kubernetes/pull/92824), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] </del> <ins> - NO ([#95690](https://github.com/kubernetes/kubernetes/pull/95690), [@nikhita](https://github.com/nikhita)) [SIG Release] </ins> ## Dependencies ### Added <del> _Nothing has changed._ </del> <ins> - github.com/form3tech-oss/jwt-go: [v3.2.2+incompatible](https://github.com/form3tech-oss/jwt-go/tree/v3.2.2) </ins> ### Changed <del> - github.com/cilium/ebpf: [9f1617e → 1c8d4c9](https://github.com/cilium/ebpf/compare/9f1617e...1c8d4c9) - github.com/coredns/corefile-migration: [v1.0.8 → v1.0.10](https://github.com/coredns/corefile-migration/compare/v1.0.8...v1.0.10) - github.com/google/cadvisor: [8450c56 → v0.37.0](https://github.com/google/cadvisor/compare/8450c56...v0.37.0) - github.com/json-iterator/go: [v1.1.9 → v1.1.10](https://github.com/json-iterator/go/compare/v1.1.9...v1.1.10) - github.com/opencontainers/runc: [1b94395 → 819fcc6](https://github.com/opencontainers/runc/compare/1b94395...819fcc6) - github.com/prometheus/client_golang: [v1.6.0 → v1.7.1](https://github.com/prometheus/client_golang/compare/v1.6.0...v1.7.1) - github.com/prometheus/common: [v0.9.1 → v0.10.0](https://github.com/prometheus/common/compare/v0.9.1...v0.10.0) - github.com/prometheus/procfs: [v0.0.11 → v0.1.3](https://github.com/prometheus/procfs/compare/v0.0.11...v0.1.3) - github.com/rubiojr/go-vhd: [0bfd3b3 → 02e2102](https://github.com/rubiojr/go-vhd/compare/0bfd3b3...02e2102) - sigs.k8s.io/structured-merge-diff/v3: v3.0.0 → 43c19bb </del> <ins> - github.com/Azure/go-autorest/autorest/adal: [v0.9.0 → v0.9.5](https://github.com/Azure/go-autorest/autorest/adal/compare/v0.9.0...v0.9.5) - github.com/Azure/go-autorest/autorest/mocks: [v0.4.0 → v0.4.1](https://github.com/Azure/go-autorest/autorest/mocks/compare/v0.4.0...v0.4.1) - golang.org/x/crypto: 75b2880 → 7f63de1 </ins> ### Removed _Nothing has changed._ <del> # v1.19.0-beta.2 </del> <ins> # v1.20.0-alpha.3 </ins> <del> ## Downloads for v1.19.0-beta.2 </del> <ins> ## Downloads for v1.20.0-alpha.3 </ins> ### Source Code filename | sha512 hash -------- | ----------- <del> [kubernetes.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes.tar.gz) | 806c1734a57dfc1800730fcb25aeb60d50d19d248c0e2a92ede4b6c4565745b4f370d4fd925bef302a96fba89102b7560b8f067240e0f35f6ec6caa29971dea4 [kubernetes-src.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-src.tar.gz) | 507372c6d7ea380ec68ea237141a2b62953a2e1d1d16288f37820b605e33778c5f43ac5a3dedf39f7907d501749916221a8fa4d50be1e5a90b3ce23d36eaa075 </del> <ins> [kubernetes.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes.tar.gz) | 542cc9e0cd97732020491456402b6e2b4f54f2714007ee1374a7d363663a1b41e82b50886176a5313aaccfbfd4df2bc611d6b32d19961cdc98b5821b75d6b17c [kubernetes-src.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-src.tar.gz) | 5e5d725294e552fd1d14fd6716d013222827ac2d4e2d11a7a1fdefb77b3459bbeb69931f38e1597de205dd32a1c9763ab524c2af1551faef4f502ef0890f7fbf </ins> ### Client binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-client-darwin-386.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-client-darwin-386.tar.gz) | 6d20ca8d37b01213dcb98a1e49d44d414043ce485ae7df9565dfb7914acb1ec42b7aeb0c503b8febc122a8b444c6ed13eec0ff3c88033c6db767e7af5dbbc65d [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-client-darwin-amd64.tar.gz) | e9caa5463a662869cfc8b9254302641aee9b53fa2119244bd65ef2c66e8c617f7db9b194a672ff80d7bc42256e6560db9fe8a00b2214c0ef023e2d6feed58a3a [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-client-linux-386.tar.gz) | 48296417fcd2c2f6d01c30dcf66956401ea46455c52a2bbd76feb9b117502ceaa2fb10dae944e087e7038b9fdae5b835497213894760ca01698eb892087490d2 [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-client-linux-amd64.tar.gz) | e2cc7819974316419a8973f0d77050b3262c4e8d078946ff9f6f013d052ec1dd82893313feff6e4493ae0fd3fb62310e6ce4de49ba6e80f8b9979650debf53f2 [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-client-linux-arm.tar.gz) | 484aac48a7a736970ea0766547453b7d37b25ed29fdee771734973e3e080b33f6731eecc458647db962290b512d32546e675e4658287ced3214e87292b98a643 [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-client-linux-arm64.tar.gz) | f793078dc2333825a6679126b279cb0a3415ded8c650478e73c37735c6aa9576b68b2a4165bb77ef475884d50563ea236d8db4c72b2e5552b5418ea06268daae [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-client-linux-ppc64le.tar.gz) | 4c204b8d3b2717470ee460230b6bdc63725402ad3d24789397934bfe077b94d68041a376864b618e01f541b5bd00d0e63d75aa531a327ab0082c01eb4b9aa5ee [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-client-linux-s390x.tar.gz) | d0f6e4ddbf122ebcb4c5a980d5f8e33a23213cb438983341870f288afd17e73ec42f0ded55a3a9622c57700e68999228508d449ca206aca85f3254f7622375db [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-client-windows-386.tar.gz) | a615a7821bba1f8e4115b7981347ed94a79947c78d32c692cd600e21e0de29fedfc4a39dc08ca516f2f35261cf4a6d6ce557008f034e0e1d311fa9e75478ec0c [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-client-windows-amd64.tar.gz) | 34046130c5ebb3afe17e6e3cf88229b8d3281a9ac9c28dece1fd2d49a11b7be011700b74d9b8111dee7d0943e5ebfa208185bae095c2571aa54e0f9201e2cddd </del> <ins> [kubernetes-client-darwin-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-client-darwin-amd64.tar.gz) | 60004939727c75d0f06adc4449e16b43303941937c0e9ea9aca7d947e93a5aed5d11e53d1fc94caeb988be66d39acab118d406dc2d6cead61181e1ced6d2be1a [kubernetes-client-linux-386.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-client-linux-386.tar.gz) | 7edba9c4f1bf38fdf1fa5bff2856c05c0e127333ce19b17edf3119dc9b80462c027404a1f58a5eabf1de73a8f2f20aced043dda1fafd893619db1a188cda550c [kubernetes-client-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-client-linux-amd64.tar.gz) | db1818aa82d072cb3e32a2a988e66d76ecf7cebc6b8a29845fa2d6ec27f14a36e4b9839b1b7ed8c43d2da9cde00215eb672a7e8ee235d2e3107bc93c22e58d38 [kubernetes-client-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-client-linux-arm.tar.gz) | d2922e70d22364b1f5a1e94a0c115f849fe2575b231b1ba268f73a9d86fc0a9fbb78dc713446839a2593acf1341cb5a115992f350870f13c1a472bb107b75af7 [kubernetes-client-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-client-linux-arm64.tar.gz) | 2e3ae20e554c7d4fc3a8afdfcafe6bbc81d4c5e9aea036357baac7a3fdc2e8098aa8a8c3dded3951667d57f667ce3fbf37ec5ae5ceb2009a569dc9002d3a92f9 [kubernetes-client-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-client-linux-ppc64le.tar.gz) | b54a34e572e6a86221577de376e6f7f9fcd82327f7fe94f2fc8d21f35d302db8a0f3d51e60dc89693999f5df37c96d0c3649a29f07f095efcdd59923ae285c95 [kubernetes-client-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-client-linux-s390x.tar.gz) | 5be1b70dc437d3ba88cb0b89cd1bc555f79896c3f5b5f4fa0fb046a0d09d758b994d622ebe5cef8e65bba938c5ae945b81dc297f9dfa0d98f82ea75f344a3a0d [kubernetes-client-windows-386.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-client-windows-386.tar.gz) | 88cf3f66168ef3bf9a5d3d2275b7f33799406e8205f2c202997ebec23d449aa4bb48b010356ab1cf52ff7b527b8df7c8b9947a43a82ebe060df83c3d21b7223a [kubernetes-client-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-client-windows-amd64.tar.gz) | 87d2d4ea1829da8cfa1a705a03ea26c759a03bd1c4d8b96f2c93264c4d172bb63a91d9ddda65cdc5478b627c30ae8993db5baf8be262c157d83bffcebe85474e </ins> ### Server binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-server-linux-amd64.tar.gz) | c922058ce9c665e329d3d4647aac5d2dd22d9a8af63a21e6af98943dfd14f2b90268c53876f42a64093b96499ee1109803868c9aead4c15fd8db4b1bbec58fd9 [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-server-linux-arm.tar.gz) | 4f17489b946dc04570bfab87015f2c2401b139b9ee745ed659bc94ccd116f3f23e249f83e19aaa418aa980874fffb478b1ec7340aa25292af758c9eabd4c2022 [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-server-linux-arm64.tar.gz) | 69e44a63d15962de95a484e311130d415ebfec16a9da54989afc53a835c5b67de20911d71485950d07259a0f8286a299f4d74f90c73530e905da8dc60e391597 [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-server-linux-ppc64le.tar.gz) | 66b30ebad7a8226304150aa42a1bd660a0b3975fecbfd8dbbea3092936454d9f81c8083841cc67c6645ab771383b66c7f980dd65319803078c91436c55d5217a [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-server-linux-s390x.tar.gz) | 0e197280f99654ec9e18ea01a9fc848449213ce28521943bc5d593dd2cac65310b6a918f611ea283b3a0377347eb718e99dd59224b8fad8adb223d483fa9fecb </del> <ins> [kubernetes-server-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-server-linux-amd64.tar.gz) | 7af691fc0b13a937797912374e3b3eeb88d5262e4eb7d4ebe92a3b64b3c226cb049aedfd7e39f639f6990444f7bcf2fe58699cf0c29039daebe100d7eebf60de [kubernetes-server-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-server-linux-arm.tar.gz) | 557c47870ecf5c2090b2694c8f0c8e3b4ca23df5455a37945bd037bc6fb5b8f417bf737bb66e6336b285112cb52de0345240fdb2f3ce1c4fb335ca7ef1197f99 [kubernetes-server-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-server-linux-arm64.tar.gz) | 981de6cf7679d743cdeef1e894314357b68090133814801870504ef30564e32b5675e270db20961e9a731e35241ad9b037bdaf749da87b6c4ce8889eeb1c5855 [kubernetes-server-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-server-linux-ppc64le.tar.gz) | 506578a21601ccff609ae757a55e68634c15cbfecbf13de972c96b32a155ded29bd71aee069c77f5f721416672c7a7ac0b8274de22bfd28e1ecae306313d96c5 [kubernetes-server-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-server-linux-s390x.tar.gz) | af0cdcd4a77a7cc8060a076641615730a802f1f02dab084e41926023489efec6102d37681c70ab0dbe7440cd3e72ea0443719a365467985360152b9aae657375 </ins> ### Node binaries filename | sha512 hash -------- | ----------- <del> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-node-linux-amd64.tar.gz) | f40afee38155c5163ba92e3fa3973263ca975f3b72ac18535799fb29180413542ef86f09c87681161affeef94eb0bd38e7cf571a73ab0f51a88420f1aedeaeec [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-node-linux-arm.tar.gz) | 6088b11767b77f0ec932a9f1aee9f0c7795c3627529f259edf4d8b1be2e1a324a75c89caed65c6aa277c2fd6ee23b3ebeb05901f351cd2dde0a833bbbd6d6d07 [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-node-linux-arm64.tar.gz) | e790c491d057721b94d0d2ad22dd5c75400e8602e95276471f20cd2181f52c5be38e66b445d8360e1fb671627217eb0b7735b485715844d0e9908cf3de249464 [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-node-linux-ppc64le.tar.gz) | 04f696cfab66f92b4b22c23807a49c344d6a157a9ac3284a267613369b7f9f5887f67902cb8a2949caa204f89fdc65fe442a03c2c454013523f81b56476d39a0 [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-node-linux-s390x.tar.gz) | c671e20f69f70ec567fb16bbed2fecac3099998a3365def1e0755e41509531fd65768f7a04015b27b17e6a5884e65cddb82ff30a8374ed011c5e2008817259db [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.19.0-beta.2/kubernetes-node-windows-amd64.tar.gz) | 23d712fb2d455b5095d31b9c280d92442f7871786808528a1b39b9babf169dc7ae467f1ee2b2820089d69aa2342441d0290edf4f710808c78277e612f870321d </del> <ins> [kubernetes-node-linux-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-node-linux-amd64.tar.gz) | 2d92c61596296279de1efae23b2b707415565d9d50cd61a7231b8d10325732b059bcb90f3afb36bef2575d203938c265572721e38df408e8792d3949523bd5d9 [kubernetes-node-linux-arm.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-node-linux-arm.tar.gz) | c298de9b5ac1b8778729a2d8e2793ff86743033254fbc27014333880b03c519de81691caf03aa418c729297ee8942ce9ec89d11b0e34a80576b9936015dc1519 [kubernetes-node-linux-arm64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-node-linux-arm64.tar.gz) | daa3c65afda6d7aff206c1494390bbcc205c2c6f8db04c10ca967a690578a01c49d49c6902b85e7158f79fd4d2a87c5d397d56524a75991c9d7db85ac53059a7 [kubernetes-node-linux-ppc64le.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-node-linux-ppc64le.tar.gz) | 05661908bb73bfcaf9c2eae96e9a6a793db5a7a100bce6df9e057985dd53a7a5248d72e81b6d13496bd38b9326c17cdb2edaf0e982b6437507245fb846e1efc6 [kubernetes-node-linux-s390x.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-node-linux-s390x.tar.gz) | 845e518e2c4ef0cef2c3b58f0b9ea5b5fe9b8a249717f789607752484c424c26ae854b263b7c0a004a8426feb9aa3683c177a9ed2567e6c3521f4835ea08c24a [kubernetes-node-windows-amd64.tar.gz](https://dl.k8s.io/v1.20.0-alpha.3/kubernetes-node-windows-amd64.tar.gz) | 530e536574ed2c3e5973d3c0f0fdd2b4d48ef681a7a7c02db13e605001669eeb4f4b8a856fc08fc21436658c27b377f5d04dbcb3aae438098abc953b6eaf5712 </ins> <del> ## Changelog since v1.19.0-beta.1 </del> <ins> ## Changelog since v1.20.0-alpha.2 </ins> ## Changes by Kind <del> ### Deprecation - Kubeadm: remove the deprecated \"--use-api\" flag for \"kubeadm alpha certs renew\" ([#90143](https://github.com/kubernetes/kubernetes/pull/90143), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle] - Scheduler's alpha feature 'ResourceLimitsPriorityFunction' is completely removed due to lack of usage ([#91883](https://github.com/kubernetes/kubernetes/pull/91883), [@SataQiu](https://github.com/SataQiu)) [SIG Scheduling and Testing] </del> ### API Change <del> - Remove `BindTimeoutSeconds` from schedule configuration `KubeSchedulerConfiguration` ([#91580](https://github.com/kubernetes/kubernetes/pull/91580), [@cofyc](https://github.com/cofyc)) [SIG Scheduling and Testing] - Resolve regression in metadata.managedFields handling in update/patch requests submitted by older API clients ([#91748](https://github.com/kubernetes/kubernetes/pull/91748), [@apelisse](https://github.com/apelisse)) [SIG API Machinery and Testing] - The CertificateSigningRequest API is promoted to certificates.k8s.io/v1 with the following changes: - `spec.signerName` is now required, and requests for `kubernetes.io/legacy-unknown` are not allowed to be created via the `certificates.k8s.io/v1` API - `spec.usages` is now required, may not contain duplicate values, and must only contain known usages - `status.conditions` may not contain duplicate types - `status.conditions[*].status` is now required - `status.certificate` must be PEM-encoded, and contain only CERTIFICATE blocks ([#91685](https://github.com/kubernetes/kubernetes/pull/91685), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Architecture, Auth, CLI and Testing] - The Kubelet's `--cloud-provider` and `--cloud-config` options are now marked as deprecated. ([#90408](https://github.com/kubernetes/kubernetes/pull/90408), [@knabben](https://github.com/knabben)) [SIG Cloud Provider and Node] </del> <ins> - New parameter `defaultingType` for `PodTopologySpread` plugin allows to use k8s defined or user provided default constraints ([#95048](https://github.com/kubernetes/kubernetes/pull/95048), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] </ins> ### Feature <del> - A new extension point `PostFilter` is introduced to scheduler framework which runs after Filter phase to resolve scheduling filter failures. A typical implementation is running preemption logic. ([#91314](https://github.com/kubernetes/kubernetes/pull/91314), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling and Testing] - Added --privileged flag to kubectl run ([#90569](https://github.com/kubernetes/kubernetes/pull/90569), [@brianpursley](https://github.com/brianpursley)) [SIG CLI] - Enable feature Gate DefaultPodTopologySpread to use PodTopologySpread plugin to do defaultspreading. In doing so, legacy DefaultPodTopologySpread plugin is disabled. ([#91793](https://github.com/kubernetes/kubernetes/pull/91793), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - Extend AWS azToRegion method to support Local Zones ([#90874](https://github.com/kubernetes/kubernetes/pull/90874), [@Jeffwan](https://github.com/Jeffwan)) [SIG Cloud Provider] - Kube-Proxy now supports IPv6DualStack on Windows with the IPv6DualStack feature gate. ([#90853](https://github.com/kubernetes/kubernetes/pull/90853), [@kumarvin123](https://github.com/kumarvin123)) [SIG Network, Node and Windows] - Kube-controller-manager: the `--experimental-cluster-signing-duration` flag is marked as deprecated for removal in v1.22, and is replaced with `--cluster-signing-duration`. ([#91154](https://github.com/kubernetes/kubernetes/pull/91154), [@liggitt](https://github.com/liggitt)) [SIG Auth and Cloud Provider] - Support kubectl create deployment with replicas ([#91562](https://github.com/kubernetes/kubernetes/pull/91562), [@zhouya0](https://github.com/zhouya0)) [SIG CLI] - The RotateKubeletClientCertificate feature gate has been promoted to GA, and the kubelet --feature-gate RotateKubeletClientCertificate parameter will be removed in 1.20. ([#91780](https://github.com/kubernetes/kubernetes/pull/91780), [@liggitt](https://github.com/liggitt)) [SIG Auth and Node] - The metric label name of `kubernetes_build_info` has been updated from `camel case` to `snake case`: - gitVersion --> git_version - gitCommit --> git_commit - gitTreeState --> git_tree_state - buildDate --> build_date - goVersion --> go_version This change happens in `kube-apiserver`、`kube-scheduler`、`kube-proxy` and `kube-controller-manager`. ([#91805](https://github.com/kubernetes/kubernetes/pull/91805), [@RainbowMango](https://github.com/RainbowMango)) [SIG API Machinery, Cluster Lifecycle and Instrumentation] - `EventRecorder()` is exposed to `FrameworkHandle` interface so that scheduler plugin developers can choose to log cluster-level events. ([#92010](https://github.com/kubernetes/kubernetes/pull/92010), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling] </del> <ins> - Added new k8s.io/component-helpers repository providing shared helper code for (core) components. ([#92507](https://github.com/kubernetes/kubernetes/pull/92507), [@ingvagabund](https://github.com/ingvagabund)) [SIG Apps, Node, Release and Scheduling] - Adds `create ingress` command to `kubectl` ([#78153](https://github.com/kubernetes/kubernetes/pull/78153), [@amimof](https://github.com/amimof)) [SIG CLI and Network] - Kubectl create now supports creating ingress objects. ([#94327](https://github.com/kubernetes/kubernetes/pull/94327), [@rikatz](https://github.com/rikatz)) [SIG CLI and Network] - New default scheduling plugins order reduces scheduling and preemption latency when taints and node affinity are used ([#95539](https://github.com/kubernetes/kubernetes/pull/95539), [@soulxu](https://github.com/soulxu)) [SIG Scheduling] - SCTP support in API objects (Pod, Service, NetworkPolicy) is now GA. Note that this has no effect on whether SCTP is enabled on nodes at the kernel level, and note that some cloud platforms and network plugins do not support SCTP traffic. ([#95566](https://github.com/kubernetes/kubernetes/pull/95566), [@danwinship](https://github.com/danwinship)) [SIG Apps and Network] - Scheduling Framework: expose Run[Pre]ScorePlugins functions to PreemptionHandle which can be used in PostFilter extention point. ([#93534](https://github.com/kubernetes/kubernetes/pull/93534), [@everpeace](https://github.com/everpeace)) [SIG Scheduling and Testing] - SelectorSpreadPriority maps to PodTopologySpread plugin when DefaultPodTopologySpread feature is enabled ([#95448](https://github.com/kubernetes/kubernetes/pull/95448), [@alculquicondor](https://github.com/alculquicondor)) [SIG Scheduling] - SetHostnameAsFQDN has been graduated to Beta and therefore it is enabled by default. ([#95267](https://github.com/kubernetes/kubernetes/pull/95267), [@javidiaz](https://github.com/javidiaz)) [SIG Node] </ins> ### Bug or Regression <del> - Azure: set dest prefix and port for IPv6 inbound security rule ([#91831](https://github.com/kubernetes/kubernetes/pull/91831), [@aramase](https://github.com/aramase)) [SIG Cloud Provider] - Fix etcd version migration script in etcd image. ([#91925](https://github.com/kubernetes/kubernetes/pull/91925), [@wenjiaswe](https://github.com/wenjiaswe)) [SIG API Machinery] - Fix issues when supported huge page sizes changes ([#80831](https://github.com/kubernetes/kubernetes/pull/80831), [@odinuge](https://github.com/odinuge)) [SIG Node and Testing] - Fix kubectl describe output format for empty annotations. ([#91405](https://github.com/kubernetes/kubernetes/pull/91405), [@iyashu](https://github.com/iyashu)) [SIG CLI] - Fixed an issue that a Pod's nominatedNodeName cannot be cleared upon node deletion. ([#91750](https://github.com/kubernetes/kubernetes/pull/91750), [@Huang-Wei](https://github.com/Huang-Wei)) [SIG Scheduling and Testing] - Fixed several bugs involving the IPFamily field when creating or updating services in clusters with the IPv6DualStack feature gate enabled. Beware that the behavior of the IPFamily field is strange and inconsistent and will likely be changed before the dual-stack feature goes GA. Users should treat the field as \"write-only\" for now and should not make any assumptions about a service based on its current IPFamily value. ([#91400](https://github.com/kubernetes/kubernetes/pull/91400), [@danwinship](https://github.com/danwinship)) [SIG Apps and Network] - Kube-apiserver: fixes scale subresource patch handling to avoid returning unnecessary 409 Conflict error to clients ([#90342](https://github.com/kubernetes/kubernetes/pull/90342), [@liggitt](https://github.com/liggitt)) [SIG Apps, Autoscaling and Testing] - Kube-up: fixes setup of validating admission webhook credential configuration ([#91995](https://github.com/kubernetes/kubernetes/pull/91995), [@liggitt](https://github.com/liggitt)) [SIG Cloud Provider and Cluster Lifecycle] - Kubeadm: Add retries for kubeadm join / UpdateStatus to make update status more resilient by adding a retry loop to this operation ([#91952](https://github.com/kubernetes/kubernetes/pull/91952), [@xlgao-zju](https://github.com/xlgao-zju)) [SIG Cluster Lifecycle] - On AWS nodes with multiple network interfaces, kubelet should now more reliably report addresses from secondary interfaces. ([#91889](https://github.com/kubernetes/kubernetes/pull/91889), [@anguslees](https://github.com/anguslees)) [SIG Cloud Provider] - Resolve regression in metadata.managedFields handling in create/update/patch requests not using server-side apply ([#91690](https://github.com/kubernetes/kubernetes/pull/91690), [@apelisse](https://github.com/apelisse)) [SIG API Machinery and Testing] </del> <ins> - An issues preventing volume expand controller to annotate the PVC with `volume.kubernetes.io/storage-resizer` when the PVC StorageClass is already updated to the out-of-tree provisioner is now fixed. ([#94489](https://github.com/kubernetes/kubernetes/pull/94489), [@ialidzhikov](https://github.com/ialidzhikov)) [SIG API Machinery, Apps and Storage] - Change the mount way from systemd to normal mount except ceph and glusterfs intree-volume. ([#94916](https://github.com/kubernetes/kubernetes/pull/94916), [@smileusd](https://github.com/smileusd)) [SIG Apps, Cloud Provider, Network, Node, Storage and Testing] - Fix azure disk attach failure for disk size bigger than 4TB ([#95463](https://github.com/kubernetes/kubernetes/pull/95463), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider] - Fix azure disk data loss issue on Windows when unmount disk ([#95456](https://github.com/kubernetes/kubernetes/pull/95456), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] - Fix verb & scope reporting for kube-apiserver metrics (LIST reported instead of GET) ([#95562](https://github.com/kubernetes/kubernetes/pull/95562), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery and Testing] - Fix vsphere detach failure for static PVs ([#95447](https://github.com/kubernetes/kubernetes/pull/95447), [@gnufied](https://github.com/gnufied)) [SIG Cloud Provider and Storage] - Fix: smb valid path error ([#95583](https://github.com/kubernetes/kubernetes/pull/95583), [@andyzhangx](https://github.com/andyzhangx)) [SIG Storage] - Fixed a bug causing incorrect formatting of `kubectl describe ingress`. ([#94985](https://github.com/kubernetes/kubernetes/pull/94985), [@howardjohn](https://github.com/howardjohn)) [SIG CLI and Network] - Fixed a bug in client-go where new clients with customized `Dial`, `Proxy`, `GetCert` config may get stale HTTP transports. ([#95427](https://github.com/kubernetes/kubernetes/pull/95427), [@roycaihw](https://github.com/roycaihw)) [SIG API Machinery] - Fixes high CPU usage in kubectl drain ([#95260](https://github.com/kubernetes/kubernetes/pull/95260), [@amandahla](https://github.com/amandahla)) [SIG CLI] - Support the node label `node.kubernetes.io/exclude-from-external-load-balancers` ([#95542](https://github.com/kubernetes/kubernetes/pull/95542), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider] </ins> ### Other (Cleanup or Flake) <del> - Deprecate the `--target-ram-md` flags that is no longer used for anything. ([#91818](https://github.com/kubernetes/kubernetes/pull/91818), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery] - Replace framework.Failf with ExpectNoError ([#91811](https://github.com/kubernetes/kubernetes/pull/91811), [@lixiaobing1](https://github.com/lixiaobing1)) [SIG Instrumentation, Storage and Testing] - The Kubelet's `--experimental-allocatable-ignore-eviction` option is now marked as deprecated. ([#91578](https://github.com/kubernetes/kubernetes/pull/91578), [@knabben](https://github.com/knabben)) [SIG Node] - Update corefile-migration library to 1.0.8 ([#91856](https://github.com/kubernetes/kubernetes/pull/91856), [@wawa0210](https://github.com/wawa0210)) [SIG Node] </del> <ins> - Fix func name NewCreateCreateDeploymentOptions ([#91931](https://github.com/kubernetes/kubernetes/pull/91931), [@lixiaobing1](https://github.com/lixiaobing1)) [SIG CLI] - Kubeadm: update the default pause image version to 1.4.0 on Windows. With this update the image supports Windows versions 1809 (2019LTS), 1903, 1909, 2004 ([#95419](https://github.com/kubernetes/kubernetes/pull/95419), [@jsturtevant](https://github.com/jsturtevant)) [SIG Cluster Lifecycle and Windows] - Upgrade snapshot controller to 3.0.0 ([#95412](https://github.com/kubernetes/kubernetes/pull/95412), [@saikat-royc](https://github.com/saikat-royc)) [SIG Cloud Provider] - Remove the dependency of csi-translation-lib module on apiserver/cloud-provider/controller-manager ([#95543](https://github.com/kubernetes/kubernetes/pull/95543), [@wawa0210](https://github.com/wawa0210)) [SIG Release] - Scheduler framework interface moved from pkg/scheduler/framework/v1alpha to pkg/scheduler/framework ([#95069](https://github.com/kubernetes/kubernetes/pull/95069), [@farah](https://github.com/farah)) [SIG Scheduling, Storage and Testing] - UDP and SCTP protocols can left stale connections that need to be cleared to avoid services disruption, but they can cause problems that are hard to debug. Kubernetes components using a loglevel greater or equal than 4 will log the conntrack operations and its output, to show the entries that were deleted. ([#95694](https://github.com/kubernetes/kubernetes/pull/95694), [@aojea](https://github.com/aojea)) [SIG Network] </ins> ## Dependencies"}
{"_id":"q-en-website-9e567c762b93950a945b731f0865d04a307c5f3e9d57b2ca569813bcad8e22a9","text":"Hit enter for command prompt <del> / # wget -s --timeout=1 nginx </del> <ins> / # wget --spider --timeout=1 nginx </ins> Connecting to nginx (10.100.0.16:80) wget: download timed out / #"}
{"_id":"q-en-website-9f21fcf763f67d972bbd5f1a308f5cfe8f5604041ce019377e88123a9a9282fa","text":"<ins> --- title: 클러스터에서 캐스케이딩 삭제 사용 content_type: task --- <!--overview--> 이 페이지에서는 {{<glossary_tooltip text=\"가비지 수집\" term_id=\"garbage-collection\">}} 중 클러스터에서 사용할 [캐스케이딩 삭제](ko/docs/concepts/architecture/garbage-collection/#cascading-deletion) 타입을 지정하는 방법을 보여준다. ## {{% heading \"prerequisites\" %}} {{< include \"task-tutorial-prereqs.md\" >}} 또한 다양한 타입들의 캐스케이딩 삭제를 실험하려면 [샘플 디플로이먼트를 생성](ko/docs/tasks/run-application/run-stateless-application-deployment/#nginx-디플로이먼트-생성하고-탐색하기)할 필요가 있다. 각 타입에 대해 디플로이먼트를 다시 생성해야 할 수도 있다. ## 파드에서 소유자 참조 확인 파드에서 `ownerReferences` 필드가 존재하는지 확인한다. ```shell kubectl get pods -l app=nginx --output=yaml ``` 출력은 다음과 같이 `ownerReferences` 필드를 가진다. ```yaml apiVersion: v1 ... ownerReferences: - apiVersion: apps/v1 blockOwnerDeletion: true controller: true kind: ReplicaSet name: nginx-deployment-6b474476c4 uid: 4fdcd81c-bd5d-41f7-97af-3a3b759af9a7 ... ``` ## 포그라운드(foreground) 캐스케이딩 삭제 사용 {#use-foreground-cascading-deletion} 기본적으로 쿠버네티스는 종속 오브젝트를 삭제하기 위해서 [백그라운드 캐스케이딩 삭제](/ko/docs/concepts/architecture/garbage-collection/#background-deletion)를 사용한다. 클러스터를 실행하는 쿠버네티스 버전에 따라 `kubectl` 또는 쿠버네티스 API를 사용해 포그라운드 캐스케이딩 삭제로 전환할 수 있다. {{<version-check>}} {{<tabs name=\"foreground_deletion\">}} {{% tab name=\"쿠버네티스 1.20.x 이후 버전\" %}} `kubectl` 또는 쿠버네티스 API를 사용해 포그라운드 캐스케이딩 삭제로 오브젝트들을 삭제할 수 있다. **kubectl 사용** 다음 명령어를 실행한다. <!--TODO: verify release after which the --cascade flag is switched to a string in https://github.com/kubernetes/kubectl/commit/fd930e3995957b0093ecc4b9fd8b0525d94d3b4e--> ```shell kubectl delete deployment nginx-deployment --cascade=foreground ``` **쿠버네티스 API 사용** 1. 로컬 프록시 세션을 시작한다. ```shell kubectl proxy --port=8080 ``` 1. 삭제를 작동시키기 위해 `curl`을 사용한다. ```shell curl -X DELETE localhost:8080/apis/apps/v1/namespaces/default/deployments/nginx-deployment  -d '{\"kind\":\"DeleteOptions\",\"apiVersion\":\"v1\",\"propagationPolicy\":\"Foreground\"}'  -H \"Content-Type: application/json\" ``` 출력에는 다음과 같이 `foregroundDeletion` {{<glossary_tooltip text=\"파이널라이저(finalizer)\" term_id=\"finalizer\">}}가 포함되어 있다. ``` \"kind\": \"Deployment\", \"apiVersion\": \"apps/v1\", \"metadata\": { \"name\": \"nginx-deployment\", \"namespace\": \"default\", \"uid\": \"d1ce1b02-cae8-4288-8a53-30e84d8fa505\", \"resourceVersion\": \"1363097\", \"creationTimestamp\": \"2021-07-08T20:24:37Z\", \"deletionTimestamp\": \"2021-07-08T20:27:39Z\", \"finalizers\": [ \"foregroundDeletion\" ] ... ``` {{% /tab %}} {{% tab name=\"쿠버네티스 1.20.x 전 버전\" %}} 쿠버네티스 API를 사용해 포그라운드 캐스케이딩 삭제로 오브젝트들을 삭제할 수 있다. 상세한 내용은 [쿠버네티스 버전에 따른 문서](ko/docs/home/supported-doc-versions/)를 참고한다. 1. 로컬 프록시 세션을 시작한다. ```shell kubectl proxy --port=8080 ``` 1. 삭제를 작동시키기 위해 `curl`을 사용한다. ```shell curl -X DELETE localhost:8080/apis/apps/v1/namespaces/default/deployments/nginx-deployment  -d '{\"kind\":\"DeleteOptions\",\"apiVersion\":\"v1\",\"propagationPolicy\":\"Foreground\"}'  -H \"Content-Type: application/json\" ``` 출력에는 다음과 같이 `foregroundDeletion` {{<glossary_tooltip text=\"파이널라이저(finalizer)\" term_id=\"finalizer\">}}가 포함되어 있다. ``` \"kind\": \"Deployment\", \"apiVersion\": \"apps/v1\", \"metadata\": { \"name\": \"nginx-deployment\", \"namespace\": \"default\", \"uid\": \"d1ce1b02-cae8-4288-8a53-30e84d8fa505\", \"resourceVersion\": \"1363097\", \"creationTimestamp\": \"2021-07-08T20:24:37Z\", \"deletionTimestamp\": \"2021-07-08T20:27:39Z\", \"finalizers\": [ \"foregroundDeletion\" ] ... ``` {{% /tab %}} {{</tabs>}} ## 백그라운드 캐스케이딩 삭제 사용 {#use-background-cascading-deletion} 1. [샘플 디플로이먼트를 생성한다](/ko/docs/tasks/run-application/run-stateless-application-deployment/#nginx-디플로이먼트-생성하고-탐색하기). 1. 클러스터를 실행하는 쿠버네티스 버전에 따라 디플로이먼트를 삭제하기 위해 `kubectl` 또는 쿠버네티스 API를 사용한다. {{<version-check>}} {{<tabs name=\"background_deletion\">}} {{% tab name=\"쿠버네티스 1.20.x 이후 버전\" %}} `kubectl` 또는 쿠버네티스 API를 사용해 백그라운드 캐스케이딩 삭제로 오브젝트들을 삭제할 수 있다. 쿠버네티스는 기본적으로 백그라운드 캐스케이딩 삭제를 사용하므로, `--cascade` 플래그 또는 `propagationPolicy` 인수 없이 다음 명령을 실행해도 같은 작업을 수행한다. **kubectl 사용** 다음 명령어를 실행한다. ```shell kubectl delete deployment nginx-deployment --cascade=background ``` **쿠버네티스 API 사용** 1. 로컬 프록시 세션을 시작한다. ```shell kubectl proxy --port=8080 ``` 1. 삭제를 작동시키기 위해 `curl`을 사용한다. ```shell curl -X DELETE localhost:8080/apis/apps/v1/namespaces/default/deployments/nginx-deployment  -d '{\"kind\":\"DeleteOptions\",\"apiVersion\":\"v1\",\"propagationPolicy\":\"Background\"}'  -H \"Content-Type: application/json\" ``` 출력은 다음과 유사하다. ``` \"kind\": \"Status\", \"apiVersion\": \"v1\", ... \"status\": \"Success\", \"details\": { \"name\": \"nginx-deployment\", \"group\": \"apps\", \"kind\": \"deployments\", \"uid\": \"cc9eefb9-2d49-4445-b1c1-d261c9396456\" } ``` {{% /tab %}} {{% tab name=\"쿠버네티스 1.20.x 전 버전\" %}} 쿠버네티스는 기본적으로 백그라운드 캐스케이딩 삭제를 사용하므로, `--cascade` 플래그 또는 `propagationPolicy: Background` 인수 없이 다음 명령을 실행해도 같은 작업을 수행한다. 상세한 내용은 [쿠버네티스 버전에 따른 문서](ko/docs/home/supported-doc-versions/)를 참고한다. **kubectl 사용** 다음 명령어를 실행한다. ```shell kubectl delete deployment nginx-deployment --cascade=true ``` **쿠버네티스 API 사용** 1. 로컬 프록시 세션을 시작한다. ```shell kubectl proxy --port=8080 ``` 1. 삭제를 작동시키기 위해 `curl`을 사용한다. ```shell curl -X DELETE localhost:8080/apis/apps/v1/namespaces/default/deployments/nginx-deployment  -d '{\"kind\":\"DeleteOptions\",\"apiVersion\":\"v1\",\"propagationPolicy\":\"Background\"}'  -H \"Content-Type: application/json\" ``` 출력은 다음과 유사하다. ``` \"kind\": \"Status\", \"apiVersion\": \"v1\", ... \"status\": \"Success\", \"details\": { \"name\": \"nginx-deployment\", \"group\": \"apps\", \"kind\": \"deployments\", \"uid\": \"cc9eefb9-2d49-4445-b1c1-d261c9396456\" } ``` {{% /tab %}} {{</tabs>}} ## 소유자 오브젝트 및 종속된 고아(orphan) 오브젝트 삭제 {#set-orphan-deletion-policy} 기본적으로, 쿠버네티스에 오브젝트를 삭제하도록 지시하면 {{<glossary_tooltip text=\"컨트롤러\" term_id=\"controller\">}}는 종속 오브젝트들도 제거한다. 클러스터를 실행하는 쿠버네티스 버전에 따라 `kubectl` 또는 쿠버네티스 API를 사용해 종속 오브젝트를 쿠버네티스 *고아*로 만들 수 있다. {{<version-check>}} {{<tabs name=\"orphan_objects\">}} {{% tab name=\"쿠버네티스 1.20.x 이후 버전\" %}} **kubectl 사용** 다음 명령어를 실행한다. ```shell kubectl delete deployment nginx-deployment --cascade=orphan ``` **쿠버네티스 API 사용** 1. 로컬 프록시 세션을 시작한다. ```shell kubectl proxy --port=8080 ``` 1. 삭제를 작동시키기 위해 `curl`을 사용한다. ```shell curl -X DELETE localhost:8080/apis/apps/v1/namespaces/default/deployments/nginx-deployment  -d '{\"kind\":\"DeleteOptions\",\"apiVersion\":\"v1\",\"propagationPolicy\":\"Orphan\"}'  -H \"Content-Type: application/json\" ``` 출력에는 다음과 같이 `finalizers` 필드에 `orphan`이 포함되어 있다. ``` \"kind\": \"Deployment\", \"apiVersion\": \"apps/v1\", \"namespace\": \"default\", \"uid\": \"6f577034-42a0-479d-be21-78018c466f1f\", \"creationTimestamp\": \"2021-07-09T16:46:37Z\", \"deletionTimestamp\": \"2021-07-09T16:47:08Z\", \"deletionGracePeriodSeconds\": 0, \"finalizers\": [ \"orphan\" ], ... ``` {{% /tab %}} {{% tab name=\"쿠버네티스 1.20.x 전 버전\" %}} 상세한 내용은 [쿠버네티스 버전에 따른 문서](ko/docs/home/supported-doc-versions/)를 참고한다. **kubectl 사용** 다음 명령어를 실행한다. ```shell kubectl delete deployment nginx-deployment --cascade=orphan ``` **쿠버네티스 API 사용** 1. 로컬 프록시 세션을 시작한다. ```shell kubectl proxy --port=8080 ``` 1. 삭제를 작동시키기 위해 `curl`을 사용한다. ```shell curl -X DELETE localhost:8080/apis/apps/v1/namespaces/default/deployments/nginx-deployment  -d '{\"kind\":\"DeleteOptions\",\"apiVersion\":\"v1\",\"propagationPolicy\":\"Orphan\"}'  -H \"Content-Type: application/json\" ``` 출력에는 다음과 같이 `finalizers` 필드에 `orphan`이 포함되어 있다. ``` \"kind\": \"Deployment\", \"apiVersion\": \"apps/v1\", \"namespace\": \"default\", \"uid\": \"6f577034-42a0-479d-be21-78018c466f1f\", \"creationTimestamp\": \"2021-07-09T16:46:37Z\", \"deletionTimestamp\": \"2021-07-09T16:47:08Z\", \"deletionGracePeriodSeconds\": 0, \"finalizers\": [ \"orphan\" ], ... ``` {{% /tab %}} {{</tabs>}} 디플로이먼트가 관리하는 파드들이 계속 실행 중인지 확인할 수 있다. ```shell kubectl get pods -l app=nginx ``` ## {{% heading \"whatsnext\" %}} * 쿠버네티스의 [소유자와 종속 오브젝트](/docs/concepts/overview/working-with-objects/owners-dependents/)에 대해 알아보자. * 쿠버네티스 [파이널라이저(finalizers)](/docs/concepts/overview/working-with-objects/finalizers/)에 대해 알아보자. * [가비지(garbage) 수집](/ko/docs/concepts/architecture/garbage-collection/)에 대해 알아보자. </ins>"}
{"_id":"q-en-website-9f384f366b89fbb86057f48b555d21f799285f7da1fe676a12ca419e7eb2b520","text":"<ins> --- title: EndpointSlice content_type: concept weight: 15 --- <!-- overview --> {{< feature-state for_k8s_version=\"v1.17\" state=\"beta\" >}} *EndpointSlice*は、Kubernetesクラスター内にあるネットワークエンドポイントを追跡するための単純な手段を提供します。EndpointSliceは、よりスケーラブルでより拡張可能な、Endpointの代わりとなるものです。 <!-- body --> ## 動機 Endpoints APIはKubernetes内のネットワークエンドポイントを追跡する単純で直観的な手段を提供してきました。残念ながら、KubernetesクラスターやServiceが大規模になるにつれて、Endpoints APIの限界が明らかになってきました。最も顕著な問題の1つに、ネットワークエンドポイントの数が大きくなったときのスケーリングの問題があります。 Serviceのすべてのネットワークエンドポイントが単一のEndpointsリソースに格納されていたため、リソースのサイズが非常に大きくなる場合がありました。これがKubernetesのコンポーネント(特に、マスターコントロールプレーン)の性能に悪影響を与え、結果として、Endpointsに変更があるたびに、大量のネットワークトラフィックと処理が発生するようになってしまいました。EndpointSliceは、この問題を緩和するとともに、トポロジカルルーティングなどの追加機能のための拡張可能なプラットフォームを提供します。 ## EndpointSliceリソース {#endpointslice-resource} Kubernetes内ではEndpointSliceにはネットワークエンドポイントの集合へのリファレンスが含まれます。EndpointSliceコントローラーは、{{< glossary_tooltip text=\"セレクター\" term_id=\"selector\" >}}が指定されると、Kubernetes Serviceに対するEndpointSliceを自動的に作成します。これらのEndpointSliceにはServiceセレクターに一致する任意のPodへのリファレクンスが含まれます。EndpointSliceはネットワークエンドポイントをユニークなServiceとPortの組み合わせでグループ化します。EndpointSliceオブジェクトの名前は有効な[DNSサブドメイン名](/ja/docs/concepts/overview/working-with-objects/names#dns-subdomain-names)である必要があります。 一例として、以下に`example`というKubernetes Serviceに対するサンプルのEndpointSliceリソースを示します。 ```yaml apiVersion: discovery.k8s.io/v1beta1 kind: EndpointSlice metadata: name: example-abc labels: kubernetes.io/service-name: example addressType: IPv4 ports: - name: http protocol: TCP port: 80 endpoints: - addresses: - \"10.1.2.3\" conditions: ready: true hostname: pod-1 topology: kubernetes.io/hostname: node-1 topology.kubernetes.io/zone: us-west2-a ``` デフォルトではEndpointSliceコントローラーが管理するEndpointSliceには、1つにつき最大で100個のエンドポイントしか所属しません。この規模以下であれば、EndpointSliceはEndpointとServiceが1対1対応になり、性能は変わらないはずです。 EndpointSliceは内部トラフィックのルーティング方法に関して、kube-proxyに対する唯一のソース(source of truth)として振る舞うことができます。EndpointSliceを有効にすれば、非常に多数のエンドポイントを持つServiceに対して性能向上が得られるはずです。 ### アドレスの種類 EndpointSliceは次の3種類のアドレスをサポートします。 * IPv4 * IPv6 * FQDN (Fully Qualified Domain Name、完全修飾ドメイン名) ### トポロジー EndpointSliceに属する各エンドポイントは、関連するトポロジーの情報を持つことができます。この情報は、エンドポイントの場所を示すために使われ、対応するNode、ゾーン、リージョンに関する情報が含まれます。値が利用できる場合にはEndpointSliceコントローラーによって次のようなTopologyラベルが設定されます。 * `kubernetes.io/hostname` - このエンドポイントが存在するNodeの名前。 * `topology.kubernetes.io/zone` - このエンドポイントが存在するゾーン。 * `topology.kubernetes.io/region` - このエンドポイントが存在するリージョン。 これらのラベルの値はスライス内の各エンドポイントと関連するリソースから継承したものです。hostnameラベルは対応するPod上のNodeNameフィールドの値を表します。zoneとregionラベルは対応するNode上の同じ名前のラベルの値を表します。 ### 管理 EndpointSliceはデフォルトではEndpointSliceコントローラーによって作成・管理されます。EndpointSliceには他にもサービスメッシュの実装などのさまざまなユースケースがあるため、他のエンティティやコントローラーがEndpointSliceの追加の集合を管理する場合もあります。複数のエンティティが互いに干渉せずにEndpointSliceを管理できるようにするために、EndpointSliceを管理しているエンティティを表す`endpointslice.kubernetes.io/managed-by`ラベルが使用されます。EndpointSliceコントローラーの場合、管理対象のすべてのEndpointSliceに対して、このラベルの値として`endpointslice-controller.k8s.io`を設定します。EndpointSliceを管理するその他のエンティティも同様に、このラベルにユニークな値を設定する必要があります。 ### 所有権 ほとんどのユースケースでは、EndpointSliceは対象のエンドポイントが追跡しているServiceによって所有されます。これは、各EndpointSlice上のownerリファレンスと`kubernetes.io/service-name`ラベルによって示されます。これにより、Serviceに属するすべてのEndpointSliceを簡単に検索できるようになっています。 ## EndpointSliceコントローラー EndpointSliceコントローラーは対応するEndpointSliceが最新の状態であることを保証するために、ServiceとPodを監視します。このコントローラーはセレクターが指定した各Serviceに対応するEndpointSliceを管理します。EndpointSliceはServiceセレクターに一致するPodのIPを表します。 ### EndpointSliceのサイズ デフォルトでは、それぞれのEndpointSliceのサイズの上限は100個のEndpointsに制限されています。この制限は{{< glossary_tooltip text=\"kube-controller-manager\" term_id=\"kube-controller-manager\" >}}に`--max-endpoints-per-slice`フラグを使用することで、最大で1000まで設定できます。 ### EndpointSliceの分散 それぞれのEndpointSliceにはポートの集合があり、リソース内のすべてのエンドポイントに適用されます。サービスが名前付きポートを使用した場合、Podが同じ名前のポートに対して、結果的に異なるターゲットポート番号が使用されて、異なるEndpointSliceが必要になる場合があります。これはサービスの部分集合がEndpointsにグループ化される場合と同様です。 コントローラーはEndpointSliceをできる限り充填しようとしますが、積極的にリバランスを行うことはありません。コントローラーのロジックは極めて単純で、以下のようになっています。 1. 既存のEndpointSliceをイテレートし、もう必要のないエンドポイントを削除し、変更があったエンドポイントを更新する。 2. 前のステップで変更されたEndpointSliceをイテレートし、追加する必要がある新しいエンドポイントで充填する。 3. まだ追加するべき新しいエンドポイントが残っていた場合、これまで変更されなかったスライスに追加を試み、その後、新しいスライスを作成する。 ここで重要なのは、3番目のステップでEndpointSliceを完全に分散させることよりも、EndpointSliceの更新を制限することを優先していることです。たとえば、もし新しい追加するべきエンドポイントが10個あり、2つのEndpointSliceにそれぞれ5個の空きがあった場合、このアプローチでは2つの既存のEndpointSliceを充填する代わりに、新しいEndpointSliceが作られます。言い換えれば、1つのEndpointSliceを作成する方が複数のEndpointSliceを更新するよりも好ましいということです。 各Node上で実行されているkube-proxyはEndpointSliceを監視しており、EndpointSliceに加えられた変更はクラスター内のすべてのNodeに送信されるため、比較的コストの高い処理になります。先ほどのアプローチは、たとえ複数のEndpointSliceが充填されない結果となるとしても、すべてのNodeへ送信しなければならない変更の数を抑制することを目的としています。 現実的には、こうしたあまり理想的ではない分散が発生することは稀です。EndpointSliceコントローラーによって処理されるほとんどの変更は、既存のEndpointSliceに収まるほど十分小さくなるためです。そうでなかったとしても、すぐに新しいEndpointSliceが必要になる可能性が高いです。また、Deploymentのローリングアップデートが行われれば、自然な再充填が行われます。Podとそれに対応するエンドポイントがすべて置換されるためです。 ## {{% heading \"whatsnext\" %}} * [EndpointSliceを有効にする](/docs/tasks/administer-cluster/enabling-endpointslices) * [サービスとアプリケーションの接続](/ja/docs/concepts/services-networking/connect-applications-service/)を読む </ins>"}
{"_id":"q-en-website-9f3cf4265827018b86eb8f4f0adda19ac934287e52f9136a2e9551850f09e9d1","text":"See [Control Topology Management Policies on a Node](/docs/tasks/administer-cluster/topology-manager/) for more information. <del> ## Graceful node shutdown {#graceful-node-shutdown} {{< feature-state feature_gate_name=\"GracefulNodeShutdown\" >}} The kubelet attempts to detect node system shutdown and terminates pods running on the node. Kubelet ensures that pods follow the normal [pod termination process](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination) during the node shutdown. During node shutdown, the kubelet does not accept new Pods (even if those Pods are already bound to the node). The Graceful node shutdown feature depends on systemd since it takes advantage of [systemd inhibitor locks](https://www.freedesktop.org/wiki/Software/systemd/inhibit/) to delay the node shutdown with a given duration. Graceful node shutdown is controlled with the `GracefulNodeShutdown` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) which is enabled by default in 1.21. Note that by default, both configuration options described below, `shutdownGracePeriod` and `shutdownGracePeriodCriticalPods` are set to zero, thus not activating the graceful node shutdown functionality. To activate the feature, the two kubelet config settings should be configured appropriately and set to non-zero values. Once systemd detects or notifies node shutdown, the kubelet sets a `NotReady` condition on the Node, with the `reason` set to `\"node is shutting down\"`. The kube-scheduler honors this condition and does not schedule any Pods onto the affected node; other third-party schedulers are expected to follow the same logic. This means that new Pods won't be scheduled onto that node and therefore none will start. The kubelet **also** rejects Pods during the `PodAdmission` phase if an ongoing node shutdown has been detected, so that even Pods with a {{< glossary_tooltip text=\"toleration\" term_id=\"toleration\" >}} for `node.kubernetes.io/not-ready:NoSchedule` do not start there. At the same time when kubelet is setting that condition on its Node via the API, the kubelet also begins terminating any Pods that are running locally. During a graceful shutdown, kubelet terminates pods in two phases: 1. Terminate regular pods running on the node. 2. Terminate [critical pods](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/#marking-pod-as-critical) running on the node. Graceful node shutdown feature is configured with two [`KubeletConfiguration`](/docs/tasks/administer-cluster/kubelet-config-file/) options: * `shutdownGracePeriod`: * Specifies the total duration that the node should delay the shutdown by. This is the total grace period for pod termination for both regular and [critical pods](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/#marking-pod-as-critical). * `shutdownGracePeriodCriticalPods`: * Specifies the duration used to terminate [critical pods](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/#marking-pod-as-critical) during a node shutdown. This value should be less than `shutdownGracePeriod`. {{< note >}} There are cases when Node termination was cancelled by the system (or perhaps manually by an administrator). In either of those situations the Node will return to the `Ready` state. However, Pods which already started the process of termination will not be restored by kubelet and will need to be re-scheduled. {{< /note >}} For example, if `shutdownGracePeriod=30s`, and `shutdownGracePeriodCriticalPods=10s`, kubelet will delay the node shutdown by 30 seconds. During the shutdown, the first 20 (30-10) seconds would be reserved for gracefully terminating normal pods, and the last 10 seconds would be reserved for terminating [critical pods](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/#marking-pod-as-critical). {{< note >}} When pods were evicted during the graceful node shutdown, they are marked as shutdown. Running `kubectl get pods` shows the status of the evicted pods as `Terminated`. And `kubectl describe pod` indicates that the pod was evicted because of node shutdown: ``` Reason:         Terminated Message:        Pod was terminated in response to imminent node shutdown. ``` {{< /note >}} ### Pod Priority based graceful node shutdown {#pod-priority-graceful-node-shutdown} {{< feature-state feature_gate_name=\"GracefulNodeShutdownBasedOnPodPriority\" >}} To provide more flexibility during graceful node shutdown around the ordering of pods during shutdown, graceful node shutdown honors the PriorityClass for Pods, provided that you enabled this feature in your cluster. The feature allows cluster administers to explicitly define the ordering of pods during graceful node shutdown based on [priority classes](/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass). The [Graceful Node Shutdown](#graceful-node-shutdown) feature, as described above, shuts down pods in two phases, non-critical pods, followed by critical pods. If additional flexibility is needed to explicitly define the ordering of pods during shutdown in a more granular way, pod priority based graceful shutdown can be used. When graceful node shutdown honors pod priorities, this makes it possible to do graceful node shutdown in multiple phases, each phase shutting down a particular priority class of pods. The kubelet can be configured with the exact phases and shutdown time per phase. Assuming the following custom pod [priority classes](/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass) in a cluster, |Pod priority class name|Pod priority class value| |-------------------------|------------------------| |`custom-class-a`         | 100000                 | |`custom-class-b`         | 10000                  | |`custom-class-c`         | 1000                   | |`regular/unset`          | 0                      | Within the [kubelet configuration](/docs/reference/config-api/kubelet-config.v1beta1/) the settings for `shutdownGracePeriodByPodPriority` could look like: |Pod priority class value|Shutdown period| |------------------------|---------------| | 100000                 |10 seconds     | | 10000                  |180 seconds    | | 1000                   |120 seconds    | | 0                      |60 seconds     | The corresponding kubelet config YAML configuration would be: ```yaml shutdownGracePeriodByPodPriority: - priority: 100000 shutdownGracePeriodSeconds: 10 - priority: 10000 shutdownGracePeriodSeconds: 180 - priority: 1000 shutdownGracePeriodSeconds: 120 - priority: 0 shutdownGracePeriodSeconds: 60 ``` The above table implies that any pod with `priority` value >= 100000 will get just 10 seconds to stop, any pod with value >= 10000 and < 100000 will get 180 seconds to stop, any pod with value >= 1000 and < 10000 will get 120 seconds to stop. Finally, all other pods will get 60 seconds to stop. One doesn't have to specify values corresponding to all of the classes. For example, you could instead use these settings: |Pod priority class value|Shutdown period| |------------------------|---------------| | 100000                 |300 seconds    | | 1000                   |120 seconds    | | 0                      |60 seconds     | In the above case, the pods with `custom-class-b` will go into the same bucket as `custom-class-c` for shutdown. If there are no pods in a particular range, then the kubelet does not wait for pods in that priority range. Instead, the kubelet immediately skips to the next priority class value range. If this feature is enabled and no configuration is provided, then no ordering action will be taken. Using this feature requires enabling the `GracefulNodeShutdownBasedOnPodPriority` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/), and setting `ShutdownGracePeriodByPodPriority` in the [kubelet config](/docs/reference/config-api/kubelet-config.v1beta1/) to the desired configuration containing the pod priority class values and their respective shutdown periods. {{< note >}} The ability to take Pod priority into account during graceful node shutdown was introduced as an Alpha feature in Kubernetes v1.23. In Kubernetes {{< skew currentVersion >}} the feature is Beta and is enabled by default. {{< /note >}} Metrics `graceful_shutdown_start_time_seconds` and `graceful_shutdown_end_time_seconds` are emitted under the kubelet subsystem to monitor node shutdowns. ## Non-graceful node shutdown handling {#non-graceful-node-shutdown} {{< feature-state feature_gate_name=\"NodeOutOfServiceVolumeDetach\" >}} A node shutdown action may not be detected by kubelet's Node Shutdown Manager, either because the command does not trigger the inhibitor locks mechanism used by kubelet or because of a user error, i.e., the ShutdownGracePeriod and ShutdownGracePeriodCriticalPods are not configured properly. Please refer to above section [Graceful Node Shutdown](#graceful-node-shutdown) for more details. When a node is shutdown but not detected by kubelet's Node Shutdown Manager, the pods that are part of a {{< glossary_tooltip text=\"StatefulSet\" term_id=\"statefulset\" >}} will be stuck in terminating status on the shutdown node and cannot move to a new running node. This is because kubelet on the shutdown node is not available to delete the pods so the StatefulSet cannot create a new pod with the same name. If there are volumes used by the pods, the VolumeAttachments will not be deleted from the original shutdown node so the volumes used by these pods cannot be attached to a new running node. As a result, the application running on the StatefulSet cannot function properly. If the original shutdown node comes up, the pods will be deleted by kubelet and new pods will be created on a different running node. If the original shutdown node does not come up, these pods will be stuck in terminating status on the shutdown node forever. To mitigate the above situation, a user can manually add the taint `node.kubernetes.io/out-of-service` with either `NoExecute` or `NoSchedule` effect to a Node marking it out-of-service. If the `NodeOutOfServiceVolumeDetach`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled on {{< glossary_tooltip text=\"kube-controller-manager\" term_id=\"kube-controller-manager\" >}}, and a Node is marked out-of-service with this taint, the pods on the node will be forcefully deleted if there are no matching tolerations on it and volume detach operations for the pods terminating on the node will happen immediately. This allows the Pods on the out-of-service node to recover quickly on a different node. During a non-graceful shutdown, Pods are terminated in the two phases: 1. Force delete the Pods that do not have matching `out-of-service` tolerations. 2. Immediately perform detach volume operation for such pods. {{< note >}} - Before adding the taint `node.kubernetes.io/out-of-service`, it should be verified that the node is already in shutdown or power off state (not in the middle of restarting). - The user is required to manually remove the out-of-service taint after the pods are moved to a new node and the user has checked that the shutdown node has been recovered since the user was the one who originally added the taint. {{< /note >}} ### Forced storage detach on timeout {#storage-force-detach-on-timeout} In any situation where a pod deletion has not succeeded for 6 minutes, kubernetes will force detach volumes being unmounted if the node is unhealthy at that instant. Any workload still running on the node that uses a force-detached volume will cause a violation of the [CSI specification](https://github.com/container-storage-interface/spec/blob/master/spec.md#controllerunpublishvolume), which states that `ControllerUnpublishVolume` \"**must** be called after all `NodeUnstageVolume` and `NodeUnpublishVolume` on the volume are called and succeed\". In such circumstances, volumes on the node in question might encounter data corruption. The forced storage detach behaviour is optional; users might opt to use the \"Non-graceful node shutdown\" feature instead. Force storage detach on timeout can be disabled by setting the `disable-force-detach-on-timeout` config field in `kube-controller-manager`. Disabling the force detach on timeout feature means that a volume that is hosted on a node that is unhealthy for more than 6 minutes will not have its associated [VolumeAttachment](/docs/reference/kubernetes-api/config-and-storage-resources/volume-attachment-v1/) deleted. After this setting has been applied, unhealthy pods still attached to a volumes must be recovered via the [Non-Graceful Node Shutdown](#non-graceful-node-shutdown) procedure mentioned above. {{< note >}} - Caution must be taken while using the [Non-Graceful Node Shutdown](#non-graceful-node-shutdown) procedure. - Deviation from the steps documented above can result in data corruption. {{< /note >}} </del> ## Swap memory management {#swap-memory} {{< feature-state feature_gate_name=\"NodeSwap\" >}}"}
{"_id":"q-en-website-9fef1fc78c79d0c8f222d59372b551eb7d9f47c5746e709a5f30bbc1217561ba","text":"sudo sysctl --system ``` <del> Make sure that the `br_netfilter` module is loaded before this step. This can be done by running `lsmod | grep br_netfilter`. To load it explicitly call `sudo modprobe br_netfilter`. </del> For more details please see the [Network Plugin Requirements](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#network-plugin-requirements) page. ## Check required ports"}
{"_id":"q-en-website-a0214217bb691dbe7b10cdc75237b8e57c73447ab3e388567647647c26bc08e6","text":"- containerPort: 80 ``` <del> ### Deployment with kubeadm and cluster API </del> <ins> ### kubeadmとクラスターAPIを使用したデプロイ </ins> <del> Kubeadm is becoming the de facto standard for users to deploy a Kubernetes cluster. Windows node support in kubeadm will come in a future release. We are also making investments in cluster API to ensure Windows nodes are properly provisioned. </del> <ins> Kubeadmは、ユーザーがKubernetesクラスターをデプロイするための事実上の標準になりつつあります。kubeadmのWindowsノードのサポートは、将来のリリースで提供予定です。Windowsノードが適切にプロビジョニングされるように、クラスターAPIにも投資しています。 </ins> <del> ### A few other key features * Beta support for Group Managed Service Accounts * More CNIs * More Storage Plugins </del> <ins> ### その他の主な機能 * グループ管理サービスアカウントのベータサポート * その他のCNI * その他のストレージプラグイン </ins>"}
{"_id":"q-en-website-a05b7979d9920739861309d2326901a1f06bb50fd09588f928d420347694658d","text":"#### Configure and start the Kubernetes cluster The startup process will first download all the required binaries automatically. <del> By default etcd version is 2.2.1, flannel version is 0.5.5 and k8s version is 1.1.4. </del> <ins> By default etcd version is 2.2.1, flannel version is 0.5.5 and k8s version is 1.1.8. </ins> You can customize your etcd version, flannel version, k8s version by changing corresponding variables `ETCD_VERSION` , `FLANNEL_VERSION` and `KUBE_VERSION` like following. ```shell <del> $ export KUBE_VERSION=1.0.5 </del> <ins> $ export KUBE_VERSION=1.1.8 </ins> $ export FLANNEL_VERSION=0.5.0 $ export ETCD_VERSION=2.2.0 ```"}
{"_id":"q-en-website-a05f2abd59021d3a6a81d9817466e3ae4fdd48a6fca4adbb8c33640a7d53bda2","text":"service.beta.kubernetes.io/aws-load-balancer-extra-security-groups: \"sg-53fae93f,sg-42efd82e\" #  A list of additional security groups to be added to the created ELB, this leaves the uniquely generated security group in place, this ensures that every ELB # has a unique security group ID and a matching permit line to allow traffic to the target worker nodes (service traffic and health checks). <del> # Security groups defined here can be shared between services. </del> <ins> # Security groups defined here can be shared between services. </ins> service.beta.kubernetes.io/aws-load-balancer-target-node-labels: \"ingress-gw,gw-name=public-api\" # A comma separated list of key-value pairs which are used"}
{"_id":"q-en-website-a0798901a8c5fae5784fae0299e8b706d46c603d71c46cfeb55a10d004cb6e6e","text":"<ins> --- title: \"Containers\" weight: 40 --- </ins>"}
{"_id":"q-en-website-a0ddc0f3ad6ab70107268290e37f6c578e928eddd85a0452fc0298bb7cc00fa1","text":"为客户提供无缝的服务。 <!-- <del> ## Enabling API groups </del> <ins> ## Enabling or disabling API groups </ins> Certain resources and API groups are enabled by default.  They can be enabled or disabled by setting `--runtime-config` <del> on apiserver. `--runtime-config` accepts comma separated values. For ex: to disable batch/v1, set </del> <ins> on apiserver. `--runtime-config` accepts comma separated values. For example: to disable batch/v1, set </ins> `--runtime-config=batch/v1=false`, to enable batch/v2alpha1, set `--runtime-config=batch/v2alpha1`. The flag accepts comma separated set of key=value pairs describing runtime configuration of the apiserver. <del> IMPORTANT: Enabling or disabling groups or resources requires restarting apiserver and controller-manager </del> <ins> Enabling or disabling groups or resources requires restarting apiserver and controller-manager </ins> to pick up the `--runtime-config` changes. -->"}
{"_id":"q-en-website-a3a019c74ffd026c879a8bdfb18ba45ae980fc7a9eac9cf425ffef3992796d7e","text":"<ins> --- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: default-deny-ingress spec: podSelector: {} policyTypes: - Ingress </ins>"}
{"_id":"q-en-website-a424342547749cb8f5ee1251c4c5389a2889a16f8b1a65b0c40050b7bfecd85b","text":"<ins> --- title: ConfigMap content_type: concept weight: 20 --- <!-- overview --> {{< glossary_definition term_id=\"configmap\" prepend=\"ConfigMapは、\" length=\"all\" >}} {{< caution >}} ConfigMapは機密性や暗号化を提供しません。保存したいデータが機密情報である場合は、ConfigMapの代わりに{{< glossary_tooltip text=\"Secret\" term_id=\"secret\" >}}を使用するか、追加の(サードパーティー)ツールを使用してデータが非公開になるようにしてください。 {{< /caution >}} <!-- body --> ## 動機 アプリケーションのコードとは別に設定データを設定するには、ConfigMapを使用します。 たとえば、アプリケーションを開発していて、(開発用時には)自分のコンピューター上と、(実際のトラフィックをハンドルするときは)クラウド上とで実行することを想像してみてください。あなたは、`DATABASE_HOST`という名前の環境変数を使用するコードを書きます。ローカルでは、この変数を`localhost`に設定します。クラウド上では、データベースコンポーネントをクラスター内に公開するKubernetesの{{< glossary_tooltip text=\"Service\" term_id=\"service\" >}}を指すように設定します。 こうすることで、必要であればクラウド上で実行しているコンテナイメージを取得することで、ローカルでも完全に同じコードを使ってデバッグができるようになります。 ## ConfigMapオブジェクト ConfigMapは、他のオブジェクトが使うための設定を保存できるAPI[オブジェクト](/ja/docs/concepts/overview/working-with-objects/kubernetes-objects/)です。ほとんどのKubernetesオブジェクトに`spec`セクションがあるのとは違い、ConfigMapにはアイテム(キー)と値を保存するための`data`セクションがあります。 ConfigMapの名前は、有効な[DNSのサブドメイン名](/ja/docs/concepts/overview/working-with-objects/names#dns-subdomain-names)でなければなりません。 ## ConfigMapとPod ConfigMapを参照して、ConfigMap内のデータを元にしてPod内のコンテナの設定をするPodの`spec`を書くことができます。このとき、PodとConfigMapは同じ{{< glossary_tooltip text=\"名前空間\" term_id=\"namespace\" >}}内に存在する必要があります。 以下に、ConfigMapの例を示します。単一の値を持つキーと、Configuration形式のデータ片のような値を持つキーがあります。 ```yaml apiVersion: v1 kind: ConfigMap metadata: name: game-demo data: # プロパティーに似たキー。各キーは単純な値にマッピングされている player_initial_lives: \"3\" ui_properties_file_name: \"user-interface.properties\" # # ファイルに似たキー game.properties: | enemy.types=aliens,monsters player.maximum-lives=5 user-interface.properties: | color.good=purple color.bad=yellow allow.textmode=true ``` ConfigMapを利用してPod内のコンテナを設定する方法には、次の4種類があります。 1. コマンドライン引数をコンテナのエントリーポイントに渡す 1. 環境変数をコンテナに渡す 1. 読み取り専用のボリューム内にファイルを追加し、アプリケーションがそのファイルを読み取る 1. Kubernetes APIを使用してConfigMapを読み込むコードを書き、そのコードをPod内で実行する これらのさまざまな方法は、利用するデータをモデル化するのに役立ちます。最初の3つの方法では、{{< glossary_tooltip text=\"kubelet\" term_id=\"kubelet\" >}}がPodのコンテナを起動する時にConfigMapのデータを使用します。 4番目の方法では、ConfigMapとそのデータを読み込むためのコードを自分自身で書く必要があります。しかし、Kubernetes APIを直接使用するため、アプリケーションはConfigMapがいつ変更されても更新イベントを受信でき、変更が発生したときにすぐに反応できます。この手法では、Kubernetes APIに直接アクセスすることで、別の名前空間にあるConfigMapにもアクセスできます。 以下に、Podを設定するために`game-demo`から値を使用するPodの例を示します。 ```yaml apiVersion: v1 kind: Pod metadata: name: configmap-demo-pod spec: containers: - name: demo image: game.example/demo-game env: # 環境変数を定義します。 - name: PLAYER_INITIAL_LIVES # ここではConfigMap内のキーの名前とは違い # 大文字が使われていることに着目してください。 valueFrom: configMapKeyRef: name: game-demo           # この値を取得するConfigMap。 key: player_initial_lives # 取得するキー。 - name: UI_PROPERTIES_FILE_NAME valueFrom: configMapKeyRef: name: game-demo key: ui_properties_file_name volumeMounts: - name: config mountPath: \"/config\" readOnly: true volumes: # Podレベルでボリュームを設定し、Pod内のコンテナにマウントします。 - name: config configMap: # マウントしたいConfigMapの名前を指定します。 name: game-demo # ファイルとして作成するConfigMapのキーの配列 items: - key: \"game.properties\" path: \"game.properties\" - key: \"user-interface.properties\" path: \"user-interface.properties\" ``` ConfigMapは1行のプロパティの値と複数行のファイルに似た形式の値を区別しません。問題となるのは、Podや他のオブジェクトによる値の使用方法です。 この例では、ボリュームを定義して、`demo`コンテナの内部で`/config`にマウントしています。これにより、ConfigMap内には4つのキーがあるにもかかわらず、2つのファイル`/config/game.properties`および`/config/user-interface.properties`だけが作成されます。 これは、Podの定義が`volumes`セクションで`items`という配列を指定しているためです。もし`items`の配列を完全に省略すれば、ConfigMap内の各キーがキーと同じ名前のファイルになり、4つのファイルが作成されます。 ## ConfigMapを使う ConfigMapは、データボリュームとしてマウントできます。ConfigMapは、Podへ直接公開せずにシステムの他の部品として使うこともできます。たとえば、ConfigMapには、システムの他の一部が設定のために使用するデータを保存できます。 {{< note >}} ConfigMapの最も一般的な使い方では、同じ名前空間にあるPod内で実行されているコンテナに設定を構成します。ConfigMapを独立して使用することもできます。 たとえば、ConfigMapに基づいて動作を調整する{{< glossary_tooltip text=\"アドオン\" term_id=\"addons\" >}}や{{< glossary_tooltip text=\"オペレーター\" term_id=\"operator-pattern\" >}}を見かけることがあるかもしれません。 {{< /note >}} ### ConfigMapをPodからファイルとして使う ConfigMapをPod内のボリュームで使用するには、次のようにします。 1. ConfigMapを作成するか、既存のConfigMapを使用します。複数のPodから同じConfigMapを参照することもできます。 1. Podの定義を修正して、`.spec.volumes[]`以下にボリュームを追加します。ボリュームに任意の名前を付け、`.spec.volumes[].configMap.name`フィールドにConfigMapオブジェクトへの参照を設定します。 1. ConfigMapが必要な各コンテナに`.spec.containers[].volumeMounts[]`を追加します。`.spec.containers[].volumeMounts[].readOnly = true`を指定して、`.spec.containers[].volumeMounts[].mountPath`には、ConfigMapのデータを表示したい未使用のディレクトリ名を指定します。 1. イメージまたはコマンドラインを修正して、プログラムがそのディレクトリ内のファイルを読み込むように設定します。ConfigMapの`data`マップ内の各キーが、`mountPath`以下のファイル名になります。 以下は、ボリューム内にConfigMapをマウントするPodの例です。 ```yaml apiVersion: v1 kind: Pod metadata: name: mypod spec: containers: - name: mypod image: redis volumeMounts: - name: foo mountPath: \"/etc/foo\" readOnly: true volumes: - name: foo configMap: name: myconfigmap ``` 使用したいそれぞれのConfigMapごとに、`.spec.volumes`内で参照する必要があります。 Pod内に複数のコンテナが存在する場合、各コンテナにそれぞれ別の`volumeMounts`のブロックが必要ですが、`.spec.volumes`はConfigMapごとに1つしか必要ありません。 #### マウントしたConfigMapの自動的な更新 ボリューム内で現在使用中のConfigMapが更新されると、射影されたキーも最終的に(eventually)更新されます。kubeletは定期的な同期のたびにマウントされたConfigMapが新しいかどうか確認します。しかし、kubeletが現在のConfigMapの値を取得するときにはローカルキャッシュを使用します。キャッシュの種類は、[KubeletConfiguration構造体](https://github.com/kubernetes/kubernetes/blob/{{< param \"docsbranch\" >}}/staging/src/k8s.io/kubelet/config/v1beta1/types.go)の中の`ConfigMapAndSecretChangeDetectionStrategy`フィールドで設定可能です。ConfigMapは、監視(デフォルト)、ttlベース、またはすべてのリクエストを直接APIサーバーへ単純にリダイレクトする方法のいずれかによって伝搬されます。その結果、ConfigMapが更新された瞬間から、新しいキーがPodに射影されるまでの遅延の合計は、最長でkubeletの同期期間+キャッシュの伝搬遅延になります。ここで、キャッシュの伝搬遅延は選択したキャッシュの種類に依存します(監視の伝搬遅延、キャッシュのttl、または0に等しくなります)。 {{< feature-state for_k8s_version=\"v1.18\" state=\"alpha\" >}} Kubernetesのアルファ版の機能である _イミュータブルなSecretおよびConfigMap_ は、個別のSecretやConfigMapをイミュータブルに設定するオプションを提供します。ConfigMapを広範に使用している(少なくとも数万のConfigMapがPodにマウントされている)クラスターでは、データの変更を防ぐことにより、以下のような利点が得られます。 - アプリケーションの停止を引き起こす可能性のある予想外の(または望まない)変更を防ぐことができる - ConfigMapをイミュータブルにマークして監視を停止することにより、kube-apiserverへの負荷を大幅に削減し、クラスターの性能が向上する この機能を使用するには、`ImmutableEmphemeralVolumes`[フィーチャーゲート](/ja/docs/reference/command-line-tools-reference/feature-gates/)を有効にして、SecretやConfigMapの`immutable`フィールドを`true`に設定してください。次に例を示します。 ```yaml apiVersion: v1 kind: ConfigMap metadata: ... data: ... immutable: true ``` {{< note >}} 一度ConfigMapやSecretがイミュータブルに設定すると、この変更を元に戻したり、`data`フィールドのコンテンツを変更することは*できません*。既存のPodは削除されたConfigMapのマウントポイントを保持するため、こうしたPodは再作成することをおすすめします。 {{< /note >}} ## {{% heading \"whatsnext\" %}} * [Secret](/docs/concepts/configuration/secret/)について読む。 * [Podを構成してConfigMapを使用する](/ja/docs/tasks/configure-pod-container/configure-pod-configmap/)を読む。 * コードを設定から分離する動機を理解するために[The Twelve-Factor App](https://12factor.net/ja/)を読む。 </ins>"}
{"_id":"q-en-website-a44719a9d859bd422c6fc5be1cb8f334bd35a5a9387b529b5de9cff05b1a0520","text":"weight: 40 --> <ins> {{< feature-state for_k8s_version=\"v1.19\" state=\"stable\" >}} <!-- leave this shortcode in place until the note about EvenPodsSpread is obsolete --> </ins> <!-- overview --> <!--"}
{"_id":"q-en-website-a4808d7293c947b3d08ccae6549d3cd62f55215494012efe9518632a6773c22b","text":"<del> --- reviewers: - bowei - zihongz title:  Debugging DNS Resolution content_type: task min-kubernetes-server-version: v1.6 --- <!-- overview --> This page provides hints on diagnosing DNS problems. ## {{% heading \"prerequisites\" %}} {{< include \"task-tutorial-prereqs.md\" >}} Your cluster must be configured to use the CoreDNS {{< glossary_tooltip text=\"addon\" term_id=\"addons\" >}} or its precursor, kube-dns. {{% version-check %}} <!-- steps --> ### Create a simple Pod to use as a test environment {{< codenew file=\"admin/dns/dnsutils.yaml\" >}} Use that manifest to create a Pod: ```shell kubectl apply -f https://k8s.io/examples/admin/dns/dnsutils.yaml ``` ``` pod/dnsutils created ``` …and verify its status: ```shell kubectl get pods dnsutils ``` ``` NAME      READY     STATUS    RESTARTS   AGE dnsutils   1/1       Running   0          <some-time> ``` Once that Pod is running, you can exec `nslookup` in that environment. If you see something like the following, DNS is working correctly. ```shell kubectl exec -i -t dnsutils -- nslookup kubernetes.default ``` ``` Server:    10.0.0.10 Address 1: 10.0.0.10 Name:      kubernetes.default Address 1: 10.0.0.1 ``` If the `nslookup` command fails, check the following: ### Check the local DNS configuration first Take a look inside the resolv.conf file. (See [Inheriting DNS from the node](/docs/tasks/administer-cluster/dns-custom-nameservers/#inheriting-dns-from-the-node) and [Known issues](#known-issues) below for more information) ```shell kubectl exec -ti dnsutils -- cat /etc/resolv.conf ``` Verify that the search path and name server are set up like the following (note that search path may vary for different cloud providers): ``` search default.svc.cluster.local svc.cluster.local cluster.local google.internal c.gce_project_id.internal nameserver 10.0.0.10 options ndots:5 ``` Errors such as the following indicate a problem with the CoreDNS (or kube-dns) add-on or with associated Services: ```shell kubectl exec -i -t dnsutils -- nslookup kubernetes.default ``` ``` Server:    10.0.0.10 Address 1: 10.0.0.10 nslookup: can't resolve 'kubernetes.default' ``` or ```shell kubectl exec -i -t dnsutils -- nslookup kubernetes.default ``` ``` Server:    10.0.0.10 Address 1: 10.0.0.10 kube-dns.kube-system.svc.cluster.local nslookup: can't resolve 'kubernetes.default' ``` ### Check if the DNS pod is running Use the `kubectl get pods` command to verify that the DNS pod is running. ```shell kubectl get pods --namespace=kube-system -l k8s-app=kube-dns ``` ``` NAME                       READY     STATUS    RESTARTS   AGE ... coredns-7b96bf9f76-5hsxb   1/1       Running   0           1h coredns-7b96bf9f76-mvmmt   1/1       Running   0           1h ... ``` {{< note >}} The value for label `k8s-app` is `kube-dns` for both CoreDNS and kube-dns deployments. {{< /note >}} If you see that no CoreDNS Pod is running or that the Pod has failed/completed, the DNS add-on may not be deployed by default in your current environment and you will have to deploy it manually. ### Check for errors in the DNS pod Use the `kubectl logs` command to see logs for the DNS containers. For CoreDNS: ```shell kubectl logs --namespace=kube-system -l k8s-app=kube-dns ``` Here is an example of a healthy CoreDNS log: ``` .:53 2018/08/15 14:37:17 [INFO] CoreDNS-1.2.2 2018/08/15 14:37:17 [INFO] linux/amd64, go1.10.3, 2e322f6 CoreDNS-1.2.2 linux/amd64, go1.10.3, 2e322f6 2018/08/15 14:37:17 [INFO] plugin/reload: Running configuration MD5 = 24e6c59e83ce706f07bcc82c31b1ea1c ``` See if there are any suspicious or unexpected messages in the logs. ### Is DNS service up? Verify that the DNS service is up by using the `kubectl get service` command. ```shell kubectl get svc --namespace=kube-system ``` ``` NAME         TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)             AGE ... kube-dns     ClusterIP   10.0.0.10      <none>        53/UDP,53/TCP        1h ... ``` {{< note >}} The service name is `kube-dns` for both CoreDNS and kube-dns deployments. {{< /note >}} If you have created the Service or in the case it should be created by default but it does not appear, see [debugging Services](/docs/tasks/debug-application-cluster/debug-service/) for more information. ### Are DNS endpoints exposed? You can verify that DNS endpoints are exposed by using the `kubectl get endpoints` command. ```shell kubectl get endpoints kube-dns --namespace=kube-system ``` ``` NAME       ENDPOINTS                       AGE kube-dns   10.180.3.17:53,10.180.3.17:53    1h ``` If you do not see the endpoints, see the endpoints section in the [debugging Services](/docs/tasks/debug-application-cluster/debug-service/) documentation. For additional Kubernetes DNS examples, see the [cluster-dns examples](https://github.com/kubernetes/examples/tree/master/staging/cluster-dns) in the Kubernetes GitHub repository. ### Are DNS queries being received/processed? You can verify if queries are being received by CoreDNS by adding the `log` plugin to the CoreDNS configuration (aka Corefile). The CoreDNS Corefile is held in a {{< glossary_tooltip text=\"ConfigMap\" term_id=\"configmap\" >}} named `coredns`. To edit it, use the command: ``` kubectl -n kube-system edit configmap coredns ``` Then add `log` in the Corefile section per the example below: ```yaml apiVersion: v1 kind: ConfigMap metadata: name: coredns namespace: kube-system data: Corefile: | .:53 { log errors health kubernetes cluster.local in-addr.arpa ip6.arpa { pods insecure upstream fallthrough in-addr.arpa ip6.arpa } prometheus :9153 proxy . /etc/resolv.conf cache 30 loop reload loadbalance } ``` After saving the changes, it may take up to minute or two for Kubernetes to propagate these changes to the CoreDNS pods. Next, make some queries and view the logs per the sections above in this document. If CoreDNS pods are receiving the queries, you should see them in the logs. Here is an example of a query in the log: ``` .:53 2018/08/15 14:37:15 [INFO] CoreDNS-1.2.0 2018/08/15 14:37:15 [INFO] linux/amd64, go1.10.3, 2e322f6 CoreDNS-1.2.0 linux/amd64, go1.10.3, 2e322f6 2018/09/07 15:29:04 [INFO] plugin/reload: Running configuration MD5 = 162475cdf272d8aa601e6fe67a6ad42f 2018/09/07 15:29:04 [INFO] Reloading complete 172.17.0.18:41675 - [07/Sep/2018:15:29:11 +0000] 59925 \"A IN kubernetes.default.svc.cluster.local. udp 54 false 512\" NOERROR qr,aa,rd,ra 106 0.000066649s ``` ## Known issues Some Linux distributions (e.g. Ubuntu) use a local DNS resolver by default (systemd-resolved). Systemd-resolved moves and replaces `/etc/resolv.conf` with a stub file that can cause a fatal forwarding loop when resolving names in upstream servers. This can be fixed manually by using kubelet's `--resolv-conf` flag to point to the correct `resolv.conf` (With `systemd-resolved`, this is `/run/systemd/resolve/resolv.conf`). kubeadm automatically detects `systemd-resolved`, and adjusts the kubelet flags accordingly. Kubernetes installs do not configure the nodes' `resolv.conf` files to use the cluster DNS by default, because that process is inherently distribution-specific. This should probably be implemented eventually. Linux's libc (a.k.a. glibc) has a limit for the DNS `nameserver` records to 3 by default. What's more, for the glibc versions which are older than glibc-2.17-222 ([the new versions update see this issue](https://access.redhat.com/solutions/58028)), the allowed number of DNS `search` records has been limited to 6 ([see this bug from 2005](https://bugzilla.redhat.com/show_bug.cgi?id=168253)). Kubernetes needs to consume 1 `nameserver` record and 3 `search` records. This means that if a local installation already uses 3 `nameserver`s or uses more than 3 `search`es while your glibc version is in the affected list, some of those settings will be lost. To work around the DNS `nameserver` records limit, the node can run `dnsmasq`, which will provide more `nameserver` entries. You can also use kubelet's `--resolv-conf` flag. To fix the DNS `search` records limit, consider upgrading your linux distribution or upgrading to an unaffected version of glibc. If you are using Alpine version 3.3 or earlier as your base image, DNS may not work properly due to a known issue with Alpine. Kubernetes [issue 30215](https://github.com/kubernetes/kubernetes/issues/30215) details more information on this. ## {{% heading \"whatsnext\" %}} - See [Autoscaling the DNS Service in a Cluster](/docs/tasks/administer-cluster/dns-horizontal-autoscaling/). - Read [DNS for Services and Pods](/docs/concepts/services-networking/dns-pod-service/) </del>"}
{"_id":"q-en-website-a4b0b3751bd06ad5d94b604b23d14bfc5ae6acb79b9ff0343a0d23f8f1eabb05","text":"<!-- overview --> <del> This document catalogs the communication paths between the API server and the Kubernetes cluster. </del> <ins> This document catalogs the communication paths between the {{< glossary_tooltip term_id=\"kube-apiserver\" text=\"API server\" >}} and the Kubernetes {{< glossary_tooltip text=\"cluster\" term_id=\"cluster\" length=\"all\" >}}. </ins> The intent is to allow users to customize their installation to harden the network configuration such that the cluster can be run on an untrusted network (or on fully public IPs on a cloud provider)."}
{"_id":"q-en-website-a56f25759da204bb730143f2a73853fa5b2f0e57c0a480c09213df28fb4d355f","text":"## {{% heading \"prerequisites\" %}} <del> {{< include \"task-tutorial-prereqs.md\" >}} {{< version-check >}} </del> <ins> {{< include \"task-tutorial-prereqs-node-upgrade.md\" >}} {{< version-check >}} </ins> * Familiarize yourself with [the process for upgrading the rest of your kubeadm cluster](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade). You will want to upgrade the control plane nodes before upgrading your Linux Worker nodes."}
{"_id":"q-en-website-a5f11d0bc7f3eef7eb1a0d3c19753e1c459401bf875167b3a90a96353737d1c2","text":"<ins> --- layout: blog title: 'Kubernetes史上最大の移行作業を完了' date: 2024-05-20 slug: completing-cloud-provider-migration --- **著者:** Andrew Sy Kim (Google), Michelle Au (Google), Walter Fender (Google), Michael McCune (Red Hat) **翻訳者:** Taisuke Okamoto (IDC Frontier Inc), [Junya Okabe](https://github.com/Okabe-Junya) (University of Tsukuba) Kubernetes v1.7以降、Kubernetesプロジェクトは、クラウドプロバイダーとの統合機能をKubernetesのコアコンポーネントから分離するという野心的な目標を追求してきました([KEP-2395](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/2395-removing-in-tree-cloud-providers/README.md))。 この統合機能はKubernetesの初期の開発と成長に重要な役割を果たしつつも、２つの重要な要因によってその分離が推進されました。 1つは、何百万行ものGoコードにわたってすべてのクラウドプロバイダーのネイティブサポートを維持することの複雑さが増大していたこと、もう1つは、Kubernetesを真にベンダーニュートラルなプラットフォームとして確立したいという願望です。 多くのリリースを経て、すべてのクラウドプロバイダー統合が、Kubernetesのコアリポジトリから外部プラグインに正常に移行されたことを喜ばしく思います。 当初の目的を達成したことに加えて、約150万行のコードを削除し、コアコンポーネントのバイナリサイズを約40%削減することで、Kubernetesを大幅に合理化しました。 この移行は、影響を受けるコンポーネントが多数あり、Google Cloud、AWS、Azure、OpenStack、vSphereの5つの初期クラウドプロバイダーの組み込み統合に依存していた重要なコードパスがあったため、複雑で長期にわたる作業となりました。 この移行を成功させるために、私たちは4つの新しいサブシステムを一から構築する必要がありました。 1. **クラウドコントローラーマネージャー** ([KEP-2392](https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/2392-cloud-controller-manager/README.md)) 2. **APIサーバーネットワークプロキシ** ([KEP-1281](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/1281-network-proxy)) 3. **kubeletクレデンシャルプロバイダープラグイン** ([KEP-2133](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2133-kubelet-credential-providers)) 4. **[CSI](https://github.com/container-storage-interface/spec?tab=readme-ov-file#container-storage-interface-csi-specification-)を使用するストレージの移行** ([KEP-625](https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/625-csi-migration/README.md)) 各サブシステムは、組み込み機能と同等の機能を実現するために不可欠であり、安全で信頼できる移行パスを使用して各サブシステムをGAレベルの成熟度にするために、いくつかのリリースが必要でした。 以下に、各サブシステムの詳細を説明します。 ### クラウドコントローラーマネージャー クラウドコントローラーマネージャーは、この取り組みで導入された最初の外部コンポーネントであり、`kube-controller-manager`と`kubelet`のうち、クラウドAPIと直接やり取りする機能を置き換えるものです。 この重要なコンポーネントは、ノードが実行されているクラウドのリージョンとゾーンを示すメタデータラベルや、クラウドプロバイダーのみが知っているIPアドレスを適用することにより、ノードを初期化する役割を担っています。 さらに、LoadBalancerタイプのServiceに対してクラウドロードバランサーをプロビジョニングするサービスコントローラーも実行します。 ![Kubernetesのコンポーネント](/images/docs/components-of-kubernetes.svg) 詳細については、Kubernetesドキュメントの[クラウドコントローラーマネージャー](/ja/docs/concepts/architecture/cloud-controller/)を参照してください。 ### APIサーバーネットワークプロキシ 2018年にSIG API Machineryと共同で開始されたAPIサーバーネットワークプロキシプロジェクトは、`kube-apiserver`内のSSHトンネラー機能を置き換えることを目的としていました。 このトンネラーは、Kubernetesのコントロールプレーンとノードとのトラフィックを安全にプロキシするために使用されていましたが、これらのSSHトンネルを確立するために、`kube-apiserver`内に組み込まれたプロバイダー固有の実装の詳細に大きく依存していました。 現在、APIサーバーネットワークプロキシは、`kube-apiserver`内のGAレベルの拡張ポイントとなっています。 これは、APIサーバーからノードへのトラフィックを安全なプロキシを介してルーティングできる汎用的なプロキシメカニズムを提供し、APIサーバーが実行されているクラウドプロバイダーを認識する必要がなくなりました。 このプロジェクトでは、本番環境での採用が進んでいるKonnectivityプロジェクトも導入されました。 APIサーバーネットワークプロキシの詳細については、[README](https://github.com/kubernetes-sigs/apiserver-network-proxy#readme)を参照してください。 ### kubeletのクレデンシャルプロバイダープラグイン `kubelet`のクレデンシャルプロバイダープラグインは、Google Cloud、AWS、またはAzureでホストされているイメージレジストリのクレデンシャルを動的に取得する`kubelet`の組み込み機能を置き換えるために開発されました。 従来の機能は便利で、`kubelet`がGCR、ECR、またはACRからイメージを取得するための短期間のトークンをシームレスに取得できるようにしていました。 しかし、Kubernetesの他の領域と同様に、これをサポートするには、`kubelet`が異なるクラウド環境とAPIについて特定の知識を持つ必要がありました。 2019年に導入されたクレデンシャルプロバイダープラグインメカニズムは、`kubelet`が様々なクラウドでホストされているイメージのクレデンシャルを動的に提供するプラグインバイナリを実行するための汎用的な拡張ポイントを提供します。 この拡張性により、`kubelet`の短期間のトークンを取得する機能が、最初の3つのクラウドプロバイダーを超えて拡張されました。 詳細については、[認証されたイメージプルのためのkubeletクレデンシャルプロバイダー](/ja/docs/concepts/containers/images/#kubelet-credential-provider)を参照してください。 ### ストレージプラグインのKubernetesコアからCSIへの移行 Container Storage Interface(CSI)は、Kubernetesやそのほかのコンテナオーケストレーターにおいてブロックおよびファイルストレージシステムを管理するためのコントロールプレーン標準であり、1.13でGAになりました。 これは、Kubernetesに直接組み込まれていたボリュームプラグインを、Kubernetesクラスター内のPodとして実行できるドライバーに置き換えるために設計されました。 これらのドライバーは、Kubernetes APIを介して`kube-controller-manager`ストレージコントローラーと通信し、ローカルのgRPCエンドポイントを介して`kubelet`と通信します。 現在、すべての主要なクラウドとストレージベンダーにわたって100以上のCSIドライバーが利用可能であり、Kubernetesでステートフルなワークロードが現実のものとなっています。 ただし、KubernetesコアのボリュームAPIの既存のすべてのユーザーをどのように扱うかという大きな課題が残っていました。 APIの後方互換性を維持するために、Kubernetesコアのボリューム APIを同等のCSI APIに変換するAPIトランスレーション層をコントローラーに組み込みました。 これにより、すべてのストレージ操作をCSIドライバーにリダイレクトすることができ、APIを削除せずにKubernetesコアのボリュームプラグインのコードを削除する道が開けました。 Kubernetesコアのストレージの移行の詳細については、[Kubernetes In-Tree to CSI Volume Migration Moves to Beta](https://kubernetes.io/blog/2019/12/09/kubernetes-1-17-feature-csi-migration-beta/)を参照してください。 ## 今後の展望 この移行は、ここ数年のSIG Cloud Providerがもっとも注力してきたことでした。 この重要なマイルストーンを達成したことで、これまでに構築してきた外部サブシステムを活用して、Kubernetesとクラウドプロバイダーをより良く統合するための新しい革新的な方法を模索する取り組みにシフトしていきます。 これには、クラスター内のノードがパブリッククラウドとプライベートクラウドの両方で実行できるハイブリッド環境でKubernetesをより賢くすることや、外部プロバイダーの開発者が統合の取り組みを簡素化・合理化するためのより良いツールとフレームワークを提供することが含まれます。 新機能やツール、フレームワークの開発が進む一方で、SIG Cloud Providerはテストの重要性も忘れてはいません。 SIGの将来の活動のもう1つの重点分野は、より多くのプロバイダーを含めるためのクラウドコントローラーテストの改善です。 この取り組みの最終目標は、できるだけ多くのプロバイダーを含むテストフレームワークを作成し、Kubernetesコミュニティに対して、Kubernetes環境に関する最高レベルの信頼性を提供することです。 v1.29より前のバージョンのKubernetesを使用していて、まだ外部クラウドプロバイダーに移行していない場合は、以前のブログ記事[Kubernetes 1.29: Cloud Provider Integrations Are Now Separate Components](/blog/2023/12/14/cloud-provider-integration-changes/)を確認することをおすすめします。 この記事では、私たちが行った変更について詳細な情報を提供し、外部プロバイダーへの移行方法についてガイダンスを提供しています。 v1.31以降、Kubernetesコアのクラウドプロバイダーは永続的に無効化され、Kubernetesのコアコンポーネントから削除されます。 貢献に興味がある方は、[隔週のSIGミーティング](https://github.com/kubernetes/community/tree/master/sig-cloud-provider#meetings)にぜひご参加ください！ </ins>"}
{"_id":"q-en-website-a610850aab965545e7e409bff8e384174d4fb0431ebac9705cf19806d9bb4abf","text":"following methods: * [TokenRequest API](/docs/reference/kubernetes-api/authentication-resources/token-request-v1/) <del> (recommended): Request a short-lived service account token using your *application code*. The token expires automatically and can rotate upon expiration. </del> <ins> (recommended): Request a short-lived service account token from within your own *application code*. The token expires automatically and can rotate upon expiration. If you have a legacy application that is not aware of Kubernetes, you could use a sidecar container within the same pod to fetch these tokens and make them available to the application workload. </ins> * [Token Volume Projection](/docs/tasks/configure-pod-container/configure-service-account/#service-account-token-volume-projection) <del> (recommended): In Kubernetes v1.20 and later, use the Pod specification to </del> <ins> (also recommended): In Kubernetes v1.20 and later, use the Pod specification to </ins> tell the kubelet to add the service account token to the Pod as a *projected volume*. Projected tokens expire automatically, and the kubelet rotates the token before it expires."}
{"_id":"q-en-website-a770e60485153ce8fa5b29f090e970c2efe6b76b85cfc625347050b52d58f69b","text":"If you would like to write a tutorial, see <del> [Content Page Types](/docs/home/contribute/style/page-content-types/) </del> <ins> [Content Page Types](/docs/contribute/style/page-content-types/) </ins> for information about the tutorial page type."}
{"_id":"q-en-website-a793689f0fb3104f5f69e02a6922db6884638150babff4d115b5595fa97f3a94","text":"{{% tab name=\"CentOS\" %}} <!-- <del> To install on the following operating systems, set the environment variable `OS` to the appropriate field in the following table: </del> <ins> To install on the following operating systems, set the environment variable `OS` to the appropriate field in the following table: </ins> | Operating system | `$OS`             | | ---------------- | ----------------- |"}
{"_id":"q-en-website-a827f522f2c1977ba9c761fa8b81f34da1eb14aa1316f68012078388bdf706d4","text":"## {{% heading \"whatsnext\" %}} <del> * Read about [creating a Pod that has an init container](/docs/tasks/configure-pod-container/configure-pod-initialization/#create-a-pod-that-has-an-init-container) * Learn how to [debug init containers](/docs/tasks/debug/debug-application/debug-init-containers/) * Read about an overview of [kubelet](/docs/reference/command-line-tools-reference/kubelet/) and [kubectl](/docs/reference/kubectl/) * Learn about the [types of probes](/docs/concepts/workloads/pods/pod-lifecycle/#types-of-probe): liveness, readiness, startup probe. </del> <ins> Learn more about the following: * [Creating a Pod that has an init container](/docs/tasks/configure-pod-container/configure-pod-initialization/#create-a-pod-that-has-an-init-container). * [Debug init containers](/docs/tasks/debug/debug-application/debug-init-containers/). * Overview of [kubelet](/docs/reference/command-line-tools-reference/kubelet/) and [kubectl](/docs/reference/kubectl/). * [Types of probes](/docs/concepts/workloads/pods/pod-lifecycle/#types-of-probe): liveness, readiness, startup probe. * [Sidecar containers](/docs/concepts/workloads/pods/sidecar-containers). </ins>"}
{"_id":"q-en-website-a8b0ca991c905915c73c069a74c619ef8ec4ad7a0bb3c3779e53ba04e5c9fe4b","text":"<ins> --- title: \"验证 kubectl 的安装效果\" description: \"如何验证 kubectl。\" headless: true --- <!-- --- title: \"verify kubectl install\" description: \"How to verify kubectl.\" headless: true --- --> <!-- In order for kubectl to find and access a Kubernetes cluster, it needs a [kubeconfig file](/docs/concepts/configuration/organize-cluster-access-kubeconfig/), which is created automatically when you create a cluster using [kube-up.sh](https://github.com/kubernetes/kubernetes/blob/master/cluster/kube-up.sh) or successfully deploy a Minikube cluster. By default, kubectl configuration is located at `~/.kube/config`. Check that kubectl is properly configured by getting the cluster state: --> 为了让 kubectl 能发现并访问 Kubernetes 集群，你需要一个 [kubeconfig 文件](/docs/zh/concepts/configuration/organize-cluster-access-kubeconfig/)， 该文件在 [kube-up.sh](https://github.com/kubernetes/kubernetes/blob/master/cluster/kube-up.sh) 创建集群时，或成功部署一个 Miniube 集群时，均会自动生成。 通常，kubectl 的配置信息存放于文件 `~/.kube/config` 中。 通过获取集群状态的方法，检查是否已恰当的配置了 kubectl： ```shell kubectl cluster-info ``` <!-- If you see a URL response, kubectl is correctly configured to access your cluster. If you see a message similar to the following, kubectl is not configured correctly or is not able to connect to a Kubernetes cluster. --> 如果返回一个 URL，则意味着 kubectl 成功的访问到了你的集群。 如果你看到如下所示的消息，则代表 kubectl 配置出了问题，或无法连接到 Kubernetes 集群。 ``` The connection to the server <server-name:port> was refused - did you specify the right host or port? （访问 <server-name:port> 被拒绝 - 你指定的主机和端口是否有误？） ``` <!-- For example, if you are intending to run a Kubernetes cluster on your laptop (locally), you will need a tool like Minikube to be installed first and then re-run the commands stated above. If kubectl cluster-info returns the url response but you can't access your cluster, to check whether it is configured properly, use: --> 例如，如果你想在自己的笔记本上（本地）运行 Kubernetes 集群，你需要先安装一个 Minikube 这样的工具，然后再重新运行上面的命令。 如果命令 `kubectl cluster-info` 返回了 url，但你还不能访问集群，那可以用以下命令来检查配置是否妥当： ```shell kubectl cluster-info dump ``` </ins>  No newline at end of file"}
{"_id":"q-en-website-a980aa5a028f02eb378420e55c7b6277306e9bc64ed8f65aaf1b3bde31db2876","text":"padding-top: 40px; } <ins> // Don't show announcements when javascript is not available html.no-js body div#announcement { display: none; } #announcement.display-announcement{ display: block; // apply this class to display the announcement } </ins> #announcement { // default background is blue; overrides are possible color: #fff; <ins> display: none; // When javascript is available, Let javascript handle the state of the announcement </ins> .announcement-main { margin-left: auto; margin-right: auto;"}
{"_id":"q-en-website-aa24104ef5b6f48b9b3410565bcf1354e6025f250daed1139d4471fff99d9c2b","text":"### SEE ALSO <del> * [kubectl](kubectl.md)\t - kubectl controls the Kubernetes cluster manager </del> <ins> * [kubectl](../kubectl.md)\t - kubectl controls the Kubernetes cluster manager </ins> ###### Auto generated by spf13/cobra on 12-Aug-2016"}
{"_id":"q-en-website-ab66c7c4d876d7e8410ebf8471cba0f88dd9b3d17627eb9183608b001825978a","text":"<ins> --- reviewers: - rickypai - thockin title: Adding entries to Pod /etc/hosts with HostAliases content_type: task weight: 60 min-kubernetes-server-version: 1.7 --- <!-- overview --> Adding entries to a Pod's `/etc/hosts` file provides Pod-level override of hostname resolution when DNS and other options are not applicable. You can add these custom entries with the HostAliases field in PodSpec. Modification not using HostAliases is not suggested because the file is managed by the kubelet and can be overwritten on during Pod creation/restart. <!-- steps --> ## Default hosts file content Start an Nginx Pod which is assigned a Pod IP: ```shell kubectl run nginx --image nginx ``` ``` pod/nginx created ``` Examine a Pod IP: ```shell kubectl get pods --output=wide ``` ``` NAME     READY     STATUS    RESTARTS   AGE    IP           NODE nginx    1/1       Running   0          13s    10.200.0.4   worker0 ``` The hosts file content would look like this: ```shell kubectl exec nginx -- cat /etc/hosts ``` ``` # Kubernetes-managed hosts file. 127.0.0.1\tlocalhost ::1\tlocalhost ip6-localhost ip6-loopback fe00::0\tip6-localnet fe00::0\tip6-mcastprefix fe00::1\tip6-allnodes fe00::2\tip6-allrouters 10.200.0.4\tnginx ``` By default, the `hosts` file only includes IPv4 and IPv6 boilerplates like `localhost` and its own hostname. ## Adding additional entries with hostAliases In addition to the default boilerplate, you can add additional entries to the `hosts` file. For example: to resolve `foo.local`, `bar.local` to `127.0.0.1` and `foo.remote`, `bar.remote` to `10.1.2.3`, you can configure HostAliases for a Pod under `.spec.hostAliases`: {{< codenew file=\"service/networking/hostaliases-pod.yaml\" >}} You can start a Pod with that configuration by running: ```shell kubectl apply -f https://k8s.io/examples/service/networking/hostaliases-pod.yaml ``` ``` pod/hostaliases-pod created ``` Examine a Pod's details to see its IPv4 address and its status: ```shell kubectl get pod --output=wide ``` ``` NAME                           READY     STATUS      RESTARTS   AGE       IP              NODE hostaliases-pod                0/1       Completed   0          6s        10.200.0.5      worker0 ``` The `hosts` file content looks like this: ```shell kubectl logs hostaliases-pod ``` ``` # Kubernetes-managed hosts file. 127.0.0.1\tlocalhost ::1\tlocalhost ip6-localhost ip6-loopback fe00::0\tip6-localnet fe00::0\tip6-mcastprefix fe00::1\tip6-allnodes fe00::2\tip6-allrouters 10.200.0.5\thostaliases-pod # Entries added by HostAliases. 127.0.0.1\tfoo.local\tbar.local 10.1.2.3\tfoo.remote\tbar.remote ``` with the additional entries specified at the bottom. ## Why does the kubelet manage the hosts file? {#why-does-kubelet-manage-the-hosts-file} The kubelet [manages](https://github.com/kubernetes/kubernetes/issues/14633) the `hosts` file for each container of the Pod to prevent Docker from [modifying](https://github.com/moby/moby/issues/17190) the file after the containers have already been started. {{< caution >}} Avoid making manual changes to the hosts file inside a container. If you make manual changes to the hosts file, those changes are lost when the container exits. {{< /caution >}} </ins>"}
{"_id":"q-en-website-ac98d5f712f4f5461b107d5e2a5182907452567b63ca3d614032948d64e568a5","text":"### CNI-Genie from Huawei <del> [CNI-Genie](https://github.com/Huawei-PaaS/CNI-Genie) is a CNI plugin that enables Kubernetes to [simultaneously have access to different implementations](https://github.com/Huawei-PaaS/CNI-Genie/blob/master/docs/multiple-cni-plugins/README.md#what-cni-genie-feature-1-multiple-cni-plugins-enables) of the [Kubernetes network model](/docs/concepts/cluster-administration/networking/#the-kubernetes-network-model) in runtime. This includes any implementation that runs as a [CNI plugin](https://github.com/containernetworking/cni#3rd-party-plugins), such as [Flannel](https://github.com/coreos/flannel#flannel), [Calico](https://docs.projectcalico.org/), [Weave-net](https://www.weave.works/products/weave-net/). </del> <ins> [CNI-Genie](https://github.com/cni-genie/CNI-Genie) is a CNI plugin that enables Kubernetes to [simultaneously have access to different implementations](https://github.com/cni-genie/CNI-Genie/blob/master/docs/multiple-cni-plugins/README.md#what-cni-genie-feature-1-multiple-cni-plugins-enables) of the [Kubernetes network model](/docs/concepts/cluster-administration/networking/#the-kubernetes-network-model) in runtime. This includes any implementation that runs as a [CNI plugin](https://github.com/containernetworking/cni#3rd-party-plugins), such as [Flannel](https://github.com/flannel-io/flannel#flannel), [Calico](https://projectcalico.docs.tigera.io/about/about-calico/), [Weave-net](https://www.weave.works/oss/net/). </ins> <del> CNI-Genie also supports [assigning multiple IP addresses to a pod](https://github.com/Huawei-PaaS/CNI-Genie/blob/master/docs/multiple-ips/README.md#feature-2-extension-cni-genie-multiple-ip-addresses-per-pod), each from a different CNI plugin. </del> <ins> CNI-Genie also supports [assigning multiple IP addresses to a pod](https://github.com/cni-genie/CNI-Genie/blob/master/docs/multiple-ips/README.md#feature-2-extension-cni-genie-multiple-ip-addresses-per-pod), each from a different CNI plugin. </ins> ### cni-ipvlan-vpc-k8s [cni-ipvlan-vpc-k8s](https://github.com/lyft/cni-ipvlan-vpc-k8s) contains a set"}
{"_id":"q-en-website-ace6ae17b40822077cda64821e6a6ced04cd16e2f6447130e46db94f2ad0ee60","text":"<!-- body --> <del> ## Introduction </del> Kubernetes DNS schedules a DNS Pod and Service on the cluster, and configures the kubelets to tell individual containers to use the DNS Service's IP to resolve DNS names."}
{"_id":"q-en-website-b04837b3bc96b7bef191b2290f3b037a3b7df076897c65086719a8ddea7581a0","text":"### Flannel <del> [Flannel](https://github.com/coreos/flannel#flannel) is a very simple overlay </del> <ins> [Flannel](https://github.com/flannel-io/flannel#flannel) is a very simple overlay </ins> network that satisfies the Kubernetes requirements. Many people have reported success with Flannel and Kubernetes."}
{"_id":"q-en-website-b2ce14faebdb72afcc0c78028089e9810e518da18b6f0d6f83f7806d9e4cb53c","text":"{{< glossary_definition term_id=\"etcd\" length=\"all\" prepend=\"etcd is a \">}} ## {{% heading \"prerequisites\" %}} {{< include \"task-tutorial-prereqs.md\" >}} {{< version-check >}} <!-- steps --> ## Prerequisites * Run etcd as a cluster of odd members. <del> * etcd is a leader-based distributed system. Ensure that the leader periodically send heartbeats on time to all followers to keep the cluster stable. </del> <ins> * etcd is a leader-based distributed system. Ensure that the leader periodically send heartbeats on time to all followers to keep the cluster stable. </ins> * Ensure that no resource starvation occurs. <del> Performance and stability of the cluster is sensitive to network and disk IO. Any resource starvation can lead to heartbeat timeout, causing instability of the cluster. An unstable etcd indicates that no leader is elected. Under such circumstances, a cluster cannot make any changes to its current state, which implies no new pods can be scheduled. </del> <ins> Performance and stability of the cluster is sensitive to network and disk I/O. Any resource starvation can lead to heartbeat timeout, causing instability of the cluster. An unstable etcd indicates that no leader is elected. Under such circumstances, a cluster cannot make any changes to its current state, which implies no new pods can be scheduled. </ins> <del> * Keeping stable etcd clusters is critical to the stability of Kubernetes clusters. Therefore, run etcd clusters on dedicated machines or isolated environments for [guaranteed resource requirements](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/hardware.md#hardware-recommendations). </del> <ins> * Keeping etcd clusters stable is critical to the stability of Kubernetes clusters. Therefore, run etcd clusters on dedicated machines or isolated environments for [guaranteed resource requirements](https://etcd.io/docs/current/op-guide/hardware/). </ins> * The minimum recommended version of etcd to run in production is `3.2.10+`. ## Resource requirements <del> Operating etcd with limited resources is suitable only for testing purposes. For deploying in production, advanced hardware configuration is required. Before deploying etcd in production, see [resource requirement reference documentation](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/hardware.md#example-hardware-configurations). </del> <ins> Operating etcd with limited resources is suitable only for testing purposes. For deploying in production, advanced hardware configuration is required. Before deploying etcd in production, see [resource requirement reference](https://etcd.io/docs/current/op-guide/hardware/#example-hardware-configurations). </ins> ## Starting etcd clusters"}
{"_id":"q-en-website-b370ea681d2424c945f225dc97fdf0ec4fbb6b0de4429b5f2d5f6d790c952633","text":"hello world ``` <del> ``` </del> <ins> ```shell </ins> # we can \"uninstall\" a plugin, by simply removing it from our PATH sudo rm /usr/local/bin/kubectl-hello ```"}
{"_id":"q-en-website-b4cf95865d87a3f0e77e8b3842d947025c4a4ed66498c0ba891240d1d4131c67","text":"<ins> --- title: \"zsh 自动补全\" description: \"zsh 自动补全的一些可选配置\" headless: true --- <!-- --- title: \"zsh auto-completion\" description: \"Some optional configuration for zsh auto-completion.\" headless: true --- --> <!-- The kubectl completion script for Zsh can be generated with the command `kubectl completion zsh`. Sourcing the completion script in your shell enables kubectl autocompletion. To do so in all your shell sessions, add the following to your `~/.zshrc` file: --> kubectl 通过命令 `kubectl completion zsh` 生成 Zsh 自动补全脚本。 在 shell 中导入（Sourcing）该自动补全脚本，将启动 kubectl 自动补全功能。 为了在所有的 shell 会话中实现此功能，请将下面内容加入到文件 `~/.zshrc` 中。 ```zsh source <(kubectl completion zsh) ``` <!-- If you have an alias for kubectl, you can extend shell completion to work with that alias: --> 如果你为 kubectl 定义了别名，可以扩展脚本补全，以兼容该别名。 ```zsh echo 'alias k=kubectl' >>~/.zshrc echo 'complete -F __start_kubectl k' >>~/.zshrc ``` <!-- After reloading your shell, kubectl autocompletion should be working. If you get an error like `complete:13: command not found: compdef`, then add the following to the beginning of your `~/.zshrc` file: --> 重新加载 shell 后，kubectl 自动补全功能将立即生效。 如果你收到 `complete:13: command not found: compdef` 这样的错误提示，那请将下面内容添加到 `~/.zshrc` 文件的开头： ```zsh autoload -Uz compinit compinit ``` </ins>"}
{"_id":"q-en-website-b511485a9ce8fe9ed7353c658b85b70a6654e25ede094107f9bb5ca135e3a26e","text":"* `apiserver_flowcontrol_current_inqueue_requests` is a gauge vector holding the instantaneous number of queued (not executing) requests, <del> broken down by the labels `priorityLevel` and `flowSchema`. </del> <ins> broken down by the labels `priority_level` and `flow_schema`. </ins> * `apiserver_flowcontrol_current_executing_requests` is a gauge vector holding the instantaneous number of executing (not waiting in a <del> queue) requests, broken down by the labels `priorityLevel` and `flowSchema`. </del> <ins> queue) requests, broken down by the labels `priority_level` and `flow_schema`. </ins> * `apiserver_flowcontrol_priority_level_request_count_samples` is a histogram vector of observations of the then-current number of requests broken down by the labels `phase` (which takes on the <del> values `waiting` and `executing`) and `priorityLevel`.  Each </del> <ins> values `waiting` and `executing`) and `priority_level`.  Each </ins> histogram gets observations taken periodically, up through the last activity of the relevant sort.  The observations are made at a high rate."}
{"_id":"q-en-website-b523eb97dcab54dcb08b540d2bd0a4075bfb211c5afa6eff34b278ff78ac6c93","text":"If you need access to multiple registries, you can create one secret for each registry. <del> Kubelet will merge any `imagePullSecrets` into a single virtual `.docker/config.json` </del> ## {{% heading \"whatsnext\" %}}"}
{"_id":"q-en-website-b82de94597e065b86b9dd3324c5c8c508ba3ac24b447194f755c510a37c6dac5","text":"abstract: \"자동화된 컨테이너 배포, 스케일링과 관리\" cid: home --- <del> {{< announcement >}} {{< deprecationwarning >}} </del> {{< blocks/section id=\"oceanNodes\" >}} {{% blocks/feature image=\"flower\" %}}"}
{"_id":"q-en-website-b891a5474d3acf87a75d8c82f045d672cdb50bad35069127abfcc5dd79ad0e9a","text":"# replace <node-to-drain> with the name of your node kubectl uncordon <node-to-drain> ``` <ins> ## {{% heading \"whatsnext\" %}} * See how to [Upgrade Linux nodes](/docs/tasks/administer-cluster/kubeadm/upgrading-linux-nodes/). </ins>"}
{"_id":"q-en-website-b8a2b3f2a3e929832ba0681431aefe521b34fb5f533ae2112313c58f37f46b9c","text":"Inspecting the logs for docker may also be useful: ```sh <del> journalctl -ul docker </del> <ins> journalctl -u docker </ins> ``` ## Pods in `RunContainerError`, `CrashLoopBackOff` or `Error` state"}
{"_id":"q-en-website-b9e6d578bd3d8d4e756298a7b1afd06841b2f7c38473394ee21dc72c70ed189c","text":"The Kubernetes DNS server is the only way to access `ExternalName` Services. You can find more information about `ExternalName` resolution in <del> [DNS Pods and Services](/docs/concepts/services-networking/dns-pod-service/). </del> <ins> [DNS for Services and Pods](/docs/concepts/services-networking/dns-pod-service/). </ins> ## Headless Services"}
{"_id":"q-en-website-ba846d6461a23beb63b9e030fb99f85def98cac6dd4c38cd9287bb534071808a","text":"* [Removing Dockershim from kubelet](https://github.com/kubernetes/enhancements/issues/2221): the Container Runtime Interface (CRI) for Docker (i.e. Dockershim) is currently a built-in container runtime in the kubelet code base. It was deprecated in v1.20. As of v1.24, the kubelet will no longer have dockershim. Check out this blog on [what you need to do be ready for v1.24](/blog/2022/03/31/ready-for-dockershim-removal/). * [Storage capacity tracking for pod scheduling](https://github.com/kubernetes/enhancements/issues/1472): The CSIStorageCapacity API supports exposing currently available storage capacity via CSIStorageCapacity objects and enhances scheduling of pods that use CSI volumes with late binding. In v1.24, the CSIStorageCapacity API will be stable. The API graduating to stable initates the deprecation of the v1beta1 CSIStorageCapacity API. Refer to the [Storage Capacity Constraints for Pod Scheduling KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1472-storage-capacity-tracking) for more information. * [The `master` label is no longer present on kubeadm control plane nodes](https://github.com/kubernetes/kubernetes/pull/107533). For new clusters, the label 'node-role.kubernetes.io/master' will no longer be added to control plane nodes, only the label 'node-role.kubernetes.io/control-plane' will be added. For more information, refer to [KEP-2067: Rename the kubeadm \"master\" label and taint](https://github.com/kubernetes/enhancements/tree/master/keps/sig-cluster-lifecycle/kubeadm/2067-rename-master-label-taint). <del> * [VolumeSnapshot v1beta1 CRD will be removed](https://github.com/kubernetes/enhancements/issues/177). Volume snapshot and restore functionality for Kubernetes and the [Container Storage Interface](https://github.com/container-storage-interface/spec/blob/master/spec.md) (CSI), which provides standardized APIs design (CRDs) and adds PV snapshot/restore support for CSI volume drivers, entered beta in v1.20. VolumeSnapshot v1beta1 was deprecated in v1.21 and is now unsupported. Refer to [KEP-177: CSI Snapshot](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/177-volume-snapshot#kep-177-csi-snapshot) and [kubernetes-csi/external-snapshotter](https://github.com/kubernetes-csi/external-snapshotter/releases/tag/v4.1.0) for more information. </del> <ins> * [VolumeSnapshot v1beta1 CRD will be removed](https://github.com/kubernetes/enhancements/issues/177). Volume snapshot and restore functionality for Kubernetes and the [Container Storage Interface](https://github.com/container-storage-interface/spec/blob/master/spec.md) (CSI), which provides standardized APIs design (CRDs) and adds PV snapshot/restore support for CSI volume drivers, moved to GA in v1.20. VolumeSnapshot v1beta1 was deprecated in v1.20 and will become unsupported with the v1.24 release. Refer to [KEP-177: CSI Snapshot](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/177-volume-snapshot#kep-177-csi-snapshot) and the [Volume Snapshot GA blog](/blog/2020/12/10/kubernetes-1.20-volume-snapshot-moves-to-ga/) blog article for more information. </ins> ## What to do"}
{"_id":"q-en-website-baf563b1a37db6ba47190962ddbaff1d127f1391e99287fcb315db48456402e5","text":"You can use {{< glossary_tooltip term_id=\"containerd\" text=\"ContainerD\" >}} 1.4.0+ as the container runtime for Kubernetes nodes that run Windows. <del> Learn how to [install ContainerD on a Windows node](/docs/setup/production-environment/container-runtimes/#install-containerd). </del> <ins> Learn how to [install ContainerD on a Windows node](/docs/setup/production-environment/container-runtimes/#containerd). </ins> {{< note >}} There is a [known limitation](/docs/tasks/configure-pod-container/configure-gmsa/#gmsa-limitations) when using GMSA with containerd to access Windows network shares, which requires a"}
{"_id":"q-en-website-be2a92e7dfeb27b0a8903490b1122a9700e30791ec77dc4f4ed9287d0f34c817","text":"```shell kubectl get -f myapp.yaml <ins> ``` 実行結果は下記のようになります。 ``` </ins> NAME        READY     STATUS    RESTARTS   AGE myapp-pod   1/1       Running   0          9m ``` <del> このシンプルな例を独自のInitコンテナを作成する際の参考にしてください。[次の項目](#whats-next)にさらに詳細な使用例に関するリンクがあります。 </del> <ins> このシンプルな例を独自のInitコンテナを作成する際の参考にしてください。[次の項目](#what-s-next)にさらに詳細な使用例に関するリンクがあります。 </ins> ## Initコンテナのふるまいに関する詳細 {#detailed-behavior} <del> Podの起動時は各Initコンテナが起動状態となるまで、kubeletはネットワーキングおよびストレージを利用可能な状態にしません。また、kubeletはPodのspecに定義された順番に従ってPodのInitコンテナを起動します。各Initコンテナは次のInitコンテナが起動する前に正常に終了しなくてはなりません。もしあるInitコンテナがランタイムもしくはエラーにより起動失敗した場合、そのPodの`restartPolicy`の値に従ってリトライされます。しかし、もしPodの`restartPolicy`が`Always`に設定されていた場合、Initコンテナの`restartPolicy`は`OnFailure`が適用されます。 </del> <ins> Podの起動時に、kubeletはネットワークおよびストレージの準備が整うまで、Initコンテナを実行可能な状態にしません。また、kubeletはPodのspecに定義された順番に従ってPodのInitコンテナを起動します。 各Initコンテナは次のInitコンテナが起動する前に正常に終了しなくてはなりません。もしあるInitコンテナがランタイムにより起動失敗した場合、もしくはエラーで終了した場合、そのPodの`restartPolicy`の値に従ってリトライされます。しかし、もしPodの`restartPolicy`が`Always`に設定されていた場合、Initコンテナの`restartPolicy`は`OnFailure`が適用されます。 </ins> Podは全てのInitコンテナが完了するまで`Ready`状態となりません。Initコンテナ上のポートはServiceによって集約されません。初期化中のPodのステータスは`Pending`となりますが、`Initialized`という値はtrueとなります。 <del> もしそのPodが[再起動](#pod-restart-reasons)されたとき、全てのInitコンテナは必ず再度実行されます。 </del> <ins> もしそのPodを[再起動](#pod-restart-reasons)するとき、または再起動されたとき、全てのInitコンテナは必ず再度実行されます。 </ins> Initコンテナの仕様の変更は、コンテナイメージのフィールドのみに制限されています。 Initコンテナのイメージフィールド値を変更すると、そのPodは再起動されます。 <del> Initコンテナは何度も再起動およびリトライ可能なため、べき等(Idempotent)である必要があります。特に、`EmptyDirs`にファイルを書き込むコードは、書き込み先のファイルがすでに存在している可能性を考慮に入れる必要があります。 </del> <ins> Initコンテナは何度も再起動、リトライおよび再実行可能なため、べき等(Idempotent)である必要があります。特に、`EmptyDirs`にファイルを書き込むコードは、書き込み先のファイルがすでに存在している可能性を考慮に入れる必要があります。 </ins> Initコンテナはアプリケーションコンテナの全てのフィールドを持っています。しかしKubernetesは、Initコンテナが完了と異なる状態を定義できないため`readinessProbe`が使用されることを禁止しています。これはバリデーションの際に適用されます。 <del> Initコンテナがずっと失敗し続けたままの状態を防ぐために、Podに`activeDeadlineSeconds`を、コンテナに`livenessProbe`をそれぞれ設定してください。`activeDeadlineSeconds`の設定はInitコンテナが実行中の時間にも適用されます。 </del> <ins> Initコンテナがずっと失敗し続けたままの状態を防ぐために、Podに`activeDeadlineSeconds`を設定してください。`activeDeadlineSeconds`の設定はInitコンテナが実行中の時間にも適用されます。しかし`activeDeadlineSeconds`はInitコンテナが終了した後でも効果があるため、チームがアプリケーションをJobとしてデプロイする場合にのみ使用することが推奨されています。 すでに正しく動作しているPodは`activeDeadlineSeconds`を設定すると強制終了されます。 </ins> Pod内の各アプリケーションコンテナとInitコンテナの名前はユニークである必要があります。他のコンテナと同じ名前を共有していた場合、バリデーションエラーが返されます。"}
{"_id":"q-en-website-be2dc79e1235e35d94affe0e8d054a5ec7c436d0134bb5e540bf5f609681fdc0","text":"{{% /tab %}} {{< /tabs >}} <ins> The preceding commands don't remove images, containers, volumes, or customized configuration files on your host. To delete them, follow Docker's instructions to [Uninstall Docker Engine](https://docs.docker.com/engine/install/ubuntu/#uninstall-docker-engine). {{< caution >}} Docker's instructions for uninstalling Docker Engine create a risk of deleting containerd. Be careful when executing commands. {{< /caution >}} </ins>"}
{"_id":"q-en-website-bfa42d775e889e1635adb0f4781e533816f0feec14ffc20edccde5fa2fd23c7a","text":"- Subject-matching properties: - `user`, type string; the user-string from `--token-auth-file`. If you specify `user`, it must match the username of the authenticated user. - `group`, type string; if you specify `group`, it must match one of the groups of the authenticated user. `system:authenticated` matches all authenticated requests. `system:unauthenticated` matches all unauthenticated requests. <del> - `readonly`, type boolean, when true, means that the policy only applies to get, list, and watch operations. </del> - Resource-matching properties: <del> - `apiGroup`, type string; an API group, such as `extensions`. `*` matches all API groups. - `namespace`, type string; a namespace string. `*` matches all resource requests. - `resource`, type string; a resource, such as `pods`. `*` matches all resource requests. </del> <ins> - `apiGroup`, type string; an API group. - Ex: `extensions` - Wildard: `*` matches all API groups. - `namespace`, type string; a namespace. - Ex: `kube-system` - Wildard: `*` matches all resource requests. - `resource`, type string; a resource type - Ex: `pods` - Wildcard: `*` matches all resource requests. </ins> - Non-resource-matching properties: <del> - `nonResourcePath`, type string; matches the non-resource request paths (like `/version` and `/apis`). `*` matches all non-resource requests. `/foo/*` matches `/foo/` and all of its subpaths. </del> <ins> - `nonResourcePath`, type string; non-resource request paths. - Ex: `/version` or `/apis` - Wildcard: - `*` matches all non-resource requests. - `/foo/*` matches `/foo/` and all of its subpaths. - `readonly`, type boolean, when true, means that the policy only applies to get, list, and watch operations. </ins> <del> An unset property is the same as a property set to the zero value for its type </del> <ins> **NOTES:** An unset property is the same as a property set to the zero value for its type </ins> (e.g. empty string, 0, false). However, unset should be preferred for readability."}
{"_id":"q-en-website-bfa600d136467e95250290743fe10e4e8aef1f457eaa562fa83f4a7d57383095","text":"<ins> --- title: ボリュームのスナップショット content_type: concept weight: 60 --- <!-- overview --> Kubernetesでは、*VolumeSnapshot*はストレージシステム上のボリュームのスナップショットを表します。このドキュメントは、Kubernetes[永続ボリューム](/ja/docs/concepts/storage/persistent-volumes/)に既に精通していることを前提としています。 <!-- body --> ## 概要 {#introduction} APIリソース`PersistentVolume`と`PersistentVolumeClaim`を使用してユーザーと管理者にボリュームをプロビジョニングする方法と同様に、`VolumeSnapshotContent`と`VolumeSnapshot`APIリソースは、ユーザーと管理者のボリュームスナップショットを作成するために提供されます。 `VolumeSnapshotContent`は、管理者によってプロビジョニングされたクラスター内のボリュームから取得されたスナップショットです。PersistentVolumeがクラスターリソースであるように、これはクラスターのリソースです。 `VolumeSnapshot`は、ユーザーによるボリュームのスナップショットの要求です。PersistentVolumeClaimに似ています。 `VolumeSnapshotClass`を使用すると、`VolumeSnapshot`に属するさまざまな属性を指定できます。これらの属性は、ストレージシステム上の同じボリュームから取得されたスナップショット間で異なる場合があるため、`PersistentVolumeClaim`の同じ`StorageClass`を使用して表現することはできません。 ボリュームスナップショットは、完全に新しいボリュームを作成することなく、特定の時点でボリュームの内容をコピーするための標準化された方法をKubernetesユーザーに提供します。この機能により、たとえばデータベース管理者は、編集または削除の変更を実行する前にデータベースをバックアップできます。 この機能を使用する場合、ユーザーは次のことに注意する必要があります。 - APIオブジェクト`VolumeSnapshot`、`VolumeSnapshotContent`、および`VolumeSnapshotClass`は{{< glossary_tooltip term_id=\"CustomResourceDefinition\" text=\"CRD\" >}}であり、コアAPIの一部ではありません。 - `VolumeSnapshot`のサポートは、CSIドライバーでのみ利用できます。 - `VolumeSnapshot`の展開プロセスの一環として、Kubernetesチームは、コントロールプレーンに展開されるスナップショットコントローラーと、CSIドライバーと共に展開されるcsi-snapshotterと呼ばれるサイドカーヘルパーコンテナを提供します。スナップショットコントローラーは、`VolumeSnapshot`および`VolumeSnapshotContent`オブジェクトを管理し、`VolumeSnapshotContent`オブジェクトの作成と削除を担当します。サイドカーcsi-snapshotterは、`VolumeSnapshotContent`オブジェクトを監視し、CSIエンドポイントに対して`CreateSnapshot`および`DeleteSnapshot`操作をトリガーします。 - スナップショットオブジェクトの厳密な検証を提供するvalidation Webhookサーバーもあります。これは、CSIドライバーではなく、スナップショットコントローラーおよびCRDと共にKubernetesディストリビューションによってインストールする必要があります。スナップショット機能が有効になっているすべてのKubernetesクラスターにインストールする必要があります。 - CSIドライバーは、ボリュームスナップショット機能を実装している場合と実装していない場合があります。ボリュームスナップショットのサポートを提供するCSIドライバーは、csi-snapshotterを使用する可能性があります。詳細については、[CSIドライバーのドキュメント](https://kubernetes-csi.github.io/docs/)を参照してください。 - CRDとスナップショットコントローラーのインストールは、Kubernetesディストリビューションの責任です。 ## ボリュームスナップショットとボリュームスナップショットのコンテンツのライフサイクル `VolumeSnapshotContents`はクラスター内のリソースです。`VolumeSnapshots`は、これらのリソースに対するリクエストです。`VolumeSnapshotContents`と`VolumeSnapshots`の間の相互作用は、次のライフサイクルに従います。 ### プロビジョニングボリュームのスナップショット スナップショットをプロビジョニングするには、事前プロビジョニングと動的プロビジョニングの2つの方法があります。 #### 事前プロビジョニング{#static} クラスター管理者は、多数の`VolumeSnapshotContents`を作成します。それらは、クラスターユーザーが使用できるストレージシステム上の実際のボリュームスナップショットの詳細を保持します。それらはKubernetesAPIに存在し、消費することができます。 #### 動的プロビジョニング 既存のスナップショットを使用する代わりに、スナップショットをPersistentVolumeClaimから動的に取得するように要求できます。[VolumeSnapshotClass](/ja/docs/concepts/storage/volume-snapshot-classes/)は、スナップショットを作成するときに使用するストレージプロバイダー固有のパラメーターを指定します。 ### バインディング スナップショットコントローラーは、事前プロビジョニングされたシナリオと動的にプロビジョニングされたシナリオの両方で、適切な`VolumeSnapshotContent`オブジェクトを使用した`VolumeSnapshot`オブジェクトのバインディングを処理します。バインディングは1対1のマッピングです。 事前プロビジョニングされたバインディングの場合、要求されたVolumeSnapshotContentオブジェクトが作成されるまで、VolumeSnapshotはバインドされないままになります。 ### スナップショットソース保護としてのPersistentVolumeClaim この保護の目的は、スナップショットがシステムから取得されている間、使用中の{{< glossary_tooltip text=\"PersistentVolumeClaim\" term_id=\"persistent-volume-claim\" >}}APIオブジェクトがシステムから削除されないようにすることです(これにより、データが失われる可能性があります）。 PersistentVolumeClaimのスナップショットが作成されている間、そのPersistentVolumeClaimは使用中です。スナップショットソースとしてアクティブに使用されているPersistentVolumeClaim APIオブジェクトを削除しても、PersistentVolumeClaimオブジェクトはすぐには削除されません。代わりに、PersistentVolumeClaimオブジェクトの削除は、スナップショットがReadyToUseになるか中止されるまで延期されます。 ### 削除 削除は`VolumeSnapshot`オブジェクトの削除によってトリガーされ、`DeletionPolicy`に従います。`DeletionPolicy`が`Delete`の場合、基になるストレージスナップショットは`VolumeSnapshotContent`オブジェクトとともに削除されます。`DeletionPolicy`が`Retain`の場合、基になるスナップショットと`VolumeSnapshotContent`の両方が残ります。 ## ボリュームスナップショット 各VolumeSnapshotには、仕様とステータスが含まれています。 ```yaml apiVersion: snapshot.storage.k8s.io/v1 kind: VolumeSnapshot metadata: name: new-snapshot-test spec: volumeSnapshotClassName: csi-hostpath-snapclass source: persistentVolumeClaimName: pvc-test ``` `persistentVolumeClaimName`は、スナップショットのPersistentVolumeClaimデータソースの名前です。このフィールドは、スナップショットを動的にプロビジョニングするために必要です。 ボリュームスナップショットは、属性`volumeSnapshotClassName`を使用して[VolumeSnapshotClass](/ja/docs/concepts/storage/volume-snapshot-classes/)の名前を指定することにより、特定のクラスを要求できます。何も設定されていない場合、利用可能な場合はデフォルトのクラスが使用されます。 事前プロビジョニングされたスナップショットの場合、次の例に示すように、スナップショットのソースとして`volumeSnapshotContentName`を指定する必要があります。事前プロビジョニングされたスナップショットには、`volumeSnapshotContentName`ソースフィールドが必要です。 ```yaml apiVersion: snapshot.storage.k8s.io/v1 kind: VolumeSnapshot metadata: name: test-snapshot spec: source: volumeSnapshotContentName: test-content ``` ## ボリュームスナップショットコンテンツ 各VolumeSnapshotContentには、仕様とステータスが含まれています。動的プロビジョニングでは、スナップショット共通コントローラーが`VolumeSnapshotContent`オブジェクトを作成します。以下に例を示します。 ```yaml apiVersion: snapshot.storage.k8s.io/v1 kind: VolumeSnapshotContent metadata: name: snapcontent-72d9a349-aacd-42d2-a240-d775650d2455 spec: deletionPolicy: Delete driver: hostpath.csi.k8s.io source: volumeHandle: ee0cfb94-f8d4-11e9-b2d8-0242ac110002 sourceVolumeMode: Filesystem volumeSnapshotClassName: csi-hostpath-snapclass volumeSnapshotRef: name: new-snapshot-test namespace: default uid: 72d9a349-aacd-42d2-a240-d775650d2455 ``` `volumeHandle`は、ストレージバックエンドで作成され、ボリュームの作成中にCSIドライバーによって返されるボリュームの一意の識別子です。このフィールドは、スナップショットを動的にプロビジョニングするために必要です。これは、スナップショットのボリュームソースを指定します。 事前プロビジョニングされたスナップショットの場合、(クラスター管理者として)次のように`VolumeSnapshotContent`オブジェクトを作成する必要があります。 ```yaml apiVersion: snapshot.storage.k8s.io/v1 kind: VolumeSnapshotContent metadata: name: new-snapshot-content-test spec: deletionPolicy: Delete driver: hostpath.csi.k8s.io source: snapshotHandle: 7bdd0de3-aaeb-11e8-9aae-0242ac110002 sourceVolumeMode: Filesystem volumeSnapshotRef: name: new-snapshot-test namespace: default ``` `snapshotHandle`は、ストレージバックエンドで作成されたボリュームスナップショットの一意の識別子です。このフィールドは、事前プロビジョニングされたスナップショットに必要です。この`VolumeSnapshotContent`が表すストレージシステムのCSIスナップショットIDを指定します。 `sourceVolumeMode`は、スナップショットが作成されるボリュームのモードです。`sourceVolumeMode`フィールドの値は、`Filesystem`または`Block`のいずれかです。ソースボリュームモードが指定されていない場合、Kubernetesはスナップショットをソースボリュームのモードが不明であるかのように扱います。 `volumeSnapshotRef`は、対応する`VolumeSnapshot`の参照です。`VolumeSnapshotContent`が事前プロビジョニングされたスナップショットとして作成されている場合、`volumeSnapshotRef`で参照される`VolumeSnapshot`がまだ存在しない可能性があることに注意してください。 ## スナップショットのボリュームモードの変換 {#convert-volume-mode} クラスターにインストールされている`VolumeSnapshots`APIが`sourceVolumeMode`フィールドをサポートしている場合、APIには、権限のないユーザーがボリュームのモードを変換するのを防ぐ機能があります。 クラスターにこの機能の機能があるかどうかを確認するには、次のコマンドを実行します。 ```yaml $ kubectl get crd volumesnapshotcontent -o yaml ``` ユーザーが既存の`VolumeSnapshot`から`PersistentVolumeClaim`を作成できるようにしたいが、ソースとは異なるボリュームモードを使用する場合は、`VolumeSnapshot`に対応する`VolumeSnapshotContent`にアノテーション`snapshot.storage.kubernetes.io/allowVolumeModeChange: \"true\"`を追加する必要があります。 事前プロビジョニングされたスナップショットの場合、クラスター管理者が`spec.sourceVolumeMode`を入力する必要があります。 この機能を有効にした`VolumeSnapshotContent`リソースの例は次のようになります。 ```yaml apiVersion: snapshot.storage.k8s.io/v1 kind: VolumeSnapshotContent metadata: name: new-snapshot-content-test annotations: - snapshot.storage.kubernetes.io/allowVolumeModeChange: \"true\" spec: deletionPolicy: Delete driver: hostpath.csi.k8s.io source: snapshotHandle: 7bdd0de3-aaeb-11e8-9aae-0242ac110002 sourceVolumeMode: Filesystem volumeSnapshotRef: name: new-snapshot-test namespace: default ``` ## スナップショットからのボリュームのプロビジョニング `PersistentVolumeClaim`オブジェクトの*dataSource*フィールドを使用して、スナップショットからのデータが事前に取り込まれた新しいボリュームをプロビジョニングできます。 詳細については、[ボリュームのスナップショットとスナップショットからのボリュームの復元](/ja/docs/concepts/storage/persistent-volumes/#volume-snapshot-and-restore-volume-from-snapshot-support)を参照してください。 </ins>"}
{"_id":"q-en-website-c27216a25e2f6197f9c963a66b1cf3716ec51deeebb2b8cb27a418287484d3ab","text":"Patch your Deployment again with this new patch: ```shell <del> kubectl patch deployment retainkeys-demo --type merge --patch-file patch-file-retainkeys.yaml </del> <ins> kubectl patch deployment retainkeys-demo --type strategic --patch-file patch-file-retainkeys.yaml </ins> ``` Examine the content of the Deployment:"}
{"_id":"q-en-website-c28412c9cc87935048373ce4c7899881947d2ae407e4782e9c2fdef39abf2d25","text":"/docs/concepts/configuration/container-command-args/     /docs/tasks/inject-data-application/define-command-argument-container/     301 /docs/concepts/configuration/manage-compute-resources-container/ /docs/concepts/configuration/manage-resources-containers/ 301 /docs/concepts/configuration/resource-bin-packing/      /docs/concepts/scheduling-eviction/resource-bin-packing/ 301 <ins> /id/docs/concepts/configuration/resource-bin-packing/      /id/docs/concepts/scheduling-eviction/resource-bin-packing/ 301 </ins> /docs/concepts/configuration/scheduler-perf-tuning/      /docs/concepts/scheduling-eviction/scheduler-perf-tuning/    301 /docs/concepts/configuration/scheduling-framework/     /docs/concepts/scheduling-eviction/scheduling-framework/    301 /docs/concepts/configuration/taint-and-toleration/     /docs/concepts/scheduling-eviction/taint-and-toleration/ 301"}
{"_id":"q-en-website-c2e9cebd3cbdfa2be0ba89ee22369aa21c0806c40fc19f5d7ffad4a9fc18902d","text":"之间的分布，例如区域（Region）、可用区（Zone）、节点和其他用户自定义拓扑域。 这样做有助于实现高可用并提升资源利用率。 <ins> <!-- {{< note >}} In versions of Kubernetes before v1.19, you must enable the `EvenPodsSpread` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) on the [API server](/docs/concepts/overview/components/#kube-apiserver) and the [scheduler](/docs/reference/generated/kube-scheduler/) in order to use Pod topology spread constraints. {{< /note >}} --> {{< note >}} 在 v1.19 之前的 Kubernetes 版本中，如果要使用 Pod 拓扑扩展约束，你必须在 [API 服务器](/zh/docs/concepts/overview/components/#kube-apiserver) 和[调度器](/zh/docs/reference/command-line-tools-referene/kube-scheduler/) 中启用 `EvenPodsSpread` [特性门控](/zh/docs/reference/command-line-tools-reference/feature-gates/)。 {{< /note >}} </ins> <!-- body --> <!--"}
{"_id":"q-en-website-c3c3e1c62e3ebceb6c033ce15d1e963d8f1e194037b38a23df348a7d1aff2b5f","text":"Refer to [Converting the volume mode of a Snapshot](/docs/concepts/storage/volume-snapshots/#convert-volume-mode) and the [Kubernetes CSI Developer Documentation](https://kubernetes-csi.github.io/docs/) for more information. <ins> ### scheduler.alpha.kubernetes.io/critical-pod (deprecated) Example: `scheduler.alpha.kubernetes.io/critical-pod: \"\"` Used on: Pod This annotation lets Kubernetes control plane know about a pod being a critical pod so that the descheduler will not remove this pod. {{< note >}} Starting in v1.16, this annotation was removed in favor of [Pod Priority](/docs/concepts/scheduling-eviction/pod-priority-preemption/). {{< /note >}} </ins> ## Annotations used for audit <!-- sorted by annotation -->"}
{"_id":"q-en-website-c3c50c54de295adddd1363800da5d9fbcf1620a6615937e83406f7c23f3075f8","text":"<ins> --- title: Bin Packing Sumber Daya untuk Sumber Daya Tambahan content_type: concept weight: 10 --- <!-- overview --> {{< feature-state for_k8s_version=\"1.16\" state=\"alpha\" >}} _Kube-scheduler_ dapat dikonfigurasikan untuk mengaktifkan pembungkusan rapat (_bin packing_) sumber daya bersama dengan sumber daya tambahan melalui fungsi prioritas `RequestedToCapacityRatioResourceAllocation`. Fungsi-fungsi prioritas dapat digunakan untuk menyempurnakan _kube-scheduler_ sesuai dengan kebutuhan. <!-- body --> ## Mengaktifkan _Bin Packing_ menggunakan RequestedToCapacityRatioResourceAllocation Sebelum Kubernetes 1.15, _kube-scheduler_ digunakan untuk memungkinkan mencetak skor berdasarkan rasio permintaan terhadap kapasitas sumber daya utama seperti CPU dan Memori. Kubernetes 1.16 menambahkan parameter baru ke fungsi prioritas yang memungkinkan pengguna untuk menentukan sumber daya beserta dengan bobot untuk setiap sumber daya untuk memberi nilai dari Node berdasarkan rasio permintaan terhadap kapasitas. Hal ini memungkinkan pengguna untuk _bin pack_ sumber daya tambahan dengan menggunakan parameter yang sesuai untuk meningkatkan pemanfaatan sumber daya yang langka dalam klaster yang besar. Perilaku `RequestedToCapacityRatioResourceAllocation` dari fungsi prioritas dapat dikontrol melalui pilihan konfigurasi yang disebut ` RequestToCapacityRatioArguments`. Argumen ini terdiri dari dua parameter yaitu `shape` dan `resources`. Shape memungkinkan pengguna untuk menyempurnakan fungsi menjadi yang paling tidak diminta atau paling banyak diminta berdasarkan nilai `utilization` dan `score`. Sumber daya terdiri dari `name` yang menentukan sumber daya mana yang dipertimbangkan selama penilaian dan `weight` yang menentukan bobot masing-masing sumber daya. Di bawah ini adalah contoh konfigurasi yang menetapkan `requestedToCapacityRatioArguments` pada perilaku _bin packing_ untuk sumber daya tambahan` intel.com/foo` dan `intel.com/bar` ```json { \"kind\" : \"Policy\", \"apiVersion\" : \"v1\", ... \"priorities\" : [ ... { \"name\": \"RequestedToCapacityRatioPriority\", \"weight\": 2, \"argument\": { \"requestedToCapacityRatioArguments\": { \"shape\": [ {\"utilization\": 0, \"score\": 0}, {\"utilization\": 100, \"score\": 10} ], \"resources\": [ {\"name\": \"intel.com/foo\", \"weight\": 3}, {\"name\": \"intel.com/bar\", \"weight\": 5} ] } } } ], } ``` **Fitur ini dinonaktifkan secara _default_** ### Tuning RequestedToCapacityRatioResourceAllocation Priority Function `shape` digunakan untuk menentukan perilaku dari fungsi `RequestedToCapacityRatioPriority`. ```yaml {\"utilization\": 0, \"score\": 0}, {\"utilization\": 100, \"score\": 10} ``` Argumen di atas memberikan Node nilai 0 jika utilisasi 0% dan 10 untuk utilisasi 100%, yang kemudian mengaktfikan perilaku _bin packing_. Untuk mengaktifkan dari paling yang tidak diminta, nilainya harus dibalik sebagai berikut. ```yaml {\"utilization\": 0, \"score\": 100}, {\"utilization\": 100, \"score\": 0} ``` `resources` adalah parameter opsional yang secara _default_ diatur ke: ``` yaml \"resources\": [ {\"name\": \"CPU\", \"weight\": 1}, {\"name\": \"Memory\", \"weight\": 1} ] ``` Ini dapat digunakan untuk menambahkan sumber daya tambahan sebagai berikut: ```yaml \"resources\": [ {\"name\": \"intel.com/foo\", \"weight\": 5}, {\"name\": \"CPU\", \"weight\": 3}, {\"name\": \"Memory\", \"weight\": 1} ] ``` Parameter `weight` adalah opsional dan diatur ke 1 jika tidak ditentukan. Selain itu, `weight` tidak dapat diatur ke nilai negatif. ### Bagaimana Fungsi Prioritas RequestedToCapacityRatioResourceAllocation Menilai Node Bagian ini ditujukan bagi kamu yang ingin memahami secara detail internal dari fitur ini. Di bawah ini adalah contoh bagaimana nilai dari Node dihitung untuk satu kumpulan nilai yang diberikan. ``` Sumber daya yang diminta intel.com/foo : 2 Memory: 256MB CPU: 2 Bobot dari sumber daya intel.com/foo : 5 Memory: 1 CPU: 3 FunctionShapePoint {{0, 0}, {100, 10}} Spesifikasi dari Node 1 Tersedia: intel.com/foo : 4 Memory : 1 GB CPU: 8 Digunakan: intel.com/foo: 1 Memory: 256MB CPU: 1 Nilai Node: intel.com/foo  = resourceScoringFunction((2+1),4) =  (100 - ((4-3)*100/4) =  (100 - 25) =  75 =  rawScoringFunction(75) = 7 Memory         = resourceScoringFunction((256+256),1024) = (100 -((1024-512)*100/1024)) = 50 = rawScoringFunction(50) = 5 CPU            = resourceScoringFunction((2+1),8) = (100 -((8-3)*100/8)) = 37.5 = rawScoringFunction(37.5) = 3 NodeScore   =  (7 * 5) + (5 * 1) + (3 * 3) / (5 + 1 + 3) =  5 Spesifikasi dari Node 2 Tersedia: intel.com/foo: 8 Memory: 1GB CPU: 8 Digunakan: intel.com/foo: 2 Memory: 512MB CPU: 6 Nilai Node: intel.com/foo  = resourceScoringFunction((2+2),8) =  (100 - ((8-4)*100/8) =  (100 - 25) =  50 =  rawScoringFunction(50) = 5 Memory         = resourceScoringFunction((256+512),1024) = (100 -((1024-768)*100/1024)) = 75 = rawScoringFunction(75) = 7 CPU            = resourceScoringFunction((2+6),8) = (100 -((8-8)*100/8)) = 100 = rawScoringFunction(100) = 10 NodeScore   =  (5 * 5) + (7 * 1) + (10 * 3) / (5 + 1 + 3) =  7 ``` </ins>"}
{"_id":"q-en-website-c49887b3ddeb27d17700c6aaac5539182d1ebf0c47dfae85271c0f81c57d770a","text":"Later in this page you can read about various kube-proxy implementations work. Overall, you should note that, when running `kube-proxy`, kernel level rules may be <del> modified (for example, iptables rules might get created), which won't get cleaned up, </del> <ins> modified (for example, iptables rules might get created), which won't get cleaned up, </ins> in some cases until you reboot.  Thus, running kube-proxy is something that should only be done by an administrator which understands the consequences of having a low level, privileged network proxying service on a computer.  Although the `kube-proxy`"}
{"_id":"q-en-website-c49aedf2b0de58cd4ae6b7d35fc18d0f60b328a69f33e6816a47cd4eb462ed00","text":"10.240.0.96 - - [06/Jun/2018:02:45:51 +0000] \"GET / HTTP/1.1\" 200 612 \"-\" \"curl/7.47.0\" \"-\" ``` <del> ### Run a pod sandbox Using `crictl` to run a pod sandbox is useful for debugging container runtimes. On a running Kubernetes cluster, the sandbox will eventually be stopped and deleted by the Kubelet. 1. Create a JSON file like the following: ```json { \"metadata\": { \"name\": \"nginx-sandbox\", \"namespace\": \"default\", \"attempt\": 1, \"uid\": \"hdishd83djaidwnduwk28bcsb\" }, \"log_directory\": \"/tmp\", \"linux\": { } } ``` 2. Use the `crictl runp` command to apply the JSON and run the sandbox. ```shell crictl runp pod-config.json ``` The ID of the sandbox is returned. ### Create a container Using `crictl` to create a container is useful for debugging container runtimes. On a running Kubernetes cluster, the container will eventually be stopped and deleted by the Kubelet. 1. Pull a busybox image ```shell crictl pull busybox ``` ```none Image is up to date for busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47 ``` 2. Create configs for the pod and the container: **Pod config**: ```json { \"metadata\": { \"name\": \"busybox-sandbox\", \"namespace\": \"default\", \"attempt\": 1, \"uid\": \"aewi4aeThua7ooShohbo1phoj\" }, \"log_directory\": \"/tmp\", \"linux\": { } } ``` **Container config**: ```json { \"metadata\": { \"name\": \"busybox\" }, \"image\":{ \"image\": \"busybox\" }, \"command\": [ \"top\" ], \"log_path\":\"busybox.log\", \"linux\": { } } ``` 3. Create the container, passing the ID of the previously-created pod, the container config file, and the pod config file. The ID of the container is returned. ```shell crictl create f84dd361f8dc51518ed291fbadd6db537b0496536c1d2d6c05ff943ce8c9a54f container-config.json pod-config.json ``` 4. List all containers and verify that the newly-created container has its state set to `Created`. ```shell crictl ps -a ``` The output is similar to this: ``` CONTAINER ID        IMAGE               CREATED             STATE               NAME                ATTEMPT 3e025dd50a72d       busybox             32 seconds ago      Created             busybox             0 ``` ### Start a container To start a container, pass its ID to `crictl start`: ```shell crictl start 3e025dd50a72d956c4f14881fbb5b1080c9275674e95fb67f965f6478a957d60 ``` The output is similar to this: ``` 3e025dd50a72d956c4f14881fbb5b1080c9275674e95fb67f965f6478a957d60 ``` Check the container has its state set to `Running`. ```shell crictl ps ``` The output is similar to this: ``` CONTAINER ID   IMAGE    CREATED              STATE    NAME     ATTEMPT 3e025dd50a72d  busybox  About a minute ago   Running  busybox  0 ``` </del> ## {{% heading \"whatsnext\" %}} * [Learn more about `crictl`](https://github.com/kubernetes-sigs/cri-tools)."}
{"_id":"q-en-website-c662d9b866f0bd140909be9176a841e5d5077cf3245963e1d0542b5f14538c0d","text":"NAME                  DATA      AGE ... <del> dns-autoscaler        1         ... </del> <ins> kube-dns-autoscaler   1         ... </ins> ... Modify the data in the ConfigMap: ```shell <del> kubectl edit configmap dns-autoscaler --namespace=kube-system </del> <ins> kubectl edit configmap kube-dns-autoscaler --namespace=kube-system </ins> ``` Look for this line:"}
{"_id":"q-en-website-c7f8a0712b310b0cbdc8da97dd158b5277c0f5d505a71d2a84de6303f78260c5","text":"title: Pod Priority id: pod-priority date: 2019-01-31 <del> full_link: /docs/concepts/configuration/pod-priority-preemption/#pod-priority </del> <ins> full_link: /docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority </ins> short_description: > Pod Priority indicates the importance of a Pod relative to other Pods."}
{"_id":"q-en-website-c8a0af703c8056ec8dfc992dfd92ad68cb1b6b42c6c2e9212b8624b6c56f3166","text":"When a bound token is presented to the kube-apiserver, the service account authenticator will extract and verify these claims. <ins> If the referenced object or the ServiceAccount is pending deletion (for example, due to finalizers), then for any instant that is 60 seconds (or more) after the `.metadata.deletionTimestamp` date, authentication with that token would fail. </ins> If the referenced object no longer exists (or its `metadata.uid` does not match), the request will not be authenticated."}
{"_id":"q-en-website-c901d620b8a04c92c09f4c9e383bd2e674b024cd7d257f277599d55b4ea53ed4","text":"trust relationship exists. Depending on how the token was issued (either time-limited using a `TokenRequest` or using a legacy mechanism with a Secret), a ServiceAccount token might also have an expiry time, an audience, <del> and a time after which the token *starts* being valid. When a process running in a Pod attempts to communicate with the Kubernetes API server, it adds an `Authorization: Bearer <token>` header to the HTTP request. The API server checks the validity of the bearer token as follows: </del> <ins> and a time after which the token *starts* being valid. When a client that is acting as a ServiceAccount tries to communicate with the Kubernetes API server, the client includes an `Authorization: Bearer <token>` header with the HTTP request. The API server checks the validity of that bearer token as follows: </ins> 1. Check the token signature. 1. Check whether the token has expired. <del> 1. Checks whether object references in the token claims are currently valid </del> <ins> 1. Check whether object references in the token claims are currently valid. </ins> 1. Check whether the token is currently valid. 1. Check the audience claims. <ins> The TokenRequest API produces _bound tokens_ for a ServiceAccount. This binding is linked to the lifetime of the client, such as a Pod, that is acting as that ServiceAccount. </ins> For tokens issued using the `TokenRequest` API, the API server also checks that the specific object reference that is using the ServiceAccount still exists, matching by the {{< glossary_tooltip term_id=\"uid\" text=\"unique ID\" >}} of that"}
{"_id":"q-en-website-cb17a1b8f7c33141ba0f346aeb5cd7c925c7ac8a5ac72d06f85b6afa9f12a75e","text":"durable external storage, or provide ephemeral storage, or they might offer a read-only interface to information using a filesystem paradigm. <del> Kubernetes also includes support for [FlexVolume](/docs/concepts/storage/volumes/#flexvolume) plugins, </del> <ins> Kubernetes also includes support for [FlexVolume](/docs/concepts/storage/volumes/#flexvolume-deprecated) plugins, </ins> which are deprecated since Kubernetes v1.23 (in favour of CSI). FlexVolume plugins allow users to mount volume types that aren't natively supported by Kubernetes. When"}
{"_id":"q-en-website-cb492b541fca0ba014cc5ddb84dce9f1188da0614b043a472cea887a83ef2691","text":"* [API definition for Node](/docs/reference/generated/kubernetes-api/{{< param \"version\" >}}/#node-v1-core). * [Node](https://git.k8s.io/design-proposals-archive/architecture/architecture.md#the-kubernetes-node) section of the architecture design document. <ins> * [Graceful/non-graceful node shutdown](/docs/concepts/cluster-administration/node-shutdown/). </ins> * [Cluster autoscaling](/docs/concepts/cluster-administration/cluster-autoscaling/) to manage the number and size of nodes in your cluster. * [Taints and Tolerations](/docs/concepts/scheduling-eviction/taint-and-toleration/)."}
{"_id":"q-en-website-cbc98e382c600c2f9266230f5853a35194e520562de5104bbdde41da459e81fa","text":"## Targeting a Namespace by its name <del> {{< feature-state state=\"beta\" for_k8s_version=\"1.21\" >}} </del> <ins> {{< feature-state for_k8s_version=\"1.22\" state=\"stable\" >}} </ins> The Kubernetes control plane sets an immutable label `kubernetes.io/metadata.name` on all namespaces, provided that the `NamespaceDefaultLabelName`"}
{"_id":"q-en-website-cc6bcaa05fa1ec387338cdd7ba7ad0e6078ce5c354390b6c5e9d51615a5be354","text":"## {{% heading \"whatsnext\" %}} <ins> Learn more about the following: </ins> * Follow the [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/) tutorial <del> * Read about [Ingress](/docs/concepts/services-networking/ingress/) * Read about [EndpointSlices](/docs/concepts/services-networking/endpoint-slices/) </del> <ins> * [Ingress](/docs/concepts/services-networking/ingress/) exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. * [EndpointSlices](/docs/concepts/services-networking/endpoint-slices/) </ins> For more context: <del> * Read [Virtual IPs and Service Proxies](/docs/reference/networking/virtual-ips/) * Read the [API reference](/docs/reference/kubernetes-api/service-resources/service-v1/) for the Service API * Read the [API reference](/docs/reference/kubernetes-api/service-resources/endpoints-v1/) for the Endpoints API * Read the [API reference](/docs/reference/kubernetes-api/service-resources/endpoint-slice-v1/) for the EndpointSlice API </del> <ins> * [Virtual IPs and Service Proxies](/docs/reference/networking/virtual-ips/) * [API reference](/docs/reference/kubernetes-api/service-resources/service-v1/) for the Service API * [API reference](/docs/reference/kubernetes-api/service-resources/endpoints-v1/) for the Endpoints API * [API reference](/docs/reference/kubernetes-api/service-resources/endpoint-slice-v1/) for the EndpointSlice API </ins>"}
{"_id":"q-en-website-cd1139a0f7cb0a970dea4d54d72089c9f4b47b3822dd8037e80f0dd27f06186c","text":"You can directly configure CSI volumes within the Pod specification. Volumes specified in this way are ephemeral and do not persist across pod restarts. See [Ephemeral <del> Volumes](/docs/concepts/storage/ephemeral-volumes/#csi-ephemeral-volume) </del> <ins> Volumes](/docs/concepts/storage/ephemeral-volumes/#csi-ephemeral-volumes) </ins> for more information. For more information on how to develop a CSI driver, refer to the"}
{"_id":"q-en-website-cdc5653ec1dec9f0125e07a77d4ec1fd1db0dfdb578f8d82a7cc96d33ea4ac27","text":"client-key: fake-key-file - name: experimenter user: <ins> # Documentation note (this comment is NOT part of the command output). # Storing passwords in Kubernetes client config is risky. # A better alternative would be to use a credential plugin # and store the credentials separately. # See https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins </ins> password: some-password username: exp ```"}
{"_id":"q-en-website-ced5a2f61821b029e2ab2c50d1b701e16c7cda95eae84c3bd846c616a6255b4d","text":"kubectl delete pod fine-pod --wait --now ``` <del> ## Create Pod that uses the container runtime default seccomp profile Most container runtimes provide a sane set of default syscalls that are allowed or not. You can adopt these defaults for your workload by setting the seccomp type in the security context of a pod or container to `RuntimeDefault`. {{< note >}} If you have the `SeccompDefault` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) enabled, then Pods use the `RuntimeDefault` seccomp profile whenever no other seccomp profile is specified. Otherwise, the default is `Unconfined`. {{< /note >}} Here's a manifest for a Pod that requests the `RuntimeDefault` seccomp profile for all its containers: {{< codenew file=\"pods/security/seccomp/ga/default-pod.yaml\" >}} Create that Pod: ```shell kubectl apply -f https://k8s.io/examples/pods/security/seccomp/ga/default-pod.yaml ``` ```shell kubectl get pod default-pod ``` The Pod should be showing as having started successfully: ``` NAME        READY   STATUS    RESTARTS   AGE default-pod 1/1     Running   0          20s ``` Finally, now that you saw that work OK, clean up: ```shell kubectl delete pod default-pod --wait --now ``` </del> ## {{% heading \"whatsnext\" %}} You can learn more about Linux seccomp:"}
{"_id":"q-en-website-d05a39e12d5fc87b8d37e7351c68f4ac3f6bcdfc4292c9f09704ce083c590c12","text":"Watch out when using this type of volume, because: <ins> * HostPaths can expose privileged system credentials (such as for the Kubelet) or privileged APIs (such as container runtime socket), which can be used for container escape or to attack other parts of the cluster. </ins> * Pods with identical configuration (such as created from a PodTemplate) may behave differently on different nodes due to different files on the nodes * The files or directories created on the underlying hosts are only writable by root. You"}
{"_id":"q-en-website-d0b27671093f4ab42a9fc6526ae5911e2bc503d01602a86ba6520db4e6add618","text":"If you don't specify a registry hostname, Kubernetes assumes that you mean the Docker public registry. <del> After the image name part you can add a _tag_ (as also using with commands such as `docker` and `podman`). </del> <ins> After the image name part you can add a _tag_ (in the same way you would when using with commands like `docker` or `podman`). </ins> Tags let you identify different versions of the same series of images. Image tags consist of lowercase and uppercase letters, digits, underscores (`_`),"}
{"_id":"q-en-website-d0da8b4a279ff5ae39202289da1eec6ca5b600de2d0ede35af836b64b9e50a96","text":"- annotation，注解 - anti-affinity，反亲和性 - attach，挂接 <ins> - authenticate，身份验证 - authorize，授权或鉴权 - 将权限授予某主体时，译为“授权” - 根据某些参数/条件来确定具有哪些权限时，译为“鉴权” - authorizer，鉴权器 </ins> - autoscale，自动扩缩容 - bearer token，持有者令牌 - capabilities"}
{"_id":"q-en-website-d0f68568ff07f877db6865b1dd48ea4cb83952a05dcc90a59e3f811c6694bec4","text":"`JobTrackingWithFinalizers`機能が無効になっている時に作成されたJobについては、コントロールプレーンを1.26にアップグレードしても、ファイナライザーを使用してJobを追跡しません。 {{< /note >}} <del> コントロールプレーンは任意のJobに属するPodを追跡し、そのPodがAPIサーバーから削除されたかどうか認識します。そのためJobコントローラはファイナライザー`batch.kubernetes.io/job-tracking`を持つPodを作成します。コントローラーがファイナライザーを削除するのは、PodがJobステータスに反映された後なので、他のコントローラーやユーザがPodを削除することができます。 </del> <ins> コントロールプレーンは任意のJobに属するPodを追跡し、そのPodがAPIサーバーから削除されたかどうか認識します。そのためJobコントローラーはファイナライザー`batch.kubernetes.io/job-tracking`を持つPodを作成します。コントローラーがファイナライザーを削除するのは、PodがJobステータスに反映された後なので、他のコントローラーやユーザがPodを削除することができます。 </ins> Kubernetes 1.26にアップグレードする前、またはフィーチャーゲート`JobTrackingWithFinalizers`が有効になる前に作成されたJobは、Podファイナライザーを使用せずに追跡されます。Job{{< glossary_tooltip term_id=\"controller\" text=\"コントローラー\" >}}は、クラスタに存在するPodのみに基づいて、`succeeded`Podと`failed`Podのステータスカウンタを更新します。クラスタからPodが削除されると、コントロールプレーンはJobの進捗を見失う可能性があります。"}
{"_id":"q-en-website-d1028c4693673478509b0aff0edf8be51b3f417b902a3a68b5c0519e990b7806","text":"对象的定义中包含了更多的细节信息。 * 博客 [分布式系统工具箱：复合容器模式](/blog/2015/06/the-distributed-system-toolkit-patterns/) 中解释了在同一 Pod 中包含多个容器时的几种常见布局。 <del> * 了解 [Pod 拓扑分布约束](/zh-cn/docs/concepts/workloads/pods/pod-topology-spread-constraints/)。 </del> <ins> * 了解 [Pod 拓扑分布约束](/zh-cn/docs/concepts/scheduling-eviction/topology-spread-constraints//)。 </ins> <!-- To understand the context for why Kubernetes wraps a common Pod API in other resources (such as {{< glossary_tooltip text=\"StatefulSets\" term_id=\"statefulset\" >}} or {{< glossary_tooltip text=\"Deployments\" term_id=\"deployment\" >}}), you can read about the prior art, including:"}
{"_id":"q-en-website-d2533a78bff598d600c8466b13ada6b1148685be07ce5fdd0409aac2a7416ae2","text":"| Language             | Client Library                           | | -------------------- | ---------------------------------------- | | Clojure              | [github.com/yanatan16/clj-kubernetes-api](https://github.com/yanatan16/clj-kubernetes-api) | <ins> | DotNet               | [github.com/tonnyeremin/kubernetes_gen](https://github.com/tonnyeremin/kubernetes_gen) | | DotNet (RestSharp)   | [github.com/masroorhasan/Kubernetes.DotNet](https://github.com/masroorhasan/Kubernetes.DotNet) | | Elixir               | [github.com/obmarg/kazan](https://github.com/obmarg/kazan/) | | Elixir               | [github.com/coryodaniel/k8s](https://github.com/coryodaniel/k8s) | </ins> | Go                   | [github.com/ericchiang/k8s](https://github.com/ericchiang/k8s) | | Java (OSGi)          | [bitbucket.org/amdatulabs/amdatu-kubernetes](https://bitbucket.org/amdatulabs/amdatu-kubernetes) | | Java (Fabric8, OSGi) | [github.com/fabric8io/kubernetes-client](https://github.com/fabric8io/kubernetes-client) |"}
{"_id":"q-en-website-d2d5036e3346926c5d9caaf681669a9beb80b9d2cf98a7effa9d31b308cba202","text":"} ``` <del> Note that the `resourceVersion` of the list remains constant across each request, indicating the server is showing us a consistent snapshot of the pods. Pods that are created, updated, or deleted after version `10245` would not be shown unless the user makes a list request without the `continue` token.  This allows clients to break large requests into smaller chunks and then perform a watch operation on the full set without missing any updates. </del> <ins> Note that the `resourceVersion` of the list remains constant across each request, indicating the server is showing us a consistent snapshot of the pods. Pods that are created, updated, or deleted after version `10245` would not be shown unless the user makes a list request without the `continue` token.  This allows clients to break large requests into smaller chunks and then perform a watch operation on the full set without missing any updates. `remainingItemCount` is the number of subsequent items in the list which are not included in this list response. If the list request contained label or field selectors, then the number of remaining items is unknown and the API server does not include a `remainingItemCount` field in its response. If the list is complete (either because it is not chunking or because this is the last chunk), then there are no more remaining items and the API server does not include a `remainingItemCount` field in its response. The intended use of the `remainingItemCount` is estimating the size of a collection. </ins> ## Receiving resources as Tables"}
{"_id":"q-en-website-d33e9f11169299db16ee1275d0059676ece0a8123e02fce423dae69bb7d5c521","text":"{{% tab name=\"Windows (PowerShell)\" %}} <!-- <del> Start a Powershell session, set `$Version` to the desired version (ex: `$Version=1.4.3`), and then run the following commands: </del> <ins> Start a Powershell session, set `$Version` to the desired version (ex: `$Version=1.4.3`), and then run the following commands: </ins> --> <del> 启动 Powershell 会话，将 `$Version` 设置为所需的版本（例如：`$ Version=1.4.3`）， </del> <ins> 启动 Powershell 会话，将 `$Version` 设置为所需的版本（例如：`$Version=1.4.3`）， </ins> 然后运行以下命令： <!--"}
{"_id":"q-en-website-d3a2596554a2b19d57825de1aab667ced3c070a4e5935f201c2b50e8423151e7","text":"1. Create `example-ingress.yaml` from the following file: <del> ```yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: example-ingress annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1 spec: rules: - host: hello-world.info http: paths: - path: / pathType: Prefix backend: service: name: web port: number: 8080 ``` </del> <ins> {{< codenew file=\"ingress/example-ingress.yaml\" >}} </ins> 1. Create the Ingress resource by running the following command: ```shell <del> kubectl apply -f example-ingress.yaml </del> <ins> kubectl apply -f https://k8s.io/examples/ingress/example-ingress.yaml </ins> ``` Output:"}
{"_id":"q-en-website-d44d9cfee23a913d6281353c949c552241fcbb77ba7fe92eb9a0645caf83a805","text":"what that means, check out the blog post [Don't Panic: Kubernetes and Docker](/blog/2020/12/02/dont-panic-kubernetes-and-docker/). <ins> Also, you can read [check whether Dockershim deprecation affects you](/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-deprecation-affects-you/) to check whether it does. </ins> ### Why is dockershim being deprecated? Maintaining dockershim has become a heavy burden on the Kubernetes maintainers."}
{"_id":"q-en-website-d4c007a177366bbdc317096cb51454889cfb00246f91e8ec027926726faace9f","text":"After you initialize your control-plane, the kubelet runs normally. {{< /note >}} <ins> #### Network setup kubeadm similarly to other Kubernetes components tries to find a usable IP on the network interface associated with the default gateway on a host. Such an IP is then used for the advertising and/or listening performed by a component. To find out what this IP is on a Linux host you can use: ```shell ip route show # Look for a line starting with \"default via\" ``` Kubernetes components do not accept custom network interface as an option, therefore a custom IP address must be passed as a flag to all components instances that need such a custom configuration. To configure the API server advertise address for control plane nodes created with both `init` and `join`, the flag `--apiserver-advertise-address` can be used. Preferably, this option can be set in the [kubeadm API](/docs/reference/config-api/kubeadm-config.v1beta3) as `InitConfiguration.localAPIEndpoint` and `JoinConfiguration.controlPlane.localAPIEndpoint`. For kubelets on all nodes, the `--node-ip` option can be passed in `.nodeRegistration.kubeletExtraArgs` inside a kubeadm configuration file (`InitConfiguration` or `JoinConfiguration`). For dual-stack see [Dual-stack support with kubeadm](/docs/setup/production-environment/tools/kubeadm/dual-stack-support). {{< note >}} IP addresses become part of certificates SAN fields. Changing these IP addresses would require signing new certificates and restarting the affected components, so that the change in certificate files is reflected. See [Manual certificate renewal](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/#manual-certificate-renewal) for more details on this topic. {{</ note >}} {{< warning >}} The Kubernetes project recommends against this approach (configuring all component instances with custom IP addresses). Instead, the Kubernetes maintainers recommend to setup the host network, so that the default gateway IP is the one that Kubernetes components auto-detect and use. On Linux nodes, you can use commands such as `ip route` to configure networking; your operating system might also provide higher level network management tools. If your node's default gateway is a public IP address, you should configure packet filtering or other security measures that protect the nodes and your cluster. {{< /warning >}} {{< note >}} If the host does not have a default gateway, it is recommended to setup one. Otherwise, without passing a custom IP address to a Kubernetes component, the component will exit with an error. If two or more default gateways are present on the host, a Kubernetes component will try to use the first one it encounters that has a suitable global unicast IP address. While making this choice, the exact ordering of gateways might vary between different operating systems and kernel versions. {{< /note >}} </ins> ### Preparing the required container images This step is optional and only applies in case you wish `kubeadm init` and `kubeadm join`"}
{"_id":"q-en-website-d556e2711444d0ee764f33155e9c6949fc60fc1a2fd0122713177c544ad754a6","text":"The output displays 0 in the DESIRED and CURRENT columns: <del> NAME                                 DESIRED   CURRENT   READY   AGE </del> <ins> NAME                                  DESIRED   CURRENT   READY   AGE </ins> ... <del> dns-autoscaler-6b59789fc8            0         0         0       ... </del> <ins> kube-dns-autoscaler-6b59789fc8        0         0         0       ... </ins> ... <del> ### Option 2: Delete the dns-autoscaler deployment </del> <ins> ### Option 2: Delete the kube-dns-autoscaler deployment </ins> <del> This option works if dns-autoscaler is under your own control, which means </del> <ins> This option works if kube-dns-autoscaler is under your own control, which means </ins> no one will re-create it: ```shell <del> kubectl delete deployment dns-autoscaler --namespace=kube-system </del> <ins> kubectl delete deployment kube-dns-autoscaler --namespace=kube-system </ins> ``` The output is: <del> deployment.apps \"dns-autoscaler\" deleted </del> <ins> deployment.apps \"kube-dns-autoscaler\" deleted </ins> <del> ### Option 3: Delete the dns-autoscaler manifest file from the master node </del> <ins> ### Option 3: Delete the kube-dns-autoscaler manifest file from the master node </ins> <del> This option works if dns-autoscaler is under control of the (deprecated) </del> <ins> This option works if kube-dns-autoscaler is under control of the (deprecated) </ins> [Addon Manager](https://git.k8s.io/kubernetes/cluster/addons/README.md), and you have write access to the master node. Sign in to the master node and delete the corresponding manifest file. <del> The common path for this dns-autoscaler is: </del> <ins> The common path for this kube-dns-autoscaler is: </ins> /etc/kubernetes/addons/dns-horizontal-autoscaler/dns-horizontal-autoscaler.yaml After the manifest file is deleted, the Addon Manager will delete the <del> dns-autoscaler Deployment. </del> <ins> kube-dns-autoscaler Deployment. </ins>"}
{"_id":"q-en-website-d73d973959a82b8d23b484e3771076d5dfc4bbd3c6e817d2f5b3540adb3fd426","text":"<ins> --- api_metadata: apiVersion: \"autoscaling/v1\" import: \"k8s.io/api/autoscaling/v1\" kind: \"HorizontalPodAutoscaler\" content_type: \"api_reference\" description: \"水平 Pod 自动缩放器的配置。\" title: \"HorizontalPodAutoscaler\" weight: 11 --- <-- api_metadata: apiVersion: \"autoscaling/v1\" import: \"k8s.io/api/autoscaling/v1\" kind: \"HorizontalPodAutoscaler\" content_type: \"api_reference\" description: \"configuration of a horizontal pod autoscaler.\" title: \"HorizontalPodAutoscaler\" weight: 11 auto_generated: true --> `apiVersion: autoscaling/v1` `import \"k8s.io/api/autoscaling/v1\"` <!-- ## HorizontalPodAutoscaler {#HorizontalPodAutoscaler} configuration of a horizontal pod autoscaler. <hr> --> ## HorizontalPodAutoscaler {#HorizontalPodAutoscaler} 水平 Pod 自动缩放器的配置。 <hr> <!-- - **apiVersion**: autoscaling/v1 - **kind**: HorizontalPodAutoscaler --> - **apiVersion**: autoscaling/v1 - **kind**: HorizontalPodAutoscaler <!-- - **metadata** (<a href=\"{{< ref \"../common-definitions/object-meta#ObjectMeta\" >}}\">ObjectMeta</a>) Standard object metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata --> - **metadata** (<a href=\"{{< ref \"../common-definitions/object-meta#ObjectMeta\" >}}\">ObjectMeta</a>) 标准的对象元数据。 更多信息： https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata <!-- - **spec** (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscalerSpec\" >}}\">HorizontalPodAutoscalerSpec</a>) behaviour of autoscaler. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status. --> - **spec** (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscalerSpec\" >}}\">HorizontalPodAutoscalerSpec</a>) 自动缩放器的规约。 更多信息： https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status. <!-- - **status** (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscalerStatus\" >}}\">HorizontalPodAutoscalerStatus</a>) current information about the autoscaler. --> - **status** (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscalerStatus\" >}}\">HorizontalPodAutoscalerStatus</a>) 自动缩放器的当前信息。 <!-- ## HorizontalPodAutoscalerSpec {#HorizontalPodAutoscalerSpec} specification of a horizontal pod autoscaler. <hr> --> ## HorizontalPodAutoscalerSpec {#HorizontalPodAutoscalerSpec} 水平 Pod 自动缩放器的规约。 <hr> <!-- - **maxReplicas** (int32), required upper limit for the number of pods that can be set by the autoscaler; cannot be smaller than MinReplicas. --> - **maxReplicas** (int32)，必填 自动扩缩器可以设置的 Pod 数量上限； 不能小于 minReplicas。 <!-- - **scaleTargetRef** (CrossVersionObjectReference), required reference to scaled resource; horizontal pod autoscaler will learn the current resource consumption and will set the desired number of pods by using its Scale subresource. --> - **scaleTargetRef** (CrossVersionObjectReference)，必填 对被扩缩资源的引用； 水平 Pod 自动缩放器将了解当前的资源消耗，并使用其 scale 子资源设置所需的 Pod 数量。 <!-- <a name=\"CrossVersionObjectReference\"></a> *CrossVersionObjectReference contains enough information to let you identify the referred resource.* --> <a name=\"CrossVersionObjectReference\"></a> **CrossVersionObjectReference 包含足够的信息来让你识别出所引用的资源。** <!-- - **scaleTargetRef.kind** (string), required Kind of the referent; More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\" --> - **scaleTargetRef.kind** (string)，必填 被引用对象的类别； 更多信息： https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\" <!-- - **scaleTargetRef.name** (string), required Name of the referent; More info: http://kubernetes.io/docs/user-guide/identifiers#names --> - **scaleTargetRef.name** (string)，必填 被引用对象的名称； 更多信息： http://kubernetes.io/docs/user-guide/identifiers#names <!-- - **scaleTargetRef.apiVersion** (string) API version of the referent --> - **scaleTargetRef.apiVersion** (string) 被引用对象的 API 版本。 <!-- - **minReplicas** (int32) minReplicas is the lower limit for the number of replicas to which the autoscaler can scale down.  It defaults to 1 pod. minReplicas is allowed to be 0 if the alpha feature gate HPAScaleToZero is enabled and at least one Object or External metric is configured. Scaling is active as long as at least one metric value is available. --> - **minReplicas** (int32) minReplicas 是自动缩放器可以缩减的副本数的下限。 它默认为 1 个 Pod。 如果启用了 alpha 特性门禁 HPAScaleToZero 并且配置了至少一个 Object 或 External 度量标准， 则 minReplicas 允许为 0。 只要至少有一个度量值可用，缩放就处于活动状态。 <!-- - **targetCPUUtilizationPercentage** (int32) target average CPU utilization (represented as a percentage of requested CPU) over all the pods; if not specified the default autoscaling policy will be used. --> - **targetCPUUtilizationPercentage** (int32) 所有 Pod 的目标平均 CPU 利用率（以请求 CPU 的百分比表示）； 如果未指定，将使用默认的自动缩放策略。 <!-- ## HorizontalPodAutoscalerStatus {#HorizontalPodAutoscalerStatus} current status of a horizontal pod autoscaler <hr> --> ## HorizontalPodAutoscalerStatus {#HorizontalPodAutoscalerStatus} 水平 Pod 自动缩放器的当前状态 <hr> <!-- - **currentReplicas** (int32), required current number of replicas of pods managed by this autoscaler. --> - **currentReplicas** (int32)，必填 此自动缩放器管理的 Pod 的当前副本数。 <!-- - **desiredReplicas** (int32), required desired number of replicas of pods managed by this autoscaler. --> - **desiredReplicas** (int32)，必填 此自动缩放器管理的 Pod 副本的所需数量。 <!-- - **currentCPUUtilizationPercentage** (int32) current average CPU utilization over all pods, represented as a percentage of requested CPU, e.g. 70 means that an average pod is using now 70% of its requested CPU. --> - **currentCPUUtilizationPercentage** (int32) 当前所有 Pod 的平均 CPU 利用率， 以请求 CPU 的百分比表示， 例如：70 表示平均 Pod 现在正在使用其请求 CPU 的 70%。 <!-- - **lastScaleTime** (Time) last time the HorizontalPodAutoscaler scaled the number of pods; used by the autoscaler to control how often the number of pods is changed. --> - **lastScaleTime** (Time) 上次 HorizontalPodAutoscaler 缩放 Pod 的数量； 自动缩放器用它来控制 Pod 数量的更改频率。 <!-- <a name=\"Time\"></a> *Time is a wrapper around time.Time which supports correct marshaling to YAML and JSON.  Wrappers are provided for many of the factory methods that the time package offers.* --> <a name=\"Time\"></a> **Time 是 time.Time 的包装类，支持正确地序列化为 YAML 和 JSON。 为 time 包提供的许多工厂方法提供了包装类。** <!-- - **observedGeneration** (int64) most recent generation observed by this autoscaler. --> - **observedGeneration** (int64) 此自动缩放器观察到的最新一代。 <!-- ## HorizontalPodAutoscalerList {#HorizontalPodAutoscalerList} list of horizontal pod autoscaler objects. <hr> --> ## HorizontalPodAutoscalerList {#HorizontalPodAutoscalerList} 水平 Pod 自动缩放器对象列表。 <hr> <!-- - **apiVersion**: autoscaling/v1 - **kind**: HorizontalPodAutoscalerList --> - **apiVersion**: autoscaling/v1 - **kind**: HorizontalPodAutoscalerList <!-- - **metadata** (<a href=\"{{< ref \"../common-definitions/list-meta#ListMeta\" >}}\">ListMeta</a>) Standard list metadata. --> - **metadata** (<a href=\"{{< ref \"../common-definitions/list-meta#ListMeta\" >}}\">ListMeta</a>) 标准的列表元数据。 <!-- - **items** ([]<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>), required list of horizontal pod autoscaler objects. --> - **items** ([]<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>), required 水平 Pod 自动缩放器对象的列表。 <!-- ## Operations {#Operations} <hr> --> ## 操作 {#Operations} <hr> <!-- ### `get` read the specified HorizontalPodAutoscaler --> ### `get` 读取特定的 HorizontalPodAutoscaler <!-- #### HTTP Request GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name} --> #### HTTP 请求 GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name} <!-- #### Parameters --> #### 参数 <!-- - **name** (*in path*): string, required name of the HorizontalPodAutoscaler --> - **name** （**路径参数**）: string，必填 HorizontalPodAutoscaler 的名称。 <!-- - **namespace** (*in path*): string, required <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> --> - **namespace** （**路径参数**）: string，必填 <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> <!-- - **pretty** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> --> - **pretty** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> <!-- #### Response 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): OK 401: Unauthorized --> #### 响应 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): OK 401: Unauthorized <!-- ### `get` read status of the specified HorizontalPodAutoscaler #### HTTP Request GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status --> ### `get` 读取特定 HorizontalPodAutoscaler 的状态 #### HTTP 请求 GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status <!-- #### Parameters --> #### 参数 <!-- - **name** (*in path*): string, required name of the HorizontalPodAutoscaler --> - **name** （**路径参数**）: string，必填 HorizontalPodAutoscaler 的名称。 <!-- - **namespace** (*in path*): string, required <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> --> - **namespace** （**路径参数**）: string，必填 <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> <!-- - **pretty** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> --> - **pretty** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> <!-- #### Response 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): OK 401: Unauthorized --> #### 响应 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): OK 401: Unauthorized <!-- ### `list` list or watch objects of kind HorizontalPodAutoscaler --> ### `list` 列出或监视 HorizontalPodAutoscaler 类别的对象 <!-- #### HTTP Request GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers --> #### HTTP 参数 GET /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers <!-- #### Parameters --> #### 参数 <!-- - **namespace** (*in path*): string, required <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> --> - **namespace** （**路径参数**）: string，必填 <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> <!-- - **allowWatchBookmarks** (*in query*): boolean <a href=\"{{< ref \"../common-parameters/common-parameters#allowWatchBookmarks\" >}}\">allowWatchBookmarks</a> --> - **allowWatchBookmarks** （**查询参数**）: boolean <a href=\"{{< ref \"../common-parameters/common-parameters#allowWatchBookmarks\" >}}\">allowWatchBookmarks</a> <!-- - **continue** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#continue\" >}}\">continue</a> --> - **continue** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#continue\" >}}\">continue</a> <!-- - **fieldSelector** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldSelector\" >}}\">fieldSelector</a> --> - **fieldSelector** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldSelector\" >}}\">fieldSelector</a> <!-- - **labelSelector** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#labelSelector\" >}}\">labelSelector</a> --> - **labelSelector** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#labelSelector\" >}}\">labelSelector</a> <!-- - **limit** (*in query*): integer <a href=\"{{< ref \"../common-parameters/common-parameters#limit\" >}}\">limit</a> --> - **limit** （**查询参数**）: integer <a href=\"{{< ref \"../common-parameters/common-parameters#limit\" >}}\">limit</a> <!-- - **pretty** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> --> - **pretty** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> <!-- - **resourceVersion** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#resourceVersion\" >}}\">resourceVersion</a> --> - **resourceVersion** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#resourceVersion\" >}}\">resourceVersion</a> <!-- - **resourceVersionMatch** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#resourceVersionMatch\" >}}\">resourceVersionMatch</a> --> - **resourceVersionMatch** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#resourceVersionMatch\" >}}\">resourceVersionMatch</a> <!-- - **timeoutSeconds** (*in query*): integer <a href=\"{{< ref \"../common-parameters/common-parameters#timeoutSeconds\" >}}\">timeoutSeconds</a> --> - **timeoutSeconds** (*查询参数**): integer <a href=\"{{< ref \"../common-parameters/common-parameters#timeoutSeconds\" >}}\">timeoutSeconds</a> <!-- - **watch** (*in query*): boolean <a href=\"{{< ref \"../common-parameters/common-parameters#watch\" >}}\">watch</a> --> - **watch** （**查询参数**）: boolean <a href=\"{{< ref \"../common-parameters/common-parameters#watch\" >}}\">watch</a> <!-- #### Response 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscalerList\" >}}\">HorizontalPodAutoscalerList</a>): OK 401: Unauthorized --> #### 响应 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscalerList\" >}}\">HorizontalPodAutoscalerList</a>): OK 401: Unauthorized <!-- ### `list` list or watch objects of kind HorizontalPodAutoscaler #### HTTP Request GET /apis/autoscaling/v1/horizontalpodautoscalers --> ### `list` 列出或监视 HorizontalPodAutoscaler 类别的对象 #### HTTP 请求 GET /apis/autoscaling/v1/horizontalpodautoscalers <!-- #### Parameters --> #### 参数 <!-- - **allowWatchBookmarks** (*in query*): boolean <a href=\"{{< ref \"../common-parameters/common-parameters#allowWatchBookmarks\" >}}\">allowWatchBookmarks</a> --> - **allowWatchBookmarks** （**查询参数**）: boolean <a href=\"{{< ref \"../common-parameters/common-parameters#allowWatchBookmarks\" >}}\">allowWatchBookmarks</a> <!-- - **continue** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#continue\" >}}\">continue</a> --> - **continue** (*查询参数**): string <a href=\"{{< ref \"../common-parameters/common-parameters#continue\" >}}\">continue</a> <!-- - **fieldSelector** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldSelector\" >}}\">fieldSelector</a> --> - **fieldSelector** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldSelector\" >}}\">fieldSelector</a> <!-- - **labelSelector** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#labelSelector\" >}}\">labelSelector</a> --> - **labelSelector** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#labelSelector\" >}}\">labelSelector</a> <!-- - **limit** (*in query*): integer <a href=\"{{< ref \"../common-parameters/common-parameters#limit\" >}}\">limit</a> --> - **limit** （**查询参数**）: integer <a href=\"{{< ref \"../common-parameters/common-parameters#limit\" >}}\">limit</a> <!-- - **pretty** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> --> - **pretty** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> <!-- - **resourceVersion** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#resourceVersion\" >}}\">resourceVersion</a> --> - **resourceVersion** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#resourceVersion\" >}}\">resourceVersion</a> <!-- - **resourceVersionMatch** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#resourceVersionMatch\" >}}\">resourceVersionMatch</a> --> - **resourceVersionMatch** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#resourceVersionMatch\" >}}\">resourceVersionMatch</a> <!-- - **timeoutSeconds** (*in query*): integer <a href=\"{{< ref \"../common-parameters/common-parameters#timeoutSeconds\" >}}\">timeoutSeconds</a> --> - **timeoutSeconds** （**查询参数**）: integer <a href=\"{{< ref \"../common-parameters/common-parameters#timeoutSeconds\" >}}\">timeoutSeconds</a> <!-- - **watch** (*in query*): boolean <a href=\"{{< ref \"../common-parameters/common-parameters#watch\" >}}\">watch</a> --> - **watch** （**查询参数**）: boolean <a href=\"{{< ref \"../common-parameters/common-parameters#watch\" >}}\">watch</a> <!-- #### Response 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscalerList\" >}}\">HorizontalPodAutoscalerList</a>): OK 401: Unauthorized --> #### 响应 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscalerList\" >}}\">HorizontalPodAutoscalerList</a>): OK 401: Unauthorized <!-- ### `create` create a HorizontalPodAutoscaler #### HTTP Request POST /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers --> ### `create` 创建一个 HorizontalPodAutoscaler #### HTTP 请求 POST /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers <!-- #### Parameters --> #### 参数 <!-- - **namespace** (*in path*): string, required <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> --> - **namespace** （**路径参数**）: string，必填 <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> <!-- - **body**: <a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>, required --> - **body**: <a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>，必填 <!-- - **dryRun** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#dryRun\" >}}\">dryRun</a> --> - **dryRun** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#dryRun\" >}}\">dryRun</a> <!-- - **fieldManager** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldManager\" >}}\">fieldManager</a> --> - **fieldManager** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldManager\" >}}\">fieldManager</a> <!-- - **fieldValidation** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldValidation\" >}}\">fieldValidation</a> --> - **fieldValidation** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldValidation\" >}}\">fieldValidation</a> <!-- - **pretty** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> --> - **pretty** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> <!-- #### Response 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): OK 201 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): Created 202 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): Accepted 401: Unauthorized --> #### 响应 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): OK 201 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): Created 202 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): Accepted 401: Unauthorized <!-- ### `update` replace the specified HorizontalPodAutoscaler #### HTTP Request PUT /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name} --> ### `update` 替换特定的 HorizontalPodAutoscaler #### HTTP 请求 PUT /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name} <!-- #### Parameters --> #### 参数 <!-- - **name** (*in path*): string, required name of the HorizontalPodAutoscaler --> - **name** （**路径参数**）: string，必填 HorizontalPodAutoscaler 的名称 <!-- - **namespace** (*in path*): string, required <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> --> - **namespace** （**路径参数**）: string，必填 <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> <!-- - **body**: <a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>, required --> - **body**: <a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>，必填 <!-- - **dryRun** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#dryRun\" >}}\">dryRun</a> --> - **dryRun** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#dryRun\" >}}\">dryRun</a> <!-- - **fieldManager** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldManager\" >}}\">fieldManager</a> --> - **fieldManager** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldManager\" >}}\">fieldManager</a> <!-- - **fieldValidation** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldValidation\" >}}\">fieldValidation</a> --> - **fieldValidation** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldValidation\" >}}\">fieldValidation</a> <!-- - **pretty** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> --> - **pretty** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> <!-- #### Response 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): OK 201 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): Created 401: Unauthorized --> #### 响应 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): OK 201 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): Created 401: Unauthorized <!-- ### `update` replace status of the specified HorizontalPodAutoscaler #### HTTP Request PUT /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status --> ### `update` 替换特定 HorizontalPodAutoscaler 的状态 #### HTTP 请求 PUT /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status <!-- #### Parameters --> #### 参数 <!-- - **name** (*in path*): string, required name of the HorizontalPodAutoscaler --> - **name** （**路径参数**）: string，必填 HorizontalPodAutoscaler 的名称 <!-- - **namespace** (*in path*): string, required <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> --> - **namespace** （**路径参数**）: string，必填 <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> <!-- - **body**: <a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>, required --> - **body**: <a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>，必填 <!-- - **dryRun** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#dryRun\" >}}\">dryRun</a> --> - **dryRun** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#dryRun\" >}}\">dryRun</a> <!-- - **fieldManager** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldManager\" >}}\">fieldManager</a> --> - **fieldManager** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldManager\" >}}\">fieldManager</a> <!-- - **fieldValidation** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldValidation\" >}}\">fieldValidation</a> --> - **fieldValidation** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldValidation\" >}}\">fieldValidation</a> <!-- - **pretty** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> --> - **pretty** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> <!-- #### Response 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): OK 201 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): Created 401: Unauthorized --> #### 响应 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): OK 201 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): Created 401: Unauthorized <!-- ### `patch` partially update the specified HorizontalPodAutoscaler #### HTTP Request PATCH /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name} --> ### `patch` 部分更新特定的 HorizontalPodAutoscaler #### HTTP 请求 PATCH /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name} <!-- #### Parameters --> #### 参数 <!-- - **name** (*in path*): string, required name of the HorizontalPodAutoscaler --> - **name** （**路径参数**）: string，必填 HorizontalPodAutoscaler 的名称 <!-- - **namespace** (*in path*): string, required <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> --> - **namespace** （**路径参数**）: string，必填 <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> <!-- - **body**: <a href=\"{{< ref \"../common-definitions/patch#Patch\" >}}\">Patch</a>, required --> - **body**: <a href=\"{{< ref \"../common-definitions/patch#Patch\" >}}\">Patch</a>，必填 <!-- - **dryRun** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#dryRun\" >}}\">dryRun</a> --> - **dryRun** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#dryRun\" >}}\">dryRun</a> <!-- - **fieldManager** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldManager\" >}}\">fieldManager</a> --> - **fieldManager** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldManager\" >}}\">fieldManager</a> <!-- - **fieldValidation** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldValidation\" >}}\">fieldValidation</a> --> - **fieldValidation** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldValidation\" >}}\">fieldValidation</a> <!-- - **force** (*in query*): boolean <a href=\"{{< ref \"../common-parameters/common-parameters#force\" >}}\">force</a> --> - **force** （**查询参数**）: boolean <a href=\"{{< ref \"../common-parameters/common-parameters#force\" >}}\">force</a> <!-- - **pretty** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> --> - **pretty** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> <!-- #### Response 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): OK 201 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): Created 401: Unauthorized --> #### 响应 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): OK 201 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): Created 401: Unauthorized <!-- ### `patch` partially update status of the specified HorizontalPodAutoscaler #### HTTP Request PATCH /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status --> ### `patch` 部分更新特定 HorizontalPodAutoscaler 的状态 #### HTTP 请求 PATCH /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name}/status <!-- #### Parameters --> #### 参数 <!-- - **name** (*in path*): string, required name of the HorizontalPodAutoscaler --> - **name** （**路径参数**）: string，必填 HorizontalPodAutoscaler 的名称 <!-- - **namespace** (*in path*): string, required <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> --> - **namespace** （**路径参数**）: string，必填 <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> <!-- - **body**: <a href=\"{{< ref \"../common-definitions/patch#Patch\" >}}\">Patch</a>, required --> - **body**: <a href=\"{{< ref \"../common-definitions/patch#Patch\" >}}\">Patch</a>，必填 <!-- - **dryRun** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#dryRun\" >}}\">dryRun</a> --> - **dryRun** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#dryRun\" >}}\">dryRun</a> <!-- - **fieldManager** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldManager\" >}}\">fieldManager</a> --> - **fieldManager** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldManager\" >}}\">fieldManager</a> <!-- - **fieldValidation** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldValidation\" >}}\">fieldValidation</a> --> - **fieldValidation** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldValidation\" >}}\">fieldValidation</a> <!-- - **force** (*in query*): boolean <a href=\"{{< ref \"../common-parameters/common-parameters#force\" >}}\">force</a> --> - **force** （**查询参数**）: boolean <a href=\"{{< ref \"../common-parameters/common-parameters#force\" >}}\">force</a> <!-- - **pretty** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> --> - **pretty** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> <!-- #### Response 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): OK 201 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): Created 401: Unauthorized --> #### 响应 200 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): OK 201 (<a href=\"{{< ref \"../workload-resources/horizontal-pod-autoscaler-v1#HorizontalPodAutoscaler\" >}}\">HorizontalPodAutoscaler</a>): Created 401: Unauthorized <!-- ### `delete` delete a HorizontalPodAutoscaler #### HTTP Request DELETE /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name} --> ### `delete` 删除一个 HorizontalPodAutoscaler #### HTTP 请求 DELETE /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers/{name} <!-- #### Parameters --> #### 参数 <!-- - **name** (*in path*): string, required name of the HorizontalPodAutoscaler --> - **name** （**路径参数**）: string，必填 HorizontalPodAutoscaler 的名称 <!-- - **namespace** (*in path*): string, required <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> --> - **namespace** （**路径参数**）: string，必填 <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> <!-- - **body**: <a href=\"{{< ref \"../common-definitions/delete-options#DeleteOptions\" >}}\">DeleteOptions</a> --> - **body**: <a href=\"{{< ref \"../common-definitions/delete-options#DeleteOptions\" >}}\">DeleteOptions</a> <!-- - **dryRun** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#dryRun\" >}}\">dryRun</a> --> - **dryRun** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#dryRun\" >}}\">dryRun</a> <!-- - **gracePeriodSeconds** (*in query*): integer <a href=\"{{< ref \"../common-parameters/common-parameters#gracePeriodSeconds\" >}}\">gracePeriodSeconds</a> --> - **gracePeriodSeconds** （**查询参数**）: integer <a href=\"{{< ref \"../common-parameters/common-parameters#gracePeriodSeconds\" >}}\">gracePeriodSeconds</a> <!-- - **pretty** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> --> - **pretty** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> <!-- - **propagationPolicy** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#propagationPolicy\" >}}\">propagationPolicy</a> --> - **propagationPolicy** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#propagationPolicy\" >}}\">propagationPolicy</a> <!-- #### Response 200 (<a href=\"{{< ref \"../common-definitions/status#Status\" >}}\">Status</a>): OK 202 (<a href=\"{{< ref \"../common-definitions/status#Status\" >}}\">Status</a>): Accepted 401: Unauthorized --> #### 响应 200 (<a href=\"{{< ref \"../common-definitions/status#Status\" >}}\">Status</a>): OK 202 (<a href=\"{{< ref \"../common-definitions/status#Status\" >}}\">Status</a>): Accepted 401: Unauthorized <!-- ### `deletecollection` delete collection of HorizontalPodAutoscaler #### HTTP Request DELETE /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers --> ### `deletecollection` 删除 HorizontalPodAutoscaler 的集合 #### HTTP 请求 DELETE /apis/autoscaling/v1/namespaces/{namespace}/horizontalpodautoscalers <!-- #### Parameters --> #### 参数 <!-- - **namespace** (*in path*): string, required <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> --> - **namespace** （**路径参数**）: string，必填 <a href=\"{{< ref \"../common-parameters/common-parameters#namespace\" >}}\">namespace</a> <!-- - **body**: <a href=\"{{< ref \"../common-definitions/delete-options#DeleteOptions\" >}}\">DeleteOptions</a> --> - **body**: <a href=\"{{< ref \"../common-definitions/delete-options#DeleteOptions\" >}}\">DeleteOptions</a> <!-- - **continue** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#continue\" >}}\">continue</a> --> - **continue** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#continue\" >}}\">continue</a> <!-- - **dryRun** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#dryRun\" >}}\">dryRun</a> --> - **dryRun** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#dryRun\" >}}\">dryRun</a> <!-- - **fieldSelector** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldSelector\" >}}\">fieldSelector</a> --> - **fieldSelector** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#fieldSelector\" >}}\">fieldSelector</a> <!-- - **gracePeriodSeconds** (*in query*): integer <a href=\"{{< ref \"../common-parameters/common-parameters#gracePeriodSeconds\" >}}\">gracePeriodSeconds</a> --> - **gracePeriodSeconds** （**查询参数**）: integer <a href=\"{{< ref \"../common-parameters/common-parameters#gracePeriodSeconds\" >}}\">gracePeriodSeconds</a> <!-- - **labelSelector** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#labelSelector\" >}}\">labelSelector</a> --> - **labelSelector** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#labelSelector\" >}}\">labelSelector</a> <!-- - **limit** (*in query*): integer <a href=\"{{< ref \"../common-parameters/common-parameters#limit\" >}}\">limit</a> --> - **limit** （**查询参数**）: integer <a href=\"{{< ref \"../common-parameters/common-parameters#limit\" >}}\">limit</a> <!-- - **pretty** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> --> - **pretty** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#pretty\" >}}\">pretty</a> <!-- - **propagationPolicy** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#propagationPolicy\" >}}\">propagationPolicy</a> --> - **propagationPolicy** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#propagationPolicy\" >}}\">propagationPolicy</a> <!-- - **resourceVersion** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#resourceVersion\" >}}\">resourceVersion</a> --> - **resourceVersion** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#resourceVersion\" >}}\">resourceVersion</a> <!-- - **resourceVersionMatch** (*in query*): string <a href=\"{{< ref \"../common-parameters/common-parameters#resourceVersionMatch\" >}}\">resourceVersionMatch</a> --> - **resourceVersionMatch** （**查询参数**）: string <a href=\"{{< ref \"../common-parameters/common-parameters#resourceVersionMatch\" >}}\">resourceVersionMatch</a> <!-- - **timeoutSeconds** (*in query*): integer <a href=\"{{< ref \"../common-parameters/common-parameters#timeoutSeconds\" >}}\">timeoutSeconds</a> --> - **timeoutSeconds** （**查询参数**）: integer <a href=\"{{< ref \"../common-parameters/common-parameters#timeoutSeconds\" >}}\">timeoutSeconds</a> <!-- #### Response 200 (<a href=\"{{< ref \"../common-definitions/status#Status\" >}}\">Status</a>): OK 401: Unauthorized --> #### 响应 200 (<a href=\"{{< ref \"../common-definitions/status#Status\" >}}\">Status</a>): OK 401: Unauthorized </ins>  No newline at end of file"}
{"_id":"q-en-website-d748dd1edf74f0fef798af560dbb043b6e15a6bba477b472bb3393184c042d08","text":"このリポジトリには、[KubernetesのWebサイトとドキュメント](https://kubernetes.io/)をビルドするために必要な全アセットが格納されています。貢献に興味を持っていただきありがとうございます！ <ins> - [ドキュメントに貢献する](#contributing-to-the-docs) - [翻訳された`README.md`一覧](#localization-readmemds) </ins> # リポジトリの使い方 Hugo(Extended version)を使用してWebサイトをローカルで実行することも、コンテナランタイムで実行することもできます。コンテナランタイムを使用することを強くお勧めします。これにより、本番Webサイトとのデプロイメントの一貫性が得られます。"}
{"_id":"q-en-website-d8f0a1623752d9c6c33a1b9fd83f667975f999fca79f78f83837a365c657624f","text":"`zk-1` is scheduled. ```shell <del> kubectl drain $(kubectl get pod zk-1 --template {{.spec.nodeName}}) --ignore-daemonsets --force --delete-local-data \"kubernetes-node-ixsl\" cordoned </del> <ins> kubectl drain $(kubectl get pod zk-1 --template {{.spec.nodeName}}) --ignore-daemonsets --force --delete-emptydir-data \"kubernetes-node-ixsl\" cordoned </ins> ``` ```"}
{"_id":"q-en-website-da11bf126711f1cdc217b68ccf8a8186aad1941e7982b012acdf46020c0d5501","text":"check the documentation for that version. {{< /note >}} <!-- body --> ## Install and configure prerequisites <del> The following steps apply common settings for Kubernetes nodes on Linux. </del> <ins> The following steps apply common settings for Kubernetes nodes on Linux. </ins> You can skip a particular setting if you're certain you don't need it. <del> For more information, see [Network Plugin Requirements](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#network-plugin-requirements) or the documentation for your specific container runtime. </del> <ins> For more information, see [Network Plugin Requirements](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#network-plugin-requirements) or the documentation for your specific container runtime. </ins> ### Forwarding IPv4 and letting iptables see bridged traffic"}
{"_id":"q-en-website-dbc48a263efe98343fd985bc66c4ff05b4c40d1aa204b19e9553b98c8d4bbb9e","text":"## Version skew policy {#version-skew-policy} <del> The `kubeadm` tool of version v{{< skew latestVersion >}} may deploy clusters with a control plane of version v{{< skew latestVersion >}} or v{{< skew prevMinorVersion >}}. `kubeadm` v{{< skew latestVersion >}} can also upgrade an existing kubeadm-created cluster of version v{{< skew prevMinorVersion >}}. </del> <ins> While kubeadm allows version skew against some components that it manages, it is recommended that you match the kubeadm version with the versions of the control plane components, kube-proxy and kubelet. </ins> <del> Due to that we can't see into the future, kubeadm CLI v{{< skew latestVersion >}} may or may not be able to deploy v{{< skew nextMinorVersion >}} clusters. </del> <ins> ### kubeadm's skew against the Kubernetes version </ins> <del> These resources provide more information on supported version skew between kubelets and the control plane, and other Kubernetes components: </del> <ins> kubeadm can be used with Kubernetes components that are the same version as kubeadm or one version older. The Kubernetes version can be specified to kubeadm by using the `--kubernetes-version` flag of `kubeadm init` or the [`ClusterConfiguration.kubernetesVersion`](/docs/reference/config-api/kubeadm-config.v1beta3/) field when using `--config`. This option will control the versions of kube-apiserver, kube-controller-manager, kube-scheduler and kube-proxy. </ins> <del> * Kubernetes [version and version-skew policy](/docs/setup/release/version-skew-policy/) * Kubeadm-specific [installation guide](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#installing-kubeadm-kubelet-and-kubectl) </del> <ins> Example: * kubeadm is at {{< skew latestVersion >}} * `kubernetesVersion` must be at {{< skew latestVersion >}} or {{< skew prevMinorVersion >}} ### kubeadm's skew against the kubelet Similarly to the Kubernetes version, kubeadm can be used with a kubelet version that is the same version as kubeadm or one version older. Example: * kubeadm is at {{< skew latestVersion >}} * kubelet on the host must be at {{< skew latestVersion >}} or {{< skew prevMinorVersion >}} ### kubeadm's skew against kubeadm There are certain limitations on how kubeadm commands can operate on existing nodes or whole clusters managed by kubeadm. If new nodes are joined to the cluster, the kubeadm binary used for `kubeadm join` must match the last version of kubeadm used to either create the cluster with `kubeadm init` or to upgrade the same node with `kubeadm upgrade`. Similar rules apply to the rest of the kubeadm commands with the exception of `kubeadm upgrade`. Example for `kubeadm join`: * kubeadm version {{< skew latestVersion >}} was used to create a cluster with `kubeadm init` * Joining nodes must use a kubeadm binary that is at version {{< skew latestVersion >}} Nodes that are being upgraded must use a version of kubeadm that is the same MINOR version or one MINOR version newer than the version of kubeadm used for managing the node. Example for `kubeadm upgrade`: * kubeadm version {{< skew prevMinorVersion >}} was used to create or upgrade the node * The version of kubeadm used for upgrading the node must be at {{< skew prevMinorVersion >}} or {{< skew latestVersion >}} To learn more about the version skew between the different Kubernetes component see the [Version Skew Policy](https://kubernetes.io/releases/version-skew-policy/). </ins> ## Limitations {#limitations}"}
{"_id":"q-en-website-dc93783c12b2441081d9704a6d5c1660c0ed5548a9497cb7bc88de5414f5697d","text":"<ins> --- title: Tutoriais main_menu: true no_list: true weight: 60 content_type: concept --- <!-- overview --> Essa seção da documentação contém tutoriais (em inglês). Um tutorial mostra como realizar um objetivo mais complexo que uma simples [tarefa](/docs/tasks/). Eles podem ser divididos em diversas seções, cada uma com uma sequência de passos e etapas a serem seguidos. Antes de iniciar um tutorial, é interessante que vocẽ salve a página de [Glossário](/pt/docs/reference/glossary/) para futuras referências. <!-- body --> ## Básicos * [Kubernetes básico](/docs/tutorials/kubernetes-basics/) é um tutorial interativo que auxilia no entendimento do ecossistema Kubernetes, bem como te permite testar algumas funcionalidades básicas do Kubernetes. * [Introdução ao Kubernetes (edX)](https://www.edx.org/course/introduction-kubernetes-linuxfoundationx-lfs158x#) é um curso gratuíto da edX que te guia no entendimento do Kubernetes, seus conceitos, bem como na execução de tarefas mais simples. * [Hello Minikube](/docs/tutorials/hello-minikube/) é um \"Hello World\" que te permite testar rapidamente o Kubernetes em sua estação com o uso do Minikube ## Configuração * [Configurando o Redis usando um ConfigMap](/docs/tutorials/configuration/configure-redis-using-configmap/) ## Aplicações stateless * [Expondo um Endereço de IP externo para acessar uma aplicação no Cluster](/docs/tutorials/stateless-application/expose-external-ip-address/) * [Exemplo: Implantando a aplicação de Livro de Visitas (Guestbook) em  PHP com Redis](/docs/tutorials/stateless-application/guestbook/) ## Aplicações stateful * [Básicos sobre StatefulSet](/docs/tutorials/stateful-application/basic-stateful-set/) * [Exemplo: WordPress e MySQL com Volumes Persistentes](/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/) * [Exemplo: Implantando Cassandra com Stateful Sets](/docs/tutorials/stateful-application/cassandra/) * [Executando ZooKeeper no Kubernetes](/docs/tutorials/stateful-application/zookeeper/) ## Pipelines de CI/CD * [Configurando um Pipeline CI/CD com Kubernetes Parte 1: Visão Geral](https://www.linux.com/blog/learn/chapter/Intro-to-Kubernetes/2017/5/set-cicd-pipeline-kubernetes-part-1-overview) * [Configurando um Pipeline CI/CD com um Pod Jenkins no Kubernetes (Parte 2)](https://www.linux.com/blog/learn/chapter/Intro-to-Kubernetes/2017/6/set-cicd-pipeline-jenkins-pod-kubernetes-part-2) * [Executando e escalando um aplicativo distribuído de palavras cruzadas com CI/CD no Kubernetes (Parte 3)](https://www.linux.com/blog/learn/chapter/intro-to-kubernetes/2017/6/run-and-scale-distributed-crossword-puzzle-app-cicd-kubernetes-part-3) * [Configurando um CI/CD para um aplicativo distribuído de palavras cruzadas no Kubernetes (Parte 4)](https://www.linux.com/blog/learn/chapter/intro-to-kubernetes/2017/6/set-cicd-distributed-crossword-puzzle-app-kubernetes-part-4) ## Clusters * [AppArmor](/docs/tutorials/clusters/apparmor/) ## Serviços / \"Services\" * [Usando IP de origem](/docs/tutorials/services/source-ip/) ## {{% heading \"whatsnext\" %}} Se você desejar escrever um tutorial, veja a página [Utilizando templates](/docs/home/contribute/page-templates/) para informações sobre o tipo de página e o formato a ser utilizado. </ins>"}
{"_id":"q-en-website-dd650d5ffc63e81c7620b567afd55c785ef15cfe14d75cbb3d93df1a96f4cd5f","text":"The value for this annotation must be **true** to take effect. This annotation indicates that pods running as this service account may only reference Secret API objects specified in the service account's `secrets` field. <ins> ### node.kubernetes.io/exclude-from-external-load-balancer Example: `node.kubernetes.io/exclude-from-external-load-balancer` Used on: Node Kubernetes automatically enables the `ServiceNodeExclusion` feature gate on the clusters it creates. With this feature gate enabled on a cluster, you can add labels to particular worker nodes to exclude them from the list of backend servers. The following command can be used to exclude a worker node from the list of backend servers in a backend set- `kubectl label nodes <node-name> node.kubernetes.io/exclude-from-external-load-balancers=true` </ins> ### controller.kubernetes.io/pod-deletion-cost {#pod-deletion-cost} Example: `controller.kubernetes.io/pod-deletion-cost: \"10\"`"}
{"_id":"q-en-website-de1e4827d13e7211ec26098e6d62f3541cf57eee7e84ca9b92fcee1e0ef99bb6","text":"| Scala                | [github.com/hagay3/skuber](https://github.com/hagay3/skuber) | | Scala                | [github.com/joan38/kubernetes-client](https://github.com/joan38/kubernetes-client) | | Swift                | [github.com/swiftkube/client](https://github.com/swiftkube/client) | <del> | DotNet               | [github.com/tonnyeremin/kubernetes_gen](https://github.com/tonnyeremin/kubernetes_gen) | | DotNet (RestSharp)   | [github.com/masroorhasan/Kubernetes.DotNet](https://github.com/masroorhasan/Kubernetes.DotNet) | | Elixir               | [github.com/obmarg/kazan](https://github.com/obmarg/kazan/) | | Elixir               | [github.com/coryodaniel/k8s](https://github.com/coryodaniel/k8s) | </del>"}
{"_id":"q-en-website-de6da0276fe94434d58e386c4f3bdd1e896c274f5a827096c5837e523e836e06","text":"## Letting iptables see bridged traffic <ins> Make sure that the `br_netfilter` module is loaded. This can be done by running `lsmod | grep br_netfilter`. To load it explicitly call `sudo modprobe br_netfilter`. </ins> As a requirement for your Linux Node's iptables to correctly see bridged traffic, you should ensure `net.bridge.bridge-nf-call-iptables` is set to 1 in your `sysctl` config, e.g. ```bash"}
{"_id":"q-en-website-df0277a0b9e914710c72de4cfe9ad1a6eed351cf737dabba692b0b1c6899d5f0","text":"<div class=\"row\"> <div class=\"col-md-8\"> <p><b>The Master is responsible for managing the cluster.</b> The master coordinates all activities in your cluster, such as scheduling applications, maintaining applications' desired state, scaling applications, and rolling out new updates.</p> <del> <p><b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes master. The node should also have tools for handling container operations, such as <a href=\"https://www.docker.com/\">Docker</a> or <a href=\"https://coreos.com/rkt/\">rtk</a>. A Kubernetes cluster that handles production traffic should have a minimum of three nodes.</p> </del> <ins> <p><b>A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster.</b> Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes master. The node should also have tools for handling container operations, such as <a href=\"https://www.docker.com/\">Docker</a> or <a href=\"https://coreos.com/rkt/\">rkt</a>. A Kubernetes cluster that handles production traffic should have a minimum of three nodes.</p> </ins> </div> <div class=\"col-md-4\">"}
{"_id":"q-en-website-df818dfd1bfba1c51dc55708989f8cf64764e6901069490f47efa4fc59af12d5","text":"1. Run the following: <del> ```sh ./etcd --listen-client-urls=http://$PRIVATE_IP:2379 --advertise-client-urls=http://$PRIVATE_IP:2379 ``` </del> <ins> ```sh etcd --listen-client-urls=http://$PRIVATE_IP:2379  --advertise-client-urls=http://$PRIVATE_IP:2379 ``` </ins> <del> 2. Start Kubernetes API server with the flag `--etcd-servers=$PRIVATE_IP:2379`. </del> <ins> 2. Start the Kubernetes API server with the flag `--etcd-servers=$PRIVATE_IP:2379`. </ins> <del> Replace `PRIVATE_IP` with your etcd client IP. </del> <ins> Make sure `PRIVATE_IP` is set to your etcd client IP. </ins> ### Multi-node etcd cluster <del> For durability and high availability, run etcd as a multi-node cluster in production and back it up periodically. A five-member cluster is recommended in production. For more information, see [FAQ Documentation](https://github.com/coreos/etcd/blob/master/Documentation/faq.md#what-is-failure-tolerance). </del> <ins> For durability and high availability, run etcd as a multi-node cluster in production and back it up periodically. A five-member cluster is recommended in production. For more information, see [FAQ documentation](https://etcd.io/docs/current/faq/#what-is-failure-tolerance). </ins> <del> Configure an etcd cluster either by static member information or by dynamic discovery. For more information on clustering, see [etcd Clustering Documentation](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/clustering.md). </del> <ins> Configure an etcd cluster either by static member information or by dynamic discovery. For more information on clustering, see [etcd clustering documentation](https://etcd.io/docs/current/op-guide/clustering/). </ins> <del> For an example, consider a five-member etcd cluster running with the following client URLs: `http://$IP1:2379`, `http://$IP2:2379`, `http://$IP3:2379`, `http://$IP4:2379`, and `http://$IP5:2379`. To start a Kubernetes API server: </del> <ins> For an example, consider a five-member etcd cluster running with the following client URLs: `http://$IP1:2379`, `http://$IP2:2379`, `http://$IP3:2379`, `http://$IP4:2379`, and `http://$IP5:2379`. To start a Kubernetes API server: </ins> 1. Run the following: <del> ```sh ./etcd --listen-client-urls=http://$IP1:2379, http://$IP2:2379, http://$IP3:2379, http://$IP4:2379, http://$IP5:2379 --advertise-client-urls=http://$IP1:2379, http://$IP2:2379, http://$IP3:2379, http://$IP4:2379, http://$IP5:2379 ``` </del> <ins> ```shell etcd --listen-client-urls=http://$IP1:2379,http://$IP2:2379,http://$IP3:2379,http://$IP4:2379,http://$IP5:2379 --advertise-client-urls=http://$IP1:2379,http://$IP2:2379,http://$IP3:2379,http://$IP4:2379,http://$IP5:2379 ``` </ins> <del> 2. Start Kubernetes API servers with the flag `--etcd-servers=$IP1:2379, $IP2:2379, $IP3:2379, $IP4:2379, $IP5:2379`. </del> <ins> 2. Start the Kubernetes API servers with the flag `--etcd-servers=$IP1:2379,$IP2:2379,$IP3:2379,$IP4:2379,$IP5:2379`. </ins> <del> Replace `IP` with your client IP addresses. </del> <ins> Make sure the `IP<n>` variables are set to your client IP addresses. </ins> <del> ###  Multi-node etcd cluster with load balancer </del> <ins> ### Multi-node etcd cluster with load balancer </ins> To run a load balancing etcd cluster:"}
{"_id":"q-en-website-df9a422166e3fd49a8353422f1a42abd5fa3038f3a6bce21e764511702dd2dd8","text":"<!--script src=\"https://unpkg.com/split.js/dist/split.min.js\"></script--> <script src=\"/js/split-1.6.0.js\" intregrity=\"sha384-0blL3GqHy6+9fw0cyY2Aoiwg4onHAtslAs4OkqZY7UQBrR65/K4gI+hxLdWDrjpz\"></script> <ins> <!--Script for dismissing banners/notices--> <script defer src=\"{{ \"js/dismiss_banner.js\" | relURL }}\"></script> </ins> {{- if or (.HasShortcode \"table\")  (.HasShortcode \"feature-gate-table\") -}} <script defer src=\"{{ \"js/sortable-table.js\" | relURL }}\"></script> {{- end -}}"}
{"_id":"q-en-website-dfcaea7bce6215d226bdfa5400de47cb0f17692eaea71b94fde9c7e29b7b0e9d","text":"- `Count`: Podがデフォルトの方法で処理されるべきであることを示します。`.spec.backoffLimit`のカウンターが加算されます。 {{< note >}} <del> `PodFailurePolicy`を使用すると、Jobコントローラは`Failed`フェーズのPodのみにマッチします。削除タイムスタンプを持つPodで、終了フェーズ(`Failed`または`Succeeded`)にないものは、まだ終了中と見なされます。これは、終了中Podは終了フェーズに達するまで[追跡ファイナライザー](#job-tracking-with-finalizers)を保持することを意味します。Kubernetes 1.27以降、Kubeletは削除されたPodを終了フェーズに遷移させます(参照:[Podのフェーズ](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase))。これにより、削除されたPodはJobコントローラーによってファイナライザーが削除されます。 </del> <ins> `PodFailurePolicy`を使用すると、Jobコントローラーは`Failed`フェーズのPodのみにマッチします。削除タイムスタンプを持つPodで、終了フェーズ(`Failed`または`Succeeded`)にないものは、まだ終了中と見なされます。これは、終了中Podは終了フェーズに達するまで[追跡ファイナライザー](#job-tracking-with-finalizers)を保持することを意味します。Kubernetes 1.27以降、Kubeletは削除されたPodを終了フェーズに遷移させます(参照:[Podのフェーズ](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase))。これにより、削除されたPodはJobコントローラーによってファイナライザーが削除されます。 </ins> {{< /note >}} ## Jobの終了とクリーンアップ  {#job-termination-and-cleanup}"}
{"_id":"q-en-website-e02f7a27fcb267c3630b23a9d4a9680e90bee39d8b44a7490dfcf67acadf71b6","text":"} ``` <ins> ## Create Pod that uses the container runtime default seccomp profile Most container runtimes provide a sane set of default syscalls that are allowed or not. You can adopt these defaults for your workload by setting the seccomp type in the security context of a pod or container to `RuntimeDefault`. {{< note >}} If you have the `SeccompDefault` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) enabled, then Pods use the `RuntimeDefault` seccomp profile whenever no other seccomp profile is specified. Otherwise, the default is `Unconfined`. {{< /note >}} Here's a manifest for a Pod that requests the `RuntimeDefault` seccomp profile for all its containers: {{< codenew file=\"pods/security/seccomp/ga/default-pod.yaml\" >}} Create that Pod: ```shell kubectl apply -f https://k8s.io/examples/pods/security/seccomp/ga/default-pod.yaml ``` ```shell kubectl get pod default-pod ``` The Pod should be showing as having started successfully: ``` NAME        READY   STATUS    RESTARTS   AGE default-pod 1/1     Running   0          20s ``` Finally, now that you saw that work OK, clean up: ```shell kubectl delete pod default-pod --wait --now ``` </ins> ## Create a Pod with a seccomp profile for syscall auditing To start off, apply the `audit.json` profile, which will log all syscalls of the"}
{"_id":"q-en-website-e0353a8dbbe40743bbefe914aa968e9b8c4710dd8fc1c73507c8935399beacc6","text":"[the design doc](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/instrumentation/metrics-server.md). ### Summary API Source <del> The [Kubelet](/docs/reference/command-line-tools-reference/kubelet/) gathers stats at node, volume, pod and container level, and omits them in the [Summary API](https://github.com/kubernetes/kubernetes/blob/7d309e0104fedb57280b261e5677d919cb2a0e2d/staging/src/k8s.io/kubelet/pkg/apis/stats/v1alpha1/types.go) </del> <ins> The [Kubelet](/docs/reference/command-line-tools-reference/kubelet/) gathers stats at node, volume, pod and container level, and emits their statistics in the [Summary API](https://github.com/kubernetes/kubernetes/blob/7d309e0104fedb57280b261e5677d919cb2a0e2d/staging/src/k8s.io/kubelet/pkg/apis/stats/v1alpha1/types.go) </ins> for consumers to read. Pre-1.23, these resources have been primarily gathered from [cAdvisor](https://github.com/google/cadvisor). However, in 1.23 with the"}
{"_id":"q-en-website-e03d05490f42983508e4bae02a0a98f5aee3e6056c99f1e0789b7aba4b66f873","text":"<ins> --- title: \"从 dockershim 迁移\" weight: 10 content_type: task --- <!-- title: \"Migrating from dockershim\" weight: 10 content_type: task --> <!-- overview --> <!-- This section presents information you need to know when migrating from dockershim to other container runtimes. --> 本节提供从 dockershim 迁移到其他容器运行时的必备知识。 <!-- Since the announcement of [dockershim deprecation](/blog/2020/12/08/kubernetes-1-20-release-announcement/#dockershim-deprecation) in Kubernetes 1.20, there were questions on how this will affect various workloads and Kubernetes installations. You can find this blog post useful to understand the problem better: [Dockershim Deprecation FAQ](/blog/2020/12/02/dockershim-faq/) --> 自从 Kubernetes 1.20 宣布 [弃用 dockershim](/zh/blog/2020/12/08/kubernetes-1-20-release-announcement/#dockershim-deprecation)， 各类疑问随之而来：这对各类工作负载和 Kubernetes 部署会产生什么影响。 你会发现这篇博文对于更好地理解此问题非常有用： [弃用 Dockershim 常见问题](/zh/blog/2020/12/02/dockershim-faq/) <!-- It is recommended to migrate from dockershim to alternative container runtimes. Check out [container runtimes](/docs/setup/production-environment/container-runtimes/) section to know your options. Make sure to [report issues](https://github.com/kubernetes/kubernetes/issues) you encountered with the migration. So the issue can be fixed in a timely manner and your cluster would be ready for dockershim removal. --> 建议从 dockershim 迁移到其他替代的容器运行时。 请参阅[容器运行时](/zh/docs/setup/production-environment/container-runtimes/) 一节以了解可用的备选项。 当在迁移过程中遇到麻烦，请[上报问题](https://github.com/kubernetes/kubernetes/issues)。 那么问题就可以及时修复，你的集群也可以进入移除 dockershim 前的就绪状态。 </ins>"}
{"_id":"q-en-website-e1dc67af6044016c71aa50520d48f390812354be0b393d22a3f641c5ce75094d","text":"<ins> --- layout: blog title: \"dl.k8s.io 采用内容分发网络（CDN）\" date: 2023-06-09 slug: dl-adopt-cdn --- <!-- layout: blog title: \"dl.k8s.io to adopt a Content Delivery Network\" date: 2023-06-09 slug: dl-adopt-cdn --> <!-- **Authors**: Arnaud Meukam (VMware), Hannah Aubry (Fast Forward), Frederico Muñoz (SAS Institute) --> **作者**：Arnaud Meukam (VMware), Hannah Aubry (Fast Forward), Frederico Muñoz (SAS Institute) **译者**：[Xin Li](https://github.com/my-git9) (Daocloud) <!-- We're happy to announce that dl.k8s.io, home of the official Kubernetes binaries, will soon be powered by [Fastly](https://www.fastly.com). Fastly is known for its high-performance content delivery network (CDN) designed to deliver content quickly and reliably around the world. With its powerful network, Fastly will help us deliver official Kubernetes binaries to users faster and more reliably than ever before. --> 我们很高兴地宣布，官方 Kubernetes 二进制文件的主页 dl.k8s.io 很快将由 [Fastly](https://www.fastly.com) 提供支持。 Fastly 以其高性能内容分发网络（CDN）而闻名， 该网络旨在全球范围内快速可靠地分发内容。凭借其强大的网络，Fastly 将帮助我们实现比以往更快、更可靠地向用户分发官方 Kubernetes 二进制文件。 <!-- The decision to use Fastly was made after an extensive evaluation process in which we carefully evaluated several potential content delivery network providers. Ultimately, we chose Fastly because of their commitment to the open internet and proven track record of delivering fast and secure digital experiences to some of the most known open source projects (through their [Fast Forward](https://www.fastly.com/fast-forward) program). --> 使用 Fastly 是在经过广泛的评估过程后做出的决定， 在该过程中我们仔细评估了几个潜在的内容分发网络提供商。最终，我们选择 Fastly 是因为他们对开放互联网的承诺以及在为一些著名的开源项目（通过他们的 [Fast Forward](https://www.fastly.com/fast-forward) 计划）提供快速和安全的数字体验方面的良好记录。 <!-- ## What you need to know about this change - On Monday, July 24th, the IP addresses and backend storage associated with the dl.k8s.io domain name will change. - The change will not impact the vast majority of users since the domain name will remain the same. - If you restrict access to specific IP ranges, access to the dl.k8s.io domain could stop working. --> ## 关于本次更改你需要了解的信息 - 7 月 24 日星期一，与 dl.k8s.io 域名关联的 IP 地址和后端存储将发生变化。 - 由于域名将保持不变，因此更改不会影响绝大多数用户。 - 如果你限制对特定 IP 范围的访问，则对 dl.k8s.io 域的访问可能会停止工作。 <!-- If you think you may be impacted or want to know more about this change, please keep reading. --> 如果你认为你可能会受到影响或想了解有关此次更改的更多信息，请继续阅读。 <!-- ## Why are we making this change The official Kubernetes binaries site, dl.k8s.io, is used by thousands of users all over the world, and currently serves _more than 5 petabytes of binaries each month_. This change will allow us to improve access to those resources by leveraging a world-wide CDN. --> ## 我们为什么要进行此更改 官方 Kubernetes 二进制文件网站 dl.k8s.io 被全世界成千上万的用户使用， 目前**每月提供超过 5 PB 的二进制文件服务**。本次更改将通过充分利用全球 CDN 来改善对这些资源的访问。 <!-- ## Does this affect dl.k8s.io only, or are other domains also affected? Only dl.k8s.io will be affected by this change. --> ## 这只影响 dl.k8s.io，还是其他域也受到影响？ 只有 dl.k8s.io 会受到本次变更的影响。 <!-- ## My company specifies the domain names that we are allowed to be accessed. Will this change affect the domain name? No, the domain name (`dl.k8s.io`) will remain the same: no change will be necessary, and access to the Kubernetes release binaries site should not be affected. --> ## 我公司规定了允许我们访问的域名，此更改会影响域名吗？ 不，域名（`dl.k8s.io`）将保持不变：无需更改，不会影响对 Kubernetes 发布二进制文件站点的访问。 <!-- ## My company uses some form of IP filtering. Will this change affect access to the site? If IP-based filtering is in place, it’s possible that access to the site will be affected when the new IP addresses become active. --> ## 我的公司使用某种形式的 IP 过滤，此更改会影响对站点的访问吗？ 如果已经存在基于 IP 的过滤，则当新 IP 地址变为活动状态时，对站点的访问可能会受到影响。 <!-- ## If my company doesn’t use IP addresses to restrict network traffic, do we need to do anything? No, the switch to the CDN should be transparent. --> ## 如果我的公司不使用 IP 地址来限制网络流量，我们需要做些什么吗？ 不，切换到 CDN 的过程应该是透明的。 <!-- ## Will there be a dual running period? **No, it is a cutover.** You can, however, test your networks right now to check if they can route to the new public IP addresses from Fastly.  You should add the new IPs to your network's `allowlist` before July 24th. Once the transfer is complete, ensure your networks use the new IP addresses to connect to the `dl.k8s.io` service. --> ## 会有双运行期吗？ **不，这是切换。**但是，你现在可以测试你的网络，检查它们是否可以从 Fastly 路由到新的公共 IP 地址。 你应该在 7 月 24 日之前将新 IP 添加到你网络的 `allowlist`（白名单）中。 切换完成后，确保你的网络使用新的 IP 地址连接到 `dl.k8s.io` 服务。 <!-- ## What are the new IP addresses? If you need to manage an allow list for downloads, you can get the ranges to match from the Fastly API, in JSON: [public IP address ranges](https://api.fastly.com/public-ip-list).  You don't need any credentials to download that list of ranges. --> ## 新 IP 地址是什么？ 如果你需要管理下载允许列表，你可以从 Fastly API 中获取需要匹配的范围， JSON 格式地址：[公共 IP 地址范围](https://api.fastly.com/public-ip-list)。 你不需要任何凭据即可下载该范围列表。 <!-- ## What next steps would you recommend? If you have IP-based filtering in place, we recommend the following course of action **before July, 24th**: --> ## 推荐哪些后续操作？ 如果你已经有了基于 IP 的过滤，我们建议你**在 7 月 24 日**之前采取以下行动： <!-- - Add the new IP addresses to your allowlist. - Conduct tests with your networks/firewall to ensure your networks can route to the new IP addresses. After the change is made, we recommend double-checking that HTTP calls are accessing dl.k8s.io with the new IP addresses. --> - 将新的 IP 地址添加到你的白名单。 - 对你的网络/防火墙进行测试，以确保你的网络可以路由到新的 IP 地址。 进行更改后，我们建议仔细检查 HTTP 调用是否正在使用新 IP 地址访问 dl.k8s.io。 <!-- ## What should I do if I detect some abnormality after the cutover date? If you encounter any weirdness during binaries download, please [open an issue](https://github.com/kubernetes/k8s.io/issues/new/choose). --> ## 切换后发现异常怎么办？ 如果你在二进制文件下载过程中遇到任何异常， 请[提交 Issue](https://github.com/kubernetes/k8s.io/issues/new/choose)。 </ins>"}
{"_id":"q-en-website-e22222e86c952ad58f02251f32d8f904e4b096f4b9b018b3a24518ed23695b77","text":"{{< glossary_tooltip text=\"PersistentVolumeClaim\" term_id=\"persistent-volume-claim\" >}} is being created from a VolumeSnapshot. <del> Refer to [Converting the volume mode of a Snapshot](/docs/concepts/storage/volume-snapshots/#convert-volume-mode) </del> <ins> Refer to [Converting the volume mode of a Snapshot](/docs/concepts/storage/volume-snapshots/#convert-volume-mode) </ins> and the [Kubernetes CSI Developer Documentation](https://kubernetes-csi.github.io/docs/) for more information. ## Annotations used for audit"}
{"_id":"q-en-website-e22c49a11449325ed3b8b1936d90176aa56358a8f23962bb86f498c8c4c628c6","text":"#### Creating a Secret with a Docker config <ins> You need to know the username, registry password and client email address for authenticating to the registry, as well as its hostname. </ins> Run the following command, substituting the appropriate uppercase values: ```shell"}
{"_id":"q-en-website-e230ddde4b774c0eca0154d6de0c203cce92111279131a54bff125e716919c7e","text":"## IBM Cloud Kubernetes Service ### Compute nodes <del> By using the IBM Cloud Kubernetes Service provider, you can create clusters with a mixture of virtual and physical (bare metal) nodes in a single zone or across multiple zones in a region. For more information, see [Planning your cluster and worker node setup](https://cloud.ibm.com/docs/containers?topic=containers-plan_clusters#plan_clusters). </del> <ins> By using the IBM Cloud Kubernetes Service provider, you can create clusters with a mixture of virtual and physical (bare metal) nodes in a single zone or across multiple zones in a region. For more information, see [Planning your cluster and worker node setup](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodes). </ins> The name of the Kubernetes Node object is the private IP address of the IBM Cloud Kubernetes Service worker node instance."}
{"_id":"q-en-website-e2489075fbcc0586bbacc2cdb38ca7c53b5f7526c083e40cc3fc835b76092d36","text":"Auditing allows cluster administrators to answer the following questions: --> <del> Kubernetes**审计（Auditing）**功能提供了与安全相关的、按时间顺序排列的记录集， </del> <ins> Kubernetes **审计（Auditing）** 功能提供了与安全相关的、按时间顺序排列的记录集， </ins> 记录每个用户、使用 Kubernetes API 的应用以及控制面自身引发的活动。 审计功能使得集群管理员能够回答以下问题："}
{"_id":"q-en-website-e2a673141965939b4993d9ae21d0da690cfe63a76527973748a25f75a402cb03","text":"the configurations portable. Service accounts are different from user accounts, which are authenticated <del> human users in the cluster. By default, user accounts don't exist in the Kubernetes API server; instead, the API server treats user identities as opaque </del> <ins> human users in the cluster. By default, user accounts don't exist in the Kubernetes API server; instead, the API server treats user identities as opaque </ins> data. You can authenticate as a user account using multiple methods. Some Kubernetes distributions might add custom extension APIs to represent user accounts in the API server."}
{"_id":"q-en-website-e3328989e7f2126f0b56ba5747d3728787e6589a752df1fb5bffca6e60835fe3","text":"<ins> --- title: Tarefas main_menu: true weight: 50 content_type: concept --- <!-- overview --> Essa seção da documentação contém páginas que mostram como executar tarefas individuais. Essas tarefas são organizadas em uma curta sequência de etapas e passos que te auxiliam a entender conceitos básicos. Se você desejar adicionar uma tarefa, verifique como [criar um Pull Request para a documentação](/docs/contribute/new-content/open-a-pr/). </ins>"}
{"_id":"q-en-website-e3bbe0b6c9f5b1a97e726a357c2b9e382e63bb5bc6dd90fad2e61ee6ac446bf6","text":"* [Dashboard](https://github.com/kubernetes/dashboard#kubernetes-dashboard) is a dashboard web interface for Kubernetes. <del> * [Weave Scope](https://www.weave.works/documentation/scope-latest-installing/#k8s) is a tool for graphically visualizing your containers, pods, services etc. Use it in conjunction with a [Weave Cloud account](https://cloud.weave.works/) or host the UI yourself. </del> <ins> * [Weave Scope](https://www.weave.works/documentation/scope-latest-installing/#k8s) is a tool for visualizing your containers, Pods, Services and more. </ins> ## Infrastructure"}
{"_id":"q-en-website-e3cdb2cc64b15d99d039614360440be8b27f13be0297ec5c7dc460542ee8193e","text":"### hostPath {#hostpath} <ins> {{< warning >}} HostPath volumes present many security risks, and it is a best practice to avoid the use of HostPaths when possible. When a HostPath volume must be used, it should be scoped to only the required file or directory, and mounted as ReadOnly. If restricting HostPath acccess to specific directories through AdmissionPolicy, `volumeMounts` MUST be required to use `readOnly` mounts for the policy to be effective. {{< /warning >}} </ins> A `hostPath` volume mounts a file or directory from the host node's filesystem into your Pod. This is not something that most Pods will need, but it offers a powerful escape hatch for some applications."}
{"_id":"q-en-website-e4ec1e21755dd56333792804c0944aacc0feca65181f2747cf93b63ce2e7b803","text":"sudo sysctl --system ``` <del> Verify that the `br_netfilter`, `overlay` modules are loaded by running below instructions: </del> <ins> Verify that the `br_netfilter`, `overlay` modules are loaded by running the following commands: </ins> ```bash lsmod | grep br_netfilter lsmod | grep overlay ``` <del> Verify that the `net.bridge.bridge-nf-call-iptables`, `net.bridge.bridge-nf-call-ip6tables`, `net.ipv4.ip_forward` system variables are set to 1 in your `sysctl` config by running below instruction: </del> <ins> Verify that the `net.bridge.bridge-nf-call-iptables`, `net.bridge.bridge-nf-call-ip6tables`, and `net.ipv4.ip_forward` system variables are set to `1` in your `sysctl` config by running the following command: </ins> ```bash sysctl net.bridge.bridge-nf-call-iptables net.bridge.bridge-nf-call-ip6tables net.ipv4.ip_forward ``` <del> ## Cgroup drivers </del> <ins> ## cgroup drivers </ins> On Linux, {{< glossary_tooltip text=\"control groups\" term_id=\"cgroup\" >}} are used to constrain resources that are allocated to processes. <del> Both {{< glossary_tooltip text=\"kubelet\" term_id=\"kubelet\" >}} and the </del> <ins> Both the {{< glossary_tooltip text=\"kubelet\" term_id=\"kubelet\" >}} and the </ins> underlying container runtime need to interface with control groups to enforce <del> [resource management for pods and containers](/docs/concepts/configuration/manage-resources-containers/) and set resources such as cpu/memory requests and limits. To interface with control </del> <ins> [resource management for pods and containers](/docs/concepts/configuration/manage-resources-containers/) and set resources such as cpu/memory requests and limits. To interface with control </ins> groups, the kubelet and the container runtime need to use a *cgroup driver*. <del> It's critical that the kubelet and the container runtime uses the same cgroup </del> <ins> It's critical that the kubelet and the container runtime use the same cgroup </ins> driver and are configured the same. There are two cgroup drivers available:"}
{"_id":"q-en-website-e5146c34552d13c48d60ee9f8a8f119d5c5d51a24ea7bcce3e99c2dc5965f04e","text":"Kubernetes supports many types of volumes. A {{< glossary_tooltip term_id=\"pod\" text=\"Pod\" >}} can use any number of volume types simultaneously. Ephemeral volume types have a lifetime of a pod, but persistent volumes exist beyond <del> the lifetime of a pod. Consequently, a volume outlives any containers that run within the pod, and data is preserved across container restarts. When a pod ceases to exist, Kubernetes destroys ephemeral volumes; however, Kubernetes does not destroy persistent volumes. </del> <ins> the lifetime of a pod. When a pod ceases to exist, Kubernetes destroys ephemeral volumes; however, Kubernetes does not destroy persistent volumes. For any kind of volume in a given pod, data is preserved across container restarts. </ins> At its core, a volume is just a directory, possibly with some data in it, which is accessible to the containers in a pod. How that directory comes to be, the"}
{"_id":"q-en-website-e6327bd3c8152474f92a80b8cadb0f56a6b0dc7f3ea9c1901ea65ec87f48732a","text":"もしあるPodの単一のInitコンテナが失敗した場合、Kubeletは成功するまで何度もそのInitコンテナを再起動します。しかし、もしそのPodの`restartPolicy`がNeverで、そのPodの起動時にInitコンテナが失敗した場合、KubernetesはそのPod全体を失敗として扱います。 <del> PodにInitコンテナを指定するためには、Podの仕様にそのアプリケーションの`containers`配列と並べて、`initContainers`フィールドを[Container](/docs/reference/generated/kubernetes-api/{{< param \"version\" >}}/#container-v1-core)型のオブジェクトの配列として指定してください。 </del> <ins> PodにInitコンテナを指定するためには、[Podの仕様](/docs/reference/kubernetes-api/workload-resources/pod-v1/#PodSpec)に`initContainers`フィールドを`container`アイテムの配列として追加してください(アプリケーションの`containers`フィールドとそのコンテンツに似ています)。 詳細については、APIリファレンスの[Container](/docs/reference/kubernetes-api/workload-resources/pod-v1/#Container)を参照してください。 </ins> Initコンテナのステータスは、`.status.initContainerStatuses`フィールドにコンテナのステータスの配列として返されます(`.status.containerStatuses`と同様)。 ### 通常のコンテナとの違い {#differences-from-regular-containers}"}
{"_id":"q-en-website-e6dac02ad350281a240f828f546c22404e206042357982153cc7787b1250a60b","text":"This includes any Pods created using `kubectl`, or indirectly via a replication controller. It does not include Pods created as a result of the kubelet `--manifest-url` flag, its `--config` flag, or its REST API (these are <del> not common ways to create Pods.) </del> <ins> not common ways to create Pods). The `spec` of a {{< glossary_tooltip text=\"static Pod\" term_id=\"static-pod\" >}} cannot refer to a Secret or any other API objects. </ins> Secrets must be created before they are consumed in Pods as environment variables unless they are marked as optional. References to secrets that do"}
{"_id":"q-en-website-e73272fc307fa06cd9a5b41ab4d6746d992729921d75341e4d572777f7687c64","text":"{{< tabs name=\"tab-phase\" >}} {{< tab name=\"phase\" include=\"generated/kubeadm_upgrade_node_phase.md\" />}} <ins> {{< tab name=\"preflight\" include=\"generated/kubeadm_upgrade_node_phase_preflight.md\" />}} </ins> {{< tab name=\"control-plane\" include=\"generated/kubeadm_upgrade_node_phase_control-plane.md\" />}} {{< tab name=\"kubelet-config\" include=\"generated/kubeadm_upgrade_node_phase_kubelet-config.md\" />}} {{< /tabs >}}"}
{"_id":"q-en-website-e73e805269fbe3fdb8d19c7bff3173223e3096738dec5373566fcc99d2c1fa37","text":"<ins> --- title: 在 macOS 系统上安装和设置 kubectl content_type: task weight: 10 card: name: tasks weight: 20 title: 在 macOS 系统上安装 kubectl --- <!-- --- reviewers: - mikedanese title: Install and Set Up kubectl on macOS content_type: task weight: 10 card: name: tasks weight: 20 title: Install kubectl on macOS --- --> ## {{% heading \"prerequisites\" %}} <!-- You must use a kubectl version that is within one minor version difference of your cluster. For example, a v1.2 client should work with v1.1, v1.2, and v1.3 master. Using the latest version of kubectl helps avoid unforeseen issues. --> kubectl 版本和集群之间的差异必须在一个小版本号之内。 例如：v1.2 版本的客户端只能与 v1.1、v1.2 和 v1.3 版本的集群一起工作。 用最新版本的 kubectl 有助于避免不可预见的问题。 <!-- ## Install kubectl on macOS --> ## 在 macOS 系统上安装 kubectl {#install-kubectl-on-macos} <!-- The following methods exist for installing kubectl on macOS: --> 在 macOS 系统上安装 kubectl 有如下方法： - [{{% heading \"prerequisites\" %}}](#{{% heading \"prerequisites\" %}}) - [在 macOS 系统上安装 kubectl](#install-kubectl-on-macos) - [用 curl 在 macOS 系统上安装 kubectl](#install-kubectl-binary-with-curl-on-macos) - [用 Homebrew 在 macOS 系统上安装](#install-with-homebrew-on-macos) - [用 Macports 在 macOS 上安装](#install-with-macports-on-macos) - [作为谷歌云 SDK 的一部分，在 macOS 上安装](#install-on-macos-as-part-of-the-google-cloud-sdk) - [验证 kubectl 配置](#verify-kubectl-configuration) - [可选的 kubectl 配置](#optional-kubectl-configurations) - [启用 shell 自动补全功能](#enable-shell-autocompletion) - [{{% heading \"whatsnext\" %}}](#{{% heading \"whatsnext\" %}}) <!-- ### Install kubectl binary with curl on macOS {#install-kubectl-binary-with-curl-on-macos} --> ### 用 curl 在 macOS 系统上安装 kubectl {#install-kubectl-binary-with-curl-on-macos} <!-- 1. Download the latest release: --> 1. 下载最新的发行版： ```bash curl -LO \"https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/darwin/amd64/kubectl\" ``` {{< note >}} <!-- To download a specific version, replace the `$(curl -L -s https://dl.k8s.io/release/stable.txt)` portion of the command with the specific version. For example, to download version {{< param \"fullversion\" >}} on macOS, type: --> 如果需要下载某个指定的版本，用该指定版本号替换掉命令的这个部分：`$(curl -L -s https://dl.k8s.io/release/stable.txt)`。 例如：要在 macOS 系统中下载 {{< param \"fullversion\" >}} 版本，则输入： ```bash curl -LO https://dl.k8s.io/release/{{< param \"fullversion\" >}}/bin/darwin/amd64/kubectl ``` {{< /note >}} <!-- 1. Validate the binary (optional) Download the kubectl checksum file: --> 1. 验证可执行文件（可选操作） 下载 kubectl 的校验和文件： ```bash curl -LO \"https://dl.k8s.io/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/darwin/amd64/kubectl.sha256\" ``` <!-- Validate the kubectl binary against the checksum file: --> 根据校验和文件，验证 kubectl： ```bash echo \"$(<kubectl.sha256)  kubectl\" | shasum -a 256 --check ``` <!-- If valid, the output is: --> 验证通过时，输出如下： ```console kubectl: OK ``` <!-- If the check fails, `shasum` exits with nonzero status and prints output similar to: --> 验证失败时，`shasum` 将以非零值退出，并打印如下输出： ``` kubectl: FAILED shasum: WARNING: 1 computed checksum did NOT match ``` {{< note >}} <!-- Download the same version of the binary and checksum. --> 下载的 kubectl 与校验和文件版本要相同。 {{< /note >}} <!-- 1. Make the kubectl binary executable. --> 1. 将 kubectl 置为可执行文件： ```bash chmod +x ./kubectl ``` <!-- 1. Move the kubectl binary to a file location on your system `PATH`. --> 1. 将可执行文件 kubectl 移动到系统可寻址路径 `PATH` 内的一个位置： ```bash sudo mv ./kubectl /usr/local/bin/kubectl sudo chown root: /usr/local/bin/kubectl ``` <!-- 1. Test to ensure the version you installed is up-to-date: --> 1. 测试一下，确保你安装的是最新的版本： ```bash kubectl version --client ``` <!-- ### Install with Homebrew on macOS {#install-with-homebrew-on-macos} --> ### 用 Homebrew 在 macOS 系统上安装 {#install-with-homebrew-on-macos} <!-- If you are on macOS and using [Homebrew](https://brew.sh/) package manager, you can install kubectl with Homebrew. --> 如果你是 macOS 系统，且用的是 [Homebrew](https://brew.sh/) 包管理工具， 则可以用 Homebrew 安装 kubectl。 <!-- 1. Run the installation command: --> 1. 运行安装命令： ```bash brew install kubectl ``` 或 ```bash brew install kubernetes-cli ``` <!-- 1. Test to ensure the version you installed is up-to-date: --> 1. 测试一下，确保你安装的是最新的版本： ```bash kubectl version --client ``` <!-- ### Install with Macports on macOS {#install-with-macports-on-macos} --> ### 用 Macports 在 macOS 上安装 {#install-with-macports-on-macos} <!-- If you are on macOS and using [Macports](https://macports.org/) package manager, you can install kubectl with Macports. --> 如果你用的是 macOS，且用 [Macports](https://macports.org/) 包管理工具，则你可以用 Macports 安装kubectl。 <!-- 1. Run the installation command: --> 1. 运行安装命令： ```bash sudo port selfupdate sudo port install kubectl ``` <!-- 1. Test to ensure the version you installed is up-to-date: --> 1. 测试一下，确保你安装的是最新的版本： ```bash kubectl version --client ``` <!-- ### Install on macOS as part of the Google Cloud SDK {#install-on-macos-as-part-of-the-google-cloud-sdk} --> ### 作为谷歌云 SDK 的一部分，在 macOS 上安装 {#install-on-macos-as-part-of-the-google-cloud-sdk} {{< include \"included/install-kubectl-gcloud.md\" >}} <!-- ## Verify kubectl configuration {#verify-kubectl-configuration} --> ## 验证 kubectl 配置 {#verify-kubectl-configuration} {{< include \"included/verify-kubectl.md\" >}} <!-- ## Optional kubectl configurations {#optional-kubectl-configurations} ### Enable shell autocompletion {#enable-shell-autocompletion} --> ## 可选的 kubectl 配置 {#optional-kubectl-configurations} ### 启用 shell 自动补全功能 {#enable-shell-autocompletion} <!-- kubectl provides autocompletion support for Bash and Zsh, which can save you a lot of typing. Below are the procedures to set up autocompletion for Bash and Zsh. --> kubectl 为 Bash 和 Zsh 提供自动补全功能，这可以节省许多输入的麻烦。 下面是为 Bash 和 Zsh 设置自动补全功能的操作步骤。 {{< tabs name=\"kubectl_autocompletion\" >}} {{< tab name=\"Bash\" include=\"included/optional-kubectl-configs-bash-mac.md\" />}} {{< tab name=\"Zsh\" include=\"included/optional-kubectl-configs-zsh.md\" />}} {{< /tabs >}} ## {{% heading \"whatsnext\" %}} {{< include \"included/kubectl-whats-next.md\" >}} </ins>  No newline at end of file"}
{"_id":"q-en-website-e80171b7dd4877f030999c2954a1adfe84cb2b592e80747ff657cd418e2bedfb","text":"{{< tab name=\"certificate-key\" include=\"generated/kubeadm_alpha_certs_certificate-key.md\" />}} {{< /tabs >}} <ins> ## kubeadm alpha certs generate-csr {#cmd-certs-generate-csr} This command can be used to generate certificate signing requests (CSRs) which can be submitted to a certificate authority (CA) for signing. {{< tabs name=\"tab-certs-generate-csr\" >}} {{< tab name=\"certificate-generate-csr\" include=\"generated/kubeadm_alpha_certs_generate-csr.md\" />}} {{< /tabs >}} </ins> ## kubeadm alpha certs check-expiration {#cmd-certs-check-expiration} This command checks expiration for the certificates in the local PKI managed by kubeadm."}
{"_id":"q-en-website-e86529edbedf1ebb55f3d56fa2f98d077891b68aae68f8808c102331a7856b85","text":"You can ignore this warning. You are only checking the version of `kubectl` that you have installed. {{< /note >}} Or use this for detailed view of version: ```cmd <del> kubectl version --client --output=yaml </del> <ins> kubectl version --client --output=yaml </ins> ``` ### Install using native package management"}
{"_id":"q-en-website-e8b99b0bb1cd006a998aaaff50deaf86a3e99f636a8dd4839064d03667074d0f","text":"</td> </tr> <tr><td><code>kind</code> <B>[Required]</B><br/> <del> <a href=\"https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#groupversionkind-v1-meta\"><code>meta/v1.GroupVersionKind</code></a> </del> <ins> <a href=\"https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#GroupVersionKind\"><code>meta/v1.GroupVersionKind</code></a> </ins> </td> <td> <p>Kind is the fully-qualified type of object being submitted (for example, v1.Pod or autoscaling.v1.Scale)</p> </td> </tr> <tr><td><code>resource</code> <B>[Required]</B><br/> <del> <a href=\"https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#groupversionresource-v1-meta\"><code>meta/v1.GroupVersionResource</code></a> </del> <ins> <a href=\"https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#GroupVersionResource\"><code>meta/v1.GroupVersionResource</code></a> </ins> </td> <td> <p>Resource is the fully-qualified resource being requested (for example, v1.pods)</p>"}
{"_id":"q-en-website-eac9acf0bb6adc59e4ee46def3bc633ad072800a2ac77e7778587da88740d31d","text":"- [Kubernetes Python client library](https://github.com/kubernetes-client/python) - [Kubernetes Java client library](https://github.com/kubernetes-client/java) - [Kubernetes JavaScript client library](https://github.com/kubernetes-client/javascript) <ins> - [Kubernetes C# client library](https://github.com/kubernetes-client/csharp) - [Kubernetes Haskell client library](https://github.com/kubernetes-client/haskell) </ins> ## CLIリファレンス * [kubectl](/ja/docs/reference/kubectl/) - コマンドの実行やKubernetesクラスターの管理に使う主要なCLIツールです。 <del> * [JSONPath](/ja/docs/reference/kubectl/jsonpath/) - kubectlで[JSONPath記法](https://goessner.net/articles/JsonPath/)を使うための構文ガイドです。 </del> <ins> * [JSONPath](/ja/docs/reference/kubectl/jsonpath/) - kubectlで[JSONPath記法](https://goessner.net/articles/JsonPath/)を使うための構文ガイドです。 </ins> * [kubeadm](/ja/docs/reference/setup-tools/kubeadm/) - セキュアなKubernetesクラスターを簡単にプロビジョニングするためのCLIツールです。 ## コンポーネントリファレンス"}
{"_id":"q-en-website-eb2d9445700c019e7c3e6e4ff83826704d8197805549ba76a77a891a98aea42e","text":"Hit enter for command prompt <del> / # wget -s --timeout=1 nginx </del> <ins> / # wget --spider --timeout=1 nginx </ins> Connecting to nginx (10.100.0.16:80) / # ```"}
{"_id":"q-en-website-eca039bd91573a12c7bb81716e01bc80ef70d5bf6379ae391965593bf2702c16","text":"`zk-2` is scheduled. ```shell <del> kubectl drain $(kubectl get pod zk-2 --template {{.spec.nodeName}}) --ignore-daemonsets --force --delete-local-data </del> <ins> kubectl drain $(kubectl get pod zk-2 --template {{.spec.nodeName}}) --ignore-daemonsets --force --delete-emptydir-data </ins> ``` ```"}
{"_id":"q-en-website-ecd049a7ce6967e8fda42749512b3935fb023658cc25c074d8084081860ed509","text":"* Learn more about [container lifecycle hooks](/docs/concepts/containers/container-lifecycle-hooks/). <ins> * Learn more about [sidecar containers](/docs/concepts/workloads/pods/sidecar-containers/). </ins> * For detailed information about Pod and container status in the API, see the API reference documentation covering [`status`](/docs/reference/kubernetes-api/workload-resources/pod-v1/#PodStatus) for Pod."}
{"_id":"q-en-website-ed1e0583d724fb3b8b2126be195e024d4373fa8352bd3f8f8bb7c96ce71a5a2f","text":"} } <ins> /* Announcements */ </ins> #announcement { > * { color: inherit;"}
{"_id":"q-en-website-ed7d724902c5d6f6320e63df9e0ec0fe9498f004583c3f7b8fd8f8985a537f9c","text":"This means that the Pods running on a node are visible on the API server, but cannot be controlled from there. <ins> {{< note >}} The `spec` of a static Pod cannot refer to other API objects (e.g., {{< glossary_tooltip text=\"ServiceAccount\" term_id=\"service-account\" >}}, {{< glossary_tooltip text=\"ConfigMap\" term_id=\"configmap\" >}}, {{< glossary_tooltip text=\"Secret\" term_id=\"secret\" >}}, etc). {{< /note >}} </ins> ## Container probes A _probe_ is a diagnostic performed periodically by the kubelet on a container. To perform a diagnostic, the kubelet can invoke different actions:"}
{"_id":"q-en-website-ed846a3e3090d4210c42a4ebc81f5c8ea4ea5cdd10ca00672bf9a055d08ea33f","text":"resource requests and limits for an init container are handled differently, as documented in [Resource sharing within containers](#resource-sharing-within-containers). <del> Also, init containers do not support `lifecycle`, `livenessProbe`, `readinessProbe`, or `startupProbe` because they must run to completion before the Pod can be ready. </del> <ins> Regular init containers (in other words: excluding sidecar containers) do not support the `lifecycle`, `livenessProbe`, `readinessProbe`, or `startupProbe` fields. Init containers must run to completion before the Pod can be ready; sidecar containers continue running during a Pod's lifetime, and _do_ support some probes. See [sidecar container](/docs/concepts/workloads/pods/sidecar-containers/) for further details about sidecar containers. </ins> If you specify multiple init containers for a Pod, kubelet runs each init container sequentially. Each init container must succeed before the next can run. When all of the init containers have run to completion, kubelet initializes the application containers for the Pod and runs them as usual. <ins> ### Differences from sidecar containers Init containers run and complete their tasks before the main application container starts. Unlike [sidecar containers](/docs/concepts/workloads/pods/sidecar-containers), init containers are not continuously running alongside the main containers. Init containers run to completion sequentially, and the main container does not start until all the init containers have successfully completed. init containers do not support `lifecycle`, `livenessProbe`, `readinessProbe`, or `startupProbe` whereas sidecar containers support all these [probes](/docs/concepts/workloads/pods/pod-lifecycle/#types-of-probe) to control their lifecycle. Init containers share the same resources (CPU, memory, network) with the main application containers but do not interact directly with them. They can, however, use shared volumes for data exchange. </ins> ## Using init containers Because init containers have separate images from app containers, they"}
{"_id":"q-en-website-ee1b71ca20895a741c06e44a5893e25040cd3abd58b608ebdebc40700349cebe","text":"design that links a {{< glossary_tooltip term_id=\"controller\" >}} to one or more custom resources. --> <del> [operator 模式](/zh-cn/docs/concepts/extend-kubernetes/operator/) 是一种系统设计, </del> <ins> [operator 模式](/zh-cn/docs/concepts/extend-kubernetes/operator/) 是一种系统设计， </ins> 将 {{< glossary_tooltip term_id=\"controller\" >}} 关联到一个或多个自定义资源。 <!--more-->"}
{"_id":"q-en-website-ee345e645b488ce42cb2421c43e0b46c7cf8c40869485cbd61f92af8470b992d","text":"instead. {{< /note >}} <ins> {{< note >}} The `spec` of a static Pod cannot refer to other API objects (e.g., {{< glossary_tooltip text=\"ServiceAccount\" term_id=\"service-account\" >}}, {{< glossary_tooltip text=\"ConfigMap\" term_id=\"configmap\" >}}, {{< glossary_tooltip text=\"Secret\" term_id=\"secret\" >}}, etc). {{< /note >}} </ins> ## {{% heading \"prerequisites\" %}} {{< include \"task-tutorial-prereqs.md\" >}} {{< version-check >}}"}
{"_id":"q-en-website-eef431dc44893601074a130bae818d6b3b547d43b1382ed0ed3eece1a71b7a5d","text":"## {{% heading \"whatsnext\" %}} <ins> * Tutorial to _[deploy your first app on Kubernetes with kubectl](/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro/)_. </ins> * Learn more about [Deployment objects](/docs/concepts/workloads/controllers/deployment/). * Learn more about [Deploying applications](/docs/tasks/run-application/run-stateless-application-deployment/). * Learn more about [Service objects](/docs/concepts/services-networking/service/)."}
{"_id":"q-en-website-ef34f8d0c9f01c181cdab1cf89113f9b7885e05ba9965059ecf0ebb9f28c1090","text":"</td> </tr> <tr><td><code>requestResource</code><br/> <del> <a href=\"https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#groupversionresource-v1-meta\"><code>meta/v1.GroupVersionResource</code></a> </del> <ins> <a href=\"https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#GroupVersionResource\"><code>meta/v1.GroupVersionResource</code></a> </ins> </td> <td> <p>RequestResource is the fully-qualified resource of the original API request (for example, v1.pods)."}
{"_id":"q-en-website-f015e71ef2b83cd8127e83e3f61f25a77424abecb5cb5f7f12323659565b9235","text":"<ins> --- title: \"后续内容\" description: \"安装 kubectl 之后，还可以做些什么？\" headless: true --- <!-- --- title: \"What's next?\" description: \"What's next after installing kubectl.\" headless: true --- --> <!-- * [Install Minikube](https://minikube.sigs.k8s.io/docs/start/) * See the [getting started guides](/docs/setup/) for more about creating clusters. * [Learn how to launch and expose your application.](/docs/tasks/access-application-cluster/service-access-application-cluster/) * If you need access to a cluster you didn't create, see the [Sharing Cluster Access document](/docs/tasks/access-application-cluster/configure-access-multiple-clusters/). * Read the [kubectl reference docs](/docs/reference/kubectl/kubectl/) --> * [安装 Minikube](https://minikube.sigs.k8s.io/docs/start/) * 有关创建集群的更多信息，请参阅[入门指南](/zh/docs/setup/). * [学习如何启动并对外公开你的应用程序。](/zh/docs/tasks/access-application-cluster/service-access-application-cluster/) * 如果你需要访问其他人创建的集群，请参阅 [共享集群接入文档](/zh/docs/tasks/access-application-cluster/configure-access-multiple-clusters/). * 阅读 [kubectl 参考文档](/zh/docs/reference/kubectl/kubectl/) </ins>"}
{"_id":"q-en-website-f0ff03edf2c4629a58a42a68aea16fbd61910df8c05906e70a74a74284d04c2b","text":"| | 빈 문자열 (기본값)은 이전 버전과의 호환성을 위한 것으로, hostPath 볼륨은 마운트 하기 전에 아무런 검사도 수행되지 않는다. | | `DirectoryOrCreate` | 만약 주어진 경로에 아무것도 없다면, 필요에 따라 Kubelet이 가지고 있는 동일한 그룹과 소유권, 권한을 0755로 설정한 빈 디렉터리를 생성한다. | | `Directory` | 주어진 경로에 디렉터리가 있어야 함 | <del> | `FileOrCreate` | 만약 주어진 경로에 아무것도 없다면, 필요에 따라 Kubelet이 가지고 있는 동일한 그룹과 소유권, 권한을 0644로 설정한 빈 디렉터리를 생성한다. | </del> <ins> | `FileOrCreate` | 만약 주어진 경로에 아무것도 없다면, 필요에 따라 Kubelet이 가지고 있는 동일한 그룹과 소유권, 권한을 0644로 설정한 빈 파일을 생성한다. | </ins> | `File` | 주어진 경로에 파일이 있어야 함 | | `Socket` | 주어진 경로에 UNIX 소캣이 있어야 함 | | `CharDevice` | 주어진 경로에 문자 디바이스가 있어야 함 |"}
{"_id":"q-en-website-f13d982f83614bd85070e08af8512f1bf6f9ca95ea76212f42a22ed9226a6754","text":"<ins> --- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: default-deny-all spec: podSelector: {} policyTypes: - Ingress - Egress </ins>"}
{"_id":"q-en-website-f2ee9a2f487005320477466a349929ff3d91951ffd8eea0b1a4387dc4719278c","text":"--- <del> title: v1.19 릴리스 노트 </del> <ins> title: v1.20 릴리스 노트 </ins> weight: 10 card: name: release-notes"}
{"_id":"q-en-website-f3bf20362b2d64f007b254039a316e2b090f4726ed9798ae3320d92eddb83157","text":"and direct the network traffic to the cluster nodes: 1. Make sure that <del> the `ServiceAccountTokenVolumeProjection` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled. You can enable [service account token volume protection](/docs/tasks/configure-pod-container/configure-service-account/#service-account-token-volume-projection) by providing the following flags to the kube-apiserver: ``` --service-account-issuer=api --service-account-signing-key-file=/etc/kubernetes/pki/sa.key --api-audiences=system:konnectivity-server ``` </del> <ins> [Service Account Token Volume Projection](/docs/tasks/configure-pod-container/configure-service-account/#service-account-token-volume-projection) feature enabled in your cluster. It is enabled by default since Kubernetes v1.20. </ins> 1. Create an egress configuration file such as `admin/konnectivity/egress-selector-configuration.yaml`. 1. Set the `--egress-selector-config-file` flag of the API Server to the path of your API Server egress configuration file."}
{"_id":"q-en-website-f3d7f03a2553b176b0356bc3309ab2c6e2b0ddd1ec90ff1419e384c7bbbef24f","text":"drain the node on which the `zk-0` Pod is scheduled. ```shell <del> kubectl drain $(kubectl get pod zk-0 --template {{.spec.nodeName}}) --ignore-daemonsets --force --delete-local-data </del> <ins> kubectl drain $(kubectl get pod zk-0 --template {{.spec.nodeName}}) --ignore-daemonsets --force --delete-emptydir-data </ins> ``` ```"}
{"_id":"q-en-website-f3fcc788a864dcf5912113d25cc3524d6039e9be92412f4bb9aa50d374528f3f","text":"The output of a successful command is: <del> deployment.apps/dns-autoscaler created </del> <ins> deployment.apps/kube-dns-autoscaler created </ins> DNS horizontal autoscaling is now enabled. ## Tune DNS autoscaling parameters {#tuning-autoscaling-parameters} <del> Verify that the dns-autoscaler {{< glossary_tooltip text=\"ConfigMap\" term_id=\"configmap\" >}} exists: </del> <ins> Verify that the kube-dns-autoscaler {{< glossary_tooltip text=\"ConfigMap\" term_id=\"configmap\" >}} exists: </ins> ```shell kubectl get configmap --namespace=kube-system"}
{"_id":"q-en-website-f4a9ba784f092f1f4ebd904f4cd9c32b284f5496e4eb7298b67cdd2dee44a48a","text":"SystemdCgroup = true ``` <ins> If you apply this change make sure to restart containerd again: ```shell sudo systemctl restart containerd ``` </ins> When using kubeadm, manually configure the [cgroup driver for kubelet](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#configure-cgroup-driver-used-by-kubelet-on-control-plane-node)."}
{"_id":"q-en-website-f58b916b792edcc3e8334c28f7b35cbcc3bbc22434f5d976a2ac90cd94ba3d80","text":"<ins> --- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: allow-all-egress spec: podSelector: {} egress: - {} policyTypes: - Egress </ins>"}
{"_id":"q-en-website-f67c319e20d5cba7575d9c4dfd55bc6864623b08898509d5158c9803ee5655e7","text":"The [Pod Lifecycle](/docs/concepts/workloads/pods/pod-lifecycle/) is defined by the states or phases of a Pod. There are five possible Pod phases: Pending, Running, Succeeded, Failed, and Unknown. A high-level description of the Pod state is summarized in the [PodStatus](/docs/reference/generated/kubernetes-api/{{< param \"version\" >}}/#podstatus-v1-core) `phase` field. --> [Pod 生命周期](/zh-cn/docs/concepts/workloads/pods/pod-lifecycle/) 是关于 Pod <del> 处于哪个阶段的概述。包含了下面 5 种可能的阶段: Running、Pending、Succeeded、 </del> <ins> 处于哪个阶段的概述。包含了下面 5 种可能的阶段：Running、Pending、Succeeded、 </ins> Failed、Unknown。关于 Pod 的阶段的更高级描述请查阅 [PodStatus](/docs/reference/generated/kubernetes-api/{{< param \"version\" >}}/#podstatus-v1-core) `phase` 字段。"}
{"_id":"q-en-website-f73b52d591ebf4f3f5ec9fa0db4245e6a18ba5a9f79f6ba58f060aecb8bd414a","text":"1. Download the latest release with the command: <del> ```bash </del> <ins> {{< tabs name=\"download_binary_linux\" >}} {{< tab name=\"x86-64\" codelang=\"bash\" >}} </ins> curl -LO \"https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl\" <del> ``` </del> <ins> {{< /tab >}} {{< tab name=\"ARM64\" codelang=\"bash\" >}} curl -LO \"https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/arm64/kubectl\" {{< /tab >}} {{< /tabs >}} </ins> {{< note >}} To download a specific version, replace the `$(curl -L -s https://dl.k8s.io/release/stable.txt)` portion of the command with the specific version. <del> For example, to download version {{< param \"fullversion\" >}} on Linux, type: </del> <ins> For example, to download version {{< param \"fullversion\" >}} on Linux x86-64, type: </ins> ```bash curl -LO https://dl.k8s.io/release/{{< param \"fullversion\" >}}/bin/linux/amd64/kubectl ``` <ins> And for Linux ARM64, type: ```bash curl -LO https://dl.k8s.io/release/{{< param \"fullversion\" >}}/bin/linux/arm64/kubectl ``` </ins> {{< /note >}} 1. Validate the binary (optional) Download the kubectl checksum file: <del> ```bash </del> <ins> {{< tabs name=\"download_checksum_linux\" >}} {{< tab name=\"x86-64\" codelang=\"bash\" >}} </ins> curl -LO \"https://dl.k8s.io/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl.sha256\" <del> ``` </del> <ins> {{< /tab >}} {{< tab name=\"ARM64\" codelang=\"bash\" >}} curl -LO \"https://dl.k8s.io/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/arm64/kubectl.sha256\" {{< /tab >}} {{< /tabs >}} </ins> Validate the kubectl binary against the checksum file:"}
{"_id":"q-en-website-f764da5db8f4afdfff74a890715143602a617a37988a261f90c065781dae645d","text":"[authorization plugin and policy](/docs/reference/access-authn-authz/authorization/#authorization-modules) in use. <ins> The API credentials are automatically revoked when the Pod is deleted, even if finalizers are in place. In particular, the API credentials are revoked 60 seconds beyond the `.metadata.deletionTimestamp` set on the Pod (the deletion timestamp is typically the time that the **delete** request was accepted plus the Pod's termination grace period). </ins> ### Opt out of API credential automounting If you don't want the {{< glossary_tooltip text=\"kubelet\" term_id=\"kubelet\" >}}"}
{"_id":"q-en-website-f99349e8d722aec2f8088bbee985190b75a389424e50b15ab32a72ef7a8eb868","text":"<ins> --- title: Cluster id: cluster date: 2020-08-03 full_link: short_description: > Um conjunto de servidores de processamento, também chamados de nós, que executam aplicações containerizadas. Todo cluster possui ao menos um servidor de processamento (worker node). aka: tags: - fundamental - operation --- Um conjunto de servidores de processamento, chamados {{< glossary_tooltip text=\"nós\" term_id=\"node\" >}}, que executam aplicações containerizadas. Todo cluster possui ao menos um servidor de processamento (_worker node_). <!--more--> O servidor de processamento hospeda os {{< glossary_tooltip text=\"Pods\" term_id=\"pod\" >}} que são componentes de uma aplicação. O {{< glossary_tooltip text=\"ambiente de gerenciamento\" term_id=\"control-plane\" >}} gerencia os nós de processamento e os Pods no cluster. Em ambientes de produção, o ambiente de gerenciamento geralmente executa em múltiplos computadores e um cluster geralmente executa em múltiplos nós (_nodes_) , provendo tolerância a falhas e alta disponibilidade. </ins>"}
{"_id":"q-en-website-fa121206570f4f1675e0f568182e22d330a19e22b32664774b58a859061f887f","text":"* Cloning support is only available for dynamic provisioners. * CSI drivers may or may not have implemented the volume cloning functionality. * You can only clone a PVC when it exists in the same namespace as the destination PVC (source and destination must be in the same namespace). <del> * Cloning is only supported within the same Storage Class. - Destination volume must be the same storage class as the source - Default storage class can be used and storageClassName omitted in the spec </del> <ins> * Cloning is supported with a different Storage Class. - Destination volume can be the same or a different storage class as the source. - Default storage class can be used and storageClassName omitted in the spec. </ins> * Cloning can only be performed between two volumes that use the same VolumeMode setting (if you request a block mode volume, the source MUST also be block mode)"}
{"_id":"q-en-website-fa6e1d1cd769f110a35dbde465a15e04d0b7d1550fcda33163eeb3d288b10053","text":"</td> </tr> <tr><td><code>requestKind</code><br/> <del> <a href=\"https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.27/#groupversionkind-v1-meta\"><code>meta/v1.GroupVersionKind</code></a> </del> <ins> <a href=\"https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#GroupVersionKind\"><code>meta/v1.GroupVersionKind</code></a> </ins> </td> <td> <p>RequestKind is the fully-qualified type of the original API request (for example, v1.Pod or autoscaling.v1.Scale)."}
{"_id":"q-en-website-fb7f4a1c21c3e903807dc4b462c1bfe31d35efc3a1fce2ee856d8cbb63877d29","text":"Finally if everything goes well, remove Docker. <del> {{< tabs name=\"tab-remove-docker-enigine\" >}} </del> <ins> {{< tabs name=\"tab-remove-docker-engine\" >}} </ins> {{% tab name=\"CentOS\" %}} ```shell"}
{"_id":"q-en-website-fd1f3ac5aea6e6552639e8366544353f4e3292c04cefbad9b761a606993685c6","text":"metadata: name: myapp-pod labels: <del> app: myapp </del> <ins> app.kubernetes.io/name: MyApp </ins> spec: containers: - name: myapp-container"}
{"_id":"q-en-website-fd7f98d7e56cc59eab5706ee51df201f4c07f686192b85a6d17e3fb22e07fa1b","text":"- [コンテナの環境変数](#using-secrets-as-environment-variables)として利用する - Podを生成するために[kubeletがイメージをpullする](#using-imagepullsecrets)ときに使用する <ins> KubernetesのコントロールプレーンでもSecretsは使われています。例えば、[bootstrap token Secrets](#bootstrap-token-secrets)は、ノード登録を自動化するための仕組みです。 </ins> Secretオブジェクトの名称は正当な[DNSサブドメイン名](/ja/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names)である必要があります。 シークレットの構成ファイルを作成するときに、`data`および/または`stringData`フィールドを指定できます。`data`フィールドと`stringData`フィールドはオプションです。"}
{"_id":"q-en-website-fe905f92e324d0ba3a57caa4bd954979285448f6dea9b05058aa90cd415abaff","text":"service.beta.kubernetes.io/aws-load-balancer-security-groups: \"sg-53fae93f\" # A list of existing security groups to be configured on the ELB created. Unlike the annotation <del> # service.beta.kubernetes.io/aws-load-balancer-extra-security-groups, this replaces all other security groups previously assigned to the ELB and also overrides the creation </del> <ins> # service.beta.kubernetes.io/aws-load-balancer-extra-security-groups, this replaces all other security groups previously assigned to the ELB and also overrides the creation </ins> # of a uniquely generated security group for this ELB. # The first security group ID on this list is used as a source to permit incoming traffic to target worker nodes (service traffic and health checks). # If multiple ELBs are configured with the same security group ID, only a single permit line will be added to the worker node security groups, that means if you delete any"}
{"_id":"q-en-website-feb1b56d73eb351ca2c0e9187e1de25f88dfe0a0838a071c3a942c2f86ef5ee6","text":"(backward-compatible) changes to the way the Kubernetes cluster DNS server processes DNS queries, to facilitate the lookup of federated services (which span multiple Kubernetes clusters). <del> See the [Cluster Federation Administrators' Guide](/docs/admin/federation/index.md) for more </del> <ins> See the [Cluster Federation Administrators' Guide](/docs/admin/federation) for more </ins> details on Cluster Federation and multi-site support. ## References"}
{"_id":"q-en-website-fec0bad5e20da31a281e7213c9c250125b7907c077a88ab0f94e9c23937330ea","text":"<ins> --- title: スケジューラーの設定 content_type: concept weight: 20 --- {{< feature-state for_k8s_version=\"v1.19\" state=\"beta\" >}} 設定ファイルを作成し、そのパスをコマンドライン引数として渡すことで`kube-scheduler`の振る舞いをカスタマイズすることができます。 <!-- overview --> <!-- body --> スケジューリングプロファイルは、{{< glossary_tooltip text=\"kube-scheduler\" term_id=\"kube-scheduler\" >}}でスケジューリングの 異なるステージを設定することができます。 各ステージは、拡張点に公開されています。プラグインをそれらの拡張点に1つ以上実装することで、スケジューリングの振る舞いを変更できます。 KubeSchedulerConfiguration([`v1beta2`](/docs/reference/config-api/kube-scheduler-config.v1beta2/)か[`v1beta3`](/docs/reference/config-api/kube-scheduler-config.v1beta3/))構造体を使用して、`kube-scheduler --config <filename>`を実行することで、スケジューリングプロファイルを指定することができます。 最小限の設定は次の通りです。 ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta2 kind: KubeSchedulerConfiguration clientConnection: kubeconfig: /etc/srv/kubernetes/kube-scheduler/kubeconfig ``` ## プロファイル スケジューリングプロファイルは、{{< glossary_tooltip text=\"kube-scheduler\" term_id=\"kube-scheduler\" >}}でスケジューリングの 異なるステージを設定することができます。 各ステージは[拡張点](#extension-points)に公開されています。 [プラグイン](#scheduling-plugins)をそれらの拡張点に1つ以上実装することで、スケジューリングの振る舞いを変更できます。 単一の`kube-scheduler`インスタンスで[複数のプロファイル](#multiple-profiles)を実行するように設定することも可能です。 ### 拡張点 {#extension-points} スケジューリングは一連のステージで行われ、以下の拡張点に公開されています。 1. `queueSort`: これらのプラグインは、スケジューリングキューにある`pending`状態のPodを ソートするための順序付け関数を提供します。同時に有効化できるプラグインは1つだけです。 1. `preFilter`: これらのプラグインは、フィルタリングをする前にPodやクラスターの情報のチェックや 前処理のために使用されます。これらのプラグインは、設定された順序で呼び出されます。 1. `filter`: これらのプラグインは、スケジューリングポリシーにおけるPredicatesに相当するもので、 Podの実行不可能なNodeをフィルターするために使用されます。 もし全てのNodeがフィルターされてしまった場合、Podはunschedulableとしてマークされます。 1. `postFilter`:これらのプラグインは、Podの実行可能なNodeが見つからなかった場合、 設定された順序で呼び出されます。もし`postFilter`プラグインのいずれかが、Podを __スケジュール可能__ とマークした場合、残りの`postFilter`プラグインは呼び出されません。 1. `preScore`: これは、スコアリング前の作業を行う際に使用できる情報提供のための拡張点です。 1. `score`: これらのプラグインはフィルタリングフェーズを通過してきたそれぞれのNodeに対して スコア付けを行います。その後スケジューラーは、最も高い重み付きスコアの合計を持つノードを選択します。 1. `reserve`: これは、指定されたPodのためにリソースが予約された際に、プラグインに通知する、 情報提供のための拡張点です。また、プラグインは`Reserve`中に失敗した際、または`Reserve`の後に 呼び出される`Unreserve`も実装しています。 1. `permit`: これらのプラグインではPodのバインディングを拒む、または遅延させることができます。 1. `preBind`: これらのプラグインは、Podがバインドされる前に必要な処理を実行できます。 1. `bind`: これらのプラグインはPodをNodeにバインドします。`bind`プラグインは順番に呼び出され、 1つのプラグインがバインドを完了すると、残りのプラグインはスキップされます。`bind`プラグインは 少なくとも1つは必要です。 1. `postBind`: これは、Podがバインドされた後に呼び出される情報提供のための拡張点です。 1. `multiPoint`: このフィールドは設定のみ可能で、プラグインが適用されるすべての拡張点に対して 同時に有効化または無効化することができます。 次の例のように、それぞれの拡張点に対して、特定の[デフォルトプラグイン](#scheduling-plugins)を無効化、または自作のプラグインを有効化することができます。 ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta2 kind: KubeSchedulerConfiguration profiles: - plugins: score: disabled: - name: PodTopologySpread enabled: - name: MyCustomPluginA weight: 2 - name: MyCustomPluginB weight: 1 ``` `disabled`配列の`name`フィールドに`*`を使用することで、その拡張点の全てのデフォルトプラグインを無効化できます。また、必要に応じてプラグインの順序を入れ替える場合にも使用されます。 ### Scheduling plugins {#scheduling-plugins} 以下のプラグインはデフォルトで有効化されており、1つ以上の拡張点に実装されています。 - `ImageLocality`:Podが実行するコンテナイメージを既に持っているNodeを優先します。 拡張点:`score` - `TaintToleration`:[TaintsとTolerations](/ja/docs/concepts/scheduling-eviction/taint-and-toleration/)を実行します。 実装する拡張点:`filter`、`preScore`、`score` - `NodeName`: PodのSpecのNode名が、現在のNodeと一致するかをチェックします。 拡張点:`filter` - `NodePorts`:要求されたPodのポートに対して、Nodeが空きポートを持っているかチェックします。 拡張点:`preFilter`、`filter` - `NodeAffinity`:[nodeselectors](/ja/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector) と[Nodeアフィニティ](/ja/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity) を実行します。 拡張点:`filter`、`score` - `PodTopologySpread`:[Podトポロジーの分散制約](/docs/concepts/workloads/pods/pod-topology-spread-constraints/)を実行します。 拡張点:`preFilter`、`filter`、`preScore`、`score` - `NodeUnschedulable`:`.spec.unschedulable`がtrueに設定されているNodeをフィルタリングします。 拡張点:`filter`. - `NodeResourcesFit`:Podが要求しているすべてのリソースがNodeにあるかをチェックします。 スコアは3つのストラテジのうちの1つを使用します:`LeastAllocated`(デフォルト)、`MostAllocated`、 と`RequestedToCapacityRatio` 拡張点:`preFilter`、`filter`、`score` - `NodeResourcesBalancedAllocation`:Podがスケジュールされた場合に、よりバランスの取れた リソース使用量となるNodeを優先します。 拡張点:`score` - `VolumeBinding`:Nodeが、要求された{{< glossary_tooltip text=\"ボリューム\" term_id=\"volume\" >}} を持っている、もしくはバインドしているかチェックします。 拡張点:`preFilter`、`filter`、`reserve`、`preBind`、`score` {{< note >}} `score`拡張点は、`VolumeCapacityPriority`機能が有効になっている時に有効化されます。 要求されたボリュームに適合する最小のPVを優先的に使用します。 {{< /note >}} - `VolumeRestrictions`:Nodeにマウントされたボリュームが、ボリュームプロバイダ固有の制限を満たしているかを確認します。 拡張点:`filter` - `VolumeZone`:要求されたボリュームがゾーン要件を満たしているかどうかを確認します。 拡張点:`filter` - `NodeVolumeLimits`:NodeのCSIボリューム制限を満たすかどうかをチェックします。 拡張点:`filter` - `EBSLimits`:NodeのAWSのEBSボリューム制限を満たすかどうかをチェックします。 拡張点:`filter` - `GCEPDLimits`:NodeのGCP-PDボリューム制限を満たすかどうかをチェックします。 拡張点:`filter` - `AzureDiskLimits`:NodeのAzureディスクボリューム制限を満たすかどうかをチェックします。 拡張点:`filter` - `InterPodAffinity`:[Pod間のaffinityとanti-affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity) を実行します。 拡張点:`preFilter`、`filter`、`preScore`、`score` - `PrioritySort`:デフォルトの優先順位に基づくソートを提供します。 拡張点:`queueSort`. - `DefaultBinder`:デフォルトのバインディングメカニズムを提供します。 拡張点:`bind` - `DefaultPreemption`:デフォルトのプリエンプションメカニズムを提供します。 拡張点:`postFilter` また、コンポーネント設定のAPIにより、以下のプラグインを有効にすることができます。 デフォルトでは有効になっていません。 - `SelectorSpread`:{{< glossary_tooltip text=\"サービス\" term_id=\"service\" >}}と {{< glossary_tooltip text=\"レプリカセット\" term_id=\"replica-set\" >}}、 {{< glossary_tooltip text=\"ステートフルセット\" term_id=\"statefulset\" >}}、 に属するPodのNode間の拡散を優先します。 拡張点:`preScore`、`score` - `CinderLimits`:Nodeが[`OpenStack Cinder`](https://docs.openstack.org/cinder/) ボリューム制限を満たせるかチェックします。 拡張点:`filter` ### 複数のプロファイル {#multiple-profiles} `kube-scheduler`は複数のプロファイルを実行するように設定することができます。 各プロファイルは関連するスケジューラー名を持ち、その[拡張点](#extension-points)に異なるプラグインを 設定することが可能です。 以下のサンプル設定では、スケジューラーは2つのプロファイルで実行されます。1つはデフォルトプラグインで、 もう1つはすべてのスコアリングプラグインを無効にしたものです。 ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta2 kind: KubeSchedulerConfiguration profiles: - schedulerName: default-scheduler - schedulerName: no-scoring-scheduler plugins: preScore: disabled: - name: '*' score: disabled: - name: '*' ``` 特定のプロファイルに従ってスケジュールさせたいPodは、その`.spec.schedulerName`に、対応するスケジューラー名を含めることができます。 デフォルトでは、スケジューラー名`default-scheduler`としてプロファイルが生成されます。 このプロファイルは、上記のデフォルトプラグインを含みます。複数のプロファイルを宣言する場合は、 それぞれユニークなスケジューラー名にする必要があります。 もしPodがスケジューラー名を指定しない場合、kube-apiserverは`default-scheduler`を設定します。 従って、これらのPodをスケジュールするために、このスケジューラー名を持つプロファイルが存在する必要があります。 {{< note >}} Podのスケジューリングイベントには、ReportingControllerとして`.spec.schedulerName`が設定されています。 リーダー選出のイベントには、リスト先頭のプロファイルのスケジューラー名が使用されます。 {{< /note >}} {{< note >}} すべてのプロファイルは、`queueSort`拡張点で同じプラグインを使用し、同じ設定パラメーターを持つ必要があります (該当する場合)。これは、pending状態のPodキューがスケジューラーに1つしかないためです。 {{< /note >}} ### 複数の拡張点に適用されるプラグイン {#multipoint} `kubescheduler.config.k8s.io/v1beta3`からは、プロファイル設定に`multiPoint`というフィールドが追加され、複数の拡張点でプラグインを簡単に有効・無効化できるようになりました。 `multiPoint`設定の目的は、カスタムプロファイルを使用する際に、ユーザーや管理者が必要とする設定を簡素化することです。 `MyPlugin`というプラグインがあり、`preScore`、`score`、`preFilter`、`filter`拡張点を実装しているとします。 すべての利用可能な拡張点で`MyPlugin`を有効化するためには、プロファイル設定は次のようにします。 ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta3 kind: KubeSchedulerConfiguration profiles: - schedulerName: multipoint-scheduler plugins: multiPoint: enabled: - name: MyPlugin ``` これは以下のように、`MyPlugin`を手動ですべての拡張ポイントに対して有効にすることと同じです。 ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta3 kind: KubeSchedulerConfiguration profiles: - schedulerName: non-multipoint-scheduler plugins: preScore: enabled: - name: MyPlugin score: enabled: - name: MyPlugin preFilter: enabled: - name: MyPlugin filter: enabled: - name: MyPlugin ``` `multiPoint`を使用する利点の一つは、将来的に`MyPlugin`が別の拡張点を実装した場合に、 `multiPoint`設定が自動的に新しい拡張点に対しても有効化されることです。 特定の拡張点は、その拡張点の`disabled`フィールドを使用して、`MultiPoint`の展開から除外することができます。 これは、デフォルトのプラグインを無効にしたり、デフォルト以外のプラグインを無効にしたり、 ワイルドカード(`'*'`)を使ってすべてのプラグインを無効にしたりする場合に有効です。 この例として、`Score`と`PreScore`を無効にするためには、次のようにします。 ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta3 kind: KubeSchedulerConfiguration profiles: - schedulerName: non-multipoint-scheduler plugins: multiPoint: enabled: - name: 'MyPlugin' preScore: disabled: - name: '*' score: disabled: - name: '*' ``` `v1beta3`では、`MultiPoint`を通じて、内部的に全ての[デフォルトプラグイン](#scheduling-plugins)が有効化されています。 しかしながら、デフォルト値(並び順やスコアの重みなど)を柔軟に設定し直せるように、個別の拡張点は用意されています。 例えば、2つのスコアプラグイン`DefaultScore1`と`DefaultScore2`に、重み1が設定されているとします。 その場合、次のように重さを変更し、並べ替えることができます ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta3 kind: KubeSchedulerConfiguration profiles: - schedulerName: multipoint-scheduler plugins: score: enabled: - name: 'DefaultScore2' weight: 5 ``` この例では、`MultiPoint`はデフォルトプラグインであるため、明示的にプラグイン名を指定する必要はありません。 そして、`Score`に指定されているプラグインは`DefaultScore2`のみです。 これは、特定の拡張点を通じて設定されたプラグインは、常に`MultiPoint`プラグインよりも優先されるためです。つまり、この設定例では、結果的に2つのプラグインを両方指定することなく、並び替えが行えます。 `MultiPoint`プラグインを設定する際の一般的な優先順位は、以下の通りです。 1. 特定の拡張点が最初に実行され、その設定は他の場所で設定されたものよりも優先される 2. `MultiPoint`を使用して、手動で設定したプラグインとその設定内容 3. デフォルトプラグインとそのデフォルト設定 上記の優先順位を示すために、次の例はこれらのプラグインをベースにします。 |プラグイン|拡張点| |---|---| |`DefaultQueueSort`|`QueueSort`| |`CustomQueueSort`|`QueueSort`| |`DefaultPlugin1`|`Score`, `Filter`| |`DefaultPlugin2`|`Score`| |`CustomPlugin1`|`Score`, `Filter`| |`CustomPlugin2`|`Score`, `Filter`| これらのプラグインの有効な設定例は次の通りです。 ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta3 kind: KubeSchedulerConfiguration profiles: - schedulerName: multipoint-scheduler plugins: multiPoint: enabled: - name: 'CustomQueueSort' - name: 'CustomPlugin1' weight: 3 - name: 'CustomPlugin2' disabled: - name: 'DefaultQueueSort' filter: disabled: - name: 'DefaultPlugin1' score: enabled: - name: 'DefaultPlugin2' ``` なお、特定の拡張点に`MultiPoint`プラグインを再宣言しても、エラーにはなりません。 特定の拡張点が優先されるため、再宣言は無視されます(ログは記録されます)。 このサンプルは、ほとんどのコンフィグを一箇所にまとめるだけでなく、いくつかの工夫をしています。 * カスタムの`queueSort`プラグインを有効にし、デフォルトのプラグインを無効にする。 * `CustomPlugin1`と`CustomPlugin2`を有効にし、この拡張点のプラグイン内で、最初に実行されるようにする。 * `filter`拡張点でのみ、`DefaultPlugin1`を無効にする。 * `score`拡張点で`DefaultPlugin2`が最初に実行されるように並べ替える(カスタムプラグインより先に) `v1beta3`以前のバージョンで、`multiPoint`がない場合、上記の設定例は、次のものと同等になります。 ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta2 kind: KubeSchedulerConfiguration profiles: - schedulerName: multipoint-scheduler plugins: # デフォルトQueueSortプラグインを無効化 queueSort: enabled: - name: 'CustomQueueSort' disabled: - name: 'DefaultQueueSort' # カスタムFilterプラグインを有効化 filter: enabled: - name: 'CustomPlugin1' - name: 'CustomPlugin2' - name: 'DefaultPlugin2' disabled: - name: 'DefaultPlugin1' # カスタムScoreプラグインを有効化し、実行順を並べ替える score: enabled: - name: 'DefaultPlugin2' weight: 1 - name: 'DefaultPlugin1' weight: 3 ``` これは複雑な例ですが、`MultiPoint`設定の柔軟性と、拡張点を設定する既存の方法とのシームレスな統合を実証しています。 ## スケジューラー設定の移行 {{< tabs name=\"tab_with_md\" >}} {{% tab name=\"v1beta1 → v1beta2\" %}} * v1beta2`のバージョン`の設定では、新しい`NodeResourcesFit`プラグインをスコア拡張点で使用できます。 この新しい拡張機能は、`NodeResourcesLeastAllocated`、`NodeResourcesMostAllocated`、 `RequestedToCapacityRatio`プラグインの機能を組み合わせたものです。 例えば、以前は`NodeResourcesMostAllocated`プラグインを使っていたなら、代わりに`NodeResourcesFitプラグイン を使用し(デフォルトで有効)、`pluginConfig`に次のような`scoreStrategy`を追加することになるでしょう。 ```yaml apiVersion: kubescheduler.config.k8s.io/v1beta2 kind: KubeSchedulerConfiguration profiles: - pluginConfig: - args: scoringStrategy: resources: - name: cpu weight: 1 type: MostAllocated name: NodeResourcesFit ``` * スケジューラープラグインの`NodeLabel`は廃止されました。代わりに[`NodeAffinity`](/ja/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity)プラグイン(デフォルトで有効)を使用することで同様の振る舞いを実現できます。 * スケジューラープラグインの`ServiceAffinity`は廃止されました。代わりに[`InterPodAffinity`](/ja/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity)プラグイン(デフォルトで有効)を使用することで同様の振る舞いを実現できます。 * スケジューラープラグインの`NodePreferAvoidPods`は廃止されました。代わりに[Node taints](/ja/docs/concepts/scheduling-eviction/taint-and-toleration/)を使用することで同様の振る舞いを実現できます。 * v1beta2で有効化されたプラグインは、そのプラグインのデフォルトの設定より優先されます。 * スケジューラーのヘルスとメトリクスのバインドアドレスに設定されている`host`や`port`が無効な場合、バリデーションに失敗します。 {{% /tab %}} {{% tab name=\"v1beta2 → v1beta3\" %}} * デフォルトで3つのプラグインの重みが増加しました。 * `InterPodAffinity`:1から2 * `NodeAffinity`:1から2 * `TaintToleration`:1から3 {{% /tab %}} {{< /tabs >}} ## {{% heading \"whatsnext\" %}} * [kube-schedulerリファレンス](/docs/reference/command-line-tools-reference/kube-scheduler/)を読む * [scheduling](/ja/docs/concepts/scheduling-eviction/kube-scheduler/)について学ぶ * [kube-scheduler設定(v1beta2)](/docs/reference/config-api/kube-scheduler-config.v1beta2/)のリファレンスを読む * [kube-scheduler設定(v1beta3)](/docs/reference/config-api/kube-scheduler-config.v1beta3/)のリファレンスを読む </ins>"}
{"_id":"q-en-website-ff3ddf8afb90214cd4764a17e7e15aa179c8fcb1babd1d936a34e5509e8b5c9a","text":"<br> <br> {{ end }} <ins> </div> </ins> </div> {{ end }}  No newline at end of file"}
{"_id":"q-en-website-ff43aeb6b38ec38e576b84cf5cbb42e98f790595cf5a441464c6ae27b096daee","text":"<ins> --- title: Sidecar Containers content_type: concept weight: 50 --- <!-- overview --> {{< feature-state for_k8s_version=\"v1.28\" state=\"alpha\" >}} Sidecar containers are the secondary containers that run along with the main application container within the same {{< glossary_tooltip text=\"Pod\" term_id=\"pod\" >}}. These containers are used to enhance or to extend the functionality of the main application container by providing additional services, or functionality such as logging, monitoring, security, or data synchronization, without directly altering the primary application code. <!-- body --> ## Enabling sidecar containers Starting with Kubernetes 1.28, a [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) named `SidecarContainers` allows you to specify a `restartPolicy` for containers listed in a Pod's `initContainers` field. These restartable _sidecar_ containers are independent with other [init containers](/docs/concepts/workloads/pods/init-containers/) and main application container within the same pod. These can be started, stopped, or restarted without effecting the main application container and other init containers. ## Sidecar containers and Pod lifecycle If an init container is created with its `restartPolicy` set to `Always`, it will start and remain running during the entire life of the Pod. This can be helpful for running supporting services separated from the main application containers. If a `readinessProbe` is specified for this init container, its result will be used to determine the `ready` state of the Pod. Since these containers are defined as init containers, they benefit from the same ordering and sequential guarantees as other init containers, allowing them to be mixed with other init containers into complex Pod initialization flows. Compared to regular init containers, sidecars defined within `initContainers` continue to run after they have started. This is important when there is more than one entry inside `.spec.initContainers` for a Pod. After a sidecar-style init container is running (the kubelet has set the `started` status for that init container to true), the kubelet then starts the next init container from the ordered `.spec.initContainers` list. That status either becomes true because there is a process running in the container and no startup probe defined, or as a result of its `startupProbe` succeeding. Here's an example of a Deployment with two containers, one of which is a sidecar: {{% code_sample language=\"yaml\" file=\"application/deployment-sidecar.yaml\" %}} This feature is also useful for running Jobs with sidecars, as the sidecar container will not prevent the Job from completing after the main container has finished. Here's an example of a Job with two containers, one of which is a sidecar: {{% code_sample language=\"yaml\" file=\"application/job/job-sidecar.yaml\" %}} By default, this feature is not available in Kubernetes. To avail this feature, you need to enable the [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) named `SidecarContainers`. ## Differences from regular containers Sidecar containers run alongside regular containers in the same pod. However, they do not execute the primary application logic; instead, they provide supporting functionality to the main application. Sidecar containers have their own independent lifecycles. They can be started, stopped, and restarted independently of regular containers. This means you can update, scale, or maintain sidecar containers without affecting the primary application. Sidecar containers share the same network and storage namespaces with the primary container This co-location allows them to interact closely and share resources. ## Differences from init containers Sidecar containers work alongside the main container, extending its functionality and providing additional services. Sidecar containers run concurrently with the main application container. They are active throughout the lifecycle of the pod and can be started and stopped independently of the main container. Unlike [init containers](/docs/concepts/workloads/pods/init-containers/), sidecar containers support [probes](/docs/concepts/workloads/pods/pod-lifecycle/#types-of-probe) to control their lifecycle. These containers can interact directly with the main application containers, sharing the same network namespace, filesystem, and environment variables. They work closely together to provide additional functionality. ## Resource sharing within containers {{< comment >}} This section is also present in the [init containers](/docs/concepts/workloads/pods/init-containers/) page. If you're editing this section, change both places. {{< /comment >}} Given the order of execution for init, sidecar and app containers, the following rules for resource usage apply: * The highest of any particular resource request or limit defined on all init containers is the *effective init request/limit*. If any resource has no resource limit specified this is considered as the highest limit. * The Pod's *effective request/limit* for a resource is the sum of [pod overhead](/docs/concepts/scheduling-eviction/pod-overhead/) and the higher of: * the sum of all non-init containers(app and sidecar containers) request/limit for a resource * the effective init request/limit for a resource * Scheduling is done based on effective requests/limits, which means init containers can reserve resources for initialization that are not used during the life of the Pod. * The QoS (quality of service) tier of the Pod's *effective QoS tier* is the QoS tier for all init, sidecar and app containers alike. Quota and limits are applied based on the effective Pod request and limit. Pod level control groups (cgroups) are based on the effective Pod request and limit, the same as the scheduler. ## {{% heading \"whatsnext\" %}} * Read a blog post on [native sidecar containers](/blog/2023/08/25/native-sidecar-containers/). * Read about [creating a Pod that has an init container](/docs/tasks/configure-pod-container/configure-pod-initialization/#create-a-pod-that-has-an-init-container). * Learn about the [types of probes](/docs/concepts/workloads/pods/pod-lifecycle/#types-of-probe): liveness, readiness, startup probe. * Learn about [pod overhead](/docs/concepts/scheduling-eviction/pod-overhead/). </ins>"}
{"_id":"q-en-website-ff6dc3f447e4b555ef4a5d2d15f2d75a32a35e7e84a44a3d158730273a61ed44","text":"* `apiserver_flowcontrol_rejected_requests_total` is a counter vector (cumulative since server start) of requests that were rejected, <del> broken down by the labels `flowSchema` (indicating the one that matched the request), `priorityLevel` (indicating the one to which </del> <ins> broken down by the labels `flow_schema` (indicating the one that matched the request), `priority_level` (indicating the one to which </ins> the request was assigned), and `reason`.  The `reason` label will be have one of the following values: * `queue-full`, indicating that too many requests were already"}