Paramjeet B
Paramjeet B
No , I use community edition and I have customized the xcom code to solve this problem
I'm not sure where the data is lost in between but I'm trying this code as suggested by @paul424 in this issue : https://github.com/kubernetes-client/python-base/issues/190. My understanding is that the data...
@kand617 , We use the above mentioned code to solve the issue.
@wircho Increasing the `termination_grace_period` should help to mitigate this issue.
@dirrao , please help to review the above changes.
@eladkal , When a node is drained in eks due to aws ec2 spot instance interruption or due to some other reasons , usually controllers will detect that the pods...
> @paramjeet01 We have retries with retry_delay of 5 mins. If the pod is still stuck in terminating state or whatever, then Kubernetes cluster is not working as expected. I...
Got community help , Seems like it cannot get info from cache and recreate in the next reconciliation loop
@rickbrouwer , We are still facing the same issue after upgrading to 2.17.1. Kindly please assist with further options.
Yes @rickbrouwer , We are still getting the below error before scale up > ERROR scale_handler error getting scale decision {"scaledObject.Namespace": "mynamespace", "scaledObject.Name": "cw-processor-eks", "scaler": "kafkaScaler", "error": "scaler with id...