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

How to develop Multi-Pod workspace #16850

Closed
haiye1018 opened this issue May 5, 2020 · 4 comments
Closed

How to develop Multi-Pod workspace #16850

haiye1018 opened this issue May 5, 2020 · 4 comments
Labels
kind/question Questions that haven't been identified as being feature requests or bugs. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@haiye1018
Copy link

haiye1018 commented May 5, 2020

I want to develop microservice app using Eclipse che deployed in k8s, as you know, all containers defined in one devfile are deployed in one k8s pod, this will get some difficult. In the che document, I guess one workspace pod is one k8s pod, but i find the post,

this is my devfile, these container will be in one k8s pod,

apiVersion: 1.0.0
metadata:
  generateName: hdev-
components:
  - alias: hdev
    type: kubernetes
    reference: hdevc.yaml
    referenceContent: |
      apiVersion: v1
      kind: List
      items:
      -
        apiVersion: v1
        kind: Pod
        metadata:
          name: h1
        spec:
          restartPolicy: Never
          containers:
          - name: h1
            image: ...
            imagePullPolicy: IfNotPresent
            env:
            - name: app-11
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP
      -
        apiVersion: v1
        kind: Pod
        metadata:
          name: h2
        spec:
          restartPolicy: Never
          containers:
          - name: h2
            image: ...
            imagePullPolicy: IfNotPresent
            env:
            - name: app-12
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP
@haiye1018 haiye1018 added the kind/question Questions that haven't been identified as being feature requests or bugs. label May 5, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label May 5, 2020
@RomanNikitenko
Copy link
Member

@haiye1018
I can see that Che 6 was used for Yevhen's demo.

Che 7 architecture differs from Che 6 one and described here: https://www.eclipse.org/che/docs/che-7/che-workspaces-architecture/

Unfortunately according to the doc I see no way to configure Multi-Pod workspace, but maybe someone can correct me if I'm wrong.

@RomanNikitenko RomanNikitenko added area/devfile and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels May 5, 2020
@sleshchenko
Copy link
Member

@haiye1018 Currently Che does not support running multiple pods for one workspace, the main reason of such limitation - RWO PVC access mode. We have an issue for support RWM with multiple pods but not much progress on that #11476. Probably this will speed up when #15384 will be solved.

BTW Could you elaborate more why merging all containers into a single pod does not work for you? Probably I'm able to suggest how to work around issues you faced with single pod in the end when you configure multiple in devfile.

@haiye1018
Copy link
Author

Thanks for your help.
@sleshchenko Multi pods have many Application scenario, especially in micro service application. My example is we want to develop an appliction based on one cluster including Zookeeper/Hadoop/SpringCloud using Che. Prior to Che, we code/debug in local machine, and the cluster is set up automatically using mutli virtual machines, so if the cluster runs in one Che Workspace Pod, the ports conflict at least. Forthermore, for the consistency between production enviroment and developing enviroment, changing the cluter's deploy policy is not the best solution, so if Che can support multi pods workspace, we can many pod like many virtual machines.

@che-bot
Copy link
Contributor

che-bot commented Jan 4, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2021
@che-bot che-bot closed this as completed Jan 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Questions that haven't been identified as being feature requests or bugs. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants