Starting label could be applied even if pod failed the start command #760
Description
What happened?
When giving the pod such settings that it will fail to start by crashing to a JVM fault, we still set the label starting and this happens after the Pod has crashed. Thus, leaving the cluster in a state that it looks to cass-operator that the pod is still starting while in reality this instance of the pod has never had any /start command applied to it.
What did you expect to happen?
No response
How can we reproduce it (as minimally and precisely as possible)?
See comment #711 (review) , can be reproduced in kind environment at least.
cass-operator version
1.24-dev
Kubernetes version
1.32
Method of installation
No response
Anything else we need to know?
No response
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: CASS-93