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
@@ -156,6 +165,9 @@ Adapters use this endpoint to report their status.
156
165
157
166
**Request Body:**
158
167
168
+
<details>
169
+
<summary>JSON response</summary>
170
+
159
171
```json
160
172
{
161
173
"adapter": "validator",
@@ -188,8 +200,13 @@ Adapters use this endpoint to report their status.
188
200
}
189
201
```
190
202
203
+
</details>
204
+
191
205
**Response (201 Created):**
192
206
207
+
<details>
208
+
<summary>JSON response</summary>
209
+
193
210
```json
194
211
{
195
212
"adapter": "validator",
@@ -226,28 +243,9 @@ Adapters use this endpoint to report their status.
226
243
}
227
244
```
228
245
229
-
**Note**: The API automatically sets `created_time`, `last_report_time`, and `last_transition_time` fields.
230
-
231
-
### Status Conditions
232
-
233
-
The status uses Kubernetes-style conditions instead of a single phase field:
246
+
</details>
234
247
235
-
-**Ready** - Whether all adapters report successfully at the current generation
236
-
-`True`: All required adapters report `Available=True` at current spec generation
237
-
-`False`: One or more adapters report Available=False at current generation
238
-
- After every spec change, `Ready` becomes `False` since adapters take some time to report at current spec generation
239
-
- Default value when creating the cluster, when no adapters have reported yet any value
240
-
241
-
-**Available** - Aggregated adapter result for a common `observed_generation`
242
-
-`True`: All required adapters report Available=True for the same observed_generation
243
-
-`False`: At least one adapter reports Available=False when all adapters report the same observed_generation
244
-
- Default value when creating the cluster, when no adapters have reported yet any value
245
-
246
-
`Available` keeps its value unchanged in case adapters report from a different `observed_generation` or there is already a mix of `observed_generation` statuses
247
-
248
-
- e.g. `Available=True` for `observed_generation==1`
249
-
- One adapter reports `Available=False` for `observed_generation=1``Available` transitions to `False`
250
-
- One adapter reports `Available=False` for `observed_generation=2``Available` keeps its `True` status
248
+
**Note**: The API automatically sets `created_time`, `last_report_time`, and `last_transition_time` fields.
251
249
252
250
## NodePool Management
253
251
@@ -281,6 +279,9 @@ POST /api/hyperfleet/v1/clusters/{cluster_id}/nodepools/{nodepool_id}/statuses
281
279
282
280
**Response (201 Created):**
283
281
282
+
<details>
283
+
<summary>JSON response</summary>
284
+
284
285
```json
285
286
{
286
287
"kind": "NodePool",
@@ -307,7 +308,7 @@ POST /api/hyperfleet/v1/clusters/{cluster_id}/nodepools/{nodepool_id}/statuses
307
308
"status": "False",
308
309
"reason": "AwaitingAdapters",
309
310
"message": "Waiting for adapters to report status",
310
-
"observed_generation": 0,
311
+
"observed_generation": 1,
311
312
"created_time": "2025-01-01T00:00:00Z",
312
313
"last_updated_time": "2025-01-01T00:00:00Z",
313
314
"last_transition_time": "2025-01-01T00:00:00Z"
@@ -317,7 +318,7 @@ POST /api/hyperfleet/v1/clusters/{cluster_id}/nodepools/{nodepool_id}/statuses
317
318
"status": "False",
318
319
"reason": "AwaitingAdapters",
319
320
"message": "Waiting for adapters to report status",
320
-
"observed_generation": 0,
321
+
"observed_generation": 1,
321
322
"created_time": "2025-01-01T00:00:00Z",
322
323
"last_updated_time": "2025-01-01T00:00:00Z",
323
324
"last_transition_time": "2025-01-01T00:00:00Z"
@@ -327,12 +328,17 @@ POST /api/hyperfleet/v1/clusters/{cluster_id}/nodepools/{nodepool_id}/statuses
0 commit comments