Installing chart fails

[protectyrjewels]

Tried to install this chart with the following helmfile.yaml:

helmDefaults:
  wait: true
  waitForJobs: true
  atomic: true
  timeout: 90

repositories:
- name: backstage
  url:  https://backstage.github.io/charts

releases:
- name: backstage
  namespace: backstage
  chart: backstage/backstage

My pod is crashing with the following error message:

Loading config from MergedConfigSource{FileConfigSource{path="/app/app-config.yaml"}, EnvConfigSource{count=1}}
{"level":"info","message":"Found 1 new secrets in config that will be redacted","service":"backstage"}
{"level":"info","message":"Listening on :7007","service":"rootHttpRouter"}
/app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1496
          throw new Error(
                ^

Error: Failed to instantiate service 'core.httpRouter' for 'app' because the factory function threw an error, Error: Failed to instantiate service 'core.auth' for 'app' because the factory function threw an error, Error: Failed to instantiate service 'core.tokenManager' for 'app' because the factory function threw an error, Error: Failed to instantiate service 'core.tokenManager' because createRootContext threw an error, Error: You must configure at least one key in backend.auth.keys for production.
    at /app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1496:17
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async _ServiceRegistry.initializeEagerServicesWithScope (/app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1427:11)
    at async /app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1768:7
    at async Promise.all (index 0)
    at async BackendInitializer.doStart_fn (/app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1766:3)
    at async BackendInitializer.start (/app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1626:5)
    at async BackstageBackend.start (/app/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1894:5)

Node.js v18.20.2

Chart version: 1.9.2

Using ghcr.io/backstage/backstage:1.15.0 image works.

[cloudymax]

Seeing the same here, backend.auth.keys isnt defined anywhere in the chart or chart docs

[sabre1041]

Newer versions of Backstage have auth enabled by default. This results in the requirement to define a key for the authentication system. The following can be included within a customapp-config

backend:
  auth:
    keys:
      - secret: ${BACKEND_SECRET}

[hamzisco]

Newer versions of Backstage have auth enabled by default. This results in the requirement to define a key for the authentication system. The following can be included within a customapp-config

backend:
  auth:
    keys:
      - secret: ${BACKEND_SECRET}

Hi, how do I go about doing this exactly? Should I create an app-config.yaml file and kubectl apply it? Also for the secret can it just be literally anything? Apologies I am new to using k8s and helm and such 😅

[fordneild]

Im seeing that this keys: property is deprecated. I see this issue even when dangerouslyDisableDefaultAuthPolicy is set to true

[vinzscam]

Since Backstage 1.27, no secret is needed anymore, which should fix this issue.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.