fdb-kubernetes-operator
fdb-kubernetes-operator copied to clipboard
Distinguishing conditions for incorrect metadata, incorrect pod specs, and incorrect config maps
We currently use the IncorrectPodSpec condition for multiple different scenarios - incorrect pod metadata, incorrect pod specs, and incorrect config maps. This can be confusing when looking at the cluster status, as these scenarios have different causes and different implications for remediation. I think we should separate these conditions into different condition types.