How Istio works in Dev Spaces

[Zachery2008]

Does Istio work with Dec Spaces now? Our company is using Istio for quite a long time, and we're about to implement Dev Spaces for development. But I got stuck on how to implement Isito. I didn't find any useful info online about this.

[amsoedal]

Hi @Zachery2008, thanks for bringing this issue to us! Unfortunately Dev Spaces currently does not integrate with Istio. However I will bring this issue to the team and we will continue to investigate. In the long term it's possible we may support this.

[irperez]

Please support Istio. We're looking to leverage it for its security aspects in the Health care space. So its vital to us. Keep in mind Istio is becoming the defacto standard for service meshes. So not supporting it would block a lot of customers from adopting Azure Dev Spaces feature altogether.

[mstrommennh]

Support for an ITSIO sidecar shouldn't be too hard to add. https://rancher.com/ has a fairly mature flow for adding ITSIO sidecars to running pods. I am more on the ops side but it seems like this workflow could lend itself to something like Dev Spaces.

I'd like to add that it is highly important for those of us in a highly regulated environments to be using the fewest amount of security products which accomplish our goal. Decreasing complexity is a cornerstone of properly deployed access controls. ITSIO is already in place in our environments and we are looking closely at azure adoption. Being able to incorporate our current production and staging ITSIO rules to our development space would significantly increase our adoption rate on the azure services side.

Love what you're doing with Dev Spaces to enable developers, keep it up.

[karoldeland]

Not so easy IMHO :
MicrosoftDocs/azure-docs#33166

[mstrommennh]

Not so easy IMHO :
MicrosoftDocs/azure-docs#33166

Really sheds some light on it. I still want the feature though.

[irperez]

I've been doing alot of homework on how to handle a dev cluster vs a QA or Prod cluster configuration and how to handle deployments. The one thing here that I think allows me to work around this limitation is the use of the K8s admission controller. So by not having Istio in dev is fine for us. But in the QA & Prod environments we're looking to utilize the admissions controller to add configuration that may not have been there in the dev environment to account for those environmental differences.

Microsoft, you should probably give some guidance on this aspect for those that need Istio.