Adds a Kubernetes pipeline with three main stages:
- Deploy to a development environment
- Wait for manual judgement
- Deploy to a production environment
The pipeline will be triggered by any new tag pushed to the target repository and will also clean up previous deployments.
This must be executed on a machine with a running Spinnaker instance.
| Name | Description |
|---|---|
| --account_name -an |
The Spinnaker account name for your registry |
| --registry -rg |
The Azure Container Registry url, for example 'sample-microsoft.azurecr.io'. |
| --repository -rp |
The repository, for example 'Fabrikam/app1'. Any new tag pushed to this repository will trigger the pipeline. |
| --port -p |
(optional) The port used when creating load balancers for the pipeline. The container deployed by your pipeline is expected to be listening on this port. The default is '8000'. |
| --user_name -un |
(optional) The user name for creating the pipeline. The default is '[anonymous]'. |
| --user_email -ue |
(optional) The user email for creating the pipeline. The default is '[email protected]'. |
| --artifacts_location -al |
(optional) The url for referencing other scripts/artifacts. The default is this github repository. |
| --sas_token -st |
(optional) A sas token needed if the artifacts location is private. |
./add_k8s_pipeline.sh --acount-name "azure-container-registry" --registry "sample-microsoft.azurecr.io" --repository "Fabrikam/application1"