Easy ChatOps based Release Automation with Tekton, ArgoCD and GitHub Actions

Prerequisites

1. An OpenShift cluster, with credentials stored as GitHub Repository Secrets

• OPENSHIFT_PASSWORD
• OPENSHIFT_SERVER

2. ArgoCD deployed and repo added
3. Tekton deployed and Tasks + Pipelines deployed
4. Personal Access Token configured for chatops slash commands and GitHub Repository Secret created named: SLASH_TOKEN

Notes

This example repo uses the idea of a trunk based development

How everything works

Tekton is building in the cluster based off of any changes to the src directory via GitHub action .github/workflows/tekton-build.yaml

Once you are ready to release, create an Issue (use the Release Issue template for more documentation)

/release to create a tagged release based on the name
/promote to change the appropriate ArgoCD configs to point the new tag
/deploy to deploy via ArgoCD Application documentation here

GitHub Actions are from:

• https://github.com/peter-evans/slash-command-dispatch
• https://github.com/redhat-actions/openshift-tools-installer
• https://github.com/redhat-actions/oc-login
• https://github.com/mikefarah/yq
• https://github.com/peter-evans/close-issue
• https://github.com/peter-evans/create-or-update-comment
• https://github.com/peterjgrainger/action-create-branch
• https://github.com/stefanzweifel/git-auto-commit-action

Tekton Tasks & Pipelines are from:

• https://hub.tekton.dev/tekton/task/s2i
• https://hub.tekton.dev/tekton/task/git-clone