A Helm chart for deploying the rindexer application. This chart supports integration with PostgreSQL and allows the injection of environment variables via an external Kubernetes Secret.

• Kubernetes 1.16+
• Helm 3.0+
• PersistentVolume provisioner support in the underlying infrastructure

To install the chart with the release name my-release:

helm install my-release ./rindexer

The command deploys the rindexer application on the Kubernetes cluster using the default configuration.

To uninstall/delete the my-release deployment:

helm uninstall my-release

This command removes all the Kubernetes components associated with the chart and deletes the release.

The following table lists the configurable parameters of the rindexer chart and their default values.

If PostgreSQL is enabled, the chart will configure the application to connect to it using the specified credentials.

To configure the Helm chart to use an external PostgreSQL database, you need to:

1. Set postgresql.enabled to true in the values.yaml file.
2. Create a Kubernetes Secret that contains the PostgreSQL credentials, including POSTGRES_PASSWORD and DATABASE_URL.
3. Specify the name of this secret in the externalSecret parameter in values.yaml.

Example configuration in values.yaml:

postgresql:
  enabled: true

externalSecret: "my-postgres-secret"

Your Kubernetes Secret (my-postgres-secret) should include the following keys:

• POSTGRES_PASSWORD: The password for the PostgreSQL user.
• DATABASE_URL: The connection URL for the PostgreSQL database.

Example command to create the Kubernetes Secret:

kubectl create secret generic my-postgres-secret   --from-literal=POSTGRES_PASSWORD=mysecretpassword   --from-literal=DATABASE_URL=postgres://user:mysecretpassword@host:5432/dbname

This setup ensures that the application can connect to an external PostgreSQL database using the provided credentials.

If you prefer to manage PostgreSQL credentials directly within the Helm chart, you can extend the values.yaml to include fields like username, password, host, port, and database.

Example configuration in values.yaml:

postgresql:
  enabled: true
  auth:
    username: "rindexer"
    password: "yourpassword"
    database: "rindexerdb"
    host: "localhost"
    port: "5432"

externalSecret: ""

The corresponding secret.yaml:

{{- if .Values.postgresql.enabled }}
{{- if not .Values.externalSecret }}
apiVersion: v1
kind: Secret
metadata:
  name: {{ include "rindexer.fullname" . }}-postgresql
  labels:
    {{- include "rindexer.labels" . | nindent 4 }}
type: Opaque
data:
  postgresql-password: {{ .Values.postgresql.auth.password | b64enc | quote }}
  database-url: {{ printf "postgres://%s:%s@%s:%s/%s" .Values.postgresql.auth.username .Values.postgresql.auth.password .Values.postgresql.auth.host .Values.postgresql.auth.port .Values.postgresql.auth.database | b64enc | quote }}
{{- end }}
{{- end }}

ingress:
  enabled: true
  annotations:
    kubernetes.io/ingress.class: "nginx"
    nginx.ingress.kubernetes.io/rewrite-target: /
  hosts:
    - host: rindexer.local
      paths:
        - path: /
          pathType: Prefix

ingress:
  enabled: true
  annotations:
    kubernetes.io/ingress.class: "alb"
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/ssl-redirect: "true"
    alb.ingress.kubernetes.io/certificate-arn: "arn:aws:acm:us-east-1:123456789012:certificate/your-certificate-arn"
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS": 443}]'
    alb.ingress.kubernetes.io/target-type: "ip"
    alb.ingress.kubernetes.io/backend-protocol: "HTTP"
  hosts:
    - host: rindexer.example.com
      paths:
        - path: /
          pathType: Prefix