Re: [I] request help: Question about Composite Ingress feature maturity and GA plans [apisix-ingress-controller]
mayankmurari commented on issue #2403: URL: https://github.com/apache/apisix-ingress-controller/issues/2403#issuecomment-3035630554 @juzhiyuan Is there an estimated timeline for the GA release? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] request help: Question about Composite Ingress feature maturity and GA plans [apisix-ingress-controller]
juzhiyuan closed issue #2403: request help: Question about Composite Ingress feature maturity and GA plans URL: https://github.com/apache/apisix-ingress-controller/issues/2403 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] request help: Question about Composite Ingress feature maturity and GA plans [apisix-ingress-controller]
juzhiyuan commented on issue #2403: URL: https://github.com/apache/apisix-ingress-controller/issues/2403#issuecomment-3026265209 Updates: APISIX Ingress Controller 2.0.0 RC1 has been published. Refer to https://github.com/apache/apisix-ingress-controller/tree/master/docs -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] request help: Question about Composite Ingress feature maturity and GA plans [apisix-ingress-controller]
juzhiyuan commented on issue #2403: URL: https://github.com/apache/apisix-ingress-controller/issues/2403#issuecomment-2908254411 Hi @vortegatorres, in the new design, instead of using ETCD or Mock ETCD, the new ingress controller workflow is as follows: The Ingress Controller will work with APISIX Standalone (https://docs.api7.ai/apisix/production/deployment-modes#standalone-mode and https://github.com/api7/apisix-standalone-sample/tree/main). Within the Controller implementation, it will convert the input (YAML) into ADC format (https://github.com/api7/adc). This format will then be transformed into Standalone configurations for APISIX to use, thus addressing the issue of reliance on ETCD. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] request help: Question about Composite Ingress feature maturity and GA plans [apisix-ingress-controller]
vortegatorres commented on issue #2403: URL: https://github.com/apache/apisix-ingress-controller/issues/2403#issuecomment-2900199851 > updates: https://lists.apache.org/thread/r8ydjz4nq35xokov2lc6sfhppybqwgrn Thanks for the information. I’ve sent you an email to coordinate the call in case you’re still available. Appreciate it! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] request help: Question about Composite Ingress feature maturity and GA plans [apisix-ingress-controller]
juzhiyuan commented on issue #2403: URL: https://github.com/apache/apisix-ingress-controller/issues/2403#issuecomment-2897964630 updates: https://lists.apache.org/thread/r8ydjz4nq35xokov2lc6sfhppybqwgrn -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] request help: Question about Composite Ingress feature maturity and GA plans [apisix-ingress-controller]
vortegatorres commented on issue #2403: URL: https://github.com/apache/apisix-ingress-controller/issues/2403#issuecomment-2893370290 > Hi [@vortegatorres](https://github.com/vortegatorres) , thank you for your interest. The core team is building the new ingress controller and will release the middle of June. > > the new architecture doesn't need mock etcd and real etcd, so we can keep far away the issue that etcd is not stable in k8s. > > if you are interested in the new design, let me know (juzhiyuan at apache.org) and we can setup a quick call as the documents are not public yet. @juzhiyuan Thanks so much for your response. I'm actually quite interested because we're using APISIX in our production environment and have experienced some instability issues related to `etcd`. That's why we're currently testing the Composite Architecture. However, if you're working with a different architecture that's more likely to be production-ready than Composite, I'd be very interested in learning more about it. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] request help: Question about Composite Ingress feature maturity and GA plans [apisix-ingress-controller]
juzhiyuan commented on issue #2403: URL: https://github.com/apache/apisix-ingress-controller/issues/2403#issuecomment-2892541010 Hi @vortegatorres , thank you for your interest. The core team is building the new ingress controller and will release the middle of June. the new architecture doesn't need mock etcd and real etcd, so we can keep far away the issue that etcd is not stable in k8s. if you are interested in the new design, let me know (juzhiyuan at apache.org) and we can setup a quick call as the documents are not public yet. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
