**Current behaviour**
The disk indicator reports the following when a data node is yellow or red but has no indices.
- Symptom: 
> 1 node with roles: [data] is out of disk or running low on disk space.
- Impact: None
- Diagnosis:
> 0 indices reside on nodes that have run or are likely to run out of space, this can temporarily disable writing on these indices. 
> Enable autoscaling (if applicable), add disk capacity or free up disk space to resolve this. If you have already taken action please wait for the rebalancing to complete.

**Expected behaviour**
The disk indicator reports the following when a data node is yellow or red but has no indices.
- Symptom:
> 1 node with roles: [data] is out of disk or running low on disk space.
- Impact:
> 1 node with roles: [data] has run out or is likely to run out of disk space, this node cannot be used by the cluster to store data. `AREA: DEPLOYMENT_MANAGEMENT`
- Diagnosis:
> Disk is almost full.
> Enable autoscaling (if applicable), add disk capacity or free up disk space to resolve this. If you have already taken action please wait for the rebalancing to complete.

As an area of impact I added `DEPLOYMENT_MANAGEMENT` considering that this is not a healthy deployment if one node is not usable. I am trying to avoid listing `INGEST` since for now we can still ingest data. Any thoughts?

See: #90305
server/src/main/java/org/elasticsearch/health/node/DiskHealthIndicatorService.java
Map<String, DiskHealthInfo> diskHealthInfoMap = healthInfo.diskInfoByNode();
        if (diskHealthInfoMap == null || diskHealthInfoMap.isEmpty()) {
            /*
             * If there is no disk health info, that either means that a new health node was just elected, or something is seriously
             * wrong with health data collection on the health node. Either way, we immediately return UNKNOWN. If there are at least
             * some health info results then we work with what we have (and log any missing ones at debug level immediately below this).
             */
            return createIndicator(
                HealthStatus.UNKNOWN,
                "No disk usage data.",
                HealthIndicatorDetails.EMPTY,
                Collections.emptyList(),
                Collections.emptyList()
            );
        }
        ClusterState clusterState = clusterService.state();
        logNodesMissingHealthInfo(diskHealthInfoMap, clusterState);
        DiskHealthAnalyzer diskHealthAnalyzer = new DiskHealthAnalyzer(diskHealthInfoMap, clusterState);
        return createIndicator(
            diskHealthAnalyzer.getHealthStatus(),
            diskHealthAnalyzer.getSymptom(),
            diskHealthAnalyzer.getDetails(explain),
            diskHealthAnalyzer.getImpacts(),
            diskHealthAnalyzer.getDiagnoses()
        );
    }
    /**
     * This method logs if any nodes in the cluster state do not have health info results reported. This is logged at debug level and is
     * not ordinary important, but could be useful in tracking down problems where nodes have stopped reporting health node information.
     * @param diskHealthInfoMap A map of nodeId to DiskHealthInfo