fix: Switch Harbor to Let's Encrypt staging to bypass rate limit

Rate limit error: 429 too many certificates (5) issued for harbor.dvirlabs.com
Must wait until March 23, 2026 07:00:21 UTC before using production again.

Changes:
- Created letsencrypt-staging ClusterIssuer
- Updated Harbor to use staging issuer temporarily
- Deleted failed certificate resources

After March 23, change cert-manager.io/cluster-issuer back to 'letsencrypt'

letsencrypt-staging-issuer.yaml

@@ -0,0 +1,17 @@
+apiVersion: cert-manager.io/v1
+kind: ClusterIssuer
+metadata:
+  name: letsencrypt-staging
+spec:
+  acme:
+    # Let's Encrypt Staging server - no rate limits for testing
+    server: https://acme-staging-v02.api.letsencrypt.org/directory
+    email: dvirlabs@gmail.com
+    privateKeySecretRef:
+      name: letsencrypt-staging-account-key
+    solvers:
+    - dns01:
+        cloudflare:
+          apiTokenSecretRef:
+            key: api-token
+            name: cloudflare-api-token

manifests/harbor/values.yaml

@@ -12,8 +12,8 @@ expose:
   ingress:
     className: traefik
     annotations:
-      # cert-manager annotation - will create the certificate automatically
-      cert-manager.io/cluster-issuer: letsencrypt
+      # TEMPORARY: Using staging to avoid rate limits (switch back to 'letsencrypt' after March 23, 2026)
+      cert-manager.io/cluster-issuer: letsencrypt-staging
       # Traefik specific annotations for HTTPS routing
       traefik.ingress.kubernetes.io/router.entrypoints: websecure
       traefik.ingress.kubernetes.io/router.tls: "true"