bump(charts): v1.0.0-alpha.8

[sabineschaller]

Why does the action complain about

npm ERR! Missing script: "knex -- migrate:latest --env production"

Is that something in another PR that needs to go in first for this to not fail?

[golobitch]

Why does the action complain about

npm ERR! Missing script: "knex -- migrate:latest --env production"

Is that something in another PR that needs to go in first for this to not fail?

The problem was in wrong command. I fixed that and also added env so that it will now where to connect. This has been tested locally and it works now. Now the next challenge will be to install also postgresql into our pipeline + redis, to be 100% sure that everything is working. I will create separate ticket for that.

[sabineschaller]

Now we get

failed installing charts: failed processing charts
Error: Process completed with exit code 1.

[golobitch]

Now we get

failed installing charts: failed processing charts
Error: Process completed with exit code 1.

This is general error, however, we can see few different errors here https://github.com/interledger/helm-charts/actions/runs/8636782800/job/23677473710

For example, look at line #151

getaddrinfo ENOTFOUND postgres.example.com
Error: getaddrinfo ENOTFOUND postgres.example.com
    at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26)

This is in init containers. It tries to run migrations manually in init containers, however, values are just an example values added. And also, it doesn't have any postgresql installed on this system. This is the same for rafiki-auth and rafiki-backend. It was tested locally with minikube and it works.

Furthermore, if we check line #430 we can see that frontend is failing due to that already known remix issue :)

This remix issue is easy solvable, but that with postgresql is not :)

[golobitch]

Moved to #35