Skip to main content

Hi All,

 

>Sun Dec 11 15:40:33 GST 2022] - SEVERE: Failed to create namespace
>Sun Dec 11 15:40:33 GST 2022] - SEVERE: Failed to install ifs-cloud. Collected logs from command:
INFO: Creating namespace
Unable to connect to the server: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "xxx.xxx.xxx.xxx")
SEVERE: Failed to create namespace

 

The above error occurred during a delivery installation; the delivery went well in TEST, but this occurred during MIG installation. 

Anyone knows how to fix this?

I have had this many times and usually because I’d forgotten to update the cert in the local user profile:

Get the kubeconfig file from the Kubernetes cluster in Middle Tier Server.

This command grabs the kube config file from the Kubernetes cluster and copies it over to the Windows VM. This file is used to access Kubernetes when used with command line tools such as kubectl and helm.

ps> .\main.ps1 -resource 'GETKUBECONFIG'

Copy the file ifsroot\config\kube\config to c:\users\.kube

ps> mkdir $HOME\.kube
ps> copy .\config\kube\config $HOME\.kube\

Dear @Darshana Herath 

Can you please mark the answer as best solution? Or can you make sure to reply?

 

Would be great to know that the comment from @PROAHAR helped you.

 

Kind regards,

Tobias

I have had this many times and usually because I’d forgotten to update the cert in the local user profile:

Get the kubeconfig file from the Kubernetes cluster in Middle Tier Server.

This command grabs the kube config file from the Kubernetes cluster and copies it over to the Windows VM. This file is used to access Kubernetes when used with command line tools such as kubectl and helm.

ps> .\main.ps1 -resource 'GETKUBECONFIG'

Copy the file ifsroot\config\kube\config to c:\users\.kube

ps> mkdir $HOME\.kube
ps> copy .\config\kube\config $HOME\.kube\

 

 

Hi, thank you very much for your answer.

The issue was that the middle tier had been upgraded to a higher version, and the authentication command was a little bit changed.

There were two solutions.

  1. Keep the updated version and change the SSH command in the file.
  2. Downgrade to the recommended version.

Thank you and best regards, Sorry for the late reply.

Would be helpful if you can provide the cahnged SSH command.

 

Reply


Terms & ConditionsCookie settings