-
Notifications
You must be signed in to change notification settings - Fork 1.1k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Unable to delete the scaled object deployed in Azure AKS and Namespace in terminating state #5090
Comments
Could you provide the events of scaledobject or logs of keda-operator? |
Do you have KEDA operator up and running? |
@zroubalik we have keda operator running running in the cluster.But other applications are also using this same Keda |
So try to remove these scaledobjects first, then namespace |
@zroubalik this is keda namespace .Could you please clarify. Or do we need to delete this |
just delete all scaledobjects in the namespace you are about to remote: k delete scaledobject --all -n YOUR_NAMESPACE And also check keda-operator pod logs to see if there are any errors or anything |
@zroubalik I tried deleting the same and is stuck like this |
@zroubalik I could see some errors in the keda operator log related to this namespace which we are trying to delete 2023-10-19T03:28:51Z ERROR scale_handler error getting metric for scaler {"scaledObject.Namespace": "autozoning-live-ibr-34", "scaledObject.Name": "recognitionicr-autoscaler", "scaler": "azureServiceBusScaler", "error": "scaler with id 2 not found, len = 0, cache has been probably already invalidated"} |
@zroubalik any update |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Report
Unable to delete the scaled object deployed in Azure AKS and Namespace in terminating state
Expected Behavior
As we tried deleting the namespace its in terminating state because of the above scaled object in that namespace
Actual Behavior
Namesapce should be deleted after the scaled object is deleted
Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version
2.11.1
Kubernetes Version
1.25
Platform
Microsoft Azure
Scaler Details
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: