Skip to content

Commit

Permalink
add ns create before create secret and add a notes about pipeline cli
Browse files Browse the repository at this point in the history
Signed-off-by: LiZhenCheng9527 <[email protected]>
  • Loading branch information
LiZhenCheng9527 committed Jan 17, 2024
1 parent fded0e7 commit c6c8269
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 0 deletions.
1 change: 1 addition & 0 deletions docs/content/en/docs/pipeline/operation.md
Original file line number Diff line number Diff line change
Expand Up @@ -177,6 +177,7 @@ Kurator's CLI provides a very convenient way to view the execution status of a p
which user can directly list all the pipeline execution and access all task execution logs with a specific command.

You can view the execution instance of the currently triggered pipeline using the following command.
Note: You need to specify the kubeconfig file to use via the `--kubeconfig` flag in the command line, even if you are running the Kurator Pipeline in a single cluster environment.

```console
$ kurator pipeline execution list -n kurator-pipeline --kubeconfig /root/.kube/kurator-host.config
Expand Down
2 changes: 2 additions & 0 deletions docs/content/en/docs/pipeline/setting.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,8 @@ Since the first task in a pipeline often involves pulling code from a Git reposi
This can be done by creating a Kubernetes secret containing the authentication details. Use the following command to create this secret:

```console
kubectl create ns kurator-pipeline

kubectl create secret generic git-credentials \
--namespace=kurator-pipeline \
--from-literal=.gitconfig=$'[credential "https://github.com"]\n\thelper = store' \
Expand Down

0 comments on commit c6c8269

Please sign in to comment.