Extend the chart to support to create the ingress resource. #5

[cmoulliard]

What

• Extend the existing helm chart to support to create the ingress resource.
• Add a new ingress template
• Add within the values.yaml files the new ingress parameter See issue #5

How to

• Create a backstage project using command npx @backstage/create-app
• Add the missing package and build/push the image

  yarn add --cwd packages/backend better-sqlite3
  yarn build
  yarn build-image -t backstage:dev
  kind load docker-image backstage:dev

• Create a configmap

  DOMAIN_NAME="192.168.1.90.nip.io"
  cat <<EOF > $HOME/backstage/app-config.extra.yaml
  app:
  baseUrl: http://backstage.$DOMAIN_NAME
  title: Backstage
  backend:
  baseUrl: http://backstage.$DOMAIN_NAME
  cors:
  origin: http://backstage.$DOMAIN_NAME
  
  # This is for local development only, it is not recommended to use this in production
  # The production database configuration is stored in app-config.production.yaml
  database:
  client: better-sqlite3
  connection: ':memory:'
  cache:
  store: memory
  techdocs:
  builder: 'local' # Alternatives - 'external'
  generator:
  runIn: 'docker' # Alternatives - 'local'
  publisher:
  type: 'local' # Alternatives - 'googleGcs' or 'awsS3'. Read documentation for using alternatives.    
  EOF

• Create the values.yaml fileto be used to install the helm chart

  cat <<EOF > $HOME/backstage/my-values.yml
  ingress:
  enabled: true
  host: backstage.$DOMAIN_NAME
  backstage:
  image:
  registry: "docker.io/library"
  repository: "backstage"
  tag: "dev"
  extraAppConfig:
  - filename: app-config.extra.yaml
    configMapRef: my-app-config      
  EOF

• deploy the helm chart and configmap

  helm install -f $HOME/backstage/my-values.yml --create-namespace -n backstage my-backstage ./charts/backstage
  kubectl create configmap my-app-config -n backstage --from-file=app-config.extra.yaml=$HOME/backstage/app-config.extra.yaml

[cmoulliard]

Can you approve it please to merge the code ? @vinzscam