Hard-code the name of the target repo's default branch instead of using the githubbranch parameter value

This commit is contained in:
Mengjiao Liu
2021-08-10 11:15:28 +08:00
parent 2bc25c1496
commit f945335af6
20 changed files with 33 additions and 33 deletions
@@ -632,7 +632,7 @@ of custom controller for those Pods. This allows the most flexibility, but may
complicated to get started with and offers less integration with Kubernetes.
One example of this pattern would be a Job which starts a Pod which runs a script that in turn
starts a Spark master controller (see [spark example](https://github.com/kubernetes/examples/tree/{{< param "githubbranch" >}}/staging/spark/README.md)), runs a spark
starts a Spark master controller (see [spark example](https://github.com/kubernetes/examples/tree/master/staging/spark/README.md)), runs a spark
driver, and then cleans up.
An advantage of this approach is that the overall process gets the completion guarantee of a Job