You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, it seems like main Unleash Helm is requesting tag with version 5.9.6 to be in place. As far as I can it doesn't exist on DockerHub yet and main Unleash container deployment breaks with following message:
Failed to pull image "unleashorg/unleash-community-azure:5.9.6": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/unleashorg/unleash │
│ -community-azure:5.9.6": failed to resolve reference "docker.io/unleashorg/unleash-community-azure:5.9.6": docker.io/unleashorg/unleash-community-azure:5.9.6: not found
Hello, thanks for your opened issue, currently the process to create a new community docker image is a manual process and needs manual approval in order to push new version images to the docker hub repository.
I have approved and merged the new version and is being pushed to the dockerhub now.
Describe the bug
I'm using latest Unleash Helm chart v4.0.0: https://github.com/Unleash/helm-charts/releases/tag/unleash-4.0.0
and in addition to
unleash-community-azure
Docker image for Azure Entra ID authentication.However, it seems like main Unleash Helm is requesting tag with version
5.9.6
to be in place. As far as I can it doesn't exist on DockerHub yet and main Unleash container deployment breaks with following message:https://github.com/Unleash/helm-charts/blob/9b430c25ecfca5ec08fae32ae290489f7760b183/charts/unleash/values.yaml#L147
Are you planning to release latest version so that it would be compatible with latest Unleash Helm chart?
Steps to reproduce the bug
No response
Expected behavior
No response
Logs, error output, etc.
No response
Screenshots
No response
Additional context
No response
Unleash version
5.9.6
Subscription type
Open source
Hosting type
Self-hosted
SDK information (language and version)
Helm
The text was updated successfully, but these errors were encountered: