Components, operators and builders resources not created when installing Yatai with postgresql.enabled=false about yatai HOT 10 CLOSED

Hi @parano, thanks for your answer.
Indeed I am writing a yatai install script, including creation of cloud resources (RDS, S3 bucket, secrets), so that I can install several development and testing environments in an automated way.

from yatai.

Hey @amelki

Thank you for reporting the issue, really appreciate it. I am looking to the issue.

I would love you to clarify a few things for me

1. What version of yatai chart you are using?
2. did you have the database yatai created in your Postgresql?
3. Are you able to access the yatai UI? Is the yatai service running successfully?
4. if you are not able to, can you share with me the log of the crashed yatai service? You can find the crashed logs with

kubectl logs <POD_NAME> --previous -n yatai-system

from yatai.

cc @yetone

from yatai.

Hey @yubozhao

1. What version of yatai chart you are using?

The latest one, in https://bentoml.github.io/yatai-char

2. did you have the database yatai created in your Postgresql?

Yes : I first installed Yatai with an embedded Postgresql. Then I upgraded with an external RDS, which created the yatai database at some point.
Then I deleted the Yatai release from my K8s cluster, but kept the yatai database in my RDS instance. And when I reinstall the helm chart, referencing my RDS instance, components, operators and builders resources are not created
Maybe this is the issue. Shall I retry from an empty RDS database ?

3. Are you able to access the yatai UI? Is the yatai service running successfully?

If I install the charts with postgresql=true first, first and then upgrade with my external RDS, yes, I end up with a properly installed Yatai

4. if you are not able to, can you share with me the log of the crashed yatai service? You can find the crashed logs with

kubectl logs <POD_NAME> --previous -n yatai-system

from yatai.

@amelki Yes, you should either retry from an empty RDS database or manually install the yatai deployment component in the yatai UI.

from yatai.

Guys, I see you reopened the issue. I just tried to reinstall Yatai with an empty RDS database, and it does not seem to work either... Do you confirm ?

from yatai.

OK, I had to manually create the yatai DB in my RDS instance, and it worked OK

from yatai.

@amelki The thing is, when you tell yatai the name of the database, yatai will think that the database is already created

from yatai.

@yetone that is fine with me, I have adapted my install scripts to make sure the DB always exists and is empty when the helm charts are installed. I guess you can close the issue.

from yatai.

Thanks for the update @amelki - our team dive into the issue a bit more and this is definitely something we should improve in documentation. The root cause of the issue is due to installing Yatai helm chat with a database that has information on a previous installation. A regular installation from clean state should not run into this issue.

Yatai has a fairly complex architecture with multiple cluster components, both migrating to a new installation or reinstalling yatai from old DB requires a few extra steps to make sure the cluster state and DB state are in-sync. Our team will work on related documentation soon, as for now, we'd suggest try installing from a clean state as you did in your install script.

It sounds like you are trying to write a script that reinstalls Yatai, may I ask what is this used for? Is it for testing purpose?

from yatai.