<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Istio on BrainBit Latest Articles</title><link>https://brainbit.uk/tags/istio/</link><description>Recent content in Istio on BrainBit Latest Articles</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 25 Jul 2018 11:52:35 +0000</lastBuildDate><atom:link href="https://brainbit.uk/tags/istio/index.xml" rel="self" type="application/rss+xml"/><item><title>Tracing services with Istio</title><link>https://brainbit.uk/posts/tracing-services-with-istio/</link><pubDate>Wed, 25 Jul 2018 11:52:35 +0000</pubDate><guid>https://brainbit.uk/posts/tracing-services-with-istio/</guid><description>Super quick post , When istio injects the envoy container side car into your pod , each request that comes in and out is “appended” with a numbers of http headers that then they’re use for tracing .
This is one of the many benefits of the “side car injection” approach that istio has embrace , bit intrusive yea , but so far seems to work nicely.
Ok so quickly you can deploy jaeger and zipkin by enabling it on the chart:</description></item><item><title>Istio Mixer Adapters.</title><link>https://brainbit.uk/posts/istio-mixer-adapters/</link><pubDate>Tue, 24 Jul 2018 12:31:22 +0000</pubDate><guid>https://brainbit.uk/posts/istio-mixer-adapters/</guid><description>Quick article about Mixer and adapters , one of the things i wanted to find out is what’s the involvement of Istio/Mixer when traffic is sent from one pod to another , having that kind of segregation or isolation could be useful , for example let’s imagine a 3 tier app in 3 different pods , you wouldn’t want your view layer speaking directly with the model , for example:</description></item><item><title>K8 Istio little Deep Dive</title><link>https://brainbit.uk/posts/k-istio-little-deep-dive/</link><pubDate>Sat, 21 Jul 2018 19:51:13 +0000</pubDate><guid>https://brainbit.uk/posts/k-istio-little-deep-dive/</guid><description>I’ve been playing a little bit with Istio mostly egress , but today i wanted to write about ingresses .
Basically Istio ingresses are a number of proxies (envoy) that kind of talk to each other to deal with access , throttling and app routing in general.
What is really interesting about the istio approach is the sidecar injection, imagine that you’re running a container execs nginx (port80 )S
What istio does is “inject” a sidecar container , that runs on the same pod , that means , sharing the kernel network namespace with privileged mode and NET_ADMIN capabilities.</description></item></channel></rss>