deployment.md

Big Bang Deployment

Table of Contents

• Big Bang Deployment
  • GitOps
  • Installation
  • Upgrade
  • Monitor

GitOps

Big Bang follows a GitOps approach to deployment. All configuration changes will be pulled and reconciled with what is stored in the Git repository. The only exception to this is the initial manifests (e.g. dev.yaml) which points to the Git repository and path.

Installation

1. Before pushing changes to Git, validate all configuration is syntactically correct.

   # If everything is successful, YAML should be output
   kustomize build ./dev

2. If you have not already done so, push configuration changes to Git

   git push

3. Validate the Kubernetes context is correct

   # This should match the environment you intend to deploy
   kubectl config current-context

4. Deploy the Big Bang manifest to the cluster

   kubectl apply -f dev.yaml

5. Monitor the deployment

Upgrade

All changes to the Big Bang cluster should be made through Git. After changes are pushed, Big Bang will automatically reconcile the difference with the cluster.

It may take Big Bang up to 10 minutes to recognize your changes and start to deploy them. This is based on the interval value set for polling. You can force Big Bang to immediately check for changes by running the sync.sh script.