Add team_name tags to Kubernetes executor metrics

[SameerMesiah97]

Description

This change adds a team_name tag to Kubernetes executor metrics to improve per-team observability in multi-team deployments.

The following metrics now include the team_name tag when the executor is configured with a team:

• kubernetes_executor.pod_creation
• kubernetes_executor.pod_deletion
• kubernetes_executor.pod_patching
• kubernetes_executor.adopt_task_instances.duration
• kubernetes_executor.pod_creation_status
• kubernetes_executor.pod_deletion_status
• kubernetes_executor.pod_patching_status

The metric kubernetes_executor.clear_not_launched_queued_tasks.duration was not updated because it is no longer present in the current Kubernetes executor implementation.

With the exception of kubernetes_executor.adopt_task_instances.duration, all of the above metrics are emitted from AirflowKubernetesScheduler.

Rationale

The Kubernetes executor supports multi-team scheduling, but its operational metrics could not previously be attributed to individual teams. Adding the team_name tag enables per-team dashboards, alerting, and troubleshooting while remaining backwards compatible for deployments that do not use teams.

Notes

team_name is owned by KubernetesExecutor, while most of the affected metrics are emitted from AirflowKubernetesScheduler. To allow scheduler-emitted metrics to include the team_name tag, the value is passed to AirflowKubernetesScheduler when it is constructed by the executor.

For compatibility with previous Airflow releases, team_name is initialized only if it is not already defined, since the attribute was introduced as part of multi-team support.

Tests

Updated the existing unit tests for kubernetes_executor.pod_deletion and kubernetes_executor.pod_deletion_status to verify metrics are emitted both with and without the team_name tag. The test cases for team_name being present in the metrics are skipped when airflow version is less than 3.1.0 as the team_name attribute was added in version 3.1.0.

The following metrics do not currently have dedicated unit test coverage, so no test-related adjustments were made for them:

• kubernetes_executor.pod_creation
• kubernetes_executor.pod_creation_status
• kubernetes_executor.pod_patching
• kubernetes_executor.pod_patching_status
• kubernetes_executor.adopt_task_instances.duration

Backwards Compatibility

This change is additive only. Existing metric names remain unchanged, and the team_name tag is emitted only when the Kubernetes executor is configured with a team. Existing dashboards and integrations that do not use the new tag continue to function unchanged.

Related: #68996

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Generated-by: [GPT 5.5] following the guidelines

[ferruzzi]

I'd like to see the unit tests added for the missing paths. Improving the coverage while you are in there seems reasonable and they shouldn't be too difficult to follow the existing patterns.

[SameerMesiah97]

I'd like to see the unit tests added for the missing paths. Improving the coverage while you are in there seems reasonable and they shouldn't be too difficult to follow the existing patterns.

Okay. I was thinking of submitting a follow-up PR for them but I can them to this PR on your request.

[ferruzzi]

For these timers, can you run a manual test and confirm they work as intended? Technically this is a change; even if team_name is None, this will now be called with tags={} where previously it didn't get a tags at all. You may need to do something like tags=prune_dict(...) or None?

[justinpakzad]

Just chiming in here as I was doing some testing for amazon and I think we should be covered based on what I found here in the stats.py file:

airflow/shared/observability/src/airflow_shared/observability/metrics/stats.py

Lines 269 to 271 in 438107f

	regular_kw: dict[str, Any] = {**kwargs}
	if tags:
	regular_kw["tags"] = tags

Still worth running some manual tests but figured I'd share that.