Tags / Cloud and DevOps /
A CLI, TUI, kubectl plugin, or dashboard to operate Kubernetes clusters; not an operator.
The 42repositories with this Tag gained +2,688 net stars in the last 30 days, 77% more than the 30 days before.
3 created in the last 90 days · 15 published a release in the last 30 days · 333K stars in total
Oct 6, 2026Nov 4, 2026
Most net stars, last 30 days
dsx-ai-factory/run-aiRun:ai is the AI workload orchestration platform for Kubernetes. This monorepo contains the control plane services, in-cluster Kubernetes operator/controllers, shared libraries and clients, the installer, and the local dev environment.
+666
25% of the net stars of this Tag
Largest Pace, last 30 days
No other repository gained 2 or more times the net stars of the 30 days before.
Most stars, created in the last 90 days
eooce/Cloudflare-Tunnel-PanelTranslatedA multi-account tunnel management panel deployed with Cloudflare Workers
258
stars in total · created 16 days ago
Net stars gained each week. The repositories that gained the most have their own color.
portainer/portainer gained 14% of the net stars of this Tag in the last 13 weeks.
3 of 42 repositories: Created on GitHub in the last 90 days. Select a column name to change the order.
| # | Repository | Stars | Gained, 90 days | Pace | |
|---|---|---|---|---|---|
| 1 | dsx-ai-factory/run-ai Run:ai is the AI workload orchestration platform for Kubernetes. This monorepo contains the control plane services, in-cluster Kubernetes operator/controllers, shared libraries and clients, the installer, and the local dev environment. | 703 | +703 | new | |
| 2 | eooce/Cloudflare-Tunnel-Panel TranslatedA multi-account tunnel management panel deployed with Cloudflare Workers | 258 | +263 | new | |
| 3 | Rocky-true/vmware-to-kubernetes TranslatedKubernetes automation, migration and ops toolkit. Kubernetes automation, operations and migration tool: Alibaba Cloud 3-master HA, Compose→K8s, Terraform, Kubekey, deployment verification and troubleshooting. | 157 | +157 | new |
Net stars of the last 30 days are 2 or more times those of the 30 days before.
No repository with this Tag meets this rule now.
Net stars of the last 30 days are 50% or less of those of the 30 days before.
No repository with this Tag meets this rule now.
Created on GitHub in the last 90 days.
Created more than 2 years ago, with a push in the last 7 days and a GitHub release in the last 30 days.
The newest GitHub release is more than 180 days old. A repository that never published a release is not in this list.
An agent reads the description, the GitHub topics, and the start of the README of each repository. It chooses Tags only from the Tag list in the AwesomeRepos source code. For each Tag, it quotes the text. A code check keeps the Tag only when the quote is in that text. The page of each repository shows the quote of each of its Tags. A Tag does not rank repositories. It does not say that one repository can replace another. To report a wrong Tag, use "Report a problem with this page" on the page of the repository.
All numbers come from the Star History of the repositories that have the Tag now. A period is a run of complete UTC days. All numbers on this page count only the repositories that AwesomeRepos shows in lists. A machine computes them each hour.
For each repository, a period counts only when Star History has each of its days, or when the repository was created in the period. Otherwise the table shows "–". The bars of a week with no complete data are grey.
The Pace is the net stars of a period divided by the net stars of the period before. It shows only when Star History covers each day of the period before, with at least 3 net stars a day on average.
The chart at the top adds up the net stars of all the repositories with the Tag. A rising Admission comes into the Repository Index because it gained stars quickly. Its Star History before its Admission comes from the Repository Host. Thus the days before many rising Admissions are higher than they were for the repositories in the index at that time.
The releases are the GitHub releases of each repository. The lists and the table do not rank repositories, and they do not say that one repository can replace another.