add required labels to keptn task definition

Signed-off-by: Moritz Wiesinger <[email protected]>
keptn · Oct 31, 2023 · 2489ab0 · 2489ab0
1 parent e35b110
commit 2489ab0
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/docs/content/en/docs/yaml-crd-ref/taskdefinition.md b/docs/content/en/docs/yaml-crd-ref/taskdefinition.md
@@ -87,7 +87,7 @@ spec:
     [Kubernetes Object Names and IDs](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names)
     specification.
 * **spec**
-  * **deno | python | container** -- Define the container type
+  * **deno | python | container** (required) -- Define the container type
   to use for this task.
   Each task can use one type of runner,
   identified by this field:
@@ -107,10 +107,10 @@ spec:
       and code the functionality to match the container you define.
       See
       [Synopsis for container-runtime container](#synopsis-for-container-runtime).
-  * **retries** (optional) -- specifies the number of times
+  * **retries** -- specifies the number of times
     a job executing the `KeptnTaskDefinition`
     should be restarted if an attempt is unsuccessful.
-  * **timeout** (optional) -- specifies the maximum time
+  * **timeout** -- specifies the maximum time
     to wait for the task to be completed successfully.
     The value supplied should specify the unit of measurement;
     for example, `5s` indicates 5 seconds and `5m` indicates 5 minutes.