apache / apache/apisix-ingress-controller
feat: As a user, I want to discover the external ip on the ApisixRoute, so that i can expose it trough automated dns
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 390
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
### Description
As a user, I want to discover the external ip on the ApisixRoute CRD, so that i can expose it trough automated dns.
This would enable me to integrate external-dns against the custom CRD without requering access to the api and multiple round trips to the kubernetes api.
This would also align the route crd to gateway routes and ingress spec.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the ApisixRoute CRD and its status handling, then compare the external-address fields exposed by Gateway routes and Ingress. Check how external-dns consumes custom resources and define done as publishing the external IP on ApisixRoute in a compatible status field without extra Kubernetes API round trips.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100