(You can keep publishing to DockerHub if you want, and then use a tool like crane cp to copy them to ghcr.io.)
DockerHub has fairly aggressive rate-limits for image downloads (100 or 200 pulls per 6 hours per IP address). Since these charts don't ensure that the namespace has credentials for pulling the images, OpenFGA can fail if some other namespace blows through the DockerHub rate limits for the cluster.
ghcr.io does not have these pull limitations, and is also free for open-source projects. I'd suggest switching the default image repository for the helm chart to point to ghcr.io to avoid these issues for users (which typically only happen when something else is also having a bad day).
(You can keep publishing to DockerHub if you want, and then use a tool like
crane cpto copy them toghcr.io.)DockerHub has fairly aggressive rate-limits for image downloads (100 or 200 pulls per 6 hours per IP address). Since these charts don't ensure that the namespace has credentials for pulling the images, OpenFGA can fail if some other namespace blows through the DockerHub rate limits for the cluster.
ghcr.iodoes not have these pull limitations, and is also free for open-source projects. I'd suggest switching the default image repository for the helm chart to point toghcr.ioto avoid these issues for users (which typically only happen when something else is also having a bad day).Another option may be to apply for the Docker Open Source Project program, but switching to
ghcr.ioseems likely to be just as easy.