Skip to main content
Solved

IFS cloud installation for 23R1 - ifs-ingress missing

  • December 19, 2023
  • 2 replies
  • 311 views

Forum|alt.badge.img+7

This is on IFS cloud installation for 23R1

main_config.json is as below.

                "Linuxhost":  "10.1.1.11",

                "Dns":  "8.8.8.8 10.1.2.4 10.1.2.5",
                "MaxVMRebootWaitSecs":  1200,
                "IFSCloudNamespace":  "xxxxxxxxxxxx",
                "FirewallPorts": "",
                "ManagementServerIP": "10.1.1.12",
                "PodCidrRange": "192.168.0.0/16",
                "LocalNetworkIpRange": "10.1.1.0/24",
                "LoadBalancerPrivateIP":  ""

After executing main.ps1, 5 pods for ifs-ingress are not available. That is when I issue, kubectl get pods -A, those are not available.

Unavailable pods,
linkerd-proxy-injector-
linkerd-destination-
linkerd-identity-
ingress-ingress-nginx-defaultbackend-
ingress-ingress-nginx-controller

There are no errors at ifsremote\ifsroot\logs\main-script\Install-IfsIngress\Install-IfsIngress.log
Also no errors if I issue command .\main.ps1 or .\main.ps1  -resource  'INGRESS'

Available pods are
NAMESPACE     NAME                                         READY   STATUS    RESTARTS      AGE
kube-system   dashboard-metrics-scraper-6f5d989bcd-cgwsb   1/1     Running   2 (34m ago)   45m
kube-system   hostpath-provisioner-657b6c745b-hzvdv        1/1     Running   2 (34m ago)   45m
ifs-storage   csi-smb-controller-685948f8ff-rjllc          3/3     Running   6 (34m ago)   45m
ifs-storage   csi-smb-node-g9mgb                           3/3     Running   6 (34m ago)   45m
kube-system   coredns-6cf745454c-dttml                     1/1     Running   2 (34m ago)   45m
kube-system   kubernetes-dashboard-5d6c79457c-rvt2s        1/1     Running   2 (34m ago)   45m
kube-system   calico-kube-controllers-794f7cc9f8-stcgw     1/1     Running   1 (34m ago)   37m
kube-system   calico-node-q9hk7                            1/1     Running   1 (34m ago)   37m
kube-system   metrics-server-5c874f7c87-kffhj              1/1     Running   2 (34m ago)   45m


/etc/sudoers file is as below,
ifs ALL=(ALL:ALL) ALL

Ubuntu firewall has disabled
sudo ufw disable

IFS remote versions as below,
ifs-remote-2.8.2.zip
ifs-remote-bins-2.4.0.zip

What is the cause for unavailability for ifs-ingress?

Thanks

Best answer by CovMayurJ

Hi Ben,

Thanks for the reply.

Now I have ifs-ingress after doing following,

  • "Dns":  "10.1.2.4 10.1.2.5",
  • helm version in main_config.json file and main_config.json.template was different.

                "HelmVersion":  "v3.10.3" and "HelmVersion":  "v3.11.3",

                So changed as the template file.

Best Regards,

Mayura

View original

2 replies

Forum|alt.badge.img+14
  • Superhero (Employee)
  • 156 replies
  • December 20, 2023

Hi Mayura,

A few things to check and try to determine where in the process it is failing:

  • Please share the output from running .\main.ps1  -resource  'INGRESS'.
  • Please check that the Username and Password entered are correct.
  • Does the ifs-ingress namespace exist? → kubectl get namespaces
  • Was ifs-ingress downloaded into ifsroot\infrastructure\ifs-ingress? (In Windows Management server.)
  • Check that the ifs-ingress deployments were created. → kubectl get deployments -n ifs-ingress

Not sure if it is relevant, but the DNS settings look odd to me.
I would remove 8.8.8.8 and let your DNS servers at 10.1.2.4 10.1.2.5 resolve non-local DNS.
It can be added as a forwarder to your DNS setup if necessary.
Ensure that you can resolve external resources from both the Windows Management and ifs-remote servers.

Best regards -- Ben


Forum|alt.badge.img+7
  • Author
  • Do Gooder (Partner)
  • 18 replies
  • Answer
  • December 20, 2023

Hi Ben,

Thanks for the reply.

Now I have ifs-ingress after doing following,

  • "Dns":  "10.1.2.4 10.1.2.5",
  • helm version in main_config.json file and main_config.json.template was different.

                "HelmVersion":  "v3.10.3" and "HelmVersion":  "v3.11.3",

                So changed as the template file.

Best Regards,

Mayura


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings