Open octane100 opened 1 month ago
Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
This Issue 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. Thanks for the feedback.
I have this problem too
I fixed it with:
externalAccess:
enabled: true
service:
type: LoadBalancer
annotations:
service.beta.kubernetes.io/openstack-internal-load-balancer: "true"
loadBalancerIPs:
- "10.98.3.51"
- "10.98.3.52"
annotationsList:
- external-dns.alpha.kubernetes.io/hostname: ks01mongodb.sales.crm
- external-dns.alpha.kubernetes.io/hostname: ks01mongodb.sales.crm
but, that's a patch, not a fix.
Thank you for sharing the information regarding how you fixed the issue. As @carrodher mentioned above, would you like to contribute to this project? The team will review the changes and the whole community will benefit of the the update.
This Issue 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. Thanks for the feedback.
Name and Version
bitnami/mongodb 15.6.0
What architecture are you using?
amd64
What steps will reproduce the bug?
Deploying a Mongodb cluster with 3 replicasets and externalAccess enabled:
Are you using any custom parameters or values?
values.yaml :
What is the expected behavior?
Deployment running without error
What do you see instead?
Additional information
The issue has occurred since version 15.3.0 (https://github.com/bitnami/charts/pull/25397).
I can workaround the issue by adding these lines to the values.yaml :