-
Notifications
You must be signed in to change notification settings - Fork 315
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
customize node config #323
Comments
Right now no, beyond |
possibly the configuration mentioned here #245 |
I have some rather large images in ACR that timeout pulling the images. Some info here: changing to KUBELET_OPTS=--image-pull-progress-deadline=10m Being able to edit these should be made easier as I'm sure as more and more customers use AKS, each customer's scenario will require changing kubelet options. |
This seems like a duplicate of #245 |
I'm actually curious about whether and how we could use a different option (--cpu-manager-policy) passed in to KUBELET_OPTS as part of our node provisioning. Is there a generic way to do this or is the plan to expose specific functionality through other AKS knobs and have those turn on the appropriate flags indirectly for users? |
@doubleyewdee It would be the latter - depending on the complexity of the option (some aren't well suited for AKS as a managed solution). AKS would expose the knobs and then handle application behind the scenes. |
+1 to need to set my eviction limits |
How about Dynamic Kubelet Configuration ? I'm using It's required by |
@jnoller I understand that certain configs are not suitable for managed AKS, but is it possible to have a blacklist/whitelist on the dynamic configurations? So that we can at least setup the cluster and VMSS better suited to the latency sensitive production traffic. Some of the latency and perf related settings for AKS that I wish to be able to set when I have Cluster AutoScaler enabled,
Thank you for your consideration. |
I would need to set ConfigMapAndSecretChangeDetectionStrategy |
What is the latest status of this ask? |
Custom kubelet config would also allow to solve #686 which is failing an important deployment on my cluster |
After couple of trial-and-error, I settled with updating the kubelet config using Kured, please check out this gist. You need to change the init-containers script to fit your specific needs. It works with VMSS and HPA/CA, but this feels like a hack to me and I would love to see AKS to support this natively. |
Dynamic Kubelet configuration is great but first you need to chante this kubelet option |
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment. |
I'm curious about an update to this issue. I am myself facing issues with scraping the kubelet from :2550/metrics (http scrape) but am getting a 'connection refused' message thrown back... |
I might be wrong about this but I believe the kubelet binds to localhost, so it's inaccessible to prometheus |
|
AKS will soon provide for more bootstrap options to configure the node OS and kubelet for a nodepool. |
More options should be available for other K8S services: allow to configure additional parameters for kube-api, kube-controller-manager etc. If AKS shall play production grade cluster, we need to have capabilities to setup parameters according to guidelines. |
It is possible to update kubelet (any node config actually) via DaemonSet like example: |
@slawekww any specific requests/use cases for setting parameters on those components? please do open a specific issue with those, happy to discuss there. |
Looking for options to customize the kueblet root dir. Is this supported or planned to be supported?
|
@palma21 Hey, we are looking to evaluate this preview, is there any samples you can share? |
I would add setting logging verbosity ( |
@palma21 when will the |
As claimed in Support for custom log options, So I have similiar question on when containerLog related config goes GA. |
@palma21 any ETA please ?
|
Is there a plan to allow for custom config of --kube-config=cpu=xxxx,memory=xxxx for customers that prefer to have more simplistic QoS configs for deployments? |
For reference, I believe these are the relevant shipped features: |
Is there any way to customize the kubelet config such as KUBELET_HARD_EVICTION_THRESHOLD in the AKS cluster?
The text was updated successfully, but these errors were encountered: