Azure Machine Learning Terminal Instance HTTP Access Disruption

@杨彪 If you have setup your endpoint to be secure and if it was working prior to the failure then was there any config change in your setup?

You might also want to look at this setup to check if this is how you want your endpoint to be available. Thanks!!

Thank you for your reply. We did not make any changes before the problem occurred. It had been working normally for several months before that. After the problem occurred, we could only temporarily modify the DNS resolution to the external IP to ensure normal service.

@杨彪 I feel at this point to debug the issue you might have to submit a support case to look at issues with private link or this compute instance. It might be easier to redo the setup with a new instance and kubernetes setup without disturbing your current configuration and check if that works as expected. This would give a chance to look at configuration settings in both instances and find out any differences that might be causing the older one to stop working.

Also, with the existing compute instance, if you have been using private IP with private link, was there any change in IP probably due to a maintenance activity? Thanks!!