Skip to content
This repository has been archived by the owner on Sep 28, 2021. It is now read-only.

Latest commit

 

History

History
31 lines (23 loc) · 1.85 KB

development.md

File metadata and controls

31 lines (23 loc) · 1.85 KB

Development

Upload to container registry

To build and upload images to your container registry of choice, you should customize the Makefile with the necessary details (specifically image names and registry URL). Then, you can run the following commands:

  • ./various/changeversion.sh oldVersion newVersion to update version in the Makefile and in the deployment YAML files
  • make buildremote to build the images
  • make pushremote to push the images to the container registry
  • check installation document for the next steps

Local development and e2e testing

For local development and testing we have been using project Kind - Kubernetes IN Docker to run a local Kubernetes environment. To use it on your local workstation:

  • install Docker (if not already installed)
  • install kind using go get sigs.k8s.io/kind
  • make createcluster to create a local cluster using
  • make builddockerlocal to build Docker images locally
  • customize the variables on the 'e2elocal' build step on the Makefile
  • make e2elocal to run the e2e tests as well as the unit tests
  • make deletecluster

You can also run the tests on Minikube or Docker for Mac/Windows. Don't forget to go get github.com/stretchr/testify/assert as it's needed for testing!

Remote e2e testing

For remote development and testing you can use an Azure AKS cluster. Steps to run the e2e tests:

  • make buildremotedebug to build the images
  • make pushremotedebug to push the images to the container registry of your choice (Docker Hub is the default)
  • customize the variables on the 'e2eremotedebug' build step on the Makefile
  • make e2eremotedebug to run the e2e tests towards your AKS cluster