Skip to main content
In this fourth project status meeting, Alice and her team have successfully implemented the GitHub Actions workflow for their Node.js application. Building on that progress, Dasher Technologies now plans to adopt the same CI/CD strategy for their Java and Python projects. Since all three applications share a Kubernetes deployment pattern, the team will reuse the existing deployment job steps to streamline the process.
The image is a project status meeting chart listing tasks, all assigned to Alice, with their statuses marked as completed. Some tasks have comments suggesting reusing steps for other projects.

​
Why Reusable Workflows?

By extracting common deployment logic into reusable workflows, the team will be able to:
  • Maintain a single source of truth for Kubernetes deployments
  • Ensure consistency across Node.js, Java, and Python applications
  • Simplify updates and reduce duplication in each repository
Reusable workflows allow you to centralize steps like building Docker images, pushing to a registry, and applying manifests to your cluster. You can invoke them from any repository with minimal configuration.

​
Reuse Strategy Overview

LanguageDeployment ToolingWorkflow File Path
Node.jsHelm.github/workflows/deploy-nodejs.yaml
JavaKubernetes CLI.github/workflows/deploy-java.yaml
PythonKustomize.github/workflows/deploy-python.yaml

​
Next Steps

  1. Author the Reusable Workflow
    • Define inputs (e.g., cluster_name, namespace, image_tag).
    • Encapsulate build, push, and deploy steps in a single workflow file under the .github/workflows/ directory of your common workflow repository.
  2. Consume the Reusable Workflow
    • In each service repository, create a lightweight workflow that calls the central workflow.
    • Pass environment-specific parameters to customize deployments per language.
  3. Validate and Iterate
    • Test deployments in a staging environment first.
    • Monitor logs and update the central workflow as new requirements emerge.
Ensure that each consuming repository has the necessary GitHub secrets configured (e.g., KUBE_CONFIG_DATA, DOCKER_REGISTRY_TOKEN) before invoking the reusable workflow.

Watch Video