Missing documentation regarding installation on clusters with existing cnpg operator installs

[AntonOfTheWoods]

Describe the bug
If CloudNativePG is already installed in your cluster, you may experience conflicts. See the Helm chart documentation for options to skip the CNPG dependency.

To Reproduce
Steps to reproduce the behavior:

1. Read the official installation docs on the official website
2. Search through all the helm chart docs and not find the referenced documentation

Expected behavior
Documentation to be up-to-date and accurate

Kubernetes Environment (please complete the following information):

• All

Additional context
It is a little unclear how one would install without the cnpg chart when there is the following helm go template in documentdb:

apiVersion: v1
kind: Namespace
metadata:
  name: cnpg-system
  labels:
    app.kubernetes.io/name: {{ include "documentdb-chart.name" . }}
    app.kubernetes.io/managed-by: "Helm"

That is the full template, with no guard for installing or not the namespace. If helm sees that it is being asked to do something that another chart has already done, at the very least it will refuse to do this by default (is this overridable?).

[documentdb-triage-tool]

🤖 Auto-triaged by documentdb-triage-tool.

Applied: documentation, bug
Project fields suggested: Component docs · Priority P2 · Effort M · Status In Progress
Confidence: 0.82 (llm)

Reasoning

LLM: Documentation references CNPG conflict guidance that doesn't exist, and the Helm chart template lacks a conditional guard for the cnpg-system namespace, breaking installs on clusters with an existing CNPG operator.

If a label is wrong, remove it manually and ping @patty-chow so the rules can be tuned. The bot will not re-label items that already have component labels.

[documentdb-triage-tool]

👋 @xgerman — this issue has been assigned for 14 days with no activity. Is it still in progress? If you've made progress, please leave a quick update. Otherwise it'll be flagged for re-assignment at the next triage meeting.