<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>pipetail Blog</title>
    <link>https://blog.pipetail.io/</link>
    <description>Recent content on pipetail Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2026 pipetail. All rights reserved.</copyright>
    <lastBuildDate>Thu, 29 Oct 2020 07:00:00 +0100</lastBuildDate><atom:link href="https://blog.pipetail.io/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>10 most common mistakes using terraform</title>
      <link>https://blog.pipetail.io/posts/2020-10-29-most-common-mistakes-terraform/</link>
      <pubDate>Thu, 29 Oct 2020 07:00:00 +0100</pubDate>
      
      <guid>https://blog.pipetail.io/posts/2020-10-29-most-common-mistakes-terraform/</guid>
      <description>&lt;p&gt;We had the chance to see quite a bit of infrastructures in our years of experience with AWS, GCP and Azure and we see some mistakes being repeated. No shame in that, we’ve done most of these too!&lt;/p&gt;
&lt;p&gt;I’ll try to show the ones we see very often and talk a bit about how to fix them.&lt;/p&gt;
&lt;p&gt;BTW we did a blogpost about &lt;a href=&#34;https://blog.pipetail.io/posts/2020-05-04-most-common-mistakes-k8s/&#34;&gt;&amp;ldquo;10 most common mistakes using kubernetes&amp;rdquo;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Improve visibility in Helm workflows with Werf!</title>
      <link>https://blog.pipetail.io/posts/2020-10-20-werf/</link>
      <pubDate>Tue, 20 Oct 2020 08:00:00 +0100</pubDate>
      
      <guid>https://blog.pipetail.io/posts/2020-10-20-werf/</guid>
      <description>What&amp;rsquo;s the most annoying thing about Helm workflows? There&amp;rsquo;s literally no visibility during the deployment process. Do you have some migration (Helm) hook that&amp;rsquo;s failing? Helm will tell you that one of the hooks failed but all the kubectling is up to.
And that&amp;rsquo;s just fine, Helm is too complex even without some live tailing of the deployment process.
The current state This article did not come out from the blue.</description>
    </item>
    
    <item>
      <title>How would I proceed with Kubernetes deployments?</title>
      <link>https://blog.pipetail.io/posts/2020-07-17-helm-free-deployment/</link>
      <pubDate>Fri, 17 Jul 2020 10:00:00 +0100</pubDate>
      
      <guid>https://blog.pipetail.io/posts/2020-07-17-helm-free-deployment/</guid>
      <description>&lt;p&gt;Last time I&amp;rsquo;ve written a few words about the &lt;a href=&#34;https://blog.pipetail.io/posts/2020-07-13-helmfile-basics/&#34;&gt;orchestration of
Helm deployments&lt;/a&gt;. I&amp;rsquo;ve mentioned
there that I&amp;rsquo;m not so big fan of Helm in terms of deployment of
applications. That&amp;rsquo;s 100% true, but do I have any other alternatives?&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Helmfile basics: get your Helm flow organized</title>
      <link>https://blog.pipetail.io/posts/2020-07-13-helmfile-basics/</link>
      <pubDate>Mon, 13 Jul 2020 10:00:00 +0100</pubDate>
      
      <guid>https://blog.pipetail.io/posts/2020-07-13-helmfile-basics/</guid>
      <description>&lt;p&gt;There are no doubts that Helm is extremely popular tool,
perhaps the most popular tool in the whole Kubernetes ecosystem.
But are there any ways how to streamline deployments of complex applications?&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>10 most common mistakes using kubernetes</title>
      <link>https://blog.pipetail.io/posts/2020-05-04-most-common-mistakes-k8s/</link>
      <pubDate>Mon, 04 May 2020 07:00:00 +0100</pubDate>
      
      <guid>https://blog.pipetail.io/posts/2020-05-04-most-common-mistakes-k8s/</guid>
      <description>&lt;p&gt;We had the chance to see quite a bit of clusters in our years of experience with kubernetes (both managed and unmanaged - on GCP, AWS and Azure), and we see some mistakes being repeated. No shame in that, we’ve done most of these too!&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ll try to show the ones we see very often and talk a bit about how to fix them.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>More EKS tips to make your life easier</title>
      <link>https://blog.pipetail.io/posts/2020-04-13-more-eks-tips/</link>
      <pubDate>Mon, 13 Apr 2020 07:00:00 +0100</pubDate>
      
      <guid>https://blog.pipetail.io/posts/2020-04-13-more-eks-tips/</guid>
      <description>We&amp;rsquo;ve spent most of the last month on implementing EKS. Surprisingly, we&amp;rsquo;re always solving the same concerns no matter what project we&amp;rsquo;re working on. Here&amp;rsquo;s couple of tips for your EKS clusters!
Skip kube2iam, go directly with IAM Roles for Service Accounts Kube2iam is amazing tool. I really like it and it helped me with granular control access in couple of projects. However, there&amp;rsquo;s a better solution that is supported out of the box: IAM roles for services accounts.</description>
    </item>
    
    <item>
      <title>Getting started with PodSecurityPolicy on EKS</title>
      <link>https://blog.pipetail.io/posts/2020-03-15-psp-on-eks/</link>
      <pubDate>Sun, 15 Mar 2020 07:00:00 +0100</pubDate>
      
      <guid>https://blog.pipetail.io/posts/2020-03-15-psp-on-eks/</guid>
      <description>&lt;p&gt;As you might already know, security is not something that a specialized department should
be responsible for. Instead, we all should bear in mind that security matters and build
secure solutions from the very beginning. Today we&amp;rsquo;re gonna talk about some practices
in the world of containerized apps and Kubernetess. So let&amp;rsquo;s say we have some best practices
for the containerized workloads. But how to enforce that? We&amp;rsquo;ll tell you right away.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>GitLab Runner on EKS</title>
      <link>https://blog.pipetail.io/posts/2020-03-05-gitlab-runner-on-eks/</link>
      <pubDate>Thu, 05 Mar 2020 08:00:00 +0100</pubDate>
      
      <guid>https://blog.pipetail.io/posts/2020-03-05-gitlab-runner-on-eks/</guid>
      <description>&lt;p&gt;GitLab-CI/CD is a great and powerful product for CI/CD pipelines. Hosted gitlab.com solution offers shared runners and some usage minutes based on your paid plan (even if the free tier). Though you might want to run your own runner in your private or public cloud. I will show how to run GitLab runner on AWS using terraform, Elastic Kubernetes Service and GitLab kubernetes integration.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>AWS Systems Manager Session Manager: bye bye bastion hosts!</title>
      <link>https://blog.pipetail.io/posts/2020-02-24-amazon-ssm-session-manager/</link>
      <pubDate>Mon, 24 Feb 2020 07:00:00 +0100</pubDate>
      
      <guid>https://blog.pipetail.io/posts/2020-02-24-amazon-ssm-session-manager/</guid>
      <description>&lt;p&gt;There are customers where public internet access is no go. But
at the same time you need to access your EC2 instances,
right? How would you approach this? Usually, we use bastion hosts,
that&amp;rsquo;s basically a different name for jump host you can use
to access internal resources. In AWS, you don&amp;rsquo;t need to manage
such extra instances and take care of all the low-level configuration.
Instead, you can leverage fully managed Session Manager from the
AWS Systems Manager suite!&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Applications are not easy, tracing is: context propagation</title>
      <link>https://blog.pipetail.io/posts/2020-02-14-opentelemtry-context-propagation/</link>
      <pubDate>Mon, 17 Feb 2020 19:00:00 +0100</pubDate>
      
      <guid>https://blog.pipetail.io/posts/2020-02-14-opentelemtry-context-propagation/</guid>
      <description>&lt;p&gt;A few weeks ago I&amp;rsquo;ve published my &lt;a href=&#34;https://blog.pipetail.io/posts/2020-02-09-opentelemetry-introduction/&#34;&gt;introduction to the tracing with OpenTelemetry
instrumentation&lt;/a&gt;.
I was trying to explain there that tracing has some value even in standalone applications. It was just a recommendation, but today we&amp;rsquo;re gonna talk about scenarios where tracing
is a must: distributed systems.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>More complicated EKS scenarios: EKS managed worker nodes without internet access</title>
      <link>https://blog.pipetail.io/posts/2020-02-12-eks-private-cluster/</link>
      <pubDate>Wed, 12 Feb 2020 08:00:00 +0100</pubDate>
      
      <guid>https://blog.pipetail.io/posts/2020-02-12-eks-private-cluster/</guid>
      <description>&lt;p&gt;Are you using EKS managed worker
pools? If you don&amp;rsquo;t have any specific reasons for not using them, you should.
It saves tons of time plus it boosts the &amp;ldquo;managed Kubernetes&amp;rdquo; feeling.
However, this pretty new offering did not cover one specific use case:
cluster with no Internet access.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Applications are not easy, tracing is: a brief introduction to OpenTelemetry</title>
      <link>https://blog.pipetail.io/posts/2020-02-09-opentelemetry-introduction/</link>
      <pubDate>Sun, 09 Feb 2020 10:00:00 +0100</pubDate>
      
      <guid>https://blog.pipetail.io/posts/2020-02-09-opentelemetry-introduction/</guid>
      <description>&lt;p&gt;I have great news! &lt;a href=&#34;https://medium.com/opentelemetry/opentelemetry-monthly-update-january-2020-73579f9cb979&#34;&gt;OpenTelemetry will be in beta&lt;/a&gt; soon!
What does it mean? Well, we can start instrumenting applications
directly with OpenTelemetry and we can skip its ancestors.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>DAPR: introduction to Distributed Application Runtime</title>
      <link>https://blog.pipetail.io/posts/2020-01-29-dapr-introduction/</link>
      <pubDate>Wed, 29 Jan 2020 20:00:00 +0100</pubDate>
      
      <guid>https://blog.pipetail.io/posts/2020-01-29-dapr-introduction/</guid>
      <description>&lt;p&gt;At the moment, there are no doubts that transformation to the new
architectural pattern, microservices architecture, is happening.
Today, I don&amp;rsquo;t want to emphasize that microservices architecture does
not solve everything. This transformation is happening and my
role here is to show you some possible ways how to minimize the struggle.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
