community VS website

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

This happened few years ago I don't remember the specifics, but I find funny to see the exact confusion still around whats supposed to be a basic functionality here with the k8 devs themselves acknowledging lack of correct docs but doing little.

Great to know! Since the kubernetes/website repo currently lacks the tr localisation, I'm pretty sure starting it there would be much appreciated by the relevant community. This guide and the #sig-docs-localizations channel in Kubernetes Slack are the best starting points for those who might be interested in it.

From the doc:

Better is probably subjective, but you have options. You can run the doc website locally (https://github.com/kubernetes/website) or search the API definitions directly (https://github.com/kubernetes/api). Good ol `git grep` I suppose.

No, I don't think so. Killercoda is one of the main options currently being considered for moving from Katacoda. You can find this discussion here.

Kubernetes*

I'm unable to find any references other than this link that confirms that the failure has to be consecutive. https://github.com/kubernetes/website/issues/37414

Discover the full power of this feature in the docs.