Details
-
Bug
-
Status: Closed
-
Medium
-
Resolution: Not a Bug
-
Dublin Release
-
None
-
local staging lab
Description
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".
Attachments
Issue Links
- relates to
-
DCAEGEN2-1593 Doc updates for VESCollector deployment to enable TLS
-
- Closed
-
-
DCAEGEN2-1594 VESCollector Healtcheck support when Authentication is enabled
-
- Closed
-
# | Subject | Branch | Project | Status | CR | V |
---|---|---|---|---|---|---|
88745,9 | Not Secured healtcheck | master | dcaegen2/collectors/ves | Status: ABANDONED | -1 | 0 |
93952,2 | Not Secured healtcheck | master | dcaegen2/collectors/ves | Status: ABANDONED | 0 | -1 |
94033,7 | Not Secured healtcheck | master | dcaegen2/collectors/ves | Status: MERGED | +2 | +1 |