Files
cozystack/packages/core/platform/sources/mongodb-application.yaml
T
Myasnikov Daniil 59555c895e fix(hack): retain controllers and APIs for selective installs
Tenant HelmReleases need a shard reconciler, and the root SeaweedFS
release creates COSI resources even when no backup suite is selected.
Without those controllers, a fresh reduced install cannot become ready.

The Kubernetes suites create worker pools through KubernetesNodes, and
MongoDB renders an operator-owned CR. Selecting only the cluster API or
application chart drops resources those suites require.

Assisted-by: LLM
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
2026-10-07 06:01:52 +03:00

40 lines
1.4 KiB
YAML

---
apiVersion: cozystack.io/v1alpha1
kind: PackageSource
metadata:
name: cozystack.mongodb-application
spec:
sourceRef:
kind: OCIRepository
name: cozystack-packages
namespace: cozy-system
path: /
variants:
- name: default
dependsOn:
- cozystack.networking
- cozystack.mongodb-operator
# cozystack-engine ships the ApplicationDefinition CRD rendered by the *-rd component below.
- cozystack.cozystack-engine
# The mongodb chart renders kind: PerconaServerMongoDB from
# psmdb.percona.com/v1, so the operator that serves that CRD is a
# prerequisite of offering the app at all. Without this edge the
# mongodb-rd HelmRelease registers the ApplicationDefinition as soon as
# the engine is up, a tenant can create a MongoDB before the operator
# exists, and its HelmRelease fails with `no matches for kind
# "PerconaServerMongoDB"`. Same shape as every other operator-backed app
# here (postgres, mariadb, kafka, redis, etcd).
- cozystack.mongodb-operator
libraries:
- name: cozy-lib
path: library/cozy-lib
components:
- name: mongodb
path: apps/mongodb
libraries: ["cozy-lib"]
- name: mongodb-rd
path: system/mongodb-rd
install:
namespace: cozy-system
releaseName: mongodb-rd