microsoft / mindaro

Bridge to Kubernetes - for Visual Studio and Visual Studio Code
MIT License
307 stars 106 forks source link

Managed Identity doesn't work #225

Open Ian1971 opened 3 years ago

Ian1971 commented 3 years ago

Describe the bug Following the guidance in the docs https://docs.microsoft.com/en-us/visualstudio/bridge/managed-identity?view=vs-2019 https://docs.microsoft.com/en-us/visualstudio/bridge/overview-bridge-to-kubernetes I am trying to use managed identity but it does not work.

To Reproduce Note that the docs refer to both KubernetesLocalProcessConfig.yaml and KubernetesLocalConfig.yaml. I am not sure if this is a typo or if they are two different files. I have tried adding the described yaml to both.

enableFeatures:
    ManagedIdentity

In KubernetesLocalProcessConfig.yaml this causes a serialization error. In KubernetesLocalConfig.yaml it doesn't seem to do anything.

**Expected behavior** I can launch my application locally using my visual studio identity to connect to the cluster in azure. I guess the first thing is to confirm the correct filename and the correct yaml structure. **Logs** [bridge-mindarocli-2021-09-07-08-29-36-52048.txt](https://github.com/microsoft/mindaro/files/7120115/bridge-mindarocli-2021-09-07-08-29-36-52048.txt) [2021-09-07T08-29-33.3973681.log](https://github.com/microsoft/mindaro/files/7120123/2021-09-07T08-29-33.3973681.log) **Environment Details** Client used Visual Studio: Client's version: 2019 16.10.3 Operating System: Win 10 **Additional context** Add any other outputs from the clients or context you would like to share.
Ian1971 commented 3 years ago

I worked it out by decompiling the extension. It is a documentation issue. The correct file name is indeed KubernetesLocalProcessConfig.yaml

and the below yaml will work (note the - was missing in the docs)

version: 0.1
enableFeatures:
  - ManagedIdentity
amsoedal commented 3 years ago

Thanks for reporting this @Ian1971! I've logged a bug on our side to fix this.

ghogen commented 3 years ago

@Ian1971 Thanks - this is fixed internally and should be reflected on the live site later today.