The Helm tests failed because of namespace conflicts in parallel test run

[deveshkul]

Apache Airflow version

Other Airflow 2 version (please specify below)

If "Other Airflow 2 version" selected, which one?

2.6.3

What happened?

While executing Helm tests simultaneously or within a common Kubernetes cluster, tests encounter failures because of namespace clashes. For instance, several test executions try to generate resources within the same namespace, resulting in errors such as:

Error: cannot re-use a name that is still in use

What you think should happen instead?

Each Helm test run should use a unique namespace to avoid conflicts. This would allow parallel test execution and improve reliability.

How to reproduce

Run two instances of the Helm tests simultaneously in the same Kubernetes cluster.

Observe namespace conflicts and test failures.

Operating System

Airflow version: 2.6.3 Kubernetes version: v1.21 Helm version: v3.7.0

Versions of Apache Airflow Providers

Airflow version: 2.6.3

Kubernetes version: v1.21

Helm version: v3.7.0

Deployment

Official Apache Airflow Helm Chart

Deployment details

The issue occurs in a Kubernetes cluster deployed using Helm v3.7.0. The cluster is running on GKE (Google Kubernetes Engine) with the following configuration:

Cluster version: v1.21.12-gke.2200

Node pool: 3 nodes (n1-standard-4)

Helm chart: Apache Airflow 2.6.3

Anything else?

This issue is particularly problematic in CI/CD environments where multiple test runs may execute concurrently. The current setup does not account for parallel execution, leading to namespace conflicts and test failures.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[potiuk]

I am not sure which tests you are talking about and whether the report is legitimate - we've been recently flooded with some AI-generated issues.

I converted it to discussion as this is definitely not airlfow issue - it has something to do with some helm testing that is not explained really.

I encourage you to explain in detail and show some examples of what problems you see and generally prove that you are human.