feat: As a user, I want to add observable reconciliation status and last reconcile timestamp for Ingress resources so that debug it

[Goend]

Description

add condition and timestamp for ingress status

[Baoyuantop]

Thanks for the request. Could you clarify whether "Ingress resources" means the native Kubernetes networking.k8s.io/v1 Ingress, or APISIX Ingress Controller CRDs such as ApisixRoute?

APISIX CRDs already expose status.conditions through ApisixStatus, and those conditions include lastTransitionTime. However, lastTransitionTime means the time when the condition changed, which is different from a per-reconcile lastReconcileTime. For native Kubernetes Ingress, the controller currently updates status.loadBalancer, and we should not assume that the APISIX CRD status shape can be added directly to the standard Ingress status.

If the target is APISIX CRDs, a reasonable direction is to add a separate status.lastReconcileTime while preserving the existing condition semantics. If the target is native Ingress, we may need to discuss alternatives such as Kubernetes Events, annotations, or another approach that does not break the standard Ingress status schema. Could you provide the target resource type and an example of the expected status YAML?

[Goend]

It's possible that I didn't describe it clearly. I simply want to add events every time an Ingress resource completes synchronization, similar to this:

[root@node-1 ~]# kubectl describe ingress -n openstack roller 
Name:             roller
Labels:           app.kubernetes.io/managed-by=Helm
Namespace:        xx
Address:          10.20.0.7,10.20.0.8,10.20.0.9
Ingress Class:    <none>
Default backend:  <default>
TLS:
  SNI routes roller,roller.openstack,roller.openstack.svc.cluster.local
Rules:
  Host        Path  Backends
  ----        ----  --------
  *           
              /ecas   roller-dashboard:80 (10.232.3.214:80,10.232.4.230:80,10.232.5.202:80)
Annotations:  ingress.kubernetes.io/affinity: cookie
              ingress.kubernetes.io/configuration-snippet: rewrite ^/ecas$ /ecas/ break;
              ingress.kubernetes.io/custom-http-errors: 404,500
              ingress.kubernetes.io/proxy-body-size: 0
              ingress.kubernetes.io/proxy-read-timeout: 1800
              ingress.kubernetes.io/proxy-redirect-from: http://
              ingress.kubernetes.io/proxy-redirect-to: https://
              ingress.kubernetes.io/session-cookie-hash: sha1
              ingress.kubernetes.io/session-cookie-name: escookie
              meta.helm.sh/release-name: roller-dashboard
              meta.helm.sh/release-namespace: openstack
              xx: xx
Events:
  Type    Reason  Age               From                      Message
  ----    ------  ----              ----                      -------
  Normal  Sync    2s (x3 over 46h)  nginx-ingress-controller  Scheduled for sync
  Normal  Sync    2s (x3 over 46h)  nginx-ingress-controller  Scheduled for sync
  Normal  Sync    2s (x2 over 46h)  nginx-ingress-controller  Scheduled for sync

Something like generating this kind of event. Additionally, if ADC synchronization fails, it would be best to have corresponding events to alert users, so as to avoid situations where configuration delivery remains unsuccessful without anyone noticing.

@Baoyuantop