Istio Multicluster

Istio Multicluster

  • December 22, 2018
Table of Contents

Istio Multicluster

Istio Multicluster is a feature of Istio–the basis of Red Hat OpenShift Service Mesh–that allows for the extension of the service mesh across multiple Kubernetes or Red Hat OpenShift clusters. The primary goal of this feature is to enable control of services deployed across multiple clusters with a single control plane. The main requirement for Istio multicluster to work is that the pods in the mesh and the Istio control plane can talk to each other.

This implies that pods need to be able to open connections between clusters.

Source: openshift.com

Tags :
Share :
comments powered by Disqus

Related Posts

Introducing Shipper

Introducing Shipper

Booking.com is proud to announce the first public release of Shipper, an open source project that provides powerful, customizable rollouts to one or manyKubernetes clusters. Shipper uses Helm charts and native Kubernetes concepts to make it easy for anyone to set up blue/green or canary rollouts for their applications. The current release uses vanilla Kubernetes traffic shifting, so you don’t need a service mesh provider to get started.

Read More
eBay Moves Away From OpenStack, Embraces Kubernetes and Docker

eBay Moves Away From OpenStack, Embraces Kubernetes and Docker

As part of an initiative to completely revamp its data center infrastructure, eBay is “re-platforming, using Kubernetes and Docker and moving away from OpenStack,” according to a message to SDxCentral from Mazen Rawashdeh, VP of platform engineering at eBay. In May 2017 at the OpenStack Summit in Boston, an eBay executive said that 95 percent of all eBay traffic ran on its OpenStack cloud, which at the time managed 167,000virtual machines(VMs) and 4,000 applications. But since then, eBay has pivoted away from OpenStack as part of a major three-year infrastructure initiative.

Read More
Cape Technical Deep Dive

Cape Technical Deep Dive

In this post, we’ll take a deep dive into the design of the Cape framework. First, we’ll discuss Cape’s architecture. Then we’ll look at the core scheduling component of the system.

Read More