v1.3.1

What's Changed

• Beginning workflow to auto-update the project version with GitHub Actions by @sgibson91 in #113
• Update autobump ci by @sgibson91 in #114
• Updating autobump CI by @sgibson91 in #115
• Developing auto-bump-version CI by @sgibson91 in #116
• 👷 Finalise CI workflow for updating semver by @sgibson91 in #117
• 🚑 Correctly write Azure ARM template to json file by @sgibson91 in #118
• Testing refs in auto-bump CI by @sgibson91 in #119
• ⚗ Experimenting by @sgibson91 in #120
• Fix CI workflow to bump versions in Azure deploy config with PR comment by @sgibson91 in #121
• Update button link by @sgibson91 in #123
• 🔥 Remove auto-version-bump.yml by @sgibson91 in #124
• Install Helm 3 in Dockerfile by @sgibson91 in #129
• 👷 Add workflow to build and push docker images to Docker Hub by @sgibson91 in #131
• ⚡️ Use regex to strip v from semver for docker tag by @sgibson91 in #132
• Replace Docker build badge in README by @sgibson91 in #133
• Add six requirement for docker_pull.py by @sgibson91 in #134
• Add manual trigger for docker-pull CI by @sgibson91 in #135
• Fix helm stable chart install by @sgibson91 in #136
• Update .dockerignore by @sgibson91 in #137
• Release v1.3.1 by @sgibson91 in #138

Full Changelog: v1.3.0...v1.3.1

Upgrade project to be compatible with Helm 3

The project now assumes Helm 3 by default to deploy the BinderHub.

Add Networking Policies

Deploy a Virtual Network so `networkpolicy` resources are obeyed

This release modifies `deploy.sh` to create a virtual network and
subnet to deploy the k8s cluster into. This ensures that
`networkpolicy` resources created by the binderhub helm chart are
obeyed and traffic to the pods is restricted.

Choose a Container Registry

This release modifies deploy.sh and the "Deploy to Azure" button such that a user can make a choice between Docker Hub and Azure Container Registry for the deployed BinderHub to store images in. The choice is made by setting the container_registry (in config.json; CONTAINER_REGISTRY for container mode) variable to either dockerhub or azurecr.

Use "Deploy to Azure" button to build a BinderHub with one click

This is version 1 of a project to automatically deploy a BinderHub to Azure cloud through a set of shell scripts or a "Deploy to Azure" button feature. The scripts ensure all the required command line interfaces are installed, then deploys a Kubernetes cluster and the BinderHub Helm Chart on Azure from a configuration defined in the config.json file. Some extra scripts are provided to easily access information and logs from the BinderHub, deploy upgrades or tear down the BinderHub. When the "Deploy to Azure" button is used, a container is spun up which executes the deployment process and pushes logs and relevant files to blob storage.