Erich Blume
dbfe7365d8
ArgoCD's resource.exclusions in argocd-cm skips all Endpoints objects (they're normally auto-managed by the control plane). The manual forge-external Endpoints must be applied directly with kubectl. Removed endpoints-forge.yaml from kustomization resources and added comments in both files explaining the situation and the apply command. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
16 lines
489 B
YAML
16 lines
489 B
YAML
---
|
|
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
|
|
namespace: tailscale
|
|
|
|
resources:
|
|
- ../tailscale-operator-base
|
|
- proxygroup-ingress.yaml
|
|
- external-secret.yaml
|
|
- svc-forge-external.yaml
|
|
# endpoints-forge.yaml is NOT managed by ArgoCD — Endpoints are globally
|
|
# excluded in argocd-cm resource.exclusions (too noisy for auto-managed
|
|
# Endpoints). Apply manually:
|
|
# kubectl --context=minikube-indri apply -f endpoints-forge.yaml
|
|
- ingress-forge.yaml
|