Google Cloud Deploy vs Weave GitOps

Google Cloud Deploy automates application delivery through an ordered set of target environments. It deploys to Google Kubernetes Engine, Cloud Run, GKE attached clusters, and custom targets, with releases promoted or rolled back through the web console, CLI, or API. Deployment options include canary and parallel rollouts, verification, deploy hooks, and automated promotion. IAM roles and conditions determine which authenticated users and service accounts can act. Cloud Audit Logs and Cloud Logging support audit trails and platform logs. Teams can invoke the service from CI through its CLI or API, including documented GitHub Actions and GitLab connections. Skaffold and Cloud Build render and deploy manifests, alongside artifact repositories and testing or workflow tools. The first active multiple-target pipeline each month costs nothing; each additional active multiple-target pipeline costs $5 a month per billing account. Underlying services may add charges. The regional system limit is 18,000 API requests per minute.

Weave GitOps extends Flux with deployment insights and tools for continuous delivery across teams. Its dashboard lets operators inspect application lifecycles, detect drift, check cluster health, roll back changes, and monitor operations. Both Open Source and Enterprise require a running Kubernetes cluster. The free Open Source edition includes a GitOps CLI for macOS and Linux. Enterprise adds deployment across multiple clusters in cloud and hybrid environments using Git and Cluster API. It supports canary, blue/green, and A/B rollouts, with success and rollback criteria based on metrics from Prometheus, Datadog, or New Relic. Enterprise also offers policy-as-code checks at commit, build, deploy, and runtime stages, plus team workspaces, multi-tenancy, role-based access, and enterprise identity integration. OIDC login and Kubernetes RBAC govern access. Infrastructure integrations include Terraform, Crossplane, and any Cluster API provider. Enterprise advertises critical 24/7 support for workloads and requires an entitlement from Weaveworks. The Open Source installation guide notes that dashboard login sessions are not persisted when scaling to multiple replicas.