Open andreiionutdamian opened 11 months ago
Thank you for reporting the issue. I see that StatefulSet processor is not up to date with Deployment. Probably, it makes sense to have a single processor for both StatefulSet and Deployment or copy label processing logic from Deployment to StatefulSet as a quick fix.
The problem is that the
StatefulSet
are not correctly generated resulting in the service not being able to correctly select coresponding pods. Basically I had this original manifest (part):after helmify I received:
So the
specs.selector.matchLabels
and thespec.template.metadata.labels
are missing a{{- include "<chart>.selectorLabels" . | nindent 6 }}
while the service template has it as it should. I replicated the identical scenario withDeployment
instead ofStatefulSet
and in the case ofDeployment
the results are correct as it is supposed to be (and service-pods communication works):