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

Set kubelet config #686

Closed
windoze opened this issue Oct 11, 2018 · 1 comment
Closed

Set kubelet config #686

windoze opened this issue Oct 11, 2018 · 1 comment

Comments

@windoze
Copy link

windoze commented Oct 11, 2018

What happened:
Failed to deploy pod which uses a large image, image pulling is always timeout.

What you expected to happen:
Successfully deploy the pod

How to reproduce it (as minimally and precisely as possible):
I have a pod uses a large container image(>7GB, based on windoze/fasttext), and the deployment was almost always fail because it exceeded the image pulling deadline.
According to the K8S document I need to change --runtime-request-timeout parameter for kubelet service, but I didn't find anywhere to change it in AKS.

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):
  • Size of cluster (how many worker nodes are in the cluster?)
  • General description of workloads in the cluster (e.g. HTTP microservices, Java app, Ruby on Rails, machine learning, etc.)
  • Others:
@seanmck
Copy link
Collaborator

seanmck commented Dec 6, 2018

AKS does not support changing kubelet configs. Please submit a feedback item at https://aka.ms/aks/feedback

@seanmck seanmck closed this as completed Dec 6, 2018
@ghost ghost locked as resolved and limited conversation to collaborators Jul 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants