You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The KAI operator reports installation health on `Config.status.conditions`. The most relevant condition types are:
77
+
78
+
- `Deployed`: the operator created the Kubernetes resources for KAI services.
79
+
- `Available`: the KAI service controllers report availability.
80
+
- `DependenciesFulfilled`: external dependencies required by the selected configuration are present and healthy.
81
+
- `Ready`: the KAI services are available.
82
+
83
+
When `global.gpuSharingMode` is `NvFractions`, the KAI operator also checks the cluster-scoped `GpuSharingConfig` resource from the GPU-sharing operator, as running fractional GPU pods depends on it.
84
+
85
+
If all KAI services are deployed and available, but the GPU-sharing operator reports a dependency failure, the KAI `Config` can look like this:
86
+
87
+
```yaml
88
+
apiVersion: kai.scheduler/v1
89
+
kind: Config
90
+
metadata:
91
+
name: kai-config
92
+
spec:
93
+
global:
94
+
gpuSharingMode: NvFractions
95
+
status:
96
+
conditions:
97
+
- type: Deployed
98
+
status: "True"
99
+
reason: deployed
100
+
message: Resources deployed
101
+
- type: Available
102
+
status: "True"
103
+
reason: available
104
+
message: System available
105
+
- type: DependenciesFulfilled
106
+
status: "False"
107
+
reason: dependencies_missing
108
+
message: Gpu Sharing is not ready. Ready=False, reason=GPUOperatorNotReady, message=ClusterPolicy is not ready
109
+
- type: Ready
110
+
status: "True"
111
+
reason: ready
112
+
message: System is ready
113
+
```
114
+
115
+
In this state the KAI pods are healthy, but NvFractions should not be considered fully operational until `DependenciesFulfilled=True`. The dependency message carries the GPU-sharing operator's config-level status reason and message so the failing external dependency is visible directly from the KAI `Config`.
116
+
74
117
## Logging
75
118
76
119
By default all KAI services use development-mode logging with colored, human-readable console
0 commit comments