python VS descheduler

One option is to use list_namespace(), as described in https://github.com/kubernetes-client/python/blob/master/kubernetes/docs/CoreV1Api.md

I have checked the python version == 2.7 and pip freeze - ipaddress==1.0.22, urllib3==1.24.1 and websocket-client==0.54.0 are the versions which satisfy the requirement - as mentioned here: https://github.com/kubernetes-client/python/blob/master/README.md#hostname-doesnt-matchfollowed the issue on this thread - https://github.com/kubernetes-client/python/issues/36 - not much help.

kubectl apply -f class.yamlkubectl apply -f rbac.yamlkubectl apply -f deployment-arm.yaml I want to use the kubernetes-client written in python to replace it. My current code, loads the there yaml files (using pyyaml), edits them a bit, inserts into a file and use the command line kubectl to execute those three commands. Some of the code:

In the Kubernetes Python client code it's called "klass":

https://github.com/kubernetes-client/python/blob/1a0cb469528e6b2bdeb3eb2c06945f1c22303dfd/kubernetes/client/api_client.py#L266

and in Apache ecosystem it's called clazz:

https://github.com/search?q=org%3Aapache+clazz&type=code

Just thought it was amusing and wanted to share

One way is to use configmap lock https://github.com/kubernetes-client/python/tree/master/kubernetes/base/leaderelection

I'm having trouble connecting to the kubernetes python client even though I'm following the examples here in the api.

As you can imagine, that's a lot of functions to choose from, luckily all of them are listed in docs and you can click on any one of them to get an example of its usage.

Problem : Uneven Pod Spreading Developers observed uneven pod distribution, especially during traffic spikes, despite configuring PodDisruptionBudget(PDB) and PodTopologySpreadConstraints(PTSC) with whenUnsatisfiable set to ScheduleAnyway. Employing the descheduler, which periodically checks the cluster and evicts pods from overcrowded nodes, forcing them to reschedule onto less crowded ones. Simple, effective, and automated.

maybe descheduler can help? https://github.com/kubernetes-sigs/descheduler

Surprised this wasn't suggested yet, you can also use a software like the k8s Descheduler that executes periodically to rebalance your workloads across the existing nodes.

Here an example of coordination api in Go https://github.com/kubernetes-sigs/descheduler/commit/3cbae5e72ba53447a609e6001755ff395e6eeceb https://github.com/kubernetes-sigs/descheduler/commit/0a52af9ab82a52fd8c864a81f4033736f11aab34

This is something a (now former) colleague of mine pointed out: that the kubernetes descheduler can enforce a maximum lifetime[0] that sort of forces continual reboots. So if your system cannot tolerate running for a long time continously, this is one method to gracefully restart long running pods.

[0]: https://github.com/kubernetes-sigs/descheduler#podlifetime

no it does not... thats why tools like https://github.com/kubernetes-sigs/descheduler exist..