Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapts Che to new dashboard next image #18332

Merged
merged 2 commits into from
Nov 24, 2020
Merged

Adapts Che to new dashboard next image #18332

merged 2 commits into from
Nov 24, 2020

Conversation

sleshchenko
Copy link
Member

@sleshchenko sleshchenko commented Nov 11, 2020

What does this PR do?

This PR adapts Che to new dashboard next image which includes the existing dashboard, that's done in che-incubator/che-dashboard-next#71
So, Che Server as previously copies resources from Dashboard + Dashboard Next resources.
Helm chart now serves the dashboard next from a separate deployment.

Screenshot/screencast of this PR

What issues does this PR fix or reference?

It's a kind of prerequisites for #17647

How to test this PR?

For Che Server image testing, just run Che in any way and check that dashboard and dashboard next are available.

For helm chart, see more:

helm chart tested configurations

SingleUser Single host

export CHART_DIR=/home/sleshche/projects/che/deploy/kubernetes/helm/che
helm upgrade --install che \
  --force \
  --namespace che \
  --set global.cheDomain=$(minikube ip).nip.io \
  --set global.ingressDomain=$(minikube ip).nip.io \
  --set cheImage=sleshchenko/che-server:no-dashboards \
  --set global.serverStrategy=single-host \
  --set global.tls.useSelfSignedCerts=true \
  -f ${CHART_DIR}/values/tls.yaml \
  ${CHART_DIR}

Multiuser Single host gateway

export CHART_DIR=/home/sleshche/projects/che/deploy/kubernetes/helm/che
helm upgrade --install che \
  --force \
  --namespace che \
  --set global.cheDomain=$(minikube ip).nip.io \
  --set global.ingressDomain=$(minikube ip).nip.io \
  --set cheImage=sleshchenko/che-server:no-dashboards \
  --set global.tls.useSelfSignedCerts=true \
  --set global.serverStrategy=single-host \
  --set cheSinglehostGateway.deploy=true \
  --set global.singleHostExposure=gateway \
  -f ${CHART_DIR}/values/tls.yaml \
  -f ${CHART_DIR}/values/multi-user.yaml \
  ${CHART_DIR}

Multiuser Multihost

export CHART_DIR=/home/sleshche/projects/che/deploy/kubernetes/helm/che
helm upgrade --install che \
  --force \
  --namespace che \
  --set global.cheDomain=$(minikube ip).nip.io \
  --set global.ingressDomain=$(minikube ip).nip.io \
  --set cheImage=sleshchenko/che-server:no-dashboards \
  --set global.serverStrategy=multi-host \
  --set global.tls.useSelfSignedCerts=true \
  -f ${CHART_DIR}/values/tls.yaml \
  -f ${CHART_DIR}/values/multi-user.yaml \
  ${CHART_DIR}

PR Checklist

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

Reviewers

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

@sleshchenko sleshchenko self-assigned this Nov 11, 2020
@che-bot che-bot added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. kind/task Internal things, technical debt, and to-do tasks to be performed. labels Nov 11, 2020
Copy link
Contributor

@akurinnoy akurinnoy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@che-bot
Copy link
Contributor

che-bot commented Nov 11, 2020

❌ E2E Happy path tests failed ❗

See Details

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.

@sleshchenko
Copy link
Member Author

rebased against master to try to fix happy path test

@che-bot
Copy link
Contributor

che-bot commented Nov 11, 2020

❌ E2E Happy path tests failed ❗

See Details

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
Copy link
Contributor

che-bot commented Nov 12, 2020

❌ E2E Happy path tests failed ❗

See Details

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.

@sleshchenko
Copy link
Member Author

crw-ci-test

@che-bot
Copy link
Contributor

che-bot commented Nov 18, 2020

✅ E2E Happy path tests succeed 🎉

See Details

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.

@sleshchenko sleshchenko added this to the 7.23 milestone Nov 19, 2020
@sleshchenko sleshchenko changed the title Adapts Che to new dashboard next image WIP Adapts Che to new dashboard next image Nov 19, 2020
@sleshchenko
Copy link
Member Author

Is WIP to avoid merging in 7.22

@sleshchenko sleshchenko changed the title WIP Adapts Che to new dashboard next image Adapts Che to new dashboard next image Nov 20, 2020
@sleshchenko
Copy link
Member Author

Rebased against master to make sure everything works before merging

@che-bot
Copy link
Contributor

che-bot commented Nov 23, 2020

✅ E2E Happy path tests succeed 🎉

See Details

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.

@sleshchenko
Copy link
Member Author

Build fails with [�[1;31mERROR�[m] Tests run: 2, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 0.756 s <<< FAILURE! - in org.eclipse.che.plugin.typescript.dto.TypeScriptDTOGeneratorMojoITest
Probably I need to wait a bit to get syncs flashed after release

@che-bot
Copy link
Contributor

che-bot commented Nov 24, 2020

❌ E2E Happy path tests failed ❗

See Details

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.

@sleshchenko

This comment has been minimized.

@sleshchenko
Copy link
Member Author

[crw-ci-test]

@ScrewTSW
Copy link
Member

[ci-build]

@che-bot
Copy link
Contributor

che-bot commented Nov 24, 2020

❌ E2E Happy path tests failed ❗

See Details

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.

@ScrewTSW
Copy link
Member

[crw-ci-test --rebuild]

@che-bot
Copy link
Contributor

che-bot commented Nov 24, 2020

❌ E2E Happy path tests failed ❗

See Details

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.

@sleshchenko
Copy link
Member Author

[crw-ci-test --rebuild]

@ScrewTSW
Copy link
Member

ScrewTSW commented Nov 24, 2020

Interesting, it's still trying to look for spring-petclinic-2.3.0.BUILD-SNAPSHOT.jar instead of spring-petclinic-2.4.0.BUILD-SNAPSHOT.jar even though the changes were merged into upstream.

@sleshchenko could you try to rebase your PR based on the latest master of eclipse/che and force-push the branch?

@ScrewTSW
Copy link
Member

[ci-build]

@che-bot
Copy link
Contributor

che-bot commented Nov 24, 2020

✅ E2E Happy path tests succeed 🎉

See Details

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.

@sleshchenko sleshchenko merged commit c1353d3 into master Nov 24, 2020
@sleshchenko sleshchenko deleted the dashboard-next branch November 24, 2020 15:46
@che-bot che-bot removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants