-
Bug
-
Resolution: Not a Bug
-
Medium
-
Dublin Release
-
None
-
local staging lab
When I change VES parameter auth.method to certOnly (only HTTPS connections available) I see a problem with failed pod rediness probe.
Healthcheck sends get request via http, while https connection is required.
Container with Ves Collector is marked as a Unheathly and because of that any traffic can't be send to that pod.
Container description. Container with Ves Collector has state Ready = False
Pod status. 1 of 2 containers are running
Kubernetes pod details. rediness probe failed because of refused connection.
Additionaly Robot healthchecks got failed when flag is other than "noAuth".
- relates to
-
DCAEGEN2-1593 Doc updates for VESCollector deployment to enable TLS
- Closed
-
DCAEGEN2-1594 VESCollector Healtcheck support when Authentication is enabled
- Closed