Add ability to use internal network for keycloak.

[AndrienkoAleksandr]

What does this PR do?

Add ability to use internal network for keycloak. Pr applies ability to use internal Keycloak url to make requests on the che-server. For user dashboard we provides public hostname url like earlier, because user dashboard is frontend and can't user internal network. We don't expose internal keycloak url though api, because this information is useful only for che-server now.

What issues does this PR fix or reference?

#17644

Related pr's:

Depends on eclipse-che/che-operator#507

How to test this PR?

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

Signed-off-by: Oleksandr Andriienko oandriie@redhat.com

[che-bot]

❌ E2E Happy path tests failed ❗

See Details

• Jenkins job

• test report

• logs and configs

• Happy path tests DevFile

• image: maxura/che-server:18225

Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)

ℹ️ Use comment "[crw-ci-test]" to rerun happy path E2E test.

[che-bot]

❌ E2E Happy path tests failed ❗

See Details

• Jenkins job

• test report

• logs and configs

• Happy path tests DevFile

• image: maxura/che-server:18225

Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)

• Use comment "[crw-ci-test]" to rerun happy path E2E test.
• Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

[che-bot]

❌ E2E Happy path tests failed ❗

See Details

• Jenkins job

• test report

• logs and configs

• Happy path tests DevFile

• image: maxura/che-server:18225

Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)

• Use comment "[crw-ci-test]" to rerun happy path E2E test.
• Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

[artaleks9]

@AndrienkoAleksandr Could you verify, that your PR is up to master branch?

[artaleks9]

Ok, I see it helped.. the pr-checking goes. Thanks.

[che-bot]

❌ E2E Happy path tests failed ❗

See Details

• Jenkins job

• test report

• logs and configs

• Happy path tests DevFile

• image: maxura/che-server:18225

Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)

• Use comment "[crw-ci-test]" to rerun happy path E2E test.
• Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

[artaleks9]

But there is some other trouble:

13:35:32 [06:35:28] → Failed to download image, reason: ErrImagePull, message: rpc error: code = Unknown desc = Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit.
13:35:32 [06:35:28] PostgreSQL pod bootstrap [failed]

QE-team needs to investigate it. It will take some time.

[artaleks9]

It seems, it's related to #18292, and there is not much we can do other than..
Let's try to relaunch PR a bit later.

[artaleks9]

@dmytro-ndp provided a workaround for this -> #18323
@AndrienkoAleksandr, please update your branch by the last changes from master - this will automatically relaunch PR check

[che-bot]

❌ E2E Happy path tests failed ❗

See Details

• Jenkins job

• test report

• logs and configs

• Happy path tests DevFile

• image: maxura/che-server:18225

Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)

• Use comment "[crw-ci-test]" to rerun happy path E2E test.
• Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

[sparkoo]

@dmytro-ndp provided a workaround for this -> #18323

Is it only increasing the limit to 200/6hr or do the used account has actually some dockerhub subscription?

[artaleks9]

@AndrienkoAleksandr Could you verify/confirm that commit is in your branch?

[AndrienkoAleksandr]

@artaleks9: @AndrienkoAleksandr Could you verify/confirm that commit is in your branch?

Yes, I have this commit.

[artaleks9]

Thanks, in this case, probably the workaround didn't help ((
I'm relaunching your PR, let's try again..

[artaleks9]

[crw-ci-test]

[che-bot]

❌ E2E Happy path tests failed ❗

See Details

• Jenkins job

• test report

• logs and configs

• Happy path tests DevFile

• image: maxura/che-server:18225

Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)

• Use comment "[crw-ci-test]" to rerun happy path E2E test.
• Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

[artaleks9]

So, Happy-path was fail, but it's a known issue (#18034)
From my side there are no objections to merge.

[AndrienkoAleksandr]

@skabashnyuk Could you take a look this pr?