Unable to deploy Odoo (Social Registry UI) pod — backend services deployed successfully but Odoo never deployed (Rancher UI and Helm CLI both tested)

Social Registry
1

Description:

I’m trying to deploy OpenG2P Social Registry module on GKE using both Rancher UI and Helm CLI.

Current status:

  • Superset, Redis, PostgreSQL, Celery background tasks are deployed successfully and running.
  • But Odoo pod (social-registry-odoo) is never deployed in any scenario.
  • I followed:
    • Rancher UI deployment via openg2p-social-registry-p2 (1.4.2)
    • Helm CLI deployment via openg2p-social-registry (2.0.6)

Observed:

  • When deploying openg2p-social-registry-p2 via Rancher UI:
    • Backend apps deployed :white_check_mark:
    • Odoo never gets installed :cross_mark: (Odoo subchart not included in p2 version)
  • When trying to deploy full openg2p-social-registry (2.0.6) via Helm CLI:
    • Install fails with:
resource mapping not found for name: "social-registry-odoo" namespace: "" from "": no matches for kind "Flow" in version "logging.banzaicloud.io/v1beta1"
  • Even after disabling logging, reporting, opensearch, kafkaUI, debezium, eSignet — the Helm chart still tries to render Flow resources.
  • BanzaiCloud LoggingOperator CRDs are deprecated and not easily installable.

Summary:

  • Backend services are deployed fine, but Odoo (core frontend) never gets installed.
  • Rancher UI version (p2) does not contain Odoo.
  • Helm CLI version (2.0.6) cannot deploy Odoo because of missing CRDs for legacy logging templates.

Request:

  • How can I cleanly deploy the Odoo pod today?
  • Is there a fully CLI-native way to deploy 2.x versions without Rancher?
  • Can you update Helm packaging to fully decouple legacy logging CRD templates when not in use?