Plug Qovery Into the Kubernetes Cluster You Already Run

Qovery has introduced a preview Bring Your Own Kubernetes (BYOK) approach for existing EKS, GKE, and Kapsule clusters through its Qovery Operator, which is installed once using Helm and lets users manage Qovery component deployments and updates from the Qovery Console. The operator addresses limitations of the prior CLI-based installation process by enabling console-managed updates, configurable platform profiles, visibility into installed components, and preflight checks for issues such as connectivity, permissions, registry access, conflicting Helm releases, and storage configuration. Qovery emphasizes that customers retain control of their clusters because it does not store kubeconfig files, the operator communicates outbound only, and deployment jobs run inside the cluster, although these jobs use cluster-admin permissions. The service installs components including logging tools, Envoy Gateway, cert-manager, ExternalDNS, and Qovery agents, while supporting coexistence with existing StorageClasses but not yet adopting existing cert-manager, ExternalDNS, or Envoy Gateway installations. ArgoCD users can continue deploying through GitOps while viewing application status, revisions, and logs in Qovery. The preview is limited to Enterprise-plan organizations, requires an eligible cluster and cluster-admin Helm access, uses Qovery-provided domains, lacks certain monitoring features, and currently requires manual component removal.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.