Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Platform Discovery timing out on Minikube #37832

Closed
leosarra opened this issue Mar 9, 2022 · 7 comments · Fixed by #37873
Closed

Platform Discovery timing out on Minikube #37832

leosarra opened this issue Mar 9, 2022 · 7 comments · Fixed by #37873

Comments

@leosarra
Copy link
Contributor

leosarra commented Mar 9, 2022

Bug Description

Hello everyone.
While running Istio 1.13 on Minikube I noticed that all proxies are subject to a flat 5-second delay when starting up.
This is due to the Platform Discovery that is performed before starting the pilot-agent.
Specifically, since Istio 1.13, the AWS check is taking more than 5 sec.
Previous releases did not show such behavior.

The issue can be easily reproduced as follows:

  1. Setup a Minikube cluster
  2. Install Istio via istioctl install
  3. Check logs of the newly deployed ingressgateway to see if the following entry is present:
    2022-03-09T10:59:41.839438Z info timed out waiting for platform detection, treating it as Unknown

I did some troubleshooting of the issue myself and I noticed that the last release added some checks on permissions errors that, if triggered, warrant for a more complex check using AWS SDK Client. (PR #36380)
In the case of Minikube, reading product UUID will lead to a permission error, due to this, since Istio 1.13, the AWS SDK Client will be used as a fallback and that will lead to the timeout.

Would it be possible to change the checks such that Minikube would not be affected by this degradation?
Or can the check using AWS SDK be changed such that it will not end up in a timeout?

Version

client version: 1.13.1
control plane version: 1.13.1
data plane version: 1.13.1 (1 proxies)
Client Version: v1.20.1
Server Version: v1.21.7

Additional Information

No response

@howardjohn
Copy link
Member

@ramaraochavali

@ramaraochavali
Copy link
Contributor

Can you please try setting CLOUD_PLATFORM to none and see if it helps?

@leosarra
Copy link
Contributor Author

leosarra commented Mar 9, 2022

Can you please try setting CLOUD_PLATFORM to none and see if it helps?

Hello @ramaraochavali
Yes, setting CLOUD_PLATFORM=none would help as Platform Discovery is getting skipped and platform is set to Unknown out-of-the-box. Even so, I feel that this is only a workaround.
The AWS check will delay startup by 5 sec when executed on Minikube with default Istio configuration. Do you think that, under these circumstances, this new delay has to be expected or not?
I also wonder if other environments may show similar behavior with the AWS check leading to a timing out.

@howardjohn
Copy link
Member

howardjohn commented Mar 9, 2022 via email

@ramaraochavali
Copy link
Contributor

Yeah. I was just trying to root cause. I will try to fix it tomorrow.

@ramaraochavali
Copy link
Contributor

@LithiumSR We discussed the same problem here #36380 (comment) and one of the reasons for adding "none" is this only. However it would be nice if we have a better solution. I am going through AWS docs and found a better way to do it.

I will submit a PR tomorrow.

@leosarra
Copy link
Contributor Author

Ahh, I see the reasoning behind the changes.
Thank you @ramaraochavali for looking into it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants