kubeflow
/
pipelines
mirror of https://github.com/kubeflow/pipelines.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix(deployment): fix database name prefix description (#4198) 

* fix wording

* Update schema.yaml

* Update schema.yaml

Co-authored-by: Yuan (Bob) Gong <gongyuan94@gmail.com>
This commit is contained in:
Renmin 2020-07-10 15:22:16 +08:00 committed by GitHub
parent e5b19fb200
commit c615e3796c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
manifests/gcp_marketplace/schema.yaml
View File

@ -120,8 +120,8 @@ properties:
description: |-
Select this option to store pipeline artifacts and metadata using
Cloud SQL and Cloud Storage. Otherwise, pipeline artifacts and metadata
are stored on Compute Engine persistent disks.
are stored on Compute Engine persistent disks.
Cloud SQL and Cloud Storage provides better reliability and performance,
as well as features such as data backup and usage monitoring.
Using Cloud SQL and Cloud Storage is recommended for production
@ -184,8 +184,8 @@ properties:
description: |-
If you are deploying Kubeflow Pipelines with managed storage, specify the
database name prefix. The prefix value must contain only lowercase
letters, numbers, and hyphens, and the prefix must start with a letter.
letters, numbers and underscores. Additionally, the prefix must start with a letter.
During the deployment process, Kubeflow Pipelines creates two databases,
"<prefix>_pipeline" and "<prefix>_metadata". If the prefix specified
matches a previous deployment, this deployment will reuse the existing