Paolo Patierno’s Post

Kubernetes 1.29: Decoupling taint-manager from node-lifecycle-controller This blog discusses a new feature in Kubernetes 1.29 to improve the handling of taint-based pod eviction. Background In Kubernetes 1.29, an improvement has been introduced to enhance the taint-based pod eviction handling on nodes. This blog discusses the changes made to node-lifecycle-controller to separate its responsibilities and improve overall code maintainability. Summary of changes node-lifecycle-controller previously combined two independent functions: Adding a pre-defined set of NoExecute taints to Node based on Node's condition. Performing pod eviction on NoExecute taint. With the Kubernetes 1.29 release, the taint-based eviction implementation has been moved out of node-lifecycle-controller into a separate and independent component called taint-eviction-controller. This separation aims to disentangle code, enhance code maintainability, and facilitate future extensions to either component. As part of the change, additional metrics were introduced to help you monitor taint-based pod evictions: pod_deletion_duration_seconds measures the latency between the time when a taint effect has been activated for the Pod and its deletion via taint-eviction-controller. pod_deletions_total reports the total number of Pods deleted by taint-eviction-controller since its start. How to use the new feature? A new feature gate, SeparateTaintEvictionController, has been added Read mode on following blog post!

Kubernetes 1.29: Decoupling taint-manager from node-lifecycle-controller This blog discusses a new feature in Kubernetes 1.29 to improve the handling of taint-based pod eviction. Background In Kubernetes 1.29, an improvement has been introduced to enhance the taint-based pod eviction handling on nodes. This blog discusses the changes made to node-lifecycle-controller to separate its responsibilities and improve overall code maintainability. Summary of changes node-lifecycle-controller previously combined two independent functions: Adding a pre-defined set of NoExecute taints to Node based on Node's condition. Performing pod eviction on NoExecute taint. With the Kubernetes 1.29 release, the taint-based eviction implementation has been moved out of node-lifecycle-controller into a separate and independent component called taint-eviction-controller. This separation aims to disentangle code, enhance code maintainability, and facilitate future extensions to either component. As part of the change, additional metrics were introduced to help you monitor taint-based pod evictions: pod_deletion_duration_seconds measures the latency between the time when a taint effect has been activated for the Pod and its deletion via taint-eviction-controller. pod_deletions_total reports the total number of Pods deleted by taint-eviction-controller since its start. How to use the new feature? A new feature gate, SeparateTaintEvictionController, has been added Read mode on following blog post!

Kubernetes 1.29: Decoupling taint-manager from node-lifecycle-controller This blog discusses a new feature in Kubernetes 1.29 to improve the handling of taint-based pod eviction. Background In Kubernetes 1.29, an improvement has been introduced to enhance the taint-based pod eviction handling on nodes. This blog discusses the changes made to node-lifecycle-controller to separate its responsibilities and improve overall code maintainability. Summary of changes node-lifecycle-controller previously combined two independent functions: Adding a pre-defined set of NoExecute taints to Node based on Node's condition. Performing pod eviction on NoExecute taint. With the Kubernetes 1.29 release, the taint-based eviction implementation has been moved out of node-lifecycle-controller into a separate and independent component called taint-eviction-controller. This separation aims to disentangle code, enhance code maintainability, and facilitate future extensions to either component. As part of the change, additional metrics were introduced to help you monitor taint-based pod evictions: pod_deletion_duration_seconds measures the latency between the time when a taint effect has been activated for the Pod and its deletion via taint-eviction-controller. pod_deletions_total reports the total number of Pods deleted by taint-eviction-controller since its start. How to use the new feature? A new feature gate, SeparateTaintEvictionController, has been added. The feature is enabled by default as Beta in Kubernetes 1.29. Please refer to the feature gate document. When this feature is enabled, users can optionally disable taint-based eviction by setting --controllers=-taint-eviction-controller in kube-controller-manager. To disable the new feature and use the old taint-manager within node-lifecylecycle-controller , users can set the feature gate SeparateTaintEvictionController=false. Use cases This new feature will allow cluster administrators to extend and enhance the default taint-eviction-controller and even replace the default taint-eviction-controller with a custom implementation to meet different needs Read mode on following blog post!

Monokle: Kubernetes Policies Made Easy #WorkSmartWithK8s #kubernetes #monokle #opensource #policy #policyenforcement #policymanagement https://lnkd.in/dTnfEp_s

✍️ New Blog Post ✍️ Hey guys! I published a new post on my newly created blog. It's a little intro about Stateful Applications and their implementation in Kubernetes. Feel free to check it out! I will update this post from time to time with more information. https://lnkd.in/eas2x7Jc

🚀 Hello connection today I have started revising of Kubernetes. 🚀 I just want to share some Kubernetes commands that I have learned today I do not have so much experience in Kubernetes if I am wrong somewhere so please correct me and also give me some suggestions in comment. ***** Command today I have used and learn **** kubectl run firstpod --image=nginx kubectl explain pod (this command is use in writing yaml file for resource) kubectl describe pod firstpod (this command is so much help full in debugging) kubectl exec firstpod -it -- bash kubectl delete pod --all (delete all pod) kubectl delete pod firstpod kubectl get pod firstpod --show-labels (How to check labels in pods by default pod name is your default label) kubectl label pod firstpod env=test (attched new label in pod) kubectl label pod firstpod env1=dev (attched new label in pod) kubectl label pod firstpod --overwrite env1=prod (how to update label in pod) kubectl label pod firstpod env1- (how to remove label in pod) kubectl create -f firstpod.yaml kubectl explain pod --recursive | less (using this command you can not learn any yaml with the help of this you can write script very esaly) kubectl run secondpod --image=nginx -o yaml --dry-run=client > nginx.yaml ****** Example of explain command ********* kubectl explain node kubectl explain node -o wide (-o is option and use for output) kubectl explain pod (po) short form of pod is po kubectl explain replicaset (rs) kubectl explain replicationcontroller (rc) kubectl explain deployment ******* If you want to check the short form of resource use the below command **** kubectl api-resource ********** To check API-version use this command ************* kubectl api-version Thanks to all where I have all things. #tarinwithshubham #shubhambhaiya #GouravSharam #abhishekbhaiya. #kubernetes #connection #devops #cncf #

Kubernetes 1.29: Decoupling taint-manager from node-lifecycle-controller Read mode on following blog post!

Kubernetes 1.29: Decoupling taint-manager from node-lifecycle-controller Read mode on following blog post!

Kubernetes 1.29: Decoupling taint-manager from node-lifecycle-controller Read mode on following blog post!

Kubernetes 1.29: Decoupling taint-manager from node-lifecycle-controller Read mode on following blog post!