Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] GCP marketplace default config values do not work #5717

Closed
Bobgy opened this issue May 21, 2021 · 5 comments · Fixed by #5777
Closed

[bug] GCP marketplace default config values do not work #5717

Bobgy opened this issue May 21, 2021 · 5 comments · Fixed by #5777

Comments

@Bobgy
Copy link
Contributor

Bobgy commented May 21, 2021

What steps did you take

  1. Install KFP from AI Platform Pipelines
  2. check managed storage
  3. fill in db connection name and gcs bucket name
  4. leave the rest as empty

What happened:

All the default values are filled by empty strings.

What did you expect to happen:

I was expecting default values in values.yaml are set, e.g.

databaseNamePrefix: '{{ .Release.Name | replace "-" "_" | replace "." "_" }}'
.

However, I verified that cache configmap in fact has db name as _cache without the prefix.

Labels

/area deployment


Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

@Bobgy Bobgy added the kind/bug label May 21, 2021
@google-oss-robot
Copy link

@Bobgy: The label(s) area/deployment cannot be applied, because the repository doesn't have them.

In response to this:

What steps did you take

  1. Install KFP from AI Platform Pipelines
  2. check managed storage
  3. fill in db connection name and gcs bucket name
  4. leave the rest as empty

What happened:

All the default values are filled by empty strings.

What did you expect to happen:

I was expecting default values in values.yaml are set, e.g.

databaseNamePrefix: '{{ .Release.Name | replace "-" "_" | replace "." "_" }}'
.

Labels

/area deployment


Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Bobgy
Copy link
Contributor Author

Bobgy commented Jun 1, 2021

@Bobgy
Copy link
Contributor Author

Bobgy commented Jun 2, 2021

Cases we need to test after the release:

  • when deploying with managed storage, leave db username as empty, and verify it defaults to "root".
  • similarly leave databasePrefixName as empty, verify dbs are created as _cache, _pipeline etc.

@Bobgy Bobgy mentioned this issue Jun 2, 2021
23 tasks
google-oss-robot pushed a commit that referenced this issue Jun 2, 2021
…when some fields left empty. Fixes #5717 (#5777)

* fix(deployment): GCP AI Platform Pipelines -- correct default values when some fields left empty

* backward compatible databaseNamePrefix behavior
@Bobgy Bobgy reopened this Jun 2, 2021
@Bobgy
Copy link
Contributor Author

Bobgy commented Jun 2, 2021

Reopen to wait for verification

@Bobgy
Copy link
Contributor Author

Bobgy commented Aug 11, 2021

Now the database username defaults to "root" on the UI.
image

@Bobgy Bobgy closed this as completed Aug 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants