maybe they are forced to be on the cert-manager namespace?

apps/production/cert-manager/certificates/fascinated-cc.yaml

@@ -1,15 +0,0 @@
----
-apiVersion: cert-manager.io/v1
-kind: Certificate
-metadata:
-  name: fascinated-cc
-  namespace: traefik
-spec:
-  secretName: fascinated-cc
-  issuerRef:
-    name: letsencrypt-production
-    kind: ClusterIssuer
-  commonName: "*.fascinated.cc"
-  dnsNames:
-    - "fascinated.cc"
-    - "*.fascinated.cc"

apps/production/cert-manager/certificates/local-fascinated-cc.yaml

@@ -1,14 +0,0 @@
----
-apiVersion: cert-manager.io/v1
-kind: Certificate
-metadata:
-  name: local-fascinated-cc
-  namespace: traefik
-spec:
-  secretName: local-fascinated-cc
-  issuerRef:
-    name: letsencrypt-production
-    kind: ClusterIssuer
-  commonName: "*.local.fascinated.cc"
-  dnsNames:
-    - "*.local.fascinated.cc"

apps/production/cert-manager/certificates/mcutils-xyz.yaml

@@ -1,15 +0,0 @@
----
-apiVersion: cert-manager.io/v1
-kind: Certificate
-metadata:
-  name: mcutils-xyz
-  namespace: traefik
-spec:
-  secretName: mcutils-xyz
-  issuerRef:
-    name: letsencrypt-production
-    kind: ClusterIssuer
-  commonName: "*.mcutils.xyz"
-  dnsNames:
-    - "mcutils.xyz"
-    - "*.mcutils.xyz"

apps/production/cert-manager/kustomization.yaml

@@ -6,6 +6,3 @@ resources:
   - namespace.yaml
   - cert-manager.yaml
   - issuer.yaml
-  - ./certificates/fascinated-cc.yaml
-  - ./certificates/local-fascinated-cc.yaml
-  - ./certificates/mcutils-xyz.yaml