Skip to main content
Skyhook provides automated CI/CD pipelines for your services using GitHub Actions. When you create or import a service, Skyhook generates ready-to-use workflows that handle building Docker images, deploying to Kubernetes, and managing your entire release process.

​
What you get

Automated builds

Docker images tagged, built, and pushed to your registry on every commit to main.

Multi-environment deploys

Promote across dev, staging, production, or any custom environment from the UI or CLI.

GitOps integration

Optional ArgoCD path — workflows update Git, ArgoCD reconciles the cluster.

Progressive delivery

Argo Rollouts canary and blue-green strategies wired into the deploy step.

Multi-cloud

AWS (EKS + ECR), GCP (GKE + Artifact Registry), Azure (AKS + ACR), or BYOK clusters.

Monorepo support

Build and deploy multiple services from a single repo with a generated matrix.
Everything is generated into your repo as plain GitHub Actions YAML — customize, fork, or replace any step.

​
How it works

When you create a service with Skyhook, we automatically generate GitHub Actions workflows in your repository: 
.github/
└── workflows/
    ├── release.yml          # Automated CI/CD on push to main
    ├── build_and_deploy.yml # Manual build + deploy
    ├── deploy.yml           # Manual deploy only
    └── build_image.yml      # Manual build only
These workflows integrate with:
  • Your container registry (ECR, GCR, ACR, Docker Hub, GHCR)
  • Your Kubernetes clusters
  • Your Git repository (for GitOps deployments)

​
Deployment methods

Two paths, picked per service. You can mix — direct for dev, GitOps for production.

GitOps with ArgoCD

Workflow updates Kubernetes manifests in Git; ArgoCD reconciles the cluster. Best for production: Git as the source of truth, drift detection, easy Git-based rollbacks.

Direct (kubectl)

Workflow authenticates to the cluster and applies manifests directly. Best for dev and staging: faster feedback, fewer moving parts, no extra infrastructure.

​
Workflow types

Release

Automatic — triggers on push to main. Builds, tags, pushes images, and (optionally) deploys to a development environment. Detects monorepo services and builds only what changed.

Build and deploy

Manual — build a new image from any ref and deploy it in one shot. Useful for promoting a feature branch to staging before merge.

Deploy existing image

Manual — deploy an already-built image without rebuilding. Promote staging → production, roll back to a known-good image, or replicate a deployment across regions.

Build only

Manual — build and push without deploying. Useful for pre-baking release candidates or testing Docker changes.
Day-to-day deployment guide →

​
Cloud and registry support

CloudClusterRegistryDefault auth
AWSEKSECROIDC + IAM role (no long-lived keys)
GCPGKEArtifact Registry / GCRWorkload Identity Federation
AzureAKSACRService principal or OIDC
BYOKAny conformant KubernetesDocker Hub, GHCR, Harbor, Quay, OCIkubeconfig + registry secret
The skyhook github setup CLI configures the OIDC trust automatically. See Configuration & Setup for the full setup walkthrough.

​
Next steps

Day-to-day deploys

Deploy modal, branch refs, image promotion, rollback patterns.

Configuration & setup

Cloud authentication, generated workflow files, advanced overrides, actions reference.

Troubleshooting

Auth failures, build issues, ArgoCD sync problems, common error messages.