Question

Your platform team uses Google Cloud Deploy to manage progressive delivery for containerized workloads. A new business unit needs to deploy artifacts to an on-premises Kubernetes cluster that is not registered as a GKE or Anthos target and requires invoking a proprietary internal CLI to apply manifests. The team wants to keep using the same Cloud Deploy pipeline model (delivery pipeline, targets, promotion, and rollback) rather than building a separate custom tool. What should you do?

Accepted Answer

Define a custom target type in Cloud Deploy using a skaffold custom action that runs a container implementing the render and deploy operations against the on-premises cluster.

Answer

Register the on-premises cluster as a standard GKE target and let Cloud Deploy apply manifests directly with its built-in Kubernetes deployer.

Answer

Abandon Cloud Deploy for this workload and orchestrate the entire promotion and rollback flow with a set of Cloud Build triggers that call the proprietary CLI.

Answer

Use a Cloud Run target in Cloud Deploy and configure a deploy hook to shell out to the proprietary CLI after the Cloud Run service is created.