spinnaker: Deployment fails when Azure Container Registry is used

Azure Container Registry cannot pass healthcheck from clouddriver. This affects Spinnaker deployments on Kubernetes when Azure ACR is connected as container registry.

Cloud Provider Kubernetes, Azure

Environment Spinnaker is deploying on top of Kubernetes on Azure Container Service

Feature Area Container registry

Description When i’m adding Azure Container Registry to configuration, Spinnaker deployment never finishes. This happens because spin-clouddriver-bootstrap pod doesn’t passes health check. After short investigation i’ve found that this happens due unhealthy Azure ACR. The strange this is when i’m adding registry via hal config provider docker-registry account add azureacr --address https://myregistry.azurecr.io --repositories myimage --username myregistry --password , it passes validation, but later, when clouddriver checks registry it fails with s.c.d.r.h.DockerRegistryHealthIndicator : Unhealthy and retrofit.RetrofitError: 401 Unauthorized in head of stack trace.

Steps to Reproduce Add Azure ACR to config and try to deploy Spinnaker on Kubernetes. 100% reproducible.