<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Containers on BrainBit Latest Articles</title><link>https://brainbit.uk/tags/containers/</link><description>Recent content in Containers 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/containers/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><item><title>Docker Quotas and Mario Bros</title><link>https://brainbit.uk/posts/docker-quotas-and-mario-bros/</link><pubDate>Thu, 08 Feb 2018 19:33:48 +0000</pubDate><guid>https://brainbit.uk/posts/docker-quotas-and-mario-bros/</guid><description>Intro: I’ve been meaning to write about docker and CFS (completely fair scheduler) for a long time , but I’ve been busy with work etc.
I’m gonna use Docker to limit process’s cpu usage, and we gonna explore what kind of metrics do we have to maybe troubleshoot an under-provisioned application , we’re going to be playing with fceux and mario
CFS (Scheduler): CFS has been the default scheduler of the linux kernel for a while , this isn’t an attempt to explain it in depth , but there’s a lot of interesting data about this , especially something about the main developer coming from the medical area or something like that.</description></item><item><title>Containers but not Docker</title><link>https://brainbit.uk/posts/containers-but-not-docker/</link><pubDate>Mon, 21 Nov 2016 20:47:08 +0000</pubDate><guid>https://brainbit.uk/posts/containers-but-not-docker/</guid><description>I’m not docker’s biggest fan , but i do see its benefits , although i think somehow it has managed to sort of hide what docker really is and what it really does, but this post isn’t about docker , but about namespaces.
Docker/lxc use a kernel feature that , in simplest terms , allows a process to have isolation a multiple levels (pids / fs / hostnames / etc)</description></item><item><title>Hardening Tools #1</title><link>https://brainbit.uk/posts/hardening-tools-sharp/</link><pubDate>Mon, 14 Nov 2016 19:03:06 +0000</pubDate><guid>https://brainbit.uk/posts/hardening-tools-sharp/</guid><description>I’d like to write short articles about cool hardening/sec tools , this is one i found the other day:
There’s a bunch of security tools around to do hardening , but one i liked very much recently is: Lynis.
Lynis is a collection of scripts in bash (?) that parse/run different things and give you a score, for example
(running ./lynis — profile default.prf ,
(default.prf is obvious your default profile where you can disable/enable things etc)</description></item></channel></rss>