search

cloudfoundry / cf-for-k8s

The open source deployment manifest for Cloud Foundry on Kubernetes
Apache License 2.0
300 stars 115 forks source link

Re: Replace VirtualService with Ingress for routing to system components #532

Closed mike1808 closed 4 years ago

mike1808 commented 4 years ago

I merged #525 to develop by mistake. Reopening this to merge to contour-ingress branch.

By removing the system component's dependency on Istio Virtual Services and using Ingress, will be able to support multiple Ingress solutions (e.g. Contour), with the Ingress API which is leveraged by both Istio and Contour.

#175234234

Acceptance Steps

When I have a cluster deployed with this PR And I get the ingresses with kubectl get -n cf-system ingress Then I see uaa, and capi Ingress resources called capi-external and uaa-external And when I get Virtual Services with kubectl get -n cf-system vs Then I only see log-cache Virtual Service* And I can push apps and see logs

Tag your pair, your PM, and/or team

@cloudfoundry/cf-for-k8s-networking

cf-gitbot commented 4 years ago

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/175296891

The labels on this github issue will be updated when the story is started.