PromucFlow_constructor/deploy/helm/tests
Wyatt Walter 708c4061c2
fix: use bitnamilegacy images temporarily (#41176)
## Description
Bitnami has deprecated the images we rely on by default in the chart. We
need to figure out how we adjust to this situation (and upgrade MongoDB
as well to get off the EOL version here). For now, use the bitnamilegacy
images.

see: https://github.com/bitnami/charts/issues/35256


Fixes #`Issue Number`  
_or_  
Fixes `Issue URL`
> [!WARNING]  
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._

## Automation

/ok-to-test tags=""

### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results  -->
> [!CAUTION]  
> If you modify the content in this section, you are likely to disrupt
the CI result for your PR.

<!-- end of auto-generated comment: Cypress test results  -->


## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [x] No


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* Chores
  * Updated Helm chart to version 3.6.4.
* Switched default container image repositories for MongoDB and
PostgreSQL to bitnamilegacy while keeping the existing tags, improving
continuity with upstream changes.
* Cleaned up a deprecated MongoDB image configuration block to avoid
confusion in values configuration.
* These changes affect deployment configuration only and do not modify
application behavior.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-08-13 10:42:10 +05:30
..
__snapshot__ fix: use bitnamilegacy images temporarily (#41176) 2025-08-13 10:42:10 +05:30
defaults_snapshot_test.yaml
README.md
runAsUser_test.yaml

Helm Chart Unit Tests

This directory contains unit tests for our Helm charts using helm-unittest, a BDD-style testing framework for Helm charts.

Running Tests Locally

You can run the tests locally using Docker:

docker run -ti --rm -v $(pwd):/apps helmunittest/helm-unittest .

Snapshot Testing

Our tests use snapshot testing to validate the rendered Kubernetes manifests. This ensures that any changes to the defaults are intentional and reviewed.

Updating Snapshots

When making changes that affect the rendered output (like updating labels or other metadata), you'll need to update the snapshots. This is particularly important during releases when labels are updated.

To update snapshots, run the tests with the -u flag:

docker run -ti --rm -v $(pwd):/apps helmunittest/helm-unittest -u .

Important: Always review the changes in the snapshots before committing them to ensure they match your expectations.

Documentation

For more information about helm-unittest, including:

  • Writing test cases
  • Available assertions
  • Test suite configuration
  • Best practices

Please refer to the official helm-unittest documentation.