You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can start a traefik container with -forceHTTPwithTraefik. I can also tell the container a certificate such that it offers services with https...
If I now add a BC Container to it ( using -useTraefik) it identifies the cases with the forceHTTP and the container will not come around with a certificate and will not flip to https ... which I expected. And is fine.
But what it will not do: show up in traefik. And this because the container gets in unhealthy state. And unhealthy will not be promoted into traefik.
So why unhealthy? well, again what I expected, navcontainerhelper copies into the my-run folder a different CheckHealth.ps1....but this check now wants to use https://localhost/ which will of course not work :)
I am curious around this checkHealth thing anyway why two files and copy arounds (maybe some legacy?) ...why not simply stick to one script and make use of the "useSSL" env ? is it set: https, if not http ?! Or, if you want to go nuts, check both? :D there is already a get-service fallback in the "normal" checkHealth.ps1... so why not https, http, service ?
and yes I am aware of the "donotcheckhealth" ... but I like this check :)
The text was updated successfully, but these errors were encountered:
I can start a traefik container with -forceHTTPwithTraefik. I can also tell the container a certificate such that it offers services with https...
If I now add a BC Container to it ( using -useTraefik) it identifies the cases with the forceHTTP and the container will not come around with a certificate and will not flip to https ... which I expected. And is fine.
But what it will not do: show up in traefik. And this because the container gets in unhealthy state. And unhealthy will not be promoted into traefik.
So why unhealthy? well, again what I expected, navcontainerhelper copies into the my-run folder a different CheckHealth.ps1....but this check now wants to use https://localhost/ which will of course not work :)
I am curious around this checkHealth thing anyway why two files and copy arounds (maybe some legacy?) ...why not simply stick to one script and make use of the "useSSL" env ? is it set: https, if not http ?! Or, if you want to go nuts, check both? :D there is already a get-service fallback in the "normal" checkHealth.ps1... so why not https, http, service ?
and yes I am aware of the "donotcheckhealth" ... but I like this check :)
The text was updated successfully, but these errors were encountered: