vortegatorres opened a new issue, #2403: URL: https://github.com/apache/apisix-ingress-controller/issues/2403
### Issue description Hi team, I’ve been reviewing the [Composite Ingress](https://apisix.apache.org/docs/ingress-controller/composite/) feature and I’m very interested in adopting it in our environment. However, I noticed that it is currently marked as experimental. I have a few questions regarding its status: Maturity: Could you share more about the current stability and real-world usage of the feature? Are there known limitations or caveats we should be aware of? GA Timeline: Is there a roadmap or estimated timeline for when the Composite Ingress feature might be promoted to General Availability? Technical Impact: I saw that this implementation removes the need for etcd. Does this change increase the load or pressure on the Kubernetes API server in any significant way? We’d like to understand the operational implications before moving forward. Thank you! ### Environment - your apisix-ingress-controller version (output of apisix-ingress-controller version --long): - your Kubernetes cluster version (output of kubectl version): - if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a): -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
