Is possible to use another cloud provider? about mindaro HOT 17 CLOSED

@k3NGuru the Visual Studio Bridge to Kubernetes extension was just updated on the marketplace with support for connecting to clusters from your local kube config

from mindaro.

https://github.com/microsoft/mindaro/projects/1#card-40812958
Looks like other cloud providers are being added right now?

from mindaro.

@iSeiryu Other cloud providers (AWS' EKS, Google Cloud's GKE, etc.) or even local Kubernetes (minikube) are already available in Bridge to Kubernetes.
However we support non-AKS clusters as preview for now, so please let us know in case you encounter any errors so that we can fix them.

The scenario mentioned by @thalesfsp was in regards to the PR Flow, which is a specific use of Bridge to Kubernetes.

Also, thank you for linking to the project's backlog page: the Wider support of Kubernetes was in the wrong column. Fixed it, thanks!

from mindaro.

@iSeiryu It is already available if you're using VS Code, and will be in a couple of weeks if you're using Visual Studio. However, I realize that I didn't mention in VS Code previously. Sorry that it was ambiguous.

from mindaro.

@pragyamehta sent email from LebedevDO

from mindaro.

Hi @thalesfsp

Thank you for your question. The PR Flow can be used on any Kubernetes, not just AKS.

Our examples are for Azure, but you can author a GitHub workflow or DevOps pipeline that does:

• Builds an image that includes the PR code changes
• Pushes that image to a image repository
• Deploys that image as a new release in your application namespace
• Applies the appropriate Bridge routing labels and annotations

The only implementation specific to Bridge is applying the routing labels:

- name: Add routing labels
      run: |
        kubectl label pods --selector="app=bikes,release=${{steps.generate-release-name.outputs.result}}" routing.visualstudio.io/route-from=bikes -n ${{ secrets.MASTER_SPACE }} --overwrite=true
        kubectl annotate pods --selector="app=bikes,release=${{steps.generate-release-name.outputs.result}}" routing.visualstudio.io/route-on-header=kubernetes-route-as=${{steps.generate-valid-branch-name.outputs.result}} -n ${{ secrets.MASTER_SPACE }} --overwrite=true

Even though the below workflow is specific to Azure/AKS, you can use it as a guide to rewrite the equivalent for other Cloud/Kubernetes providers:
GitHub Actions PR Flow Sample

Please let me know if you have any questions.
Thank you

from mindaro.

Does Visual Studio 2019 support another cloud\on-premises, not AKS?
Visual Studio Code support another provider, but in Visual Studio 2019 i see only AKS

from mindaro.

@k3NGuru It's not yet available, but it will soon be! The development is making good progress and I expect it should be available in the coming weeks.
+@danegsta for FYI.

from mindaro.

@daniv-msft wait, in your response to me you said they "are already available in Bridge to Kubernetes.".
But in your response to @k3NGuru you are saying "it's not available yet".
Which one is correct?

from mindaro.

@daniv-msft please keep us informed how are thing are going on!
May be there's some beta release of VS extension to install/test on vanila on-premises k8s?

from mindaro.

@SVronskiy Absolutely! I don't believe there is an existing beta program for the VS extension, but @danegsta please let me know if I missed it.
In any case, we expect to release this change around mid-December, so it will come quickly.

from mindaro.

@k3NGuru the Visual Studio Bridge to Kubernetes extension was just updated on the marketplace with support for connecting to clusters from your local kube config

Yes, we have already updated and are trying to work.
So far problems with setting up isolation routing

from mindaro.

Hi @k3NGuru sorry you're running into issues with the isolation. Are you seeing "Failed to get routing manager status" or other issues? If you grab the logs from your machine (%TEMP%/Bridge to Kubernetes) & from the routing manager pod, I can take a look and see if we can get you unblocked!

from mindaro.

Hi @amsoedal
We have k8s (1.18) on-promises. Our project based on .net core. When i trying apply Bridge to kubernetes to our dev namespace, doesn't apply URL (i waiting 10+ minutes).
Namespace - epp-dev

Bridge To Kubernetes.zip

from mindaro.

@k3NGuru thanks for these details! We will investigate and get back to you on this thread.

from mindaro.

Hi @k3NGuru would it be possible for you to send over your ingress yaml to us? I am trying to understand how you have setup your ingress. Please send it over to [email protected] with a link to the issue and we will try to get you unblocked asap. Thanks!

from mindaro.

Issue was resolved with the customer over an email. Closing the thread, but feel free to comment if still experiencing this behavior.

from mindaro.