I'm unhappy with Rancher for multi-cluster management

That’s understandable—Rancher isn’t always the best fit, especially if you want simpler ops, stronger GitOps workflows, or less platform overhead.

If you want alternatives for multi-cluster Kubernetes management, the best choice depends on what’s bothering you about Rancher:

Good alternatives

• Argo CD + ApplicationSets
  Best if you mainly want GitOps-driven multi-cluster deployment. Lightweight, widely used, and works well across many clusters.
• Flux
  Another strong GitOps option. Good for teams that want a more modular, Kubernetes-native approach.
• Portainer
  Easier UI-centric management, but generally lighter-weight than Rancher and less opinionated.
• OpenShift / Red Hat Advanced Cluster Management
  Best for enterprise environments if you want stronger governance and support, but it’s a bigger platform investment.
• Gardener
  Better if you need cluster lifecycle management at scale, especially in cloud-native environments.
• Cluster API
  Strong if your main need is creating and managing clusters declaratively rather than day-to-day app management.

If your pain is specifically:

• UI complexity → Portainer or GitOps tools
• Too much platform overhead → Argo CD / Flux
• Cluster lifecycle management → Cluster API / Gardener
• Enterprise governance → OpenShift ACM

A common modern setup

Many teams use:

• Argo CD for app deployment
• Cluster API or cloud-native tooling for cluster provisioning
• Prometheus/Grafana/Loki for observability
• External Secrets / Vault for secrets management

If you want, I can help you choose the best alternative based on:

1. number of clusters,
2. cloud/on-prem mix,
3. whether you need cluster provisioning or just app deployment, and
4. how much UI vs GitOps you want.