Skip to content
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.

Provide Windows container support #2082

Closed
phillipgibson opened this issue Nov 17, 2020 · 12 comments
Closed

Provide Windows container support #2082

phillipgibson opened this issue Nov 17, 2020 · 12 comments
Labels
kind/research-required Requires further research to make progress priority/P2 P2 priority size/XXL 40 days (2 months) stale

Comments

@phillipgibson
Copy link
Contributor

phillipgibson commented Nov 17, 2020

Provide the ability to service Windows containers / payloads in the mesh.

Use Cases

For applications using Windows containers to participate in the service mesh


Note: This is not about OSM Controller running on Windows. OSM Controller will continue to run on Linux containers.

@phillipgibson phillipgibson added kind/research-required Requires further research to make progress improvement / feature request labels Nov 17, 2020
@adrien-barret
Copy link

any update on this ?

@draychev draychev added this to the v0.9.0 milestone Apr 1, 2021
@draychev draychev modified the milestones: v0.9.0, v0.10.0 May 5, 2021
@draychev
Copy link
Contributor

@davinci26 I hope you are interested in this!

@davinci26
Copy link

I am super excited to be working on this feature! I am looking into this thread of work into more detail.

For now I will focus on:

  1. Making the project more portable, taking into consideration Envoy's limitation on Windows
  2. Figure out the design and how the feature will be tested on CI/Locally
  3. A PoC using private Windows binaries.

I would encourage anyone who is interested in the feature to subscribe here and I will keep the issue updated as I make more progress.

@davinci26
Copy link

Adding reference to child issues:

  1. Make demo run on Windows #3886
  2. Testing cluster with Windows workers #3883
  3. On Windows Envoy clusters should not use address 0.0.0.0 #3882
  4. Windows based demo containers #3880

@github-actions
Copy link

Added default label size/needed. Please consider re-labeling this issue appropriately.

@steeling steeling added size/XXL 40 days (2 months) priority/P2 P2 priority and removed size/needed labels Jul 15, 2022
@trstringer trstringer modified the milestones: vFuture, v1.3 Jul 19, 2022
@keithmattix keithmattix modified the milestones: v1.3, vFuture Sep 7, 2022
@zaminda
Copy link

zaminda commented Sep 18, 2022

What's the status of this now?

@trstringer trstringer removed this from the vFuture milestone Nov 14, 2022
@github-actions
Copy link

github-actions bot commented Feb 1, 2023

This issue will be closed due to a long period of inactivity. If you would like this issue to remain open then please comment or update.

@github-actions github-actions bot added the stale label Feb 1, 2023
@dasMulli
Copy link
Contributor

dasMulli commented Feb 1, 2023

Still interested in this (comment to prevent staleness)

@github-actions github-actions bot removed the stale label Feb 2, 2023
@github-actions
Copy link

github-actions bot commented Apr 4, 2023

This issue will be closed due to a long period of inactivity. If you would like this issue to remain open then please comment or update.

@github-actions github-actions bot added the stale label Apr 4, 2023
@zaminda
Copy link

zaminda commented Apr 4, 2023

Still interested!

@github-actions github-actions bot removed the stale label Apr 5, 2023
@github-actions
Copy link

github-actions bot commented Jun 4, 2023

This issue will be closed due to a long period of inactivity. If you would like this issue to remain open then please comment or update.

@github-actions github-actions bot added the stale label Jun 4, 2023
@github-actions
Copy link

Issue closed due to inactivity.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/research-required Requires further research to make progress priority/P2 P2 priority size/XXL 40 days (2 months) stale
Projects
Status: Done
Development

No branches or pull requests

10 participants