Carlos Rodríguez Hernández

> I will say try out locally you will encounter the same issue as me. > > here is what the local file looks like : > > ```yaml >...

See the second part of the [previous answer](https://github.com/bitnami/charts/issues/12259#issuecomment-1236618734), you should be able to set `aws-blah-blah.region.xyz` as the registry, using `test-oauth2` as the repository in order to form the full image...

That's because probably you are defining something at the `global` level: ```yaml global: imageRegistry: "" ``` If something is set in the `global` parameter, it will affect the main chart...

I'm not sure what should be modified in the bitnami/wordpress Helm chart. In the hpa template everything is defined as expected, see ```yaml metrics: {{- if .Values.autoscaling.targetCPU }} - type:...

Thanks for reporting this issue. Would you like to contribute by creating a PR to solve the issue? The Bitnami team will be happy to review it and provide feedback....

You can find the instructions in the [CONTRIBUTING guidelines](https://github.com/bitnami/charts/blob/master/CONTRIBUTING.md) and some generic instructions in the GitHub documentation itself, see https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

In order to list old versions you need to use a previous commit, see below the differences: ```console $ helm repo list NAME URL bitnami https://charts.bitnami.com/bitnami bitnami-index https://raw.githubusercontent.com/bitnami/charts/index/bitnami bitnami-pre-2022 https://raw.githubusercontent.com/bitnami/charts/pre-2022/bitnami...

Thanks for creating this PR. Please, note it is needed to sign the commits. Your signature certifies that you wrote the patch or otherwise have the right to contribute the...

Please, [note that the Bitnami team is not actively monitoring GitHub Issues for this Helm chart](https://github.com/bitnami/charts/tree/master/bitnami/mediawiki#community-supported-solution). This issue will stay open for 20 days to allow the community to contribute,...

I was able to reproduce the same issue when moving from node `14.20.0` to `16.17.0`. It seems there are two aspects to reproduce the issue: * Use a recent NodeJS...