[bitnami/common] _affinities

[maxisam]

Name and Version

bitnami/common 1.16.0

What steps will reproduce the bug?

charts/bitnami/common/templates/_affinities.tpl

Line 66 in 16569e0

- {{ .context.Release.Namespace | quote }}

this should be common.names.namespace

Are you using any custom parameters or values?

No response

What is the expected behavior?

No response

What do you see instead?

charts/bitnami/common/templates/_affinities.tpl

Line 66 in 16569e0

- {{ .context.Release.Namespace | quote }}

Additional information

No response

[javsalgar]

Hi,

Thank you so much for reporting! Would you like to submit a PR with the fix?

[github-actions]

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.

[maxisam]

well, I would like to but there are just too many hoops for a simple PR now, so I will just let you guys do it.

[aoterolorenzo]

Hey @maxisam, just to inform that the issue has been addressed on the above mentioned PR (#11137). Thanks for your submission!

[dosmanak]

Hello. I struggle with the helmchart inside kustomize. The namespace transformer can't reach this value and change it accordingly.

Here is the question: Why even have the podAffinityTerm populated with namespaces list with this single value? It seems to me this setup has the same effect as not defined at all.

   namespaces	<[]string>
     namespaces specifies a static list of namespace names that the term applies
     to. The term is applied to the union of the namespaces listed in this field
     and the ones selected by namespaceSelector. null or empty namespaces list
     and null namespaceSelector means "this pod's namespace"

[carrodher]

In order to provide better support so the whole community could benefit from the answers, could you please post your question in a new ticket?