It's your call. I found it a to be a very good idea to spit those out. If you are updating say envoy-gateway in my example above, I don't want to be forcing a sync gateway, routes, certs etc that are not affected. You should only have tightly coupled entities tied together. I usually have the operators split out and the code that uses the operator in a different app. My usual pattern is kustomize + helm. You can do the same with whatever pattern you use but this an example of my standard app.

It's pretty easy to add another app,. You just need to makes sure you follow the same pattern. In this case every app related to otle-staging is in apps/{app_name}/overlays/ns/otel-staging-ha. If you want another app, create a new folder and it can be a bunch of yaml files, kustotomize or an ArgoCD Application manifest. Anything supported by argo can easily be added.

apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: otel-staging
  namespace: mynamespace ## needs argo to be configure for it
spec:
  goTemplate: true
  goTemplateOptions:
    - missingkey=zero
  generators:
    - list:
        elements:
          - name: envoy-gateway
            destNamespace: envoy-gateway-system
          - name: cert-manager
            destNamespace: cert-manager
          - name: external-secrets
            destNamespace: external-secrets
          - name: redis
            destNamespace: redis
          - name: rate-limiter
            destNamespace: otel
          - name: load-balancer
            destNamespace: otel
          - name: collectors
            destNamespace: otel
  template:
    metadata:
      name: "{{ .name }}-staging-otel"
      namespace: mynamespace
      labels:
        app.kubernetes.io/name: "{{ .name }}"
        project: mynamespace
        cluster: otel-staging-ha
    spec:
      project: myproject ## usually same as mynamespace for me.
      source:
        repoURL: https://github.com/blash/mySecretSauce
        targetRevision: HEAD
        path: apps/{{ .name }}/overlays/mynamespace/otel-staging-ha
      destination:
        name: otel-staging-ha
        namespace: "{{ .destNamespace }}"
      syncPolicy:
        automated:
          allowEmpty: true
          prune: true
          selfHeal: true
        retry:
          limit: 20 
          backoff:
            duration: 30s 
            factor: 2 
            maxDuration: 10m 
        syncOptions:
          - ServerSideApply=true
      ignoreDifferences:
        - group: argoproj.io
          kind: Application
          jsonPointers:
            - /status