scottk/kubernetes
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/kubernetes.git synced 2025-10-31 02:08:13 +00:00
Code Issues Packages Projects Releases Wiki Activity

Change log: fix broken page anchor url encodings

Browse Source 
Signed-off-by: JunYang <yang.jun22@zte.com.cn>
This commit is contained in:
JunYang
2021-01-28 16:50:43 +08:00
parent 2a13cbede8
commit e5cb50f69e
2 changed files with 1 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
CHANGELOG/CHANGELOG-1.17.md
View File

@@ -1873,7 +1873,7 @@ Prior to 1.17 and for existing nodes created by `kubeadm init` where kubelet cli
`http_requests_total, http_response_size_bytes` `http_requests_total, http_response_size_bytes`
`http_response_size_bytes_sum` `http_response_size_bytes_sum`
`http_response_size_bytes_count` `http_response_size_bytes_count`
due to removal from the prometheus client library. Prometheus http request meta-metrics are now generated from [`promhttp.InstrumentMetricHandler`](https://godoc.org/github.com/prometheus/client_golang/prometheus/promhttp&#35;InstrumentMetricHandler) instead. due to removal from the prometheus client library. Prometheus http request meta-metrics are now generated from [`promhttp.InstrumentMetricHandler`](https://godoc.org/github.com/prometheus/client_golang/prometheus/promhttp#InstrumentMetricHandler) instead.
- Following metrics from kube-controller-manager are now marked as with the ALPHA stability level: - Following metrics from kube-controller-manager are now marked as with the ALPHA stability level:
`storage_count_attachable_volumes_in_use` `storage_count_attachable_volumes_in_use`
`attachdetach_controller_total_volumes` `attachdetach_controller_total_volumes`

5
CHANGELOG/CHANGELOG-1.19.md
View File

@@ -3417,13 +3417,8 @@ filename | sha512 hash
- name: shared-disk - name: shared-disk
- provisioner: kubernetes.io/azure-disk - provisioner: kubernetes.io/azure-disk
- parameters: - parameters:
<<<<<<< HEAD
- skuname: Premium_LRS # Currently only available with premium SSDs. - skuname: Premium_LRS # Currently only available with premium SSDs.
- cachingMode: None # ReadOnly host caching is not available for premium SSDs with maxShares>1 - cachingMode: None # ReadOnly host caching is not available for premium SSDs with maxShares>1
=======
- skuname: Premium_LRS #Currently only available with premium SSDs.
- cachingMode: None #ReadOnly host caching is not available for premium SSDs with maxShares>1
>>>>>>> 74bb122e0a2... Change log:Fix hyperlink of description [kube-controller-manager-kube-scheduler-and-cloud-controller-manager]
maxShares: 2 ([#89328](https://github.com/kubernetes/kubernetes/pull/89328), [@andyzhangx](https://github.com/andyzhangx)) [SIG Cloud Provider and Storage] 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] - 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: 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]