feat: Deploy Eclipse Che on a virtual Kubernetes cluster

[maheshrajrp]

What does this pull request change?

Addition of Support for Che with vCluster

What issues does this pull request fix or reference?

eclipse-che/che#22845

Specify the version of the product this pull request applies to

7.82

Pull Request checklist

The author and the reviewers validate the content of this pull request with the following checklist, in addition to the automated tests.

• Any procedure:
  • Successfully tested.
• Any page or link rename:
  • The page contains a redirection for the previous URL.
  • Propagate the URL change in:
    • Dashboard default branding data
• Builds on Eclipse Che hosted by Red Hat.
• the Validate language on files added or modified step reports no vale warnings.

[github-actions]

⚡️ Deploying pull request preview...

[github-actions]

Click here to review and test in web IDE:

[maheshrajrp]

@tolusha @deerskindoll @ibuziuk reopened PR with the latest changes.

[tolusha]

@deerskindoll
Could you confirm that the article has to be split into smaller ones?
If so, I can help with that.

this is a question for @maheshrajrp.

[maheshrajrp]

@deerskindoll
Could you confirm that the article has to be split into smaller ones?
If so, I can help with that.

this is a question for @maheshrajrp.

hi @tolusha
im not sure if we could split this, the best we could do is move just the keycloak setup. the client id, secret creation are still needed. i fear it might do more harm than it's worth it ?

in any case, do you have thoughts or suggestions @tolusha @deerskindoll ?

[deerskindoll]

I'm worried about the readability and clarity of the process. It's really long and involves many components that go beyond the process of installation. I'd prefer to shift keyclok setup to a separate process and add it as a prerequisite to the installation itself. Let me check with another writer for a second opinion.

@maheshrajrp I need you to include the fix for the missing attribute issue, the build and verify PR workflow won't passs otherwise. There's also a potential issue with the usage of [source,shell] but I need to look into it more.

[maheshrajrp]

I'm worried about the readability and clarity of the process. It's really long and involves many components that go beyond the process of installation. I'd prefer to shift keyclok setup to a separate process and add it as a prerequisite to the installation itself. Let me check with another writer for a second opinion.

@maheshrajrp I need you to include the fix for the missing attribute issue, the build and verify PR workflow won't passs otherwise. There's also a potential issue with the usage of [source,shell] but I need to look into it more.

@deerskindoll can you give some hints on what you mean by attributes issues or point me to some documentation? it would really help.. first-time contributor here, sorry and thanks !!

[deerskindoll]

No worries. I left the suggestion in your original PR. {domain_name} and {keycloak_host} are causing an asciidoc issue because asciidoc treats them as attributes.

You need to add a backslash \ to avoid this error: \{domain_name} and {{keycloak_host}`

[deerskindoll]

There are two more issues with the code blocks:

• [source, shell] https://redhat-documentation.github.io/supplementary-style-guide/#code-example-syntax-highlighting
• removing the $ prefix https://redhat-documentation.github.io/supplementary-style-guide/#commands-with-root-privileges

Can you please fix these issues?

[maheshrajrp]

@deerskindoll . Thanks for the hints. I can understand. Will fix those issues. Give me a day or two (as right now I am in the middle of a career crisis), I'll pick it up and complete it asap.

[deerskindoll]

@deerskindoll . Thanks for the hints. I can understand. Will fix those issues. Give me a day or two (as right now I am in the middle of a career crisis), I'll pick it up and complete it asap.

Take you time, there's no pressure here.

[tolusha]

Hello @maheshrajrp
How are you?