community-edition VS community

"They have even abandoned their Tanzu community edition." https://tanzucommunityedition.io/

Actually it is free for non-commercial use in a vSphere env up to 100 cores. For public cloud I have no idea how do they count the licenses/cores but you can give a shoot with the TKG. The TKG replaces the TCE. https://tanzucommunityedition.io

You choose to run production workloads on the community edition?

e.g. https://tanzucommunityedition.io/ has some opinions about how to set things up but there's no support contract, so I'd view it as providing guidance or defaults that are likely to work for most use-cases, similar to "I want to make a web app but i'm not already an expert with years of production experience, so i'll use a framework like django/rails/spring/etc. instead of writing free-form from scratch"

Tanzu Community Edition (https://tanzucommunityedition.io/) with "unmanaged clusters" is a fully free + OSS solution for using the cluster and package management tools of vmware's Tanzu without being locked in to other parts of the vmware stack. I honestly don't know all the details but there's a way of buying a support contract also.

You can check out TCE https://tanzucommunityedition.io/ This helps to setup in a single click with UI based deployment

Making its cluster available for many flavors through its Community Edition called TCE (Tanzu Community Edition)

Might I sugest Tanzu? https://tanzucommunityedition.io/

Tanzu Community Edition also supports vSphere/AWS - https://tanzucommunityedition.io/

Hey vnadkarni! Would be great for you to join the community on the Kubernetes Slack. Questions can also be posted in the GitHub Issues or Discussions.

Multiple container runtimes are supported, like conatinerd, cri-o, or other CRI compliant runtimes.

More recently, the Kubernetes SIG Network has been evolving the Gateway API to support service meshes.

https://github.com/kubernetes/kubernetes https://www.kubernetes.dev/resources/calendar/ https://github.com/kubernetes/community/blob/master/governance.md https://github.com/kubernetes/steering https://github.com/kubernetes/community/blob/master/sig-list.md

According to this doc it takes the average of CPU utilization of a pod (average across the last 1 minute) divided by the CPU requested by the pod. Then it computes the arithmetic mean of all the pods' CPU.

metrics-server has not supported kubectl top Resource Metrics API

With the Gateway API being a superset of the Ingress API, it might make sense to consolidate both. Thanks to the SIG Network community, Gateway API is still growing and will soon be production ready.

Projects in/around Kubernetes and the CNCF are generally where I spend what little time I can these days. Most communities are incredibly welcoming and provide timely feedback. But the problem space of "managing a cloud platform" can take several years to really wrap ones head around, setting aside focused topics via SIGs like networking, storage, observability, API design, etc.

Krew is a plugin manager maintained by the Kubernetes Special Interest Group (SIG) CLI community. Krew makes it easy to use kubectl plugins and helps you discover, install, and manage them on your machine. It is similar to tools like apt, dnf, or brew. Today, over 200 kubectl plugins are available on Krew - and that number is only increasing. Some projects are actively used and some get deprecated over time, but are still accessible via Krew.

[1] https://k8s.devstats.cncf.io/d/9/companies-table?orgId=1&var-period_name=Last%20decade&var-metric=contributions [2] https://kubernetes.io/releases/release/ [3] https://github.com/kubernetes/community/blob/master/governance.md [4] https://github.com/kubernetes/community/blob/master/sig-list.md