In order to benefit from further development, the Community Edition deployment scripts should be updated to use the Docker images built by the Hubs Foundation instead of the archived Mozilla Docker images.
Note: before a Community Edition service that the Hubs Foundation maintains can be transitioned, its corresponding repository must have been updated to produce Hubs Foundation Docker images. See Hubs-Foundation/.github#9 for which repositories have been updated to produce Hubs Foundation Docker images.
Updates to community-edition/input-values.yaml
Overrides
Initially, the way to use the Hubs Foundation images is to add them as overrides of the Mozilla images.
Note: the override images should use the Docker Hub path with $Container_Tag as the tag, e.g. "hubsfoundation/hubs:$Container_Tag"
Final transition
Once all the overrides have been applied, the Container_Dockerhub_Username can be changed from "mozillareality" to "hubsfoundation" and the overrides can be reset back to "No".
Updates to community-edition/ssl_script/cbb.yam
Historical notes
2026-05-12: It was originally planned that the postgrest, postgres, and haproxy services would reference the non-customized 3rd-party Docker images directly as overrides; however, it was decided at the 2026-04-21 Hubs Dev Meetup that it would be a better user experience to build Hubs Foundation Docker images of the non-customized 3rd-party services so that they can be updated at any time without requiring a release/update of the Community Edition deployment scripts.
In order to benefit from further development, the Community Edition deployment scripts should be updated to use the Docker images built by the Hubs Foundation instead of the archived Mozilla Docker images.
Note: before a Community Edition service that the Hubs Foundation maintains can be transitioned, its corresponding repository must have been updated to produce Hubs Foundation Docker images. See Hubs-Foundation/.github#9 for which repositories have been updated to produce Hubs Foundation Docker images.
Updates to
community-edition/input-values.yamlOverrides
Initially, the way to use the Hubs Foundation images is to add them as overrides of the Mozilla images.
Note: the override images should use the Docker Hub path with
$Container_Tagas the tag, e.g."hubsfoundation/hubs:$Container_Tag"OVERRIDE_RETICULUM_IMAGEOVERRIDE_POSTGREST_IMAGEOVERRIDE_POSTGRES_IMAGEOVERRIDE_PGBOUNCER_IMAGEOVERRIDE_HUBS_IMAGEOVERRIDE_SPOKE_IMAGEOVERRIDE_NEARSPARK_IMAGEOVERRIDE_PHOTOMNEMONIC_IMAGEOVERRIDE_DIALOG_IMAGEOVERRIDE_COTURN_IMAGEOVERRIDE_HAPROXY_IMAGEFinal transition
Once all the overrides have been applied, the
Container_Dockerhub_Usernamecan be changed from"mozillareality"to"hubsfoundation"and the overrides can be reset back to"No".Container_Dockerhub_Usernameand overrides resetUpdates to
community-edition/ssl_script/cbb.yamstable-latesttag.Historical notes
2026-05-12: It was originally planned that the postgrest, postgres, and haproxy services would reference the non-customized 3rd-party Docker images directly as overrides; however, it was decided at the 2026-04-21 Hubs Dev Meetup that it would be a better user experience to build Hubs Foundation Docker images of the non-customized 3rd-party services so that they can be updated at any time without requiring a release/update of the Community Edition deployment scripts.