hazelcast's topologySpreadConstraints in the default values.yaml Issue

Products

• VIP Authentication Hub

Issue/Introduction

hazelcast pods not getting spread across multiple zones 

Environment

VIP authHub prior to 3.1.1 

Resolution

Today , the values.yaml on all versions from what we saw has the wrong naming as seen in the screen shot below.

This is a Defect that was addressed in 3.3.1. The change is in the hazelcast's topologySpreadConstraints in the default values.yaml of the ssp chart, so that the app.kubernetes.io/name label uses the hazelcast's nameOverride, hazelcast-entp.
i.e.
labelSelector:
matchLabels:
app.kubernetes.io/name: hazelcast-entp

If you are running a version prior to 3.3.1 , you can manually change the values in the yaml file and redeploy.