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?
2

Hi Bhavani Shankar,

Welcome to the OpenG2P Community, and thank you for reaching out.

We’re happy to assist you with your deployment issue.

Based on your current setup, it seems the issue stems from attempting to deploy the openg2p-social-registry-p2 (v1.4.2) via Rancher UI and then layering it with openg2p-social-registry (v2.0.6) via the Helm CLI. This approach can cause conflicts and is not recommended.

Here are a few important clarifications and recommendations:

  1. Use Only Version 2.0.x It includes both P1 and P2 components bundled into a single Helm chart. There’s no need to use the separate -p2 chart when deploying v2.0.x.
  2. Currently, Rancher UI is the officially supported method for deploying the openg2p-social-registry v2.0.6 chart. A CLI-native Helm-only method is not fully supported yet due to Rancher-specific dependencies and templating.
  3. Logging cannot be fully disabled or decoupled in the current version, as several core components rely on it. We recommend installing the Logging via Rancher to satisfy these dependencies.

Could you please share the specific use case or scenario you’re exploring with the OpenG2P Social Registry? This will help us better understand your goals and guide you more effectively.

Best regards,
Pramod

3

Hi @Bhavani_Shankar

  • You don’t need to install -p2 helm charts, when you have already installed 2.0.x versions of openg2p-social-registry helm chart, as already mentioned by @Pramod_Belal.
    • If you have already installed -p2 chart, you can uninstall it.
  • The officially supported deployment method is through Rancher, because of ease of configuration and upgrades. While helm cli based installation is not officially recommended according to docs, you can still continue to install it through helm cli, but you will need to go through the values.yaml and understand the parameters.
  • You can install Logging through Rancher. It is recommended to be installed as part of Infrastructure setup, refer to docs (This will install Logging Operator, Fluentd and other dependencies).
    • If you are unable to install Logging operator, you can disable logging components during social registry installation.
      • opensearch.loggingOutput.enabled=false; this translates to Fluentd Logs Output? checkbox under OpenSearch Settings block in Rancher based installation.
      • loggingFlow.enabled=false; this translates to Enable logs capture? checkbox under Logging Settings block in Rancher based installation.

Thanks!