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

Use odo with OpenShift Service Mesh (aka Istio) #2623

Open
dudash opened this issue Feb 20, 2020 · 7 comments
Open

Use odo with OpenShift Service Mesh (aka Istio) #2623

dudash opened this issue Feb 20, 2020 · 7 comments
Labels
area/openshift Issues or PRs related to OpenShift kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.

Comments

@dudash
Copy link

dudash commented Feb 20, 2020

[kind/Feature]

Which functionality do you think we should add?

I think it'd be great to have the ability to use odo in conjunction with Istio/OpenShift Service Mesh. Service Mesh requires an annotation on the DeploymentConfigs created for each component. This is in order for the platform to inject a sidecar container with each pod. (spec/template/metadata/annotations of sidecar.istio.io/inject: "true").

See ref docs here:
https://docs.openshift.com/container-platform/4.3/service_mesh/service_mesh_day_two/prepare-to-deploy-applications-ossm.html#ossm-automatic-sidecar-injection_deploying-applications-ossm

Additionally, Services that get created should have port names that follow the naming listed here (for full support of routing and metrics):
https://istio.io/docs/ops/configuration/traffic-management/protocol-selection/
e.g.

  spec:
    ports:
    - port: 8080
      targetPort: 8080
      name: http

Why is this needed?

To allow odo to be used in conjunction with OpenShift Service Mesh

@dharmit dharmit added the kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation label Feb 21, 2020
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 9, 2020
@dudash
Copy link
Author

dudash commented Jun 11, 2020

Can we keep this open? I think it's still important.

@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 12, 2020
@dudash
Copy link
Author

dudash commented Jul 24, 2020

/lifecycle frozen

@openshift-ci-robot openshift-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jul 24, 2020
@kadel
Copy link
Member

kadel commented Jul 31, 2020

Can we keep this open? I think it's still important.

Yes, sorry about not following up on that.
This is definitely something that we want to get to.
Now we are finishing our transition to using Devfiles as a common format to describe the development environment. We will look into this right after we finish this transition

@sspeiche sspeiche added this to the backlog milestone Sep 22, 2020
@girishramnani girishramnani added kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks and removed kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation labels Nov 4, 2020
@girishramnani girishramnani removed this from the backlog milestone Nov 4, 2020
@faysou
Copy link

faysou commented Oct 3, 2021

Being able to use annotations with odo would also be useful for dapr.io which also uses a sidecar.

@kadel
Copy link
Member

kadel commented Nov 3, 2021

Devfile API was just updated to allow specifying annotations. (devfile/api#661) Before we can levarege this in odo we still need to wait for github.com/devfile/library to implement it.

@kadel kadel added the priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done. label Feb 6, 2023
@rm3l rm3l added area/openshift Issues or PRs related to OpenShift and removed area/component labels Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/openshift Issues or PRs related to OpenShift kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.
Projects
Status: No status
Development

No branches or pull requests

9 participants