Solved

IFS Cloud middletier installation kubernetes connection error

  • 5 April 2022
  • 2 replies
  • 692 views

Userlevel 1
Badge +6

Hi,

 

we are trying to install IFS Cloud as a remote deployment option.

 

We have 2 servers Ubuntu 20.04 and Windows Server 2019. The Windows server has a oracle database installed with a dump from customer’s APPS8 environment, and all the artifacts downloaded from Lifecycle experience. 

 

When running the main.ps1 script, we are running into some connection errors for the Ubuntu server:

  1. If we leave the ManagementServerIP in main_config.json empty, the main.ps1 returns following errors during execution:
    •  Error: Kubernetes cluster unreachable: Get "https://<server_ip>:16443/version?timeout=32s": dial tcp <server_ip>:16443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
  2. If we give the Windows Server IP in the main_config.json, the main.ps1 execution finished without error, but afterwards all kubectl commands return the following error (and the IFS Cloud installer.cmd returns the same error):
    • > kubectl version
      Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.7", GitCommit:"132a687512d7fb058d0f5890f07d4121b3f0a2e2", GitTreeState:"clean", BuildDate:"2021-05-12T12:40:09Z", GoVersion:"go1.15.12", Compiler:"gc", Platform:"windows/amd64"}
      Unable to connect to the server: dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it.
icon

Best answer by hhanse 8 April 2022, 10:25

View original

2 replies

Userlevel 5
Badge +10

You probably haven’t done this part:
https://docs.ifs.com/techdocs/21r2/020_installation/010_installing_fresh_system/030_preparing_server/50_windows_managementserver/#get-the-kubeconfig-file-from-the-kubernetes-cluster-in-middle-tier-server

Userlevel 1
Badge +6

Yes the issue was a missing kubeconfig file for the logged in user! We were able to continue the installation after doing the get-kubeconfig step in the documentation

Reply