Rancher

Rancher is an open-source container management platform that helps teams deploy and manage Kubernetes clusters across infrastructure.

Primary category: Coding Tools

Visit Rancher

About this data

This page reflects public online discussion, collected and scored by automated systems and summarized using AI. It is not a statement of fact, not an audit, and not our own opinion of the product. Automated analysis can be incomplete or wrong, and scores carry the limitations described in our methodology. Companies can respond with their own perspective. See how this is calculated.

Updated June 22, 2026

Overall Pulse Score

Pulse Score

+1 over this period

A 0-100 index summarizing the tone of 468 relevant public mentions gathered from public online communities across 5 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.

Weekly Sentiment Trend

Pulse Score by week over the selected period. Each point is one complete week of mentions.

This week in public discussion

Rancher discussion over the recent period was heavily dominated by bug reports and reliability concerns, with commenters filing numerous issues around cluster availability after pod restarts, image pull failures on Windows nodes, and API stalling problems. The UI also drew complaints, including mentions of outdated RKE1 options appearing in monitoring charts. Praise was sparse, with only a handful of mentions touching on features and integrations. Overall community sentiment leaned sharply negative across the tracking window.

AI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.

Sentiment mix by week

How the tone of public discussion splits each week.

PositiveMixedNeutralNegative

Most-discussed praise

Strong features3

Easy to use2

New releases2

Good integrations1

Most-discussed complaints

Bugs303

Reliability197

UI frustrations71

Missing features41

Lacking integrations23

Themes across the selected period, with mention counts.

Sample public mentions

Showing 5 of 468 analyzed public mentions in this period, with links to the original source. We do not reproduce full threads.

“[BUG] After rancher pod restart, some clusters are shown unavailable. **Rancher Server Setup** - Rancher version: 2.14.1 - Installation option (Docker install/Helm Chart): helm chart - If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): rke2 - Proxy/Cert De...”

githubMay 26, 2026

“[BUG] upgrade_manifest.sh is not reentrant (disable_kubevirt_workload_live_migration). ### Describe the Bug This was spotted while troubleshooting https://github.com/harvester/harvester/issues/10937. I kill the apply-manifest pods and find the pod become error again. To Reproduce...”

github4 days ago

“Unable to pull rke2-runtime image on Windows. Hi, I am unable to provision a Windows node with Rancher and RKE2 because an image pull of rke2-runtime fails when the Windows service rke2 tries to pull it: **Environmental Info:** RKE2 Version: C:\usr\local\bin\rke2.exe -v rke2.exe ...”

githubJun 2, 2026

“[BUG] Upgrading from v1.8.0 to master is stuck on waiting upgrading Fleet. ### Describe the Bug The upgrade process is stuck on apply-manifests job. hvst-upgrade-gmxmr-apply-manifests-hw7pk kubectl get secret --namespace cattle-system bootstrap-secret -o go-template='{{.data.boot...”

githubJun 3, 2026

“[BUG] Can not communicate to pod due to Calico uses kube-vip's macvlan interface as the VXLAN VTEP. ### Describe the Bug To Reproduce 1. Create harvester-v1.7.1 and join to rancher-v2.13.6 2. Create a 3 nodes RKE2 cluster (must be multi-nodes) 3. Create nginx pod 5. ❌ Create LB r...”

githubJun 10, 2026

465+ more analyzed mentions, full history, and theme breakdowns are part of Pro.

Get Pro

Deeper analysis

Bug reports and reliability complaints dominated the conversation by a wide margin over the four-week window.
Sentiment showed a brief mid-period uptick but retreated by the final week, leaving the overall direction essentially flat.
Integration behavior was the most contested area, drawing both the rare positive mentions and notable complaints.
Praise themes were present but extremely sparse, reflecting a discussion skewed heavily toward problem reporting.

Praise theme	Mentions
Strong features	3
Easy to use	2
New releases	2
Good integrations	1

Complaint theme	Mentions
Bugs	303
Reliability	197
UI frustrations	71
Missing features	41
Lacking integrations	23

Discussion around Rancher over the recent four-week window was dominated overwhelmingly by bug reports and reliability concerns, with complaint-side themes outnumbering praise themes by a striking margin. Mentions of bugs accounted for the single largest cluster of discussion, and reliability issues followed closely, together suggesting that a substantial portion of commenters were encountering broken or unstable behavior rather than exploring the product's capabilities. UI complaints and missing features added further weight to the negative side, while praise themes around feature quality, new releases, integrations, and ease of use appeared only in a handful of mentions, indicating that positive sentiment had very little foothold in the conversation during this period.

The score trajectory showed some movement but no sustained recovery. After a low point in late May, sentiment edged upward into early June before slipping back by mid-June, tracing a modest and inconclusive arc. The overall level remained compressed throughout, with no week showing a decisive break toward positive territory. This pattern suggested to observers that periodic upticks were not translating into durable improvements in how the product was being received publicly.

Sample mentions reinforced the complaint picture, with commenters describing cluster availability failures after pod restarts, image pull failures on Windows nodes, empty machine pool displays, and API stall conditions under specific configurations. Several mentions took the form of structured bug filings, which pointed to a technically engaged user base that was actively documenting problems rather than simply expressing frustration in passing.

Opinion was most divided around integration behavior, where a small number of commenters noted positive experiences while a larger group flagged gaps and failures. The monitoring chart retaining deprecated RKE1 options drew pointed commentary from multiple directions, with some treating it as a minor oversight and others framing it as a sign of broader quality control concerns. Overall the tone of discussion suggested a community that remained invested in the product but was carrying significant unresolved frustration.

AI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.