Add k8s pod/cluster attributes to PENDING status span

[morgan-wowk]

Add Kubernetes pod/cluster attributes to PENDING execution spans

k8s.pod.name, k8s.namespace.name, k8s.cluster.url sourced from
ContainerExecution.launcher_data. Handles kubernetes, kubernetes_job,
and non-k8s launchers (SkyPilot) gracefully via early-return guards.

The new _launcher_pod_attrs helper only emits attributes when the span
status is PENDING and launcher_data is present, so spans for other
statuses or non-Kubernetes launchers are unaffected.

Screenshots

[morgan-wowk]

• Add CPU, memory, and accelerator resource requests to PENDING span #258
• Add pipeline/parent context to root execution span #257
• Add cache hit/miss context to root execution span #256
• Add launcher type and cluster URL to root execution span #255
• Add k8s pod/cluster attributes to PENDING status span #254 👈 (View in Graphite)
• Enrich error/success status spans with failure context #253
• Add retroactive OTel execution lifecycle tracing #252
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[yuechao-qin]

Curious

• tangle-orchestrator-local - What does "local" mean and what other values can be possible there?
• what is otel.scope.name and where is it set in the code?
• span.kind what is "internal" and what other values are possible?

[morgan-wowk]

🤖 Re: review questions —

• tangle-orchestrator-local — the suffix comes from APP_ENV (or TANGLE_ENV in the OSS layer), passed as service_name=f"tangle-orchestrator-{tangle_env}" in orchestrator_main_oasis.py. In production it becomes tangle-orchestrator-production. Other services: tangle-api-{env}, tangle-metrics-poller-{env}.
• otel.scope.name — set by trace.get_tracer("tangle.orchestrator") at module level. OTel SDK populates it automatically.
• span.kind: INTERNAL — OTel default when no explicit kind is set. Other values: SERVER, CLIENT, PRODUCER, CONSUMER. Internal is correct here since these are in-process reconstructed spans, not representing network boundaries.

[morgan-wowk]

Merge activity

• Jun 5, 5:07 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jun 5, 5:09 PM UTC: Graphite rebased this pull request as part of a merge.
• Jun 5, 5:09 PM UTC: @morgan-wowk merged this pull request with Graphite.