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
This bug applies to both apid and trustd - they don't have PKI, but rather watch resources provided by the machined over COSI state socket. If the watch fails, apid and trustd stop rotating their certificates.
On watch failure, we should crash the processes so that they can restart and re-establish the watch.
: 2023/11/15 11:04:10.543784 provider.go:73: error watching for API certificates: rpc error: code = Unavailable desc = error reading from server: EOF
(the root cause of the error is not known here, might be gRPC bug)
The text was updated successfully, but these errors were encountered:
Fixessiderolabs#8345
Both `apid` and `trustd` services use a gRPC connection back to
`machined` to watch changes to the certificates (new certificates being
issued).
This refactors the code to follow regular conventions, so that a failure
to watch will crash the process, and they have a way to restart and
re-establish the watch.
Use the context and errgroup consistently.
Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
(cherry picked from commit 67ac693)
dsseng
pushed a commit
to dsseng/talos
that referenced
this issue
Mar 7, 2024
Fixessiderolabs#8345
Both `apid` and `trustd` services use a gRPC connection back to
`machined` to watch changes to the certificates (new certificates being
issued).
This refactors the code to follow regular conventions, so that a failure
to watch will crash the process, and they have a way to restart and
re-establish the watch.
Use the context and errgroup consistently.
Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
This bug applies to both apid and trustd - they don't have PKI, but rather watch resources provided by the
machined
over COSI state socket. If the watch fails, apid and trustd stop rotating their certificates.On watch failure, we should crash the processes so that they can restart and re-establish the watch.
(the root cause of the error is not known here, might be gRPC bug)
The text was updated successfully, but these errors were encountered: