Bitnami going commercial

[saska]

Hello,

Is there any plan on dealing with this happening the day after tomorrow? I see bitnami dependencies that will potentially just straight up break.

[echozio]

As of now it's still undecided. We'll most likely either drop the dependencies from the chart all together so that you'll always have to bring your own, or make our own minimally configurable replacements and gate them behind a flag that makes it clear they're not meant for production.

I still feel there is value in having something that allows for quick and easy deployment, particularly for testing and evaluation, but providing a migration path or supporting our own production-grade replacements for what Bitnami provided is not really on the table due to it being a massive undertaking.

For the time being, if you rely on these dependencies you'll likely have to switch over to the "bitnamilegacy" repo to avoid service disruption in the event of node cycling.

Regardless (even if Bitnami backtracks or we find a drop-in replacement) I'd strongly urge anyone using these subcharts in production to manage the dependencies separately in a way that meets their requirements. Our provided integrations with them do little more than enable authentication and configure connection details for Jitsu.

[saska]

I switched over to legacy for now; posting an example values.yaml below to switch over all the repositories to anyone who'd like to do the same without faffing with or upgrading a live deployment.

jitsu:
  mongodb:
    image:
      repository: bitnamilegacy/mongodb
    tls:
      image:
        repository: bitnamilegacy/nginx
    externalAccess:
      autoDiscovery:
        image.repository: bitnamilegacy/kubectl
    externalAccess:
      dnsCheck:
        image:
          repository: bitnamilegacy/kubectl
    volumePermissions:
      image:
        repository: bitnamilegacy/os-shell
    metrics:
      image:
        repository: bitnamilegacy/mongodb-exporter
  postgresql:
    image:
      repository: bitnamilegacy/postgresql
    volumePermissions:
      image:
        repository: bitnamilegacy/os-shell
    metrics:
      image:
        repository: bitnamilegacy/postgres-exporter
  redis:
    image:
      repository: bitnamilegacy/redis
    sentinel:
      image:
        repository: bitnamilegacy/redis-sentinel
    metrics:
      image:
        repository: bitnamilegacy/redis-exporter
    volumePermissions:
      image:
        repository: bitnamilegacy/os-shell
    kubectl:
      image:
        repository: bitnamilegacy/kubectl
    sysctl:
      image:
        repository: bitnamilegacy/os-shell
  kafka:
    image:
      repository: bitnamilegacy/kafka
    defaultInitContainers:
      volumePermissions:
        image:
          repository: bitnamilegacy/os-shell
    defaultInitContainers:
      autoDiscovery:
        image:
          repository: bitnamilegacy/os-shell
    metrics:
      jmx:
        image:
          repository: bitnamilegacy/jmx-exporter
  clickhouse:
    image:
      repository: bitnamilegacy/clickhouse
    keeper:
      image:
        repository: bitnamilegacy/clickhouse-keeper
    defaultInitContainers:
      volumePermissions:
        image:
          repository: bitnamilegacy/os-shell

[echozio]

This is incorporated into v2.5.0. Bitnami also delayed their retirement of the old registry, so aside from their scheduled brownouts hopefully this hasn't caused any major issues.