Skip to content

Allow ipv4-only setups, or at least allow specifying env values for the documentdb-owned pods #377

Description

@AntonOfTheWoods

Describe the bug

2026-05-17T08:31:32.707816Z  INFO documentdb_gateway_core::postgres::conn_mgmt::pool_manager: Performing the cleanup of unused pools event_id=2002  thread 'main' (1) panicked at documentdb_gateway/src/main.rs:104:10: called `Result::unwrap()` on an `Err` value: IoError { error: Os { code: 97, kind: Uncategorized, message: "Address family not supported by protocol" }, backtrace: <disabled> } note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

To Reproduce
Steps to reproduce the behavior:

  1. Install Document DB Operator following the docs on a kubernetes with ipv6 disabled

Expected behavior
It should work

Kubernetes Environment (please complete the following information):

  • DocumentDB Operator Version [e.g. 123]
    0.110.0
  • Kubernetes Version [e.g. 23]
    1.36.0
  • Kubernetes Environment [e.g. AKS, KIND]
    k3s
  • Cert Bot Version [e.g. 123]
    v1.20.2
  • CNPG Version (if not installed by our helm chart) [e.g. 123]
    0.28.1

Additional context
Add any other context about the problem here.

Metadata

Metadata

Labels

bugSomething isn't workinggoPull requests that update go code

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions