v0.3.0

Notice

☢️ Since this release was created, we have accidentally pushed a branch with duplicate tags that mean that this release no longer points at the correct commit on the release-candidate branch. Do not rely on this tag or rely on the artifacts associated with this release! ☢️

Changes

• Platform Operator can confirm that cf-for-k8s's architecture no longer includes cf-route-sync and metacontroller details, details

• Platform Operator can successfully deploy a kind cluster using Istio 1.6.x in cf-for-k8s

• Platform Operator can verify that cf-for-k8s can leverage Istio 1.6.4 using this release of cf-k8s-networking

• Platform Operator can confirm that cf-k8s-networking/master has been renamed to develop

• When a platform operator upgrades cf-for-k8s using kapp, they can confirm that new versions of istio and envoy are included

• In efforts to reach our GA scale targets of supporting 2000 application instances and 1000 routes, we have validated that routecontroller in isolation supports this scale. We also intend to test our subsystems end-to-end in the future details, details