- Sort Score
- Result 10 results
- Languages All
Results 111 - 117 of 117 for adapted (0.29 sec)
-
CHANGELOG/CHANGELOG-1.13.md
### SIG Cluster Lifecycle For 1.13 SIG Cluster Lifecycle is pleased to announce the long awaited promotion of kubeadm to stable GA, and the promotion of kubeadm’s configuration API to `v1beta1`.
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Thu May 05 13:44:43 UTC 2022 - 273.1K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.25.md
- The kube-controller-manager's deprecated `--experimental-cluster-signing-duration` flag is now removed. Adapt your machinery to use the `--cluster-signing-duration` flag that is available since v1.19. ([#108476](https://github.com/kubernetes/kubernetes/pull/108476), [@ialidzhikov](https://github.com/ialidzhikov))
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Mon May 06 09:23:20 UTC 2024 - 419.1K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.8.md
* The metrics APIs, `custom-metrics.metrics.k8s.io` and `metrics`, were moved from `v1alpha1` to `v1beta1`, and renamed to `custom.metrics.k8s.io` and `metrics.k8s.io`, respectively. If you have deployed a custom metrics adapter, ensure that it supports the new API version. If you have deployed Heapster in aggregated API server mode, upgrade Heapster to support the latest API version.
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Tue Feb 20 15:45:02 UTC 2024 - 312.2K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.21.md
### Structured Logging in Kubelet
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Fri Oct 14 07:03:14 UTC 2022 - 367.3K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.9.md
### Instrumentation In v1.9 we focused on improving stability of the components owned by the SIG, including Heapster, Custom Metrics API adapters for Prometheus, and Stackdriver. ### Network
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Tue Nov 16 10:46:27 UTC 2021 - 313.7K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.27.md
Users who maintain controllers which relied on the fact that pods with RestartPolicy=Always never enter the Succeeded phase may need to adapt their controllers. This is because as a consequence of the change pods which use RestartPolicy=Always may end up in the Succeeded phase in two scenarios: pod
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Wed Jul 17 07:48:22 UTC 2024 - 466.3K bytes - Viewed (2) -
CHANGELOG/CHANGELOG-1.22.md
### Kubernetes release cadence change
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Tue Dec 13 12:43:45 UTC 2022 - 454.1K bytes - Viewed (0)