This is a generic deployment container with the Azure CLI (az) and the Kubernetes CLI (kubectl) preinstalled.
There is a sample kubernetes.sh deployment script available, which you can use as a starting point for your own deployment scripts. It shows how to login to Azure via encrypted environment variables and configure kubectl to run commands against the AKS cluster.
The image is available via the codeship/azure-deployment repository on Docker Hub.
Codeship supports using custom images to generate dockercfg files during the build process. To use this image to integrate with Azure Container Registry, simply define an entry in your services file for this image, and reference it from any steps or services which need to interact with an Azure Container Registry via the dockercfg_service field. You'll also need to provide the following environment variables using an encrypted env file:
For now we require the Admin user for the registry to be enabled.
- AZURE_USERNAME - Your username of the Admin user of the registry
- AZURE_PASSWORD - The password associated with the above admin user
- AZURE_REGISTRY - The URL of the registry you want to access (in the form of
NAME.azurecr.io)
Here is an example of using and ECR Dockercfg generator to authenticate pushing an image.
# codeship-services.yml
app:
build:
image: codeship.azurecr.io/codeship-testing
dockerfile_path: ./Dockerfile
azure_dockercfg:
image: codeship/azure-dockercfg-generator
add_docker: true
encrypted_env_file: azure.env.encrypted# codeship-steps.yml
- service: app
type: push
tag: master
image_name: codeship.azurecr.io/codeship-testing
registry: codeship.azurecr.io
dockercfg_service: azure_dockercfg:You can also use this authentication to pull images, or use with caching, by defining the dockercfg_service field on groups of steps, or each individual step that pulls or pushes an image, or by adding the field to specific services.