APIC2018.4.1.1 OVA: How can I remove residual pods with 'Error' status, after failed Cassandra backup attempts?
I reported the failures in post: https://developer.ibm.com/answers/questions/496325/apic2018411-ova-testing-cassandra-backup-to-my-lap.html
The response to kubectl get pods --all-namespaces lists pods with Error status that do not appear to go away of their own accord:
default backup-9gl4m-t9xrw 0/1 Error 0 13h
default backup-b2hcq-sql8w 0/1 Error 0 14h
default backup-hm4kw-tbrm4 0/1 Error 0 14h
default backup-qq7kf-ndb5k 0/1 Error 0 10h
default backup-xsknz-xwm4n 0/1 Error 0 10h
...
default apiconnect-apiconnect-cc-backup-1552176000-22q84 0/1 Error 0 8h
default apiconnect-apiconnect-cc-backup-1552176000-5ls5x 0/1 Error 0 8h
default apiconnect-apiconnect-cc-backup-1552176000-cnzws 0/1 Error 0 8h
default apiconnect-apiconnect-cc-backup-1552176000-gfchz 0/1 Error 0 8h
default apiconnect-apiconnect-cc-backup-1552176000-lk9dl 0/1 Error 0 8h
default apiconnect-apiconnect-cc-backup-1552176000-zr4v7 0/1 Error 0 8h
default apiconnect-apiconnect-cc-bx7v2 1/1 Running 1 2d
I think the pod in Running status, is the one to be backed up?
Regards, John
I use the following make sure you update the namespace for your install
kubectl -n apic get pods --field-selector=status.phase==Failed -o jsonpath='{range .items[*]}{@.metadata.name} ' | xargs kubectl -n apic delete pods
HTH