fix: docs

Signed-off-by: shuangkun <[email protected]>

docs/container-set-template.md

@@ -116,3 +116,9 @@ Example B: Lopsided requests, e.g. `a -> b` where `a` is cheap and `b` is expens
 Can you see the problem here? `a` only has small requests, but the container set will use the  total of all requests. So it's as if you're using all that GPU for 10h. This will be expensive.
 
 Solution: do not use container set when you have lopsided requests.
+
+## ContainerSetRetryStrategy
+
+ContainerSetRetryStrategy describes how to retry a container nodes in the container set if it fails. 
+Nbr of retries(default 0) and sleep duration between retries(default 0s, instant retry) can be set.
+The shell command should be normal otherwise it will not be retried.

pkg/apis/workflow/v1alpha1/container_set_template_types.go

@@ -14,6 +14,7 @@ type ContainerSetTemplate struct {
 	VolumeMounts []corev1.VolumeMount `json:"volumeMounts,omitempty" protobuf:"bytes,3,rep,name=volumeMounts"`
 	// RetryStrategy describes how to retry a container nodes in the container set if it fails.
 	// Nbr of retries(default 0) and sleep duration between retries(default 0s, instant retry) can be set.
+	// The shell command should be normal otherwise it will not be retried.
 	RetryStrategy *ContainerSetRetryStrategy `json:"retryStrategy,omitempty" protobuf:"bytes,5,opt,name=retryStrategy"`
 }