Closed kudla closed 4 years ago
@kudla it looks like a timeout for DNS to be reachable. Do you have some steps to reproduce?
I'm experiencing same issue. If (platform) stack has no ACM (but has Let's Encrypt) then Ambassador load balancer cannot be created, pending forever with error due to service.beta.kubernetes.io/aws-load-balancer-ssl-cert: null
.
Let's wait for 0.6 upgrade since it will use Istio instead of Ambassador.
Duplicate of applications#137
Stack deployment logs
Enabled components:
flannel
,traefik
,dex
,cluster-autoscaler
,minio
,harbor
,cert-manager
,kubeflow