Open v0lkan opened 1 year ago
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".
We initially released it without this feature and then added documentation to ensure that users always upgrade CRDs when upgrading versions.
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: