[bitnami/mongodb] Enable publishNotReadyAddresses for ClusterIP services

[janvotava]

Description of the change

When MongoDB replicaset hosts configuration points to services (rather than pods on headless service) for inter-cluster communication (through tunnel for example), a deadlock can occur when majority Pods fail at once since services won't publish addresses until pods are ready.

This change prevents deadlocks by allowing MongoDB instances to discover each other during startup and keeps it similar to NodePort/Loadbalancer logic in external mode.

Benefits

Makes ClusterIP external replicaset mode more resilient.

Possible drawbacks

Applicable issues

• fixes #

Additional information

Checklist

• Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
• Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm
• Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
• All commits signed off and in agreement of Developer Certificate of Origin (DCO)

[carrodher]

Thank you for initiating this pull request. We appreciate your effort. This is just a friendly reminder that signing your commits is important. Your signature certifies that you either authored the patch or have the necessary rights to contribute to the changes. You can find detailed information on how to do this in the “Sign your work” section of our contributing guidelines.

Feel free to reach out if you have any questions or need assistance with the signing process.

[janvotava]

Thank you for initiating this pull request. We appreciate your effort. This is just a friendly reminder that signing your commits is important. Your signature certifies that you either authored the patch or have the necessary rights to contribute to the changes. You can find detailed information on how to do this in the “Sign your work” section of our contributing guidelines.

Feel free to reach out if you have any questions or need assistance with the signing process.

There's no correct sign-off?

[carrodher]

Here you can see the failing GH Action and some tips about how to remediate it

[janvotava]

Sorry, wrong email. 🫣 Should be fixed now.

[github-actions]

This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.

[janvotava]

Please don't close this PR.

[gongomgra]

Instead of always setting the parameter to true, can you parameterize it (with default to false)? This way we maintain the current behavior and it can be set in an easy way when required.

[janvotava]

I can do that. But I wonder, what's the use case for the current behavior - could changing the default false -> true potentially be a breaking change?

[gongomgra]

The thing is that we have not being reported with any issue related to current setup, so to be on the safe side I think it is worth it to keep it this way for now yet allowing users to customize it.