Skip to content

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

Open
@dudash

Description

@dudash

[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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/openshiftIssues or PRs related to OpenShiftkind/epicAn issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/taskslifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/LowNice to have issue. It's not immediately on the project roadmap to get it done.

    Type

    No type

    Projects

    • Status

      No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions