From 3ef973976b3b6ffd9f5ce218b96cfd57a5ebadf5 Mon Sep 17 00:00:00 2001 From: Sheng Liang Date: Sat, 29 Sep 2018 20:47:40 -0700 Subject: [PATCH] Fix pipeline doc -- image in internal registry can only be used inside the pipeline --- content/rancher/v2.x/en/tools/pipelines/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/tools/pipelines/_index.md b/content/rancher/v2.x/en/tools/pipelines/_index.md index 9714d93d2aa..c2598d90e9d 100644 --- a/content/rancher/v2.x/en/tools/pipelines/_index.md +++ b/content/rancher/v2.x/en/tools/pipelines/_index.md @@ -65,7 +65,7 @@ When you configure a pipeline in one of your projects, a namespace specifically - **Docker Registry:** - Out-of-the-box, the default target for your build-publish step is an internal Docker Registry. However, you can make configurations to push to a remote registry instead. The internal Docker Registry is only accessible from cluster nodes and cannot be directly accessed by users. Images are not persisted across multiple pipeline runs. If you need to access your images outside of a single pipeline run, please push to an external registry. + Out-of-the-box, the default target for your build-publish step is an internal Docker Registry. However, you can make configurations to push to a remote registry instead. The internal Docker Registry is only accessible from cluster nodes and cannot be directly accessed by users. Images are not persisted beyond the lifetime of the pipeline and should only be used in pipeline runs. If you need to access your images outside of pipeline runs, please push to an external registry.