The observability problem for modern DevOps is familiar: As enterprises move to microservices, containerization, multi-language RPC frameworks, and service meshes, there’s an increasing need for users to understand a highly complex, distributed architecture and the dependencies between applications. Apache SkyWalking, an application performance monitor (APM) and observability platform, is an open source project that addresses this need — with or without a service mesh.
To give you the latest on the Istio service mesh, Tetrate hosted a live Ask Me Anything about Istio webinar on Dec. 16, 2021, with Istio engineers Zack Butcher, Weston Carlson, and Vikas Choudhary; Zack Butcher is an Istio contributor and member of its steering committee. These were our top takeaways.
1.8 is the last version of Istio to be released in 2020, it keeps following the trade winds and listen to the users’ feedback, which has the following major updates:
One of Envoy’s many powers is traffic routing and load balancing. For any dynamic environment that’s subject to regular changes, it needs a dynamic configuration mechanism that is capable of enabling users to make those changes easily, and most importantly, with no downtime.
If you are looking for a more efficient solution to observe your service mesh instead of using a Mixer-based solution, this is exactly what you need.
Tetrate’s partnership with AWS, with today’s announcement of Amazon EKS Distro (EKS-D), provides their joint customers with unified application connectivity and security across workloads, on-premises and on AWS cloud. EKS-D was unveiled at re:Invent 2020 as a Kubernetes offering that can run on-premises, in data centers owned or operated by customers. There are several benefits to EKS-D that we believe will be useful for customers in accelerating, streamlining, and unifying the efforts needed to modernize their applications and cloud migration.
The latest Istio releases have been widely anticipated by users who want to extend the service mesh to their legacy workloads. Istio 1.7 laid some of the groundwork to make VMs first-class citizens in the mesh by making VMs look more like a pod in Istio. With its latest 1.8 release, Istio has resolved a key problem with DNS in the service mesh that has stood in the way of expanding the mesh to VMs and enabling seamless multicluster access and has continued to build on the groundwork laid in 1.7 to make VMs easier to enroll in the mesh.
With the popularity of service mesh at an all time high, it is important to think about how it might affect your current architecture. You might think you have to completely rework your environment, that it might not be “mesh ready.” But in fact you can integrate a service mesh into your current stack and make it work for your organization.
Istio is a popular service mesh to connect, secure, control, and observe services. When it was first introduced as open source in 2017, Kubernetes was winning the container orchestration battle and Istio answered the needs of organizations moving to microservices. Although Istio claims to support heterogeneous environments such as Nomad, Consul, Eureka, Cloud Foundry, Mesos, etc., in reality, it has always worked best with Kubernetes — on which its service discovery is based.
KubeCon North America will be held virtually this Nov. 17-20 along with the CNCF’s co-located ServiceMeshCon North America running Nov. 17 from 7 to 3 PST. Tetrate is excited to sponsor KubeCon this year & while we miss the chance to hang out IRL, we’re really looking forward to chatting with you at our booth, and our sponsor Slack channel!