.\main.ps1 -resource 'MONITORING' and IFS goes down

​@MCIPSTEV Could you please elaborate a bit more? we were able to connect normaly to IFS and Grafana & Kibana

When you say you’re unable to log in, do you mean that IFS isn’t loading at all, or that it loads but you get an incorrect username/password error?

Have you checked whether all your pods are running? Also, please make sure there are enough resources available so kubernetes could reserve ressources when starting the pods.

Also have you changed the IFSCloudNamespace et Linuxhost variables?

Linuxhost  "yourvmname.yourdomain.com" should be the same system_url as defined in the ifscloud-values.yaml. As they share the same certificate. And that is why monitoring need to be installed after IFS Cloud. 

Hello,

All my pods for ifs were running but the frontend did not reply anymore. Once monitoring removed IFS cloud worked again

I haven’t encountered this issue before.

I’d start by checking the IFS Client and IFS Client Services pod logs, as well as calling some REST API.

Also creating a case would be helpful 

good luck

It’s most probably the ingress controller that got messed up.
When monitoring is created a copy of ifs-ingress.crt secret is copied from ifscloud ns to the monitoring ns… maybe something went wrong there… 


This is roughly how my conf looks. 

kubectl exec -it svc/ingress-ingress-nginx-controller -- cat /etc/nginx/nginx.conf | grep -E 'server_name |location_path'

server_name _ ;
                        set $location_path  "";
                server_name ds1k8s.corpnet.ifsworld.com ;
                        set $location_path  "/elasticsearch(/|${literal_dollar})(.*)";
                        set $location_path  "/grafana/?(.*)";
                        set $location_path  "/favicon.ico";
                        set $location_path  "/kibana";
                        set $location_path  "/kibana";
                        set $location_path  "/";

kubectl get ingress -A
NAME                                                    HOSTS                       
ifs-stateless-ingress                           ds1k8s.corpnet.ifsworld.com   
ifs-sticky-ingress                                 ds1k8s.corpnet.ifsworld.com  
elasticsearch-master                          ds1k8s.corpnet.ifsworld.com   
kibana                                                    ds1k8s.corpnet.ifsworld.com   
kube-prometheus-stack-grafana      ds1k8s.corpnet.ifsworld.com 

kubectl get secrets -A | findstr ifs-ingress.crt
hhanseremote     ifs-ingress.crt
ifs-monitoring   ifs-ingress.crt