title: VSTS Workflow for Microservices / Share Service Endpoints
body: <p>We're using VSTS to deploy to an Azure Container Service (AKS) which is running Kubernetes.  We are building out a collection of microservices to share between several applications and, for the time being, this Kubernetes instance will manage most or all of our service orchestration.</p>
  
  <p>My confusion is with VSTS and the fact that - as stated <a href="https://docs.microsoft.com/en-us/vsts/build-release/concepts/library/service-endpoints" rel="nofollow noreferrer">here</a>:</p>
  
  <blockquote>
    <p>Service endpoints are created at project scope. An endpoint created in one project is not visible in another team project.</p>
  </blockquote>
  
  <p>Right now each microservice is its own project in VSTS.  We have another project for changes/updates to the Kubernetes Ingress (NGINX) services.  Each of these projects feels well-defined in terms of no overlap, different CI/CD tasks, etc.</p>
  
  <p>But, this means that for every single project, we have to set up duplicate Service Endpoints for Kubernetes (not to mention our private GitHub repos).  Apparently that is the intent of VSTS, but is there some other feature / workflow I'm missing that avoids all this redundancy?</p>
  
  <p>I've looked into Deployment Pools / Groups but that's a different use case.  I've also tried creating Teams, sharing across projects, etc. but to no avail.</p>