What you can do
Set up deploy on push
Monk writes a GitHub Actions workflow, built on Monk’s published actions, that builds your images and deploys to your cluster on every push. It stores a cluster service token and the registry and cluster connection details as GitHub secrets. The token is valid for 90 days. How: Ask Monk. You approve the plan in the local dashboard. See CI/CD.Review before anything is created
Monk shows the workflow file, the cluster it deploys to and the secrets it will add to the repository. Nothing is created or pushed until you approve. How: You approve the plan in the local dashboard. See CI/CD.Give GitHub credentials safely
If Monk has no GitHub credentials yet, a form opens in the local dashboard. You enter them there, never in chat. How: In the local dashboard, after asking Monk. See CI/CD.Deploy without pushing
You can still ask Monk to deploy the latest changes directly, and each deploy goes through the plan review. How: Ask Monk. You approve the plan in the local dashboard. See Deployments.Try it
Good to know
- GitHub Actions is the only CI system Monk sets up.
- The app must be deployed to a cluster at least once first, and the project needs a
MANIFESTwith images and Dockerfiles. - The workflow deploys to one fixed cluster. For an environment per branch, use preview environments.
- The token expires after 90 days. Run the setup again to mint a new one, or after moving to another cluster.
CI/CD guide
Set it up step by step
Preview environments
An environment per branch
Deployments
Plans, redeploys and rollbacks