istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Taking Shriram's advice...

This commit is contained in:
oaktowner 2020-05-15 16:53:31 -04:00
parent e4fdb9bacc
commit b7637763f3
1 changed files with 16 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
content/en/news/releases/1.6.x/announcing-1.6/_index.md
View File

@ -59,19 +59,28 @@ ability to control your trace sampling rates, and updated Grafana dashboards
(and we're even publishing them on [Grafana](https://grafana.com) on the (and we're even publishing them on [Grafana](https://grafana.com) on the
[Istio org page](https://grafana.com/orgs/istio)). [Istio org page](https://grafana.com/orgs/istio)).
## Better VM support
For those of you who are adding non-Kubernetes workloads to meshes (for
example, workloads deployed on VMs), the new
[WorkloadEntry](/docs/reference/config/networking/workload-entry/) resource
makes that easier than ever. We created this API to give non-Kubernetes
workloads first-class representation in Istio. It elevates a VM or bare metal
workloads to the same level as a Kubernetes pod, instead of just an endpoint
with an IP address. You now even have the ability to define a Service that is
backed by both Pods and VMs. Why is that useful? Well, now you now have the
ability to have a heterogeneous mix of deployments (VMs and Pods) for the same
service, providing a great way for migrating VM workloads to the mesh.
Expanding support for VM-based workloads was another theme we called out
in our roadmap post, and you can expect to see more in this area over the
coming releases.
## Other improvements ## Other improvements
There are great traffic management features (like supporting the experimental There are great traffic management features (like supporting the experimental
Kubernetes Service APIs, better support for Ingress, and better header Kubernetes Service APIs, better support for Ingress, and better header
handling). handling).
For those of you who are adding non-Kubernetes workloads to meshes (for
example, workloads deployed on VMs), the new
[WorkloadEntry](/docs/reference/config/networking/workload-entry/) resource
makes that easier than ever. VM-based workloads was another theme we called out
in our roadmap post, and you can expect to see more in this area over the
coming releases.
## Join the Istio community ## Join the Istio community
As always, there is a lot happening in the As always, there is a lot happening in the