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

support Multi-service with dependencies in separate pod #1125

Closed
yangcao77 opened this issue May 19, 2023 · 3 comments
Closed

support Multi-service with dependencies in separate pod #1125

yangcao77 opened this issue May 19, 2023 · 3 comments
Labels
area/library Common devfile library for interacting with devfiles lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. lifecycle/stale Stale items. These items have not been updated for 90 days. student Identified work that the students can work on

Comments

@yangcao77
Copy link
Contributor

Which area this feature is related to?

/area library

Which functionality do you think we should add?

Why is this needed? Is your feature request related to a problem?

Detailed description:

The services need to be deployed in expected order, i.e. will be defined by depend_on in the docker-compose file

Targets:
The containers will be built and deployed in order. MUST guarantee dependency services have been started before starting a dependent service
The services will be linked.

Implementation:

Can use service binding to connect services, see https://docs.openshift.com/container-platform/4.9/applications/connecting_applications_to_services/understanding-service-binding-operator.html

Ensure the commands for execution and deployment are in order.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

@openshift-ci openshift-ci bot added the area/library Common devfile library for interacting with devfiles label May 19, 2023
@yangcao77 yangcao77 added the student Identified work that the students can work on label May 19, 2023
@yangcao77 yangcao77 moved this to Backlog in Devfile Project May 19, 2023
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label Aug 18, 2023
@maysunfaisal
Copy link
Member

@yangcao77 do we want to track this on our board?

@github-actions github-actions bot removed the lifecycle/stale Stale items. These items have not been updated for 90 days. label Sep 19, 2023
@michael-valdron michael-valdron moved this from Backlog to Refinement in Devfile Project Nov 28, 2023
Copy link

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label Sep 19, 2024
@github-actions github-actions bot added the lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. label Nov 18, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 18, 2024
@github-project-automation github-project-automation bot moved this from Refinement to Done ✅ in Devfile Project Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/library Common devfile library for interacting with devfiles lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. lifecycle/stale Stale items. These items have not been updated for 90 days. student Identified work that the students can work on
Projects
Status: Done ✅
Development

No branches or pull requests

3 participants