Chenlu Jiao

@Naveenommi-MSFT We have successfully implemented the new feature to support multi-ingress. It will be available in about 2 weeks for the release. We're now working on updating the documentation and...

@AdamSheltz It has released, please refer to our [documentation](https://learn.microsoft.com/en-us/azure/machine-learning/how-to-troubleshoot-kubernetes-extension?view=azureml-api-2#ingress-nginx-controller), and upgrade your extenion to apply it.

Hi @tyler-suard-parker, very appreciate your feedback and suggestion, we have created a task to track this usability improvement, will evaluate priorities and add to future plan

@hao-happify For product improvement, we has released the new version of azureml-fe, and we are now transparently upgrading the azureml-fe from v1 to v2 in our customers' AKS clusters. However,...

Hi @kachely Thanks your feedback and suggestions. Not sure if you've awared that, when a node is bypassed, its output is set to **None.** And a downstream node will only...

@fbinotto we have the new “Flex flow" released. This feature enables developers to craft LLM apps using a python function or class as the entry point, encapsulating all their app...

Appreciate your feedback @sparkdemotivator @ArtyomZemlyak! These LLM settings and metrics from LLM api request/response are now exposing in the trace log of each node run. actually, you're not alone in...

Hi @ArtyomZemlyak , we have the trace graph in the vscode extension already, single run, and visualization on batch runs, not sure if it's the "tracing capabilities" you mentioned is...

Hi @sparkdemotivator, "It seems like your main concern currently is the need to individually pass the _experiment object_ to each node using flow input and output linking, which you think...