How to: databricks runtime 104 lts eol inventory

Use this local guide before 2026-11-01. Re-check official vendor documentation for authoritative dates. This site does not call vendor APIs or store tokens.

1. Step 1. Confirm 10.4 LTS EoL Nov 1 2026 and EoS Mar 18 2025 on Azure Databricks EOS table
2. Step 2. Query system.compute.clusters / job definitions for spark_version containing 10.4
3. Step 3. Scan Terraform/Pulumi/CI for spark_version literals pinned to 10.4*
4. Step 4. Mark each hit: workspace, cluster-or-job, owner, whether only API-create remains post-EoS
5. Step 5. Choose target supported LTS and note Spark behavior diffs to retest
6. Step 6. Check cluster policies still allow 10.4 and block them before EoL
7. Step 7. Retire or upgrade pools/instance groups still advertising 10.4
8. Step 8. Export Markdown residue list with official EOS URLs into the change ticket

Related: FAQ · Use cases · Home tool. Always prefer official vendor documentation for authoritative dates. Export your Markdown pack into the change ticket with the official URLs listed on the home page.

Context for operators: Databricks Runtime 10.4 LTS EOL Nov1 2026 — clusters/jobs still pinned to spark_version 10.4 (data platform Runtime domain). The gap this wedge fills: 官方 EoS 表线性；缺「spark_version 含 10.4」多 workspace 残留盘点+owner 导出。不做 Databricks 控制台 SaaS。 Keep owners assigned on every residue row so nothing silently slips past the deadline. When in doubt, re-open the official source pages rather than trusting a cached screenshot.