You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe scenario
We are currently using Istio Open source based deployment in AKS and wanted to explore if we can migrate from it to managed Istio instance. Our current setup is based on AKS behind WAG where we are using /healthz/ready for probes... I created gateway and VS along with secret for https communication. Health probe with port 80 is working fine but with port 443, I am getting 503... Any better way to ensure that all our configurations that we did with Istio Open source is there with the managed one?
The text was updated successfully, but these errors were encountered:
Describe scenario
We are currently using Istio Open source based deployment in AKS and wanted to explore if we can migrate from it to managed Istio instance. Our current setup is based on AKS behind WAG where we are using /healthz/ready for probes... I created gateway and VS along with secret for https communication. Health probe with port 80 is working fine but with port 443, I am getting 503... Any better way to ensure that all our configurations that we did with Istio Open source is there with the managed one?
The text was updated successfully, but these errors were encountered: