<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Service Meshes :: Cloud Platform Journey</title>
    <link>/k8s_basics/servicemeshes/index.html</link>
    <description>Background So, we have started to encapsulate our software components into containers (cf. Applications ), and Kubernetes takes care to distribute and/or scale these containers over our cluster nodes ensuring they are running as defined (cf. Runtime ). Inter-process communication is handled via Services , and we have found means of persisting data (cf. Storage and Stateful Sets ), helpers for getting our applications deployed following best-practices and in an organized manner (cf. Helm and Operators ), and tools for routing external accesses into our cluster (cf. Ingress ).</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <atom:link href="/k8s_basics/servicemeshes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linkerd</title>
      <link>/k8s_basics/servicemeshes/linkerd/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/k8s_basics/servicemeshes/linkerd/index.html</guid>
      <description>Linkerd is fully open source, licensed under Apache v2 , and is a Cloud Native Computing Foundation incubating project. Linkerd is the very first Service Mesh project and the project that gave birth to the term service mesh itself, cf. The Service Mesh: What Every Software Engineer Needs to Know about the World’s Most Over-Hyped Technology , and it is developed in the open in the Linkerd GitHub organization .&#xA;Buoyant , the original creators of Linkerd, offer support, training, and enterprise products around the open-source Linkerd tool.</description>
    </item>
    <item>
      <title>Istio</title>
      <link>/k8s_basics/servicemeshes/istio/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/k8s_basics/servicemeshes/istio/index.html</guid>
      <description>Istio is an open platform-independent service mesh that provides traffic management, policy enforcement, and telemetry collection:&#xA;Open: Istio is being developed and maintained as open-source software using the Apache License 2.0 . The Istio project was started by teams from Google and IBM in partnership with the Envoy team from Lyft. It’s been developed fully in the open on GitHub . Platform-independent: Istio is not targeted at any specific deployment environment. Istio currently supports environments running container orchestration platforms such as Kubernetes and Nomad with Consul. Service mesh: Istio is designed to manage communications between microservices and applications. Without requiring changes to the underlying services, Istio provides automated baseline traffic resilience, service metrics collection, distributed tracing, traffic encryption, protocol upgrades, and advanced routing functionality for all service-to-service communication. Istio also supports Traffic Access Control, Circuit Breaking and Rate Limiting, and more Chaos Monkey-style Testing (Failure Injection) and Distributed Tracing, and mTLS for all protocols and not just all except TCP as we had seen for Linkerd .</description>
    </item>
  </channel>
</rss>