You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 2, 2024. It is now read-only.
When installing this to a Vanilla Kubernetes cluster, the liveness checks never complete as they poll the http port, which never returns. Changing this from -
results in postgres being unreachable.
Modifying to the postgres port resolves this.
Backstage pod log -
�[2m2022-11-14T11:19:12.366Z�[22m �[34mbackstage�[39m �[32minfo�[39m Loaded config from app-config.yaml
�[2m2022-11-14T11:19:12.397Z�[22m �[34mbackstage�[39m �[32minfo�[39m 0 secret found in the config which will be redacted
�[2m2022-11-14T11:19:12.425Z�[22m �[34mbackstage�[39m �[32minfo�[39m Created UrlReader predicateMux{readers=azure{host=dev.azure.com,authed=false},bitbucketCloud{host=bitbucket.org,authed=false},github{host=github.com,authed=false},gitlab{host=gitlab.com,authed=false},awsS3{host=amazonaws.com,authed=false},fetch{}
Backend failed to start up Error: Failed to connect to the database to make sure that 'backstage_plugin_catalog' exists, Error: getaddrinfo ENOTFOUND backstage-postgresql.default.svc
at /opt/app-root/src/node_modules/@backstage/backend-common/dist/index.cjs.js:1015:17
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async CatalogBuilder.build (/opt/app-root/src/node_modules/@backstage/plugin-catalog-backend/dist/index.cjs.js:4092:22)
at async createPlugin$4 (/opt/app-root/src/packages/backend/dist/index.cjs.js:62:40)
at async main (/opt/app-root/src/packages/backend/dist/index.cjs.js:206:29)
Backstage-postgres endpoint
NAME ENDPOINTS AGE
backstage x.x.x.x:7007 10d
backstage-postgresql <none> 10d
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When installing this to a Vanilla Kubernetes cluster, the liveness checks never complete as they poll the http port, which never returns. Changing this from -
to this -
The secondary failure is the postgres service.
results in postgres being unreachable.
Modifying to the postgres port resolves this.
Backstage pod log -
Backstage-postgres endpoint
The text was updated successfully, but these errors were encountered: