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

Backstage Helm Charts - AWS RDS Support #25

Closed
regicsolutions opened this issue Dec 12, 2020 · 3 comments
Closed

Backstage Helm Charts - AWS RDS Support #25

regicsolutions opened this issue Dec 12, 2020 · 3 comments

Comments

@regicsolutions
Copy link

Is there any documentation on using an RDS PostgreSQL database vs using the baked in bitnami PostgreSQL image? i see the flag in values.yml but wasn't sure how the rest of the PostgreSQL configuration and keys were handled. My assumption is if rds is enabled PostgreSQL flags should be disabled?

I am looking to create 2 pods a frontend and backend that connects out to a PostgreSQL db in AWS RDS.

@martina-if
Copy link
Contributor

martina-if commented Dec 14, 2020

Hi @regicsolutions , thanks for bringing this up. I will try to add some documentation for this. Let me also explain below how to do that. Please note that these charts are used by Roadie internally and are not necessarily useful for other use cases. You can find the general Backstage charts here and the documentation here.

  1. The rds.enabled is only used to add the AWS RDS CA to a config map that can be mounted into backstage-backend and lighthouse.

  2. When postgresql.enabled=true this chart will also deploy a bitnami postgresql instance and make sure that the backstage backend and lighthouse are connected to it. In your case, I would leave this disabled.

  3. To configure access to your RDS instance you can follow these instructions.

kubectl create configmap my-company-backstage-postgres-ca --from-file=ca.crt
postgresql:
  enabled: false

appConfig:
  app:
    baseUrl: https://backstage-demo.mydomain.com
    title: Backstage
  backend:
    baseUrl: https://backstage-demo.mydomain.com
    cors:
      origin: https://backstage-demo.mydomain.com
    database:
      client: pg
      connection:
        database: backstage_plugin_catalog
        host: <host>
        user: <pg user>
        password: <password>
  lighthouse:
    baseUrl: https://backstage-demo.mydomain.com/lighthouse-api

lighthouse:
  database:
    client: pg
    connection:
      host: <host>
      user: <pg user>
      password: <password>
      database: lighthouse_audit_service

@martina-if
Copy link
Contributor

@regicsolutions We have decided we will be making these charts private. Please use the charts from the upstream backstage repo instead.

@punkle
Copy link
Contributor

punkle commented Jun 21, 2021

Hi @regicsolutions we have removed the backstage helm-chart from here. Please use the public chart. We are happy to help you where we can, but we will not be supporting charts from this location any more.

I will close this issue.

@punkle punkle closed this as completed Jun 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants