search

rancher / rio

Application Deployment Engine for Kubernetes
https://rio.io
Apache License 2.0
2.27k stars 228 forks source link

Router to publicdomain does not generate ssl cert #936

Closed rancher-max closed 4 years ago

rancher-max commented 4 years ago

Describe the bug The cert stays as the self signed cert-manager.local when creating a publicdomain to a router, so https is not available.

To Reproduce

  1. rio run -n demo -p 80 ibuildthecloud/demo:v1
  2. rio domain register my.cname.com demo

Expected behavior Should be able to get https endpoint. It looks like it is available but does not properly create the certificate.

Additional context rio -s logs cert-manager output:

cert-manager-7496c5f7cd-sr7rq cert-manager E1213 21:34:08.266623       1 sync.go:184] cert-manager/controller/challenges "msg"="propagation check failed" "error"="wrong status code '404', expected '200'" "dnsName"="maxrio.qa.rancher.space" "resource_kind"="Challenge" "resource_name"="maxrio.qa.rancher.space-tls-3540917872-3566497347-2877105551" "resource_namespace"="rio-system" "type"="http-01"
rancher-max commented 4 years ago

This works now. In testing, noticed that registering a domain to a service app endpoint in one case took over an hour to generate the ssl cert. The cert-manager logs during this time were showing error"="wrong status code '502', expected '200'", but eventually it worked. Also, the cname http endpoint was available during this time, and the https endpoint given by rio, so I believe this is working in v0.7.0-rc2.