Question

Errors during the installation of the IFSCloud environment

  • 29 April 2024
  • 3 replies
  • 71 views

Userlevel 1
Badge +4


I'm encountering an issue during the fresh installation of the IFSCloud environment. It arises after executing the following command:


.\main.ps1 -resource 'KUBERNETES'

Error      : Warning: flag --classic ignored for strictly confined snap core20
 
             Warning: flag --classic ignored for strictly confined snap core18
 
             Warning: flag --classic ignored for strictly confined snap core
 
             Infer repository core for addon dashboard

             Infer repository core for addon metrics-server

             Infer repository core for addon dns

             Infer repository core for addon metrics-server

             E0429 07:19:54.783884   23025 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request

             E0429 07:19:54.783884   23025 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request

             E0429 07:19:54.783884   23025 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request

             E0429 07:19:54.783884   23025 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request

             E0429 07:19:54.783884   23025 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request

             E0429 07:19:54.783884   23025 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request

             E0429 07:19:54.783884   23025 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request

             E0429 07:19:54.783884   23025 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request

             Infer repository core for addon storage

             Infer repository core for addon hostpath-storage

             E0429 07:19:54.783884   23025 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request

             E0429 07:19:54.783884   23025 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request

             E0429 07:19:54.783884   23025 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request


However, I have proceeded with the installation up to ifs-ingress, but I'm still encountering the same error. The pods are not starting despite repeated attempts. I would greatly appreciate any advice on resolving this issue. Thank you.


PS C:\IFS\UPG\WMS\ifsroot> kubectl get pods -n ifs-ingress


E0429 06:47:13.988143    1236 memcache.go:265] couldn't get current server API group list: Get "https://153.113.208.253:16443/api?timeout=32s":
Too many open files
E0429 06:47:14.077342    1236 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0429 06:47:14.124901    1236 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0429 06:47:14.133578    1236 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request


NAME                                                   READY   STATUS              RESTARTS   AGE
ingress-ingress-nginx-defaultbackend-fff65c6d5-6tth2   0/1     ContainerCreating   0          30m21s
linkerd-proxy-injector-69f9bdf67c-pm5td                0/2     Init:0/1            0          30m21s
linkerd-destination-64bc4c775b-phd4q                   0/4     Init:0/1            0          30m21s
linkerd-identity-5fd4b4ff46-pbz6d                      0/2     Init:0/1            0          30m21s
ingress-ingress-nginx-controller-4dvhj                 1/1     Running             0          30m21s


3 replies

Userlevel 3
Badge +6

how is the resource utilization of the VM? size of RAM and CPU?

Userlevel 3
Badge +6

Can you make the below change from the values.yaml file and run it again ?

Is this prod or test? If not work can you increase the CPU or MEM from VM ?

  scale: 10
  replicas: 1
  cpuRatio: 10 

Userlevel 1
Badge +4

We investigated and found that this issue occurred due to the failure of installing the v1beta1.metrics.k8s.io metric. This problem was resolved once we followed the Install Middle Tier Server documentation properly.

 https://docs.ifs.com/techdocs/23r1/070_remote_deploy/010_installing_fresh_system/030_preparing_server/40_middletier_server/

This component should be marked as 'True' if it's working properly, as shown below:


kubectl get apiservices | grep metrics

v1beta1.metrics.k8s.io kube-system/metrics-server True
 

Reply