Skip to content

Commit 451e915

Browse files
authored
Tweak advice about API group for Workload
1 parent b15d84a commit 451e915

File tree

1 file changed

+4
-1
lines changed
  • content/en/docs/concepts/workloads/workload-api

1 file changed

+4
-1
lines changed

content/en/docs/concepts/workloads/workload-api/_index.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,10 @@ the Workload API is supposed to provide scheduling constraints for the "true" wo
1616
## What is a Workload?
1717

1818
The Workload API resource is part of the `scheduling.k8s.io/v1alpha1`
19-
{{< glossary_tooltip text="API group" term_id="api-group" >}}.
19+
{{< glossary_tooltip text="API group" term_id="api-group" >}}
20+
(and your cluster must have that API group enabled, as well as the `GenericWorkload`
21+
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/),
22+
before you can benefit from this API).
2023
This resource acts as a structured, machine-readable definition of the scheduling requirements
2124
of a multi-Pod application. While user-facing workloads like [Jobs](/docs/concepts/workloads/controllers/job/)
2225
define what to run, the Workload resource determines how a group of Pods should be scheduled

0 commit comments

Comments
 (0)