<?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 Stewart Platt</title>
    <link>/tags/istio/</link>
    <description>Recent content in istio on Stewart Platt</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-GB</language>
    <lastBuildDate>Sun, 02 May 2021 17:26:25 +0100</lastBuildDate><atom:link href="/tags/istio/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Hardening Kubernetes/Istio Deployments</title>
      <link>/blog/hardening-kubernetes-istio-deployments/</link>
      <pubDate>Sun, 02 May 2021 17:26:25 +0100</pubDate>
      
      <guid>/blog/hardening-kubernetes-istio-deployments/</guid>
      <description>Istio is often installed on a Kubernetes cluster to leverage canary deployments. However, not everyone who installs Istio employs canary routing straight away. Some people opt for its security features, it also hosts a variety of other resilience an testing features.
Some Downtime Deployments If you&amp;rsquo;re not utilising canary deploys, you may notice that zero-downtime deployments stop being zero-downtime once you&amp;rsquo;ve enabled Istio sidecars in your Pods.
This has been raised numerous times on GitHub (7136, 7665, 10112, 11298, 12183, and 12342).</description>
    </item>
    
  </channel>
</rss>
