Skip to main content

I'm currently facing an error message while trying to install INGRESS: 'Error: Kubernetes cluster unreachable: Get "https://153.113.208.253:16443/version": context deadline exceeded'. I would greatly appreciate your assistance in resolving this issue

 

"ifscloud" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ifscloud" chart repository
Update Complete. ⎈Happy Helming!⎈
2024-04-29 04:46:03.41   RSEXIFS-91 IfsIngress downloaded successfully
2024-04-29 04:46:03.41   RSEXIFS-91 Stop Download-IfsIngress
2024-04-29 04:46:03.41   RSEXIFS-91 Start ImagePullSecret-IfsIngress
2024-04-29 04:46:03.41   RSEXIFS-91 Creating ImagePullSecret ifs-ingress namespace.......
"ifscloud" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ifscloud" chart repository
Update Complete. ⎈Happy Helming!⎈
Error: Kubernetes cluster unreachable: Get "https://153.113.208.253:16443/version":context deadline exceeded
2024-04-29 04:47:04.38   RSEXIFS-91 IFSIngress ImagePullSecret created successfully
2024-04-29 04:47:04.38   RSEXIFS-91 Stop ImagePullSecret-IfsIngress
2024-04-29 04:47:04.38   RSEXIFS-91 Start Install-IfsIngress
2024-04-29 04:47:04.38   RSEXIFS-91 Installing ifs-ingress.......
Your certificate has been saved in C:\IFS\UPG\WMS\ifsroot\utils\..\config\certs/ca.crt.
Your private key has been saved in C:\IFS\UPG\WMS\ifsroot\utils\..\config\certs/ca.key.
Your certificate has been saved in C:\IFS\UPG\WMS\ifsroot\utils\..\config\certs/issuer.crt.
Your private key has been saved in C:\IFS\UPG\WMS\ifsroot\utils\..\config\certs/issuer.key.
Error: Kubernetes cluster unreachable: Get "https://153.113.208.253:16443/version":context deadline exceeded
2024-04-29 04:48:04.63   RSEXIFS-91 ifs-ingress installed successfully
2024-04-29 04:48:04.64   RSEXIFS-91 Stop Install-IfsIngress

Ensure that your internet connection is stable and free from any proxy or firewall interruptions to access the ifs jforg repository.

 

Thank you for your response. The issue has been resolved by following the instructions provided in the technical document titled "Installing behind a Proxy." Additionally, as you highlighted, I disabled the Ubuntu firewall and also I have executed the command source /etc/environmentto apply the proxy change.

https://docs.ifs.com/techdocs/23r2/070_remote_deploy/010_installing_fresh_system/030_preparing_server/60_install_behind_proxy/

Thank you for you support.

Hi guys,

 

I am getting the same error and already check proxy (no proxy), firewall (deactivated).

Error: Kubernetes cluster unreachable: Get "https://11.0.1.205:16443/version": dial tcp 11.0.1.205: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.

Thanks,

 

Gianni Neves

During the installation of the IFS ingress in 25R1 release update the following error was encountered

Error: Kubernetes cluster unreachable: Get "https://xxx-xxx.nn35x032ja3upffgyg4pykxrbb.zx.internal.cloudapp.net:16443/version": dial tcp: lookup xxx-xxx-mw01.nn35x032ja3upffgyg4pykxrbb.zx.internal.cloudapp.net: no such host


The hostname xxx-xxx-mw01.nn35x032ja3upffgyg4pykxrbb.zx.internal.cloudapp.net could not be resolved to an IP address from the management server causing network communication failure with the Kubernetes API server.

 

Resolution Steps:

Run the following powershell command on the management server to test connectivity:

Test-NetConnection -ComputerName xxx-xxx-mw01.nn35x032ja3upffgyg4pykxrbb.zx.internal.cloudapp.net -Port 16443

If this test fails log in to the MW server run

nslookup XXX-XXX-mw01.nn35x032ja3upffgyg4pykxrbb.zx.internal.cloudapp.net

Note the IP address returned and add Host Entry on Management Server

Re-test connectivity using Test-NetConnection. If it resolves without issues from the management server the ingress command will run successfully.

Terms & ConditionsCookie settingsAccessibility statement