Hello IFS Cloud Guru’s
I have a IFS Cloud 22R1 installation where the servers restart due to power failure. When the server starts the pods crashes. I have to delete IFSCloud name space and then manually delete ifs-ingress name space. When i try to reinstall IFS-Ingress it gets struck on pod linkerd-identity-598bfdfdbb-wvwjn
The other 2 pods linkerd-destination-85bc4fc565-pc6k5 & linkerd-proxy-injector-658d844f56-6t6hc remain in PodInitializing.
I Ran curk command and got following output on MT server -
ifs@erp:~$ curl -Is https://ifscloud.jfrog.io | head -n 1
HTTP/1.1 200 OK
(23) Failed writing body
I run command kubectl describe nodes and get error
Warning InvalidDiskCapacity 3h50m kubernetes invalid capacity 0 on image filesystem
in few hours every thing starts working properly.
ifs@erp:/tmp$ curl -Is https://ifscloud.jfrog.io | head -n 1
HTTP/1.1 200 OK
ifs@erp:/tmp$
ifs-ingress name space all pods come up
kubectl describe nodes Also gives desired output.
This has happened with me many times as the power situation at client place is not stable.
Can you suggest what would have gone wrong and worked automatically after few hours
Regards
Pankaj
