Crds are in widespread use as a way to extend kubernetes to persist and serve new resource types, and have been available in beta since the 1.7 release The 1.16 release marks the graduation of crds to general availability (ga). Kubernetes 1.18 and older received approximately 9 months of patch support Kubernetes versions are expressed as x.y.z, where x is the major version, y is the minor version, and z is the patch version, following semantic versioning terminology. Addons' default limits are typically based on data collected from experience running each addon on small or medium kubernetes clusters When running on large clusters, addons often consume more of some resources than their default limits.
When you create a cluster, you normally have to assign a range that cluster will use for the pods (each pod will take an ip from that pool) There's only so many ips in that range, hence the limit It's rare that you'll use every single ip in that range, but it is possible, hence the limit. We’re pleased to announce the delivery of kubernetes 1.16, our third release of 2019 Kubernetes 1.16 consists of 31 enhancements 8 enhancements moving to stable, 8 enhancements in beta, and 15 enhancements in alpha
This page explains how to optimize cluster resources to ensure sufficient scheduling capacity for your pods by configuring the maximum number of pods per node in standard clusters on. Since kubernetes only officially supports 110 pods per node, you should preferably move pods onto other nodes or expand your cluster with more worker nodes. At v1.16, kubernetes supports clusters with up to 5000 nodes More specifically, we support configurations that meet all of the following criteria
OPEN
