Flagsmith/flagsmith-charts

helm chart 16.0 and 16.1 frontend failing to function properly

io-blaws opened this issue · 5 comments

io-blaws commented

Using fluxcd for auto-upgrading the helm chart that deploys to my kubernetes cluster.
With the release of 0.16.0 and 0.16.1, when I try to login to the frontend authentication seems to be getting attempted at https://api-staging.flagsmith.com instead of my local exposed api endpoint. Rolling back to 0.15.0 of the chart restores the functionality of the frontend.

I did not know if this was an error in the helm chart or in the build of the container for frontend explicitly. I decided to post here first in case it was an environment variable issue that was missed while incorporating the latest frontend to the helm charts.

dabeeeenster commented

Thanks for this - sounds like an error on our part - sorry! We'll take a look... cc @matthewelwell

  • 👍1
io-blaws commented

there is also a constant poll out to edge.api.flagsmith.com with a local deployment of the frontend. makes a "Staging Environment" banner show up in the UI.

matthewelwell commented

@plumdog I've had a little look into this. I have a feeling it's likely caused by the upgrade in the app version here but I was surprised to see that we're seemingly not setting the FLAGSMITH_API env var anywhere in the frontend container (apart from when running the E2E tests). Do you know why that is?

matthewelwell commented

This should be fixed in 16.2.

matthewelwell commented

re is also a constant poll out to edge.api.flagsmith.com with a local deployment of the frontend. makes a "Staging Environment" banner show up in the UI.

This is covered here: Flagsmith/flagsmith#2077 but can be resolved by configuring your own Flagsmith on Flagsmith project as described here: https://docs.flagsmith.com/deployment/overview#running-flagsmith-on-flagsmith