![]() Now, the control plane narrows the allowed inbound traffic to each IP range of the node pool subnets on ports TCP/443 and TCP/8123 multiple node pools can share one subnet.Previously, the control plane allowed inbound traffic from the entire primary IP range of the VPC on ports TCP/443 and TCP/8123, which are used by node pools.Existing clusters of previous versions were already using etcd v3.5.x and will not be downgraded to v3.4.21 during cluster upgrade these clusters will instead use v3.5.6.Ĭlusters now have per-node-pool subnet security group rules instead of VPC-wide rules: Newly-created clusters now use etcd v3.4.21 for improved stability. Non-system Pods are given 15 seconds to terminate, after which system Pods (with the system-cluster-critical or system-node-critical priority classes) have 15 seconds to gracefully terminate. For the metadata to be ingested properly, customers need to enable the Config Monitoring for Ops API.Įnabled kubelet graceful node shutdown. ![]() Improved monitoring by exporting metrics for control plane components.Įnabled sending Kubernetes resource metadata to Google Cloud Platform, improving both the user interface and cluster metrics. ![]() If they do, they must be updated to use cgroupv2. We recommend that you check if any of your applications access the cgroup filesystem.
0 Comments
Leave a Reply. |