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

istio-init waiting for too long time to start #51620

Closed
2 tasks done
Harish-R-T opened this issue Jun 18, 2024 · 1 comment
Closed
2 tasks done

istio-init waiting for too long time to start #51620

Harish-R-T opened this issue Jun 18, 2024 · 1 comment
Labels
area/perf and scalability kind/need more info Need more info or followup from the issue reporter

Comments

@Harish-R-T
Copy link

Harish-R-T commented Jun 18, 2024

Is this the right place to submit this?

  • This is not a security vulnerability or a crashing bug
  • This is not a question about how to use Istio

Bug Description

We are using Istio-enabled pods in some namespaces. Upon looking at a few job pods having issues starting the Istio-init container, it takes too much time to start. Until we restarted the pod manually, we could not see any resource issues, but a few are facing the issue internally. 

Version

$ istioctl version
client version: 1.13.2
control plane version: 1.20.3
data plane version: 1.20.3 (519 proxies)
$ kubectl version --short
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Client Version: v1.27.0
Kustomize Version: v5.0.1
Server Version: v1.28.9

Additional Information

No response

@howardjohn
Copy link
Member

Can you provide logs?

@howardjohn howardjohn added the kind/need more info Need more info or followup from the issue reporter label Jun 18, 2024
@howardjohn howardjohn closed this as not planned Won't fix, can't repro, duplicate, stale Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/perf and scalability kind/need more info Need more info or followup from the issue reporter
Projects
None yet
Development

No branches or pull requests

3 participants