Question

PROXY Settings IFS Cloud

  • 20 December 2021
  • 8 replies
  • 492 views

Userlevel 5
Badge +14

Dear Community!

For a customer I have following issue:

When installing IFS Cloud, I receive an issue with connecting to the artifactory

 

[Mon Dec 20 13:57:56 CET 2021] - SEVERE: Get "https://ifscloud.jfrog.io/artifactory/api/helm/helm/ifs-cloud-211.5.0.tgz": dial tcp 20.71.12.238:443: 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.

 

To enable this, I have to use the proxy of the customer.

This works via setting the powershell variable $env:HTTPS_PROXY="proxy…...”

 

This enables to connect to the artifactory, but results in the following error:

 

[Mon Dec 20 13:50:23 CET 2021] - SEVERE: Failed to create namespace
[Mon Dec 20 13:50:23 CET 2021] - SEVERE: Failed to install ifs-cloud. Collected logs from command:
DEBUG:    1+ if ($env:verbose) { Set-PSDebug -Trace 2; >>>> $DebugPreference = "Continue"}
DEBUG:     ! SET $DebugPreference = 'Continue'.
DEBUG:    2+  >>>> $arg=$args[0]
DEBUG:     ! SET $arg = 'dryrun'.
DEBUG:    4+ if ( >>>> "$env:namespace" -eq "") {
DEBUG:    9+ if ( >>>> "$arg" -eq "delete")  {
DEBUG:   17+  >>>> kubectl $env:kubeconfigFlag get namespace $env:namespace -o name *> $null
DEBUG:   18+ if ( >>>> !$?) {
DEBUG:   19+    >>>> write-host INFO: Creating namespace
INFO: Creating namespace
DEBUG:   20+    >>>> kubectl $env:kubeconfigFlag create namespace $env:namespace
Unable to connect to the server: Forbidden
DEBUG:   21+    >>>> kubectl $env:kubeconfigFlag label namespace $env:namespace app.kubernetes.io/managed-by=Helm
Unable to connect to the server: Forbidden
DEBUG:   22+    >>>> kubectl $env:kubeconfigFlag annotate namespace $env:namespace meta.helm.sh/release-name=ifs-cloud
Unable to connect to the server: Forbidden
DEBUG:   23+    >>>> kubectl $env:kubeconfigFlag annotate namespace $env:namespace
meta.helm.sh/release-namespace=$env:namespace
Unable to connect to the server: Forbidden
DEBUG:   24+   if ( >>>> !$?) {write-host SEVERE: Failed to create namespace;exit 1}
DEBUG:   24+   if (!$?) { >>>> write-host SEVERE: Failed to create namespace;exit 1}
SEVERE: Failed to create namespace
DEBUG:   24+   if (!$?) {write-host SEVERE: Failed to create namespace; >>>> exit 1}

[Mon Dec 20 13:50:23 CET 2021] - SEVERE: Validation failed.

 

 

Funny stuff, we have opened up the connection for the windows managed server and deactivated the proxy.

Installation was fine then.

 

So it is important to know what configuration we need to have regarding PROXY.

 

kind regards,

Tobias


This topic has been closed for comments

8 replies

Userlevel 5
Badge +14

I would really appreciate if someone with Experience would answer these questions :)

@Markus Sandin 

Do you have someone in mind who might be able to help here?

I guess this customer is not the first and will not be the last one regarding this topic.
Kind regards
Tobias

Badge +1

@Technical Toby we have identified this issue and currently we are investigating this. Will provide the necessary documentation as soon as we get this sorted . 

Userlevel 5
Badge +14

That sounds great @shaklk 

I am sure this will be very helpful in the future.

Kind regards and looking forward to the documentation
Tobias

Userlevel 5
Badge +14

@shaklk 

Any news here?

 

Would be great if I can get some kind of input.

 

Regards

Tobias

Badge +1

@Technical Toby  ,  when referring to micok8s docs for installing the proxy : https://microk8s.io/docs/install-proxy , we need to add few environment variables to /etc/environment .

HTTPS_PROXY=
HTTP_PROXY=
NO_PROXY=
https_proxy=
http_proxy=
no_proxy=

Can you please provide the configuration , you have done via powershell .

Badge +1

@Technical Toby  when investigating this issue , I have came across a question that this is kind of a feature request . because proxy settings configuration is not something we have investigated . So can you please raise a feature request upon this matter . @Markus Sandin  

Userlevel 5
Badge +14

Dear @shaklk 
I have done no specific proxy configuration via powershell. Only what is in the technical documentation.

Not sure if this is a feature request. And if yes, from your point of view, How should this be created???

Should I raise one or are you asking Markus to do that? Not sure regarding your writing style.

 

Userlevel 4
Badge +6

We tested IFS Cloud Remote Deployment Option behind a squid internet proxy (runs on port 3128).
Following are the microk8s configurations required in IFS Cloud remote deployment option to run behind a proxy.

1. Open a Powershell Window in Windows Management Server ifsroot folder, then run ./main.ps1 to install remote (microk8s)

2. Then as mentioned in the microk8s documentation https://microk8s.io/docs/install-proxy we applied the following configurations in the Ubuntu Linux Middle-Tier Server VM

  2.1. Test if proxy is working: curl -v -x http://proxyhostname:3128 http://google.com

  2.2. sudo vim /etc/environment and set below variables
HTTPS_PROXY=http://proxyhostname:3128
HTTP_PROXY=http://proxyhostname:3128
NO_PROXY=10.1.0.0/16,10.152.183.0/24,127.0.0.1
https_proxy=http://proxyhostname:3128
http_proxy=http://proxyhostname:3128
no_proxy=10.1.0.0/16,10.152.183.0/24,127.0.0.1

  2.3. Then restart microk8s
microk8s stop
microk8s start

  2.4. In a new SSH session test if the VM can reach the internet through the proxy: curl -v -x http://google.com

3. The pods should pull the images and start up.

4. Then continue to install IFSCloud by running the ifsinstaller.

Best Regards,
Damian Perera