chore(workflow-cli): pts:describe cmd add Startup field and healthchecks usage

Author: jianxiaoguo

cmd/pts.go

@@ -169,6 +169,10 @@ func printProcessTypeDetail(d *DryccCmd, ptypeStates api.PtypeStates, events api
 				tpt.Append([]string{"", fmt.Sprintf("%s from %s", mount.MountPath, mount.Name)})
 			}
 		}
+		sp := getHealthcheckString("", "", &containerState.StartupProbe)
+		if sp != "" {
+			tpt.Append([]string{"Startup:", strings.TrimSpace(sp)})
+		}
 		lp := getHealthcheckString("", "", &containerState.LivenessProbe)
 		if lp != "" {
 			tpt.Append([]string{"Liveness:", strings.TrimSpace(lp)})

go.mod

@@ -21,3 +21,5 @@ require (
 	github.com/pmezard/go-difflib v1.0.0 // indirect
 	golang.org/x/sys v0.18.0 // indirect
 )
+
+replace github.com/drycc/controller-sdk-go => github.com/jianxiaoguo/controller-sdk-go v0.0.0-20240711022759-a09abdeedfea

go.sum

@@ -4,12 +4,12 @@ github.com/davecgh/go-spew v1.1.1 h1:vj9j/u1bqnvCEfJOwUhtlOARqs3+rkHYY13jYWTU97c
 github.com/davecgh/go-spew v1.1.1/go.mod h1:J7Y8YcW2NihsgmVo/mv3lAwl/skON4iLHjSsI+c5H38=
 github.com/docopt/docopt-go v0.0.0-20180111231733-ee0de3bc6815 h1:bWDMxwH3px2JBh6AyO7hdCn/PkvCZXii8TGj7sbtEbQ=
 github.com/docopt/docopt-go v0.0.0-20180111231733-ee0de3bc6815/go.mod h1:WwZ+bS3ebgob9U8Nd0kOddGdZWjyMGR8Wziv+TBNwSE=
-github.com/drycc/controller-sdk-go v0.0.0-20240710072101-82db20de8e4a h1:ETfWMgVW7ZR5PqFwnaCYbZHsejFym/vPdsv5RLTjNkE=
-github.com/drycc/controller-sdk-go v0.0.0-20240710072101-82db20de8e4a/go.mod h1:n6eQe1irJqjwLo/7t9+Dhdv6faSESQN+ATnZRBP3/Uc=
 github.com/drycc/pkg v0.0.0-20240225112316-78fc9239f51f h1:kgjvUQJeAszDoU1Vo4vTTE92KI8Av3JPb6Qn890niXg=
 github.com/drycc/pkg v0.0.0-20240225112316-78fc9239f51f/go.mod h1:n+QxGif6ha9CEoxVnlipxb9IdmerybcUSzTEDFkvjiA=
 github.com/google/go-cmp v0.5.9 h1:O2Tfq5qg4qc4AmwVlvv0oLiVAGB7enBSJ2x2DqQFi38=
 github.com/google/go-cmp v0.5.9/go.mod h1:17dUlkBOakJ0+DkrSSNjCkIjxS6bF9zb3elmeNGIjoY=
+github.com/jianxiaoguo/controller-sdk-go v0.0.0-20240711022759-a09abdeedfea h1:okAAbWoGmFBtVwSl451+CHlhRl+sxXQ36wbnPLKMqN8=
+github.com/jianxiaoguo/controller-sdk-go v0.0.0-20240711022759-a09abdeedfea/go.mod h1:n6eQe1irJqjwLo/7t9+Dhdv6faSESQN+ATnZRBP3/Uc=
 github.com/mattn/go-runewidth v0.0.9 h1:Lm995f3rfxdpd6TSmuVCHVb/QhupuXlYr8sCI/QdE+0=
 github.com/mattn/go-runewidth v0.0.9/go.mod h1:H031xJmbD/WCDINGzjvQ9THkh0rPKHF+m2gUSrubnMI=
 github.com/olekukonko/tablewriter v0.0.5 h1:P2Ga83D34wi1o9J6Wh1mRuqd4mF/x/lgBS7N7AbDhec=

parser/healthchecks.go

@@ -82,16 +82,20 @@ Sets healthchecks for an application.
 
 By default, Workflow only checks that the application starts in their Container. A health
 check may be added by configuring a health check probe for the application. The health
-checks are implemented as Kubernetes Container Probes. A 'liveness' and a 'readiness'
-probe can be configured, and each probe can be of type 'httpGet', 'exec' or 'tcpSocket'
-depending on the type of probe the Container requires.
+checks are implemented as Kubernetes Container Probes. A 'startupProbe' 'livenessProbe' 
+and a 'readinessProbe' can be configured, and each probe can be of type 'httpGet', 'exec' 
+or 'tcpSocket' depending on the type of probe the Container requires.
 
-A 'liveness' probe is useful for applications running for long periods of time, eventually
+A 'startupProbe' indicates whether the application within the container is started.
+All other probes are disabled if a startup probe is provided, until it succeeds.
+If the startup probe fails, the container is subjected to its restart policy.
+
+A 'livenessProbe' is useful for applications running for long periods of time, eventually
 transitioning to broken states and cannot recover except by restarting them.
 
-Other times, a 'readiness' probe is useful when the Container is only temporarily unable
-to serve, and will recover on its own. In this case, if a Container fails its 'readiness'
-probe, the Container will not be shut down, but rather the Container will stop receiving
+Other times, a 'readinessProbe' is useful when the Container is only temporarily unable
+to serve, and will recover on its own. In this case, if a Container fails its 'readinessProbe'
+, the Container will not be shut down, but rather the Container will stop receiving
 incoming requests.
 
 'httpGet' probes are just as it sounds: it performs a HTTP GET operation on the Container.
@@ -110,7 +114,7 @@ Usage: drycc healthchecks:set <health-type> <probe-type> [options] [--] <args>..
 
 Arguments:
   <health-type>
-    the healthcheck type, such as 'livenessProbe' or 'readinessProbe'.
+    the healthcheck type, such as 'startupProbe' 'livenessProbe' or 'readinessProbe'.
   <probe-type>
     the healthcheck probe type, such as 'httpGet', 'exec' or 'tcpSocket'.
   <args>