NGINX Ingress Controller expects to find the TLS secret even if the provider is none
FedericoAntoniazzi opened this issue · comments
As per title, Furyctl doesn't allow creating a cluster with the ingresses available only using HTTP.
Here's the snippet of the furyctl.yaml
I'm using.
ingress:
baseDomain: minikube.demo
nginx:
type: single
tls:
provider: none
I'm using this for installing the distribution on my laptop.
Update: It was caused as a side effect of server-side apply
. Re-tested it and it works.