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
Additionally, instead of using the nightly, using the latest stable version of SPIRE Controller Manager definitely would have fixed the issue (but this way we are lucky to capture it earlier… so I’m not complaining about living on the edge :) )
The text was updated successfully, but these errors were encountered:
Also, this is a breaking change (but it’s understandable to be so since it’s a nightly build); not sure the best way to handle it though since it is up to the user to add that CRD in the first place.
This should hopefully be as easy as detecting this particular failure reason when listing the CRDs during reconciliation and treating it as "no CRDs present".
The component was working as expected ~5 days ago (today is Jul, 9, 2023).
The YAML files used to deploy SPIRE can be found at this snapshot:
https://github.com/shieldworks/aegis/tree/fbeb28f97761a768498aa9f03ca7521f41b641d6/k8s/spire
What happens:
SPIRE Server crashes. Here are the logs related to SPIRE controller manager
Expectation:
SPIRE server should have given a warning (along the lines of “
ClusterStaticEntry
CRD is missing, please download at install it from {URL}.”Or SPIRE Controller Manager container should have done a self-diagnosis and exit with a reason
Or both. Or something along those lines.
Other Notes and Resolutions:
The text was updated successfully, but these errors were encountered: