openfga / helm-charts

Official Helm charts for the OpenFGA project.
https://openfga.dev
Apache License 2.0
18 stars 29 forks source link

openfga does not start as helm child #121

Open lachnerd opened 3 months ago

lachnerd commented 3 months ago

Checklist

Description

openfga does not start if deployed on azure aks as helm child chart using postgres database engine. the pod says:

Back-off restarting failed container wait-for-migration in pod

I also see no job that does the migration i think that might be the problem.

I tested locally with docker-dekstop-k8s everything works as expected:

Any clues or hints for me?

Expectation

openfga starts with postgres backend

Reproduction

integrate as child dependency add some yaml select postgres

Store data

model_file: |
  model
    schema 1.1
  type user
  type organization
    relations
      define member: [user]
tuples:
  - user: user:anne
    relation: member
    object: organization:openfga
  - user: user:bob
    relation: member
    object: organization:openfga
tests: # remove this if not a bug in Check or ListObjects API
  - name: test-1
    check:
      - user: user:anne
        object: organization:openfga
        assertions:
          member: true
    list_objects:
      - user: user:anne
        type: organization
        assertions:
          member:
            - organization:openfga

OpenFGA version

1.40

How are you running OpenFGA?

In Kubernetes

What datastore are you using?

Postgres

OpenFGA Flags

waitForMigrations: true

Logs

No response

jon-whit commented 3 months ago

@lachnerd I don't quite have enough information to troubleshoot this issue. Could you please provide the precise helm install ... command that is not behaving as you expect?

Also, what version of the Helm chart are you using?

helm search repo openfga -l

If you're not running the latest Helm chart version 0.1.41, then please helm update and verify you are running the latest.

Let's start there and we can troubleshoot further. Cheers 🍻

antangelo commented 1 month ago

I believe I have also run into this issue on version 0.2.4