Whats the plan for handling binami's deprecation of versioned images?

[XJ-0461]

Bitnami's Alert

This would affect Keycloak.

resource "helm_release" "keycloak" {
  depends_on       = [helm_release.theia-cloud-base, kubectl_manifest.selfsigned_issuer]
  name             = "keycloak"
  repository       = "https://charts.bitnami.com/bitnami"
  chart            = "keycloak"
  version          = "15.1.8" <---
  namespace        = "keycloak"
  create_namespace = true
...

Seems like you'd have to either use 'latest' or change the repo to bitnamilegacy

[jfaltermeier]

Thanks for the report, we will look at this as part of #448. We wanted to go to a newer Keycloak version anyway, but I do not fully understand the consequences of the announcements yet, meaning if there will be a latest image per Keycloak major version or if there will be only the latest release, so I can't answer yet what we will do in the end.

[jfaltermeier]

Ticket for this: #457

Sorry that this is taking longer, but we now have a budget for it (+ other dependency updates and getting next builds going again) in November.

As a temporary hint, switching to legacy should be possible with these values in the Keycloak configuration:

image:
  repository: bitnamilegacy/keycloak
postgresql:
  image: 
    repository: bitnamilegacy/postgresql
  volumePermissions: 
    image:
      repository: bitnamilegacy/os-shell

Reference: #448 (comment)