generated from quarkiverse/quarkiverse-template
-
Notifications
You must be signed in to change notification settings - Fork 53
Open
Description
Since upgrading to 5.0.0 we're noticing different behavior when it comes to starting up our operator. Sometimes we see the following health check status in our logs indicating that Quarkus Operator SDK health check
is DOWN.
{"time":"2023-01-19T06:03:38.017Z","class":"io.smallrye.health","level":"INFO","message":"SRHCK01001: Reporting health down status: {\"status\":\"DOWN\",\"checks\":[{\"name\":\"Quarkus Operator SDK health check\",\"status\":\"DOWN\"},{\"name\":\"K8s connected to kubernetes api version v1\",\"status\":\"UP\"},{\"name\":\"Quarkus Operator SDK health check\",\"status\":\"UP\",\"data\":{\"myfirstcontroller\":\"OK\",\"mysecondcontroller\":\"OK\"}},{\"name\":\"K8s connected to kubernetes api version v1\",\"status\":\"UP\"}]}"}
Could there be a race condition here on this line?
@metacosm any chance you have some insight here wrt to this potentially being a race condition? I can have mixed results when starting our operator up.
csviri
Metadata
Metadata
Assignees
Labels
No labels