Fix Ingress class detection for github-repo-registrations-eventsource

[Copilot]

github-repo-registrations-eventsource ingress showed no CLASS in kubectl get ingress -A because it used the deprecated kubernetes.io/ingress.class annotation instead of spec.ingressClassName.

Changes

• eventsource-github-from-repo-registrations.yaml: Replace deprecated annotation with spec.ingressClassName
• ingress-authz.yaml: Add | quote to ingressClassName for consistent YAML parsing

Before:

metadata:
  annotations:
    kubernetes.io/ingress.class: {{ .Values.events.github.webhook.ingress.className | default "nginx" | quote }}
spec:
  rules:

After:

metadata:
  # no ingress class annotation
spec:
  ingressClassName: {{ .Values.events.github.webhook.ingress.className | default "nginx" | quote }}
  rules:

Once redeployed, the ingress controller will properly detect and assign an ADDRESS to the resource.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• argoproj.github.io
  • Triggering command: /usr/local/bin/helm helm repo add argo REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)